Cookie Policy

A cookie is a small text file a website asks your browser to store, so that it can recognise your browser on a later request. Related technologies — local storage, session storage, pixels, device fingerprinting — do a similar job by different means. This policy covers all of them.

As at 9 September 2026, simdu.co stores one thing by default and two more only if you accept them.

Stored without asking: your answer to the cookie question. When you press Accept or Decline, we record that choice in your browser’s local storage under the name simdu.consent.v1. It holds your decision and the time you made it, and nothing else — no identifier, no name, no email address. It exists so that we do not ask you again on every page, and so that we can prove what you chose. It is not a cookie, it is never sent to us or to anyone else, and it stays on your device until you clear your browser storage. We do not ask permission for this one because it is strictly necessary to give effect to the choice you just made — which is the narrow exemption the law provides, and the only thing on this site that relies on it. If you have never answered the question, even this is not stored.

Stored only if you accept: two Google Analytics cookies. If — and only if — you press Accept, we load Google Analytics 4, and that script sets these two:

• _ga — set by Google Analytics to hold a randomly generated identifier for your browser, so that a later visit can be recognised as the same browser as the first. First-party, and set to expire two years after your most recent visit.
• _ga_8VTZQSWQ02 — set by Google Analytics to keep the state of your visit for this particular website. First-party, and set to expire two years after your most recent visit.

In practice your browser may keep them for less time than that. Chrome caps the life of any cookie at about 400 days regardless of what the site asks for, and other browsers apply their own limits, so two years is the maximum rather than a promise. We measured it on this site: Chrome stores both of the above for roughly thirteen months.

Neither cookie contains your name, your email address or anything you typed into a form. The identifier in _ga is a random number assigned to your browser; it is not derived from anything about you. It is still personal data in the sense the UK GDPR and the EU GDPR use the term, because it singles your browser out from every other one, and this policy treats it that way.

What they are for. They let us count how many distinct people opened the site rather than how many page loads happened, tell a returning visitor from a new one, and see how far through the page people get before they leave. That is the whole purpose. Section 3.4 of our Privacy Policy describes exactly what is sent to Google alongside them, and section 10 names Google as the recipient.

They are not used for advertising. Google Signals and ad personalisation are both switched off in our configuration, so your visit is not joined to a Google advertising profile and is not used to target advertisements to you anywhere.

Specifically, and to be unambiguous, we do not use:

• session recording or heatmaps;
• advertising, retargeting or conversion pixels;
• social media embeds or share buttons that phone home;
• fonts or stylesheets served from someone else’s domain;
• A/B testing or personalisation tools; or
• device fingerprinting, or any other attempt to recognise you without a cookie.

The typefaces this site uses are served from our own domain.

We ask before we store anything, and declining is exactly as easy as accepting. The banner offers two buttons of the same size and the same prominence. It does not block the site: you can read every page, including this one, without answering — and nothing is stored while you do.

If you decline, or simply never answer, the Google Analytics script is not requested at all. No cookie is written, no data is sent to Google, and Google is not told that you visited. You do not appear in our page counts in any form, not even an anonymous one. Nothing on this site behaves differently — the analytics tag is not involved in any part of the experience.

To change your mind, at any time, use the Cookie settings link in the footer of any page. It reopens the same two buttons. If you had accepted and you now decline, we delete both cookies immediately and stop the analytics from sending anything further in that same page view — you do not need to reload, and you do not need to clear anything yourself.

Your browser gives you further routes that work regardless of anything we do, and we would rather list them than not:

• Delete them. Your browser’s settings will let you clear cookies and site data for this site, which removes both cookies and our record of your choice — after which we will ask you again.
• Block them. Most browsers can block cookies for a single site; Safari, Firefox and Brave block trackers of this kind by default.
• Block the script. Any tracker-blocking extension will stop the Google Analytics script loading even if you accepted.
• Use Google’s own opt-out. Google publishes a browser add-on that disables Google Analytics on every site that uses it.

We do not currently change our behaviour in response to a Do Not Track or Global Privacy Control signal, because we ask you directly instead and default to storing nothing. Those signals exist mainly to stop the sale of personal information and cross-site profiling, and we do neither: we sell nothing, and we build no profile of you across other websites.

Our hosting provider records ordinary server logs when a page is requested, which is a different thing from a cookie: it happens on our side and stores nothing on your device. It is not affected by your cookie choice, because it is not storage on your device at all. Section 3.3 of our Privacy Policy describes them.

Likewise, the rate limit on the waitlist form works from a hash held in our server’s memory, not from anything stored in your browser. Section 3.2 of the Privacy Policy describes that.

Google Analytics is described in section 2 above and in sections 3.4 and 4 of our Privacy Policy, which names Google as the recipient. If we add anything further that stores data on your device, or share data with any additional third party, we will update this policy first and ask for your consent before storing it. Strictly necessary storage may be used without consent, as the law permits, and section 2 lists everything we rely on that exemption for — today it is one record of your own cookie choice and nothing else.

The SIMDU Software, when released, may store settings on your own device to remember your preferences. That is local to your device, is not a cookie, and will be described in the Privacy Policy before the Software ships.

If you have a question about the above, or you think something on this site is tracking you that is not listed here, we would genuinely like to know. Email support@simdu.co.