Privacy

Accounts and stored personal data

There are no accounts, no comments and no forms on this site, so there is no personal data to hold. There is no email list either — the Briefing page says so plainly and points at the RSS feed instead, which we never see you subscribe to.

Your theme preference (system, light or dark) is kept in this browser’s localStorage under a key belonging to this site. It never leaves the device, and no other site can read it.

Analytics

Google Analytics 4 is different, and is therefore gated: it writes _ga cookies and builds a per-visitor profile across visits. It loads only after you answer yes to the banner. Advertising signals and personalisation are switched off in its configuration, so nothing collected here feeds an ad audience. Your answer is stored in this browser’s localStorage, never in a cookie, and is not sent anywhere.

When consent-gated analytics is running it records a little beyond the page view: which links were clicked, how far down a guide you scrolled, whether you reached the end of one, and when a command was copied out of a code block. On search, the words you type are recorded as the search term. That last one is text you wrote, so treat the search box the way you would any public search box and do not type anything into it you would not want recorded.

One answer stands for 365 days before the banner asks again, and a no lasts exactly as long as a yes — declining does not mean being asked on every visit. If your browser sends Global Privacy Control, that is read as a no and honoured without asking, and any analytics cookies an earlier yes created are deleted. You can change your answer below at any time.

Change your analytics-cookie answer

Withdrawing is one button. Switching to no also deletes the _ga cookies an earlier yes created, rather than merely stopping new ones. The page reloads when you do it, because a script the browser has already fetched and run cannot be unloaded — a reload is the only honest way to guarantee it is gone.

This control covers the consent question only. The device switch further down is separate and stronger: it silences measurement in this browser whatever answer was given here.

Share links

The share buttons at the foot of a guide append a utm_source and a utm_medium to the copied link. Those identify the channel a link travelled through — Reddit, Bluesky, email — and nothing about the person who shared it or the person who clicks it. Delete the query string and the guide opens exactly the same: nothing on this site behaves differently with or without it.

Turn measurement off on this device

The switch below silences every measurement this site controls — both vendors and every event described above — not just the consent-gated half. It is stored per browser, so it does not follow you to another device and does not survive clearing this site’s data. Visiting /?mmocodex-analytics=off does the same thing without coming to this page, and /?mmocodex-analytics=on undoes it.

What no switch here can reach is the counting that happens on the server’s side of the connection. Serving a page means receiving a request, and the host sees that request whatever this page is set to. That is described next.

Hosting

This site is served as static files from Cloudflare’s edge network (Workers Static Assets). Serving a request means Cloudflare processes the metadata that comes with it — IP address, user agent, the URL asked for and the time — for delivery, caching and abuse prevention. We do not receive that as a per-visitor log, and it is not connected to anything else described on this page.

Requests

Because there are no accounts and no personal data held by this site, there is usually nothing to export or delete on request — everything this site stores about you is in your own browser, and clearing this site’s data clears it. If you want to ask anyway, write to us and we will answer within 30 days.

Privacy requests go to contact@mmo-codex.com.