Cookies and local storage

Two cookies, plus the sign-in ones

NEXT_LOCALE records the language you are reading in. It lasts one year, is limited to this site (SameSite=Lax) and contains two letters. It is set because you chose a language, and it does nothing else — no consent banner asks about it, because there is nothing to consent to beyond the request you already made.

allin_ephemeris remembers the country and city you picked on the ephemeris page, in the form FR:Paris. It lasts one year, is limited to this site (SameSite=Lax) and is written only when you actually choose: a visitor who never touches the selector never receives it. It is a cookie rather than browser storage for one reason — half that page is written on the server, before any script runs, so a preference the server cannot read would be a preference the page ignores.

A visitor without an account receives two more, and both come from Google Analytics: _ga and _ga_S42JR3MKXH, which tell one browser from another so that four pages opened by one person are not counted as four people. They last two years, Google's script writes them and Google reads them — they are the only cookies here that a third party can read. None of that happens before you accept: until then the script is loaded with measurement refused and writes nothing, and refusing keeps it that way for good. If you sign in, Supabase — the service that holds the accounts — sets a few of its own, named sb-…: they carry the session token that keeps you signed in from one page to the next, they are read by nothing but this site, and signing out deletes them. They exist because you asked for a session, and they last as long as it does.

Eleven keys stored on your device

These live in your browser's storage and are readable by nobody but you. Without an account, exactly one of them ever leaves your device: allin:sid, at the end of the list. Signing in adds three — favourites, pins and recents are copied into your account, and only those three, under the conditions set out in the next section but one. Every key is named here rather than grouped, because a page that promises a complete list and delivers a category summary has said less than nothing:

• allin_favorites — the tools you starred.
• allin_recents — the tools you opened recently, so you can find them again.
• allin_pins — the tools you pinned to My Allin, in the order you arranged them.
• allin_notepad — everything you type into the online notepad, as plain text, written 400 milliseconds after you stop. It is the only key on this list that holds your own prose rather than a setting. It never leaves the browser, the tool's Clear button empties it, and a different device shows an empty pad — which is the same fact from the other side.
• allin_currency — the currency you picked, when you overrode the one guessed from your language, so the next calculator opens in it.
• allin_units — one word, metric or imperial, once you have said which. It exists so that choosing feet is not something to redo on every tool that measures anything.
• allin_image_day — three values: today's date, how many file conversions you have run today, and how many extra ones an ad earned you. It is what makes the daily allowance daily. It is not a security boundary either: it is in your browser, and emptying it resets the count.
• allin_ent and allin_preset — which features are unlocked for you. Without an account these hold a default and change nothing.
• allin_consent — granted or denied, your answer to the measurement request. It is the key that decides whether Google Analytics may store anything; while it is absent, the answer is treated as denied. The cookies page carries a control to change it.
• allin:searches — your recent searches, so the box can offer them back. This list stays on your device; what a search itself sends us is set out below.
• allin:sid — a random UUID your browser draws on arrival and keeps in the tab's own storage. It is a pseudonym and nothing else: it is derived from nothing about you, it names no person, and no table anywhere turns it back into one. It travels with the measurements described below, which makes it the one value on this list that leaves your device without an account, and it exists so that one person opening four pages can be told apart from four people opening one. It is discarded when you close the tab, it is not a cookie, and it cannot connect two visits or two websites.

The twelfth key, which is not yours

There is one more key in the code, and naming it is the only way the list above can be called complete: allin:admin-theme holds light or dark for the private administration area of this site. Nothing outside that area ever writes it, so it cannot appear in your browser unless you administer the site. Twelve keys exist; eleven of them can be yours.

Three keys that go up to the account

Signing in and opening the workspace at /app copies three of the keys above into your account: allin_favorites, allin_pins and allin_recents. Nothing does this on the public site, nothing does it while you are signed out, and the other eight are never sent anywhere — the notepad included. What reaches the server is a list of tool identifiers and the moments you opened them, in two tables, and nothing else.

The merge runs once, on arrival, and is written so that creating an account cannot cost you anything: what you starred as a guest is added to what the account already held, guest pins go after the ones already there and stop at the number your plan allows, and a tool the account has already recorded is not recorded again. From then on, starring or pinning writes to both places at once, which is what makes the library the same on your phone and on your laptop.

It is kept for as long as the account is. Removing a star or a pin deletes the row there and then; deleting the account, from the Account page in the workspace, takes all of it — and the section below says precisely what that leaves behind.

What we measure, and what we do not

We count how our own pages are used, with our own code, and we do not share any of it. No advertising network and no cookie of ours sits behind these figures: a page view, the fact that a tool was used, and the tab identifier described above. Nothing you type into a tool is ever collected — a wheel reports that it was spun, never the names on it; a calculator reports that it calculated, never the numbers. Google Analytics measures the other half — where visits come from, and which pages people leave on — and it is a third-party script: once you have accepted, it reads the two cookies named above, and what it collects reaches Google. It is the only third party on this site. The advertising placements on tool pages are still empty frames holding their space. If an advertising network is connected later, this page will say so before it goes live, and a consent request will appear where the law requires one.

All of those measurements carry the tab identifier described above, searches included. A search sends the query itself, how many results it returned and which one was opened, alongside that identifier — because a search that returns nothing is a missing tool, and there is no other way to learn of it. Since the identifier dies with the tab, none of it can be joined to a later visit or to anything outside this site. One thing goes further: in the signed-in workspace at /app, what you open and keep is recorded against your account, because whether people come back a week later cannot be answered otherwise. Signed out, that space records only the tab identifier.

Removing all of it

Clearing this site's data in your browser removes the cookie and all twelve stored keys, the tab identifier and the notepad included, and signs you out by removing the sb-… cookies. If you have never signed in, that is the whole story: what remains on our side is the measurement counts described above, which name nobody. With an account it is different — your favourites, pinned tools, saved calculations, projects and history are on our servers. They are yours: you can delete any of them from the workspace one at a time.

Or all at once: the Account page in the workspace deletes the account itself, after you have typed your own email address to confirm. That removes the sign-in, the entitlements, the profile, the favourites and pins, the collections, the saved results, the projects and the tool history — every row that names you. Two things survive on purpose and are stripped of your identifier rather than deleted: the usage counts, whose account column is set to empty so that the totals stay true while the person disappears, and the administration audit log, which is not a document anybody gets to rewrite. Neither can be traced back to you afterwards.