Privacy

Last updated: 2026-05-29

Summary

Public Services Guide is a static site. We do not set first-party cookies, we do not embed third-party trackers, and we do not ask for your name or email to read a guide. We use a cookieless Cloudflare Web Analytics beacon to measure page-load performance and basic traffic for all visitors — it sets no cookies, stores no long-term identifier, and cannot identify you as an individual. If you arrive from one of our social posts or a QR code, we also record the campaign tags on that link (which platform and which post), the page, and the time — with no cookie, no stored IP address, and no identifier that links it to you. The only other thing we store is an anonymous helpfulness vote if you tap "👍 / 👎 Was this helpful?" on a guide (see below). Aside from those, and standard Cloudflare access logs, nothing else is collected.

What Cloudflare logs

The site is hosted on Cloudflare Pages. Cloudflare records standard access logs for every request — typically IP address, user agent, request path, and timestamp. Cloudflare retains these logs per its published retention defaults. We use these logs only for operational purposes (diagnosing outages, identifying abuse) and do not cross-reference them with any other dataset.

See Cloudflare's privacy policy for their retention windows and how they handle the logs on our behalf.

Cookies

We set zero first-party cookies. You can verify this in your browser's developer tools (Application → Cookies) on any page of this site.

Cloudflare may set infrastructure cookies related to bot detection or load balancing. These are strictly necessary for the site to function and are covered by Cloudflare's privacy policy above.

Analytics

We use Cloudflare Web Analytics — a cookieless beacon that measures page-load performance, Core Web Vitals, page views, top pages, and referring sites, so we can verify the site works on slow connections (the audience often reads guides on low-end phones at government offices). The beacon:

  • sets no cookies;
  • stores no long-term identifier;
  • does not track you across days, sessions, or other sites;
  • cannot identify you as an individual.

It runs for all visitors, including the EU and EEA. Earlier we excluded EU/EEA traffic as a precaution; we now include it. The measurement stores no cookies and no long-term identifier and cannot identify you as an individual — the same cookieless approach used by privacy-first analytics tools.

You will not find Google Analytics, Plausible, Fathom, Umami, or any third-party advertising or marketing analytics on this site. The Cloudflare beacon is the only general analytics signal collected — and it is provided by our hosting provider, not a separate analytics company.

Campaign measurement

When you reach a guide from one of our social posts or a QR code, the link carries campaign tags — which platform (for example, Instagram), which post, and which on-card surface (caption, bio, or QR). A small function at our edge records only those tags, the page you landed on, and the time. It reads nothing else from the request: no IP address is stored, no cookie, no browser fingerprint, and no identifier of any kind — so this campaign record cannot be linked back to you. This is how we tell whether our posts actually help people find the guides.

Helpful-feedback votes

Each guide ends with a "Was this helpful?" widget. If you tap 👍 or 👎, we record an anonymous vote so we can find and fix the guides people struggle with. Each vote stores only:

  • the guide's name (e.g. india/aadhaar-update);
  • your vote (yes or no);
  • a timestamp.

We do not store your IP address, set any cookie, or attach any identifier — there is no way to link a vote back to you or to any other vote. Your choice is remembered in your own browser's local storage so the widget doesn't ask twice; that value never leaves your device beyond the anonymous vote itself. Voting is entirely optional, and guides work exactly the same whether or not you vote.

Third-party trackers

None. No pixel trackers, no advertising SDKs, no marketing automation. The only external scripts loaded are the cookieless Cloudflare Web Analytics beacon described above and those required for search (Pagefind, fetched from the same origin) and service-worker caching for offline use.

Email correspondence

The site lists several email aliases (general inquiries, privacy questions, security disclosures) routed through Cloudflare Email Routing to the maintainer team's mailbox. When you email any of these aliases, your address and the message contents become known to the maintainer team for the purpose of replying to you. We do not analyse this correspondence for marketing or aggregation; the message is read, acted on, and archived in the same way any one-to-one email is handled.

Data subject rights

If you are in a jurisdiction that grants data subject rights (including the EU/EEA, the UK, and many US states), you have the right to:

  • Access — ask what data we hold about you
  • Correction — ask us to correct inaccurate data
  • Deletion — ask us to delete data we hold about you
  • Portability — ask for a machine-readable copy of your data
  • Restriction — ask us to stop processing your data
  • Objection — object to specific processing

In practice, because the site holds no personal data beyond Cloudflare's access logs and any email correspondence you initiated with us, most requests are either a no-op or resolvable by emailing the privacy alias above with a brief description of what to remove.

Contact

Email [email protected] for any privacy question or data subject rights request. We aim to respond within 30 days. For urgent issues (suspected data breach affecting you), mark the subject line "URGENT" and we will prioritise it.

Changes to this statement

If the site's data posture changes — for example, if we add a different analytics tool, set first-party cookies, begin storing a persistent visitor identifier, or replace the cookieless Cloudflare beacon with anything that fingerprints or cross-correlates — this page will be updated before the change goes live, and the "Last updated" date at the top will reflect the change.