What your browser remembers.

A cookie is a small piece of information that a website can store in your browser and send with later requests. Local storage also remembers information in your browser, but it is not sent with every request. This page explains what Indian Context uses each for and which choices are in your hands.

If you sign in, cookies help maintain your session and keep it secure. Local storage can remember your theme and your analytics choice. If you choose Save for later on an article, this browser stores only its story slug, not the article text or a personal identifier. Saving does not require an account or analytics acceptance. Clearing this site's browser data can sign you out and erase these settings and saved stories.

Reading history is off by default. It starts only if you switch it on at Saved stories; after that, the browser keeps a short list of story slugs you open. You can clear the list at any time. Switching reading history off deletes the list but leaves stories you explicitly saved alone. Accepting analytics cookies does not turn on reading history.

We ask before automatically measuring reading because improving the publication is our purpose, not a necessary condition for you to read. Unless you explicitly choose Accept analytics, we do not send automatic article-view events or load configured analytics scripts. If you accept, our own counter records a daily total by published article to help us improve stories and show popular ones. It does not store visitor IDs, IP addresses or reading history in the view table; deduplication lasts only while the browser tab is open. We do not use these counts to follow readers across websites or sell them. A configured third-party script is a separate data flow and may use its own storage and practices. Essential only keeps future automatic measurement off. Saving stories, local reading history and feedback you choose to send are separate choices.

With analytics acceptance, we also measure active article-reading time, whether the viewport reaches 25%, 50%, 75% and 100% of article text, and engaged reads (30 active seconds). Time pauses in hidden or unfocused tabs and after 60 seconds without interaction; each article is capped at 30 minutes per tab. These signals and new newsletter sign-ups can be grouped by campaign labels (UTM source, medium, campaign, term and content). We retain the first landing labels seen after acceptance only in page memory during navigation; reloads start fresh and declining analytics clears attribution and unsent measurements. We store daily aggregate totals, separate from subscriber email addresses, without visitor IDs, full landing URLs or referrers. Short-lived network-address rate-limit counters protect measurement endpoints from abuse; they are separate from the engagement tables. Use campaign labels, never personal details, in UTM links. Earlier analytics acceptance requires a fresh choice for this measurement.

No third-party analytics script is currently configured. Accepting analytics currently enables only Indian Context's own article-view counts.

Some pages may display material from another service, such as Google Trends. Loading or interacting with an embed can connect your browser to that provider, which may use its own storage under its own policy. Following a link to another website takes you outside Indian Context; its cookie and privacy practices may be different from ours.

Change your analytics choice using the controls above, even if you previously accepted or chose Essential only. If a provider script was already running, switching to Essential only reloads the page to stop further activity; it cannot undo data already received by a provider. Manage reading history and remove saved stories separately at Saved stories. Browser controls can also clear cookies or local storage, though doing so may affect sign-in and preferences. For the wider picture of how information is used, read the Privacy Policy.