Cookie policy

No cookies at all, on any page, before or after any choice you make here. This site does not write a cookie and does not load anything that could write one on our behalf.

Until you answer the banner, nothing at all is stored. Reading this site without touching the banner leaves nothing behind in your browser beyond the normal cache any website produces.

If you do answer it, one entry appears in this browser's local storage under the key letsdecodeai.consent. It holds the four categories with true or false against each, the date and time you chose, and the policy version, currently 1. That entry is the whole record. It is not sent to our server, it is not shared, and deleting it is a single action described below.

A banner appears on your first visit. Refusing and accepting are one button each, the same size, in the same place, because a choice is not free if one answer is easier to give than the other. Customise opens the same categories as a form, where everything except the necessary category starts switched off and stays off unless you switch it on.

The banner does not block the page. You can ignore it, keep reading, keep scrolling, and keep using every link on the site, and nothing loads while you do. It can be operated entirely from the keyboard, and the preferences dialog closes on Escape without recording anything.

Your decision is not permanent. Cookie preferences sits in the footer of every page, and it is here too:

Cookie preferences

Withdrawing deletes the stored entry outright rather than replacing it with a record of refusal, and the banner returns as though you had never answered. That is one action, the same as granting.

One route on this domain is not part of the public site: the publishing studio our own team uses to write articles. It is not linked from anywhere here and is excluded from search engines. Signing in there is handled by Sanity's own software, which keeps sign in state in the browser of the person signing in. That applies to our team, not to visitors.

Everything is sorted into four categories, and nothing outside the first can load until you have allowed it:

• Necessary. What the site needs to work and to remember the choice you made here. This category cannot be switched off, because switching it off would include forgetting that you switched it off.
• Analytics. Counting which pages are read, so we can tell what is worth writing. Off unless you allow it.
• Advertising. Anything that measures a campaign or builds an audience. Off unless you allow it.
• Functional. Embedded things that need their own storage to work, such as a video player from another service. Off unless you allow it.

Three of those categories are currently empty, and we would rather say so than let the list above imply otherwise. Allowing analytics, advertising, or functional storage on this site right now loads nothing, because no measurement service is set up behind them. The preferences dialog says the same thing against each category, read from the running configuration rather than written by hand.

The code that would load one is written and gated. It can load Google Analytics 4 under analytics, and the Meta pixel or the LinkedIn Insight Tag under advertising, and it does so only when the category is allowed and that specific service has been configured. If a category is allowed but nothing is configured, nothing loads. None of the three is configured, so nothing loads.

If that ever changes, Google Consent Mode is set to denied for every signal before any tag is fetched, and only the categories you allowed are raised afterwards. We would also raise the policy version on this page, which makes your existing choice expire and asks you again rather than carrying an old answer over to a new question.

Use Cookie preferences, in the footer of every page, to change or withdraw your choice at any time. Withdrawing removes the stored entry and the banner comes back.

Your browser is the other control, and it is a real one. Every major browser can block or clear cookies and site data for a specific site from its settings, usually under privacy or site permissions. Clearing site data for this site deletes the consent entry along with everything else, which means you will be asked again. Nothing else here breaks, because nothing here depends on it.

If any of this changes, this page is the place we will change first, and the date at the top will show it.