Short answer
What is stored in your browser
| Mechanism | Used for | Persists across visits? |
|---|---|---|
| In-memory page state (JavaScript variables) | Holding the currently fetched village's records so you can search, sort, filter, and export them | No — cleared on reload or tab close |
| Browser cache (standard HTTP caching) |
Reusing styles.css, app.js, and
icon assets so the page loads faster on repeat visits
|
Yes, for static assets only — not personal or record data |
We do not use document.cookie,
localStorage, sessionStorage, or
IndexedDB to remember you, your searches, or your
location selections between visits.
What we don't use
- No first-party or third-party advertising cookies
- No analytics platform (no Google Analytics, no Plausible, no PostHog, no Mixpanel, and so on)
- No session-replay or heatmap scripts
- No cross-site tracking pixels
- No fingerprinting scripts
Third-party requests
Your browser does make a small number of third-party requests, all functional rather than tracking-related:
-
Google Fonts (
fonts.googleapis.com,fonts.gstatic.com) — loads the DM Sans and Fraunces typefaces used across the site. - Our own API origin — the frontend calls the BhuBharati Explorer backend to fetch districts, mandals, villages, and land records. This is first-party to the product, not a third-party tracker.
Consent controls
Because nothing non-essential is stored or tracked today, there is no cookie-consent banner or preference center on the site. If that changes, this page and the site will add one before any non-essential storage or tracking is activated — not after.
If that ever changes
Should we ever add analytics, error-tracking (e.g. an exception monitor), or preference storage, we will: list it here by name and purpose, keep it to the minimum needed to run or debug the service, and avoid third-party advertising or cross-site tracking categories entirely. The "Last updated" date above will move whenever this page's content changes.