Skip to content
Updated 11 September 2026

Cookies

This site sets no cookies. That is unusual enough to be worth explaining properly, along with the two things it does store in your browser and what would change if that changed.

Written to describe accurately what this site actually does, and reviewed against the code rather than from memory. It has not yet been reviewed by a lawyer, so treat it as a clear statement of practice rather than as settled legal drafting. If anything here matters to a decision you are making, ask and it will be confirmed.

No cookies are set

As this site is built today, it sets no cookies of its own and no advertising or tracking cookies of anyone else's. There is nothing to accept, so you are not asked to accept anything. A banner demanding consent for cookies that do not exist would be theatre.

What is stored in your browser instead

One small thing is kept by your browser and never sent anywhere. It is not a cookie, it is not readable by other sites, and it holds nothing about you.

  • A session flag recording that the animation on the About page has already played, so it does not replay every time you return to that page during a visit. It is cleared when you close the tab.

The key that releases a download

Requesting a file from the Workshop issues a short-lived signed key, which the server exchanges for the file. It expires in minutes and holds only which file you asked for and, where the file is generated from choices you made, those choices.

It is deliberately not written to your browser's storage. It is held in the page's memory for the moment between your request and the download, and it is gone when you leave the page. There is nothing to clear afterwards.

The tools themselves

The interactive tools in the Workshop keep what you type in the page's memory only. Nothing you enter into the health check, the decision tool, the automation finder or the process mapper is stored in your browser or sent anywhere unless you choose to send it, and closing the tab discards it.

The anti-spam check

The forms use Cloudflare Turnstile to tell a person from a script. Cloudflare's documentation is specific about this: the widget does not set a clearance cookie unless pre-clearance mode is switched on, and pre-clearance is off by default on every widget. It is not switched on here.

Turnstile does process technical signals about the request, such as the IP address, the browser's user agent and a fingerprint of the connection, which Cloudflare describes as strictly necessary to detect bots. That is processing, not storage on your device, and it happens only on the two pages that carry a form.

Analytics

There is no analytics on this site at present. No page views are counted, and nothing follows you between pages or between sites.

If analytics is added later, the intention is a privacy-first tool that sets no cookies and builds no profiles. If a tool that does set cookies were ever used instead, a consent banner would appear first and nothing non-essential would load until you had accepted it. Either way this page would be updated to say exactly what is running, before it ran.

Questions about any of this?

Write to harsh.sp98 at gmail.com and you will get a person, not a ticket number.