Cookie & Local Storage Policy

cursus

Last Updated: August 31, 2026
Effective Date: August 31, 2026

---

This Cookie & Local Storage Policy explains how cursus uses cookies, local storage, and similar browser technologies on cursus.in, the public marketing website, and app.cursus.in, the main cursus application.

This Policy must be read together with our Privacy Policy and Terms & Conditions. The Privacy Policy contains the broader explanation of how cursus processes personal data.

1. Our Two Web Surfaces

cursus operates two distinct web surfaces with different technology and data-processing practices.

1.1 cursus.in — Public Marketing Website

cursus.in is the public marketing and landing website. No cursus account is required to browse it, and visitors may access it anonymously.

The marketing website uses a cookie-consent mechanism before optional or non-essential analytics cookies or similar technologies are activated. The banner provides the option to Accept All or Reject optional analytics cookies.

cursus uses EU-hosted PostHog Cloud only on cursus.in for ordinary website analytics and marketing-site measurement. PostHog is activated only after the applicable analytics consent is obtained.

PostHog is not used on app.cursus.in.

1.2 app.cursus.in — Main Application

app.cursus.in is the main cursus productivity and life-management application.

The application does not use PostHog, Google Analytics, third-party product analytics, advertising analytics, or advertising trackers for product-usage measurement.

The application does not use cookies or similar technologies for Targeted Advertising, cross-site advertising, or behavioural profiling.

The application does use strictly necessary technologies required for authentication, session management, security, and operation of requested services.

2. What Are Cookies and Similar Technologies?

Cookies are small files or values stored by a website on a user's device or browser. They may be used to maintain sessions, remember preferences, or support analytics and other functions.

Local storage (including HTML5 localStorage) allows a website or web application to store information locally in the browser. cursus uses local storage for client-side interface preferences where applicable.

Other browser technologies, including session storage or similar storage/access mechanisms, may also be used where necessary to provide requested functionality, security, or performance.

3. Cookies and Technologies We Use

3.1 Strictly Necessary Authentication and Security Technologies

Strictly necessary technologies are used on app.cursus.in where they are required to provide the application or a service explicitly requested by the user.

These include the technologies used for:

• authentication and session management;
• maintaining a logged-in session;
• security and abuse prevention;
• protecting account access; and
• other core application functionality that cannot operate without the relevant technology.

Authentication and session management for app.cursus.in use server-issued cookies. The current authentication system does not use JWT-based login tokens.

These technologies are not used by cursus for Targeted Advertising or cross-site behavioural tracking.

3.2 Local Storage for Interface Preferences

Where used, localStorage stores client-side interface preferences such as sidebar state, layout choices, or similar presentation settings.

These values are intended for user-interface functionality and are not used by cursus for advertising or cross-site tracking.

3.3 Analytics on cursus.in — PostHog

The public marketing website, cursus.in, uses an EU-hosted PostHog Cloud deployment for ordinary website analytics and marketing-site measurement.

PostHog is used only to understand activity occurring on cursus.in itself, including, where available:

• which marketing pages are viewed;
• where visitors came from or the referral/source that brought them to the website;
• which buttons or links are interacted with;
• which sections are viewed or skipped;
• how visitors navigate between pages or sections; and
• approximately how long visitors spend on pages or sections.

The implementation does not use:

• session replay;
• screen recording;
• session video recording;
• surveys;
• cross-site observation; or
• Targeted Advertising.

PostHog is not used to observe what a visitor does on unrelated websites.

3.4 Analytics Consent on cursus.in

PostHog analytics on cursus.in are optional/non-essential analytics technologies.

They are activated only after the visitor is presented with the site's cookie-consent mechanism and chooses the relevant consent option.

The current consent banner provides:

• Accept All — permits the optional analytics technologies covered by the banner; and
• Reject — rejects the optional analytics technologies covered by the banner.

A visitor may use the website without accepting the optional analytics technologies.

cursus does not maintain an individual account-level database record for every anonymous marketing-site visitor's cookie-consent choice.

Cookie consent on cursus.in is separate from account consent and separate from parental consent for an app.cursus.in account.

Accepting the marketing-site cookie banner does not establish that the visitor is an adult and does not constitute verifiable parental consent.

4. Cookies and Technologies We Do NOT Use for Analytics or Advertising

cursus does not use the following on app.cursus.in for product analytics or advertising:

• Google Analytics;
• PostHog;
• third-party product-analytics platforms;
• advertising pixels or advertising trackers;
• Targeted Advertising technologies; or
• cross-site behavioural tracking technologies.

cursus also does not use PostHog on app.cursus.in to record which features, buttons, pages, or other parts of the application a user interacts with.

5. Additional Website Technologies

5.1 Google Fonts

cursus.in may load fonts from Google-hosted servers.

Google Fonts is used to provide website presentation and typography. It is not used by cursus for analytics or advertising.

Because the browser requests font resources directly from Google's servers, Google may receive technical request information in connection with delivering those resources, subject to Google's own applicable terms and privacy practices.

5.2 Social Links

cursus.in may contain links to cursus's social-media accounts.

These are ordinary links and are not embedded social-media widgets or tracking pixels operated by the social-media platforms within the cursus webpage.

When a visitor follows one of these links, the external service may process information under its own policies.

5.3 Cloudflare Turnstile

Cloudflare Turnstile is used at the Cloudflare layer to protect app.cursus.in APIs against automated abuse and bots.

Turnstile is a security/anti-bot technology, not a cursus analytics or advertising technology. cursus does not use Turnstile for product-usage analytics, Targeted Advertising, or behavioural profiling.

Cloudflare may process technical signals required to provide Turnstile and bot-protection services under its own privacy terms.

6. Cookies and Children

6.1 cursus.in

The public marketing website can be accessed anonymously, and cursus generally cannot determine whether an anonymous visitor is a child or an adult.

The marketing website therefore does not claim to identify the age of every anonymous visitor.

Optional analytics technologies on cursus.in are controlled through the site's cookie-consent mechanism. Cookie consent is not represented as age verification or parental consent.

The separate Privacy Policy explains the distinction between the public marketing website and the account-based application and describes cursus's child-protection approach for app.cursus.in.

6.2 app.cursus.in

app.cursus.in has a minimum account-registration age of 13 years. Users aged 13 to 17 require the parental-consent process described in the Privacy Policy before the account is activated.

The application does not use PostHog, Google Analytics, or other product-usage analytics technologies, and it does not use Targeted Advertising or behavioural profiling.

7. Technologies We Do Not Use for Cross-Site Tracking

cursus does not use its analytics implementation to observe or record what a visitor does on unrelated websites.

In particular, the PostHog implementation on cursus.in is limited to activity occurring on cursus.in itself. It is not used to follow a visitor's activity across unrelated websites.

cursus does not use fingerprinting technologies such as canvas or browser fingerprinting for the purpose of identifying or tracking users across sites.

8. Your Cookie Controls

8.1 Marketing-Site Consent

On cursus.in, optional analytics technologies remain inactive until the applicable consent choice is made through the cookie-consent mechanism.

Choosing Reject prevents the optional analytics technologies covered by the banner from being activated.

Where the website provides a later consent-control mechanism, visitors may use that mechanism to change their preference. Visitors may also manage or clear cookies and local storage through their browser settings.

8.2 Browser Controls

Most modern browsers allow you to:

• view stored cookies and local storage;
• delete cookies or stored site data;
• block cookies;
• restrict third-party storage; and
• configure notifications or other browser privacy controls.

Disabling strictly necessary authentication/session cookies on app.cursus.in may prevent the application from functioning correctly or may prevent you from remaining logged in.

9. Legal Treatment of Cookies and Similar Technologies

Where applicable law requires consent for storing information on, or accessing information from, a user's device, cursus obtains the relevant consent before activating optional analytics technologies on cursus.in.

For example, under the UK's Privacy and Electronic Communications Regulations (PECR), non-essential analytics cookies generally require prior consent. The ICO's current guidance also applies these principles to other storage and access technologies, not only traditional cookies. citeturn271541search0turn271541search1

Where a technology is strictly necessary to provide a service requested by the user or to transmit a communication, applicable law may provide an exemption from consent requirements. cursus nevertheless seeks to describe its use of those technologies clearly.

The DPDP Act and DPDP Rules have a phased commencement schedule. The Privacy Policy explains how cursus distinguishes current obligations from future-facing DPDP requirements. citeturn826694search36turn826694search37

10. Changes to This Policy

We may update this Cookie & Local Storage Policy when our use of cookies, local storage, similar technologies, analytics providers, or applicable legal requirements materially changes.

Where a material change affects consent or another right, cursus will provide notice or obtain consent where required by applicable law.

The current version of this Policy will be posted with its revised Last Updated date.

11. Contact

For questions about this Cookie & Local Storage Policy, cookie consent, or related privacy matters:

---

© 2026 cursus. All rights reserved.