Cookies and browser storage

Every one of them, named, with what it is for and how long it lasts. The list is short enough to print in full, so it is printed in full.

Cookies we set

None. Not one, on any page, for anybody, as this site is deployed today.

There used to be exactly one, called mp_admin, and it signed the shop operator in at /admin for eight hours. That page is now behind the same sign-in customers use, which is Clerk's and keeps its own cookies on its own terms, so ours had nothing left to do and was removed rather than left set. No code of ours sets a cookie any more.

One thing could change that answer, so it is named here rather than left to be discovered. The code that reports a sale back to Meta, so that money spent advertising this shop can be told from money wasted, is built and is switched off: without a pixel id in the deployment it loads no script, defines nothing and sends nothing, and it has never been switched on. Meta's tag does set a cookie of its own on this domain. Turning it on is therefore a change to this page, and to the consent this page is currently able to do without, before it is a change to a setting.

Cookies other people set

Marketing cookies, at the foot of every page, puts the Meta question back and deletes _fbp as it does. That is the whole of the withdrawal: one press, in the same number of taps it took to agree, and it takes effect before you answer rather than after.

Vercel counts visits for us and is the interesting absence from that list: it sets no cookie and stores nothing on your device, which is the reason it can run without asking you first. What we count says exactly what it records.

None of the three is set until you agree, sign in or pay, and none of them is ours to describe as absent. Clerk's code is fetched earlier than its cookies are set: on a browser carrying the sign-in hint listed below it is fetched the moment the shop window opens, so the shop knows what you own without your asking. A browser that has never signed in here fetches nothing of Clerk's until the account screen is opened.

Kept in your browser, which is not the same as a cookie

None of this is sent with a request. It sits on your device, it is readable by anything that can reach your browser profile, and clearing your site data removes all of it.

What Where Why How long
A world save, only if you press the button IndexedDB, mineprint-kept-worlds So a world pass can crop the same world again without finding the file each time. Fourteen days, one world
Names of worlds your device has opened localStorage, mineprint-known-worlds So a purchase can be listed by its name instead of by a digest that means nothing. Eight worlds, until you clear it
That you have signed in here before localStorage, mineprint-signed-in So the sign-in code is ready before you ask for it, and never downloaded by somebody who only looks. Until you clear it
That you have read the notice about this page localStorage, mineprint-notice-read So it appears once rather than on every visit. Until you clear it
Your answer to the marketing question localStorage, mineprint-marketing-consent So a yes is not asked for twice and a no is not quietly forgotten. One word, yes or no, and nothing about you. Clearing it puts the question back, which is what Marketing cookies in the footer does. Until you clear it
Whether you folded away the banner saying everything is free localStorage, mineprint-free-folded So the banner you folded away stays away, instead of coming back on every screen. Until you clear it
The last answer your account gave sessionStorage, mineprint-account So the account screen is not blank for a second or two while it asks again. It grants nothing. Until you close the tab
The checkout this tab is looking at, the one it paid for, and whether it delivered sessionStorage, mineprint-checkout-open, mineprint-checkout and mineprint-delivered So a refresh in the middle of a payment does not offer to charge you again, a payment made a second ago is told apart from a purchase opened from your account, and one payment delivers once. Each holds a checkout id and nothing else. Until you close the tab

The account screen has a button, Forget the world kept on your device, which clears the kept world, the remembered names, the sign-in hint and the last answer your account gave, in one go. It leaves three rows: the note that you have read the notice, which is the whole of what stops that notice appearing again, your answer to the marketing question, which is not ours to throw away on your behalf, and the one about this tab's checkout, which goes when the tab closes. Clearing your site data takes all three.

Is there anything to turn off?

One thing, and it is the one you were asked about. Marketing cookies in the footer reopens the Meta question and deletes _fbp as it goes, so a yes can be withdrawn in the same single press it was given in.

Everything else above is doing the job somebody asked for, and pretending otherwise would be the dishonest part. Visits are counted, and that count is deliberately built so there is nothing to switch off: it sets no cookie, keeps nothing on your device, and cannot be tied to you. Giving it a Reject button of its own would put a control with nothing behind it beside the one control here that actually does something, and teach you to believe neither.

Clear your site data whenever you like. The shop works exactly the same afterwards; you lose the conveniences in the table and nothing else.