This site sets no cookies
There is no banner to dismiss because there is nothing to consent to. These pages set no cookies, run no analytics and load nothing from anyone else. One preference is kept on your device: whether you want the pages light or dark.
The short version
No cookies. Not for analytics, not for advertising, not for measuring you against other readers. The word is in the title because you arrived looking for it, not because there is a list underneath it.
One item of browser storage, holding one of three words: light, dark or system. That is the complete inventory for these pages.
The app you sign in to is a different application, and it does have to remember that you are signed in. That is described further down, and it does not use cookies either.
The one preference we keep
The light and dark switch writes your choice to local storage under a key named theme-preference. The value is one of three words. There is no identifier attached to it, no timestamp, and it is never sent anywhere. The page reads it before it paints, so the screen does not flash white on its way to dark.
Local storage is not a cookie. It is never attached to a request, so our server never receives it and never learns which setting you chose. If you never touch the switch, nothing is written at all and the pages follow whatever your operating system already asked for.
If your browser refuses to store it, which private windows sometimes do, the switch still works on the page you are on and simply forgets afterwards.
How the language is chosen
English and Spanish live at different addresses. The language you are reading is decided by the address in the bar, and the switcher moves you to the other one. Nothing is stored for it.
There is one exception and it happens once. On the home page, and only the home page, the server reads the Accept-Language header your browser already sends with every request. If it asks for Spanish first, you are forwarded to the Spanish home page. Nothing is written, nothing is remembered, and every other page is served exactly as you asked for it.
That header is not something we set or collect. It is part of the request your browser makes anyway. We read the first entry to decide one thing, which home page to send you to; it is not stored on your device and it is not used to build a profile of you.
Nothing is loaded from anyone else
There is no analytics here. No tag manager, no pixel, no session recorder, no A/B testing script.
The typefaces are served from this site rather than from a font provider, with their licences sitting beside them. The images come from here too. There is no embedded video, no comment system, no chat bubble and no social button, so no other company is told which page you opened.
The browser is held to that by a content security policy sent with every page: no other host may supply an image, a font or a script, no other site may frame these pages inside its own, and a script written into the HTML runs only if its hash is on the list. A third-party tag added by accident would not load. It would be blocked.
One page does make a request. The pricing page asks our own server what a credit costs today, so a price that moved since the page was built is corrected in place. That request carries no cookie, because there is none to carry.
The app is a separate story
Signing in happens in a different application. That one has to remember you, and it does so with local storage rather than cookies: your session tokens, the account they belong to, the marketplace you last selected, and the same light-or-dark preference.
Those values stay in your browser and are attached to requests by the application itself, not by the browser on its own. Signing out removes them. Clearing site data removes them, and you will be asked to sign in again.
Payments are the one place where another company's code runs. Card details are entered into the payment provider's own components and never reach our servers. Whatever those components store on your device is governed by that provider's notice, not by this one.
Clearing it, blocking it
Every browser can block or delete local storage for a site, usually in the same settings panel as cookies. Nothing here breaks if you do. The pages lose their memory of the light-or-dark choice and fall back to your system setting, and the language keeps working because it lives in the address rather than in storage.
In the app the cost is higher: clearing storage signs you out and you will need your password again. Nothing else is lost, because everything that matters is on the server and not on the device.
There is no consent banner to change your mind about, and no vendor list sitting behind one, because neither exists.
If this ever changes
A page like this is only worth reading if it is accurate on the day you read it. If we ever add something that stores or transmits more than a display preference, this page changes first and says what it is, what it holds and how long it keeps it.
If you have measured something on this site that contradicts what is written here, tell us at [email protected]. That is a bug report, and we would rather have it than not.
This page was last reviewed on 15 August 2026.