Cookie Policy

What cookies we use

This site sets no advertising cookies, no cross-site tracking cookies and no marketing cookies. We do not use Google Analytics, advertising pixels or social media trackers, and nothing on this site follows you to other websites.

It would be odd to sell data-protection work from a site that quietly tracked the people assessing us, so we built it the other way round: nothing is stored on your device, and the measurement we do keep is aggregate and cookieless.

Exactly what is stored on your device

Here is the full inventory. The point of the table is how empty it is.

Two third-party requests do leave your browser, and we would rather name them than have you find them: the site loads its typeface from Google’s font CDN, and it sits behind Cloudflare. Neither sets a cookie or an identifier for us. Both see the IP address and browser string of the request, as any server serving you a file does. Cloudflare may set a short-lived security cookie if it has to challenge traffic it believes is malicious; that is a security function, not analytics, and it does not apply to ordinary visits.

Measurement, and how cookieless analytics actually differs

We measure how many people visit which pages using Cloudflare Web Analytics. It is cookieless: it stores nothing on your device, sets no identifier, and does not build a profile of you or track you across sites or sessions. It reports aggregate counts only — page, referrer, country, browser and device type.

The technical difference matters, so here it is in plain terms. Cookie-based analytics writes a unique identifier into your browser on the first visit and reads it back on every page you load afterwards. That identifier is what lets a tool say “this same person returned on Thursday and looked at pricing twice” — and, where the same vendor’s script is present on other websites, it is what lets them follow you between them. The identifier is the tracking.

Cloudflare Web Analytics has no identifier to write. A small script reports the page view at the edge; the data is aggregated and the request is done. Nothing persists in your browser, so there is nothing to read back on your next visit, nothing to join up across sites, and nothing that could later be linked to you as an individual. The consequence is a genuine one, and we accept it: we cannot tell new visitors from returning ones, cannot follow an individual’s path through the site, and cannot attribute an enquiry to a browsing history. We get page counts. That is enough to know which whitepapers are worth writing more of.

What the free tools keep in your browser

The DPDP gap assessment and the DPDP readiness calculator run entirely in the page you are looking at. Your answers are held in the page’s working memory while you use it, and are never transmitted to us or to anyone else.

They are also not saved to your device. We do not write them to a cookie, to localStorage, to sessionStorage or to IndexedDB. The practical effect: if you reload the page or close the tab, your answers are gone and you start again. That is mildly inconvenient and we chose it anyway, because the alternative is a file of somebody’s honest answers about their own compliance gaps sitting on a shared laptop.

If you want to keep your result, use your browser’s print or save-as-PDF before you leave the page.

What we deliberately do not collect

We do not record sessions, capture keystrokes, heat-map your behaviour or fingerprint your device. We do not buy or enrich visitor data, and we do not run reverse-IP lookups to work out which company is reading which page — a common practice in B2B consulting, and one we have declined.

Where a form on this site collects your details, those are submitted by you knowingly and used only to answer your enquiry, as set out in the Privacy Policy. The enquiry form emails our team. There is no CRM behind it, no lead database and no autoresponder sequence.

Why there is no consent banner

Consent requirements for cookies and similar technologies bite when something is stored on, or read from, your device, or when information about you is processed to identify or track you. This site does neither. Nothing is written to your device, no identifier exists, and the measurement data is aggregate and cannot be tied back to a person — so there is no processing of personal data here for you to consent to, and no storage for you to refuse.

A banner in that situation would be theatre: it would ask you to agree to something that is not happening, and it would make the notice less honest rather than more. If that ever stops being true, the banner arrives with the cookie, not after it.

Check this yourself — it takes a minute

You do not have to take our word for any of the above, and we would rather you did not. Open your browser’s developer tools on this page:

• Chrome or Edge: press F12, then open the Application tab and look under Storage → Cookies, Local Storage and Session Storage.
• Firefox: press F12, then open the Storage tab.
• Safari: enable the Develop menu in Settings → Advanced, then Develop → Show Web Inspector → Storage.

Click through a few pages, run a tool to the end, and check again. The cookie and storage lists should stay empty. While you are in there, the Network tab shows every outbound request the page makes, so you can confirm the third parties named above are the only ones, and that your tool answers never appear in a request body.

If you find something we have not disclosed on this page, that is a reporting failure on our part and we want to know: [email protected]. We will correct the page or remove the thing, and tell you which.

Managing cookies and site data

Because this site sets no tracking cookies, there is nothing here to opt out of. You can still block scripts, block third-party requests or clear site data through your browser settings, and the site will continue to work normally — the pages are static HTML and do not depend on it.

Blocking scripts will stop the analytics report, which costs us a page count and costs you nothing. It will also stop the two free tools from running, since they are the script.

If this ever changes

If we ever add a cookie or a measurement tool that identifies individuals, we will document it on this page before it is deployed, and add a consent mechanism where the law requires one.

Specifically, a change here would say: what is stored, who sets it, what it is for, how long it lasts, and whether you can refuse it without losing anything. If consent is required, it will be asked for before anything is written to your device, refusing will be as easy as accepting, and refusing will not degrade the site. The “last updated” date at the top of this page moves when any of this does.

We are not planning any of it. If a future tool on this site needs to remember something for you, we will say so here first.

Questions

If you are assessing us as a vendor and need something more specific than a public policy — a completed cookie questionnaire, confirmation for your DPIA, or a written answer about a particular script — ask and we will answer in writing.

• Email: [email protected]
• Phone: +91 98919 83813

For how we handle the details you send through the enquiry form, including your rights over them, see the Privacy Policy.