Cookies and analytics
Last updated 8 September 2026
This site sets no cookies. It stores nothing on your device, and it reads nothing from it.
That is why you were not asked to accept anything. There is nothing to accept.
What we count
We count what happens on the site so we can tell whether it explains the product: which pages are opened, which sections are read, which pricing option is pressed, and whether the early-access form is started and finished.
Each of those records four things and nothing else:
- The name of the event, from a fixed list we control.
- The path of the page it happened on.
- A random session value, generated fresh by your browser on every page load and forgotten the moment you navigate.
- A short label where one is useful, such as which section came into view or which pricing tier was pressed.
Your IP address is not recorded. Nor is your browser, your screen size, your location or anything else that could be combined into a fingerprint.
Why the session value is not a cookie
It lives in your browser’s memory for the length of one page load. It is not written to disk, not sent back to you, and not recoverable afterwards. Its only job is to let us see that one visit included both a pricing view and a click, rather than counting those as two unrelated things.
The consequence, which is worth being straight about: we cannot tell that the person who opened the homepage is the same person who later submitted the form. We accepted that in exchange for not tracking anybody. Where the form is concerned we know which link was used to reach it, because that is in the address, and that is enough.
The full audit
Everything this site can store or request, and how each is classified. There is nothing in the analytics, marketing or other categories, which is why there is no banner.
| Mechanism | Used here | Category |
|---|---|---|
| Cookies | None. The site sets no cookie of any kind. | Not applicable |
| localStorage | None. | Not applicable |
| sessionStorage | None. | Not applicable |
| IndexedDB | None. | Not applicable |
| Per-page-load session value | A random value in memory, for the length of one page load. Never written to your device. | Strictly necessary, and not storage |
| First-party event counting | Event name, page path, that session value and a short label. No IP address, no device data. | Analytics, without storage or identifiers |
| Third-party analytics, tag managers, session recorders | None. | Not applicable |
| Advertising or marketing trackers | None. | Not applicable |
| Fonts | Served from this domain as files. No request to any font service. | Strictly necessary |
| Early-access form | What you type, sent to our server only when you press the button. | Strictly necessary for the request you made |
The one thing worth explaining is the row in the middle. Counting events is an analytics purpose, but the § 25 TDDDG question is not what the purpose is, it is whether anything is stored on or read from your device. Nothing is. So there is no consent to ask for, and a banner offering you a choice that changes nothing would be a dark pattern rather than a courtesy.
The permission you tick on the early-access form is a different thing entirely, and it is kept separately: it is recorded on your request, word for word, and never mixed into the event counts.
No third-party trackers
There is no Google Analytics, no advertising pixel, no session recorder, no chat widget, no A/B testing script and no embedded video.
The fonts are files served from this domain, so no request is made to Google Fonts or any other font service when you open a page.
If that changes
If we ever add something that stores or reads information on your device beyond what is strictly necessary to show you the site, § 25 TDDDG requires your consent first. In that case you would be asked before it loaded, refusing would be as easy as accepting, and this page would say what it is and why.
What we do with the early-access form is a different matter and is covered on the privacy page.
Questions
Email hello@cantheydoit.com.