Cookies

One cookie, four keys in local storage and two keys that live no longer than the tab. That is everything.

Each is named below by the name you will see in the developer tools of your own browser, so the list can be compared rather than believed.

• NEXT_LOCALE, a cookie

  Holds a language code and nothing else. Written only when you pick a language from the menu, and kept for a year.

• armanos-theme, local storage

  Holds the word dark or the word light. Written only when you press the theme button.

• armanos_access_token, local storage

  The short lived key that proves you are signed in. Written on sign-in, removed on sign-out.

• armanos_refresh_token, local storage

  The key that asks the server for a fresh access key. Written on sign-in, removed on sign-out.

• armanos_browser_key, local storage

  A random number written on sign-in, so the list of sessions recognises this browser and shows it as one line. Signing out keeps it; our server keeps only its hash.

• armanos.fromApp, session storage

  Holds the digit one if you arrived here from the desktop app. It disappears when the tab closes.

• armanos.support.email, session storage

  Holds the email from the sign-in, sign-up or password reset form, written when you press Contact support there. The support form reads it once and deletes it; otherwise it goes with the tab. It stays out of the page address, and the password is not kept.

Both sign-in keys sit in local storage, which any script running on this page is able to read. A cookie marked http-only would be out of reach of scripts; these two are not, and that is a real difference rather than a detail.

What stands between them and a foreign script is that no foreign script runs here. The response rule named below allows scripts only from our own address, so the browser refuses a foreign one even if one ever appeared.

A visit that only reads pages leaves nothing behind. Every one of the seven is written by something you did: picking a language, pressing the theme button, signing in, arriving from the app, or pressing Contact support under a sign-in form.

Nothing is written on page load and nothing in the background. There is no service worker keeping a copy of the site, and no database in the browser holding anything of yours.

The cookie holds a language code such as en or ru. It is written by the language menu and read in exactly one place: the redirect that sends an address without a language to the right language.

It is marked lax, so another site cannot make your browser send it in the background. It is not hidden from scripts: a language code is not a secret and identifies no one.

The theme key holds one of two words. A small script built into the page reads it before the page paints, which is why a dark page does not flash white on the way in.

The key armanos.fromApp is set only for people who came here from the desktop app. It is used once, to offer opening the app already signed in, and the browser drops it with the tab.

There is no analytics on this site. No tag manager, no session recorder, no crash reporter, no advertising pixel and no social button phoning home.

That is a count rather than a claim. Every built page was walked for the things a browser fetches on its own: scripts, stylesheets, images, frames and preconnect hints. The number pointing at any host other than ours is zero.

The two typefaces are fetched once at build time and served from our own address, so reading this sends nothing to a font service. The response also switches off the browser interest cohort here, so the visit feeds no advertising group.

Open the developer tools, go to the storage panel, and look at cookies and local storage for this address. What you find should be the list above and nothing beside it.

The network panel answers the other half. Reload the page with it open and every row should carry our own address.