Cookies

The short version

Four cookies, all of them strictly necessary to do something you asked for: stay signed in, finish the sign-up you started, keep the colors you chose, keep the language you chose. Nothing here profiles you, nothing is shared, and nothing follows you to another site.

That is also why there is no cookie banner. Under ePrivacy art. 5(3) a cookie needed to provide the service you explicitly asked for does not require consent, and asking anyway would be theater. Adding an optional cookie would be a decision to need consent, and a banner would come with it.

Our cookies

• __Host-kin_session — Keeps you signed in to the account you opened. It is httpOnly, so no script can read it. It carries a signed token and nothing you entered into your account: which account it opens, which sign-in it belongs to (the session record our sign-in provider keeps for it, as the privacy notice describes), when it was issued and when it expires. Every signed-in request checks that the session record still exists, so signing out, signing out every other device, changing or resetting your PIN, or erasing your account ends those sessions by deleting their records, even before the cookie expires. Without it there is no way to stay signed in.
• __Host-kin_pending — Set only when you sign up, and only for 30 minutes. It lets this browser show the “check your inbox” page for your sign-up and send the link again. It is httpOnly and signed, and it carries which sign-up it is and when it expires — nothing you typed. It does not sign you in.
• kin_theme — Light or dark, as you chose it with the control in the header. One of three states — the third is the absence of the cookie, meaning “follow my device”. It identifies nobody, and it is read on the server so the first frame paints the right colors.
• kin_locale — The language you picked. It identifies nobody and holds one of the languages the product ships.

Third parties

Cloudflare Turnstile runs the bot check on the sign-up, sign-in, account-recovery and contact pages. Cloudflare states that it sets no cookie and does not use what it sees to profile you.

It never runs on the page a rescuer opens when they scan a tag. That page makes no outside request at all, which is the one promise here that is not tradeable.

Visits to our public pages are counted by a few lines of our own script, which tell our own server which page was opened; the server passes that on to PostHog with your IP address shortened, as the privacy notice describes. Nothing from PostHog loads in your browser, no cookie is set for it and nothing is stored on your device. It never runs on a tag's page, on your account pages, or while you are signed in.

Turning things off

Your browser can block or clear all of these. Blocking the session cookie means you cannot sign in — not because we refuse, but because there is nowhere left to keep the fact that you did. Clearing the other two loses your color and language choices and nothing else.

There is no setting on our side to switch them off, because switching off a strictly necessary cookie is switching off the thing it is necessary for.

Not stored, and worth saying

No analytics cookie or visitor identifier, no advertising identifier, no cross-site tracker, no fingerprinting, and no local copy of anyone's emergency page: the service worker deliberately never caches a tag's page, so a phone that scanned a stranger's helmet keeps nothing of theirs.

Contact

Questions: write to us.