Privacy

bharatlas runs without accounts and without tracking cookies, ad-tech, or behavioural profiling. The only thing we measure is cookieless, aggregate traffic (Cloudflare Web Analytics), with no personal data. This page is short because we collect little.

What we store

• Community submissions you publish: the file, the metadata you typed, and the time. On Cloudflare R2 (file) and D1 (metadata). Linked to a one-way SHA-256 hash of your IP for rate-limit purposes only.
• In your browser: localStorage holds the admin tokens for any submissions you made from this device, plus your basemap preference. No cookies, no fingerprinting. Nothing leaves your browser until you click Publish.
• Server logs: Cloudflare's edge logs HTTP requests for around 24 hours. We don't aggregate them, sell them, or look at them unless investigating abuse.

What we don't do

• No accounts. No email collection. No name collection.
• No behavioural, cross-site, or ad-tech analytics (no Google Analytics, no Hotjar, no Mixpanel, no fingerprinting libraries).
• No advertising. No data sharing. No data sale.
• No social-network embed pixels.

Third parties involved

• Cloudflare (Pages, R2, D1, Turnstile) hosts everything. Their privacy policy covers their edge logs.
• Turnstile (a CAPTCHA replacement, also Cloudflare) runs on the publish form to deter automated abuse. No personal data is sent to it.
• Cloudflare Web Analytics counts aggregate page views and load performance so we can see what gets used. It is cookieless, sets nothing on your device, collects no personal data, and cannot follow you across sites.
• The maps you browse stream from R2 with no usage tracking by us.

AI / LLM crawlers

We explicitly allow GPTBot, ClaudeBot, PerplexityBot, Google-Extended and other major LLM crawlers via robots.txt. The content is open under the licences shown on each card; we want it to be discoverable to anyone (human or model) who can use it.

Removal

• To remove a community submission you uploaded, use the Delete action on the /c/<id> page via the admin token you received at submit.
• If you've lost the token, email [email protected] from an address that proves ownership of the submission.
• For other privacy concerns, same address.

Changes

We'll keep this page short. Substantive changes get a note + date here.

Last updated: 2026-05-22.