Privacy.

ClackID is the account you use to sign in to our apps. It holds only what that needs:

• your email address and whether you have confirmed it;
• the name you go by, if you give one on your account page, which apps you sign in to are given when they ask for it;
• a hash of your password, if you set one (never the password itself), sealed with a key kept apart from the database;
• your Telegram id and username, if you sign in with Telegram;
• your Google account id and the address Google gives for it, if you sign in with Google. Nothing else is asked of Google: not your name, picture or contacts;
• if you link Bluesky or sign in with it: your Bluesky account id and handle; whether Bluesky has verified your age, as Bluesky itself reports it, and when that was last checked (never a birthdate; ClackID has none to hold); the two-letter country of the request that linked it, kept because Bluesky’s age check takes one and the weekly check has no request to read it from; and a token that lets ClackID ask Bluesky that one question again each week without you there, kept encrypted. The permission you give Bluesky covers who you are and that one question only: ClackID cannot post for you, read your messages or change anything on your Bluesky account. Unlinking Bluesky, or deleting your account, withdraws the token at Bluesky and deletes all of this. Apps you have signed in to can ask ClackID whether Bluesky has verified your age, and get a yes or no and the date it was checked, nothing else;
• for each passkey you add, its public key, which password manager or device made it (where it says), and when it was added and last used. ClackID receives no private key, fingerprint, face or PIN. A password manager may securely synchronize your passkey;
• which of our apps you have signed in to, and when, with a random id for you that only that app is given, until you delete your account on that app, which tells ClackID to forget it;
• if you have connected another app in the family that sells a membership, whether yours is live and paid, checked with that app at most once an hour, so other apps you use can include what comes with it;
• if you buy a plan on checkout.clackis.com, or somebody buys one for you: which plan, who pays and who it is for, whether it is active, how often it is paid, when it renews or ends, and the payment processor’s reference for you as a customer. Card details are taken and held by Stripe, never by us. Deleting your account cancels any such plan at once; if you pay, your customer record at Stripe is deleted too;
• for a week after a message to an address bounces because the mailbox refused it, a day after a mailbox kept failing for a while, or half a year after a spam complaint about one, a scrambled code made from that address (not the address itself), so we do not keep writing to it. A mail provider refusing us rather than your address is never held against the address. It is about the address, not your account, and it is deleted when the time is up;
• if you opt in to reports from an app, a scrambled submission reference, its date and whether submission was accepted, blocked or uncertain, to prevent duplicate delivery. Report content and preferences stay in that app. These references are removed when you delete your account;
• if you choose a separate report email address, that address and its confirmation status, plus a scrambled one-use confirmation reference that expires after fifteen minutes. This never changes your sign-in or recovery address and is removed when you delete your account;
• when you agreed to these terms, and which version you agreed to;
• your active sign-in sessions, stored as hashes, with when each started, was last recorded active and expires;
• for each app you approve, the sign-in permissions approved, when you approved them and whether you disconnected it;
• short-lived app approval requests, bound to your account and session, with the requested permissions and return details. They expire after ten minutes and are cleaned up on the next authorization request.

It does not hold anything you record inside an app. Each app keeps its own data and asks separately before sharing any of it. An approved app receives an id for you and, if requested and approved, your email address and confirmation status or profile name when you sign in to it (your ClackID id, or, for an app moved to its own ids, one no other app is given). It can also request the age answer above, its permitted subscription, gift and renewal status, and its checkout links. Separately connected service information is described below. When you reset your password, sign out everywhere or delete your account, ClackID tells each app you have signed in to that asks for it to sign you out there, naming you only by the id it was given.

Some apps in the family keep records that another app you use can show, such as verified check-ins. If you connect one of them here, the connection itself is kept by that app against your ClackID id, and ClackID never learns which of its accounts is yours. If you had already connected it to an account on another app in the family, signing in to that app with ClackID connects it here too, and the reverse, because both accounts are then proved to be yours. When an app you have signed in to asks, ClackID fetches those records and passes them on without keeping a copy. Only an app linked to you can ask, and each app shows them only if you switch that on there. Once you disconnect an app from Connected apps, its further ClackID access is blocked. Existing connections keep their previous access until you review or disconnect them; they are not recorded as explicit sign-in approval. Your location is never included. Disconnect from your account page.

If you had an account with one of our apps before it moved to ClackID, the first time you sign in here ClackID asks that app to check your email and password. Only once you agree is your ClackID account created, with the same password hash, sealed the same way (never the password itself), and the two are linked so the app knows it is you. When you join an existing ClackID account to an account on one of our apps instead, that app tells ClackID which of its accounts it is. Nothing is copied for anyone who does not sign in.

We do not store your IP address. Rate limits use a keyed hash of it that cannot be turned back into the address. There are no tracking or advertising cookies; the only cookies are the ones that keep you signed in.

The page for creating an account with a password runs Cloudflare Turnstile, a check that the form is being filled in by a person and not a script. Cloudflare looks at your browser to decide; ClackID is told only whether the check passed, and keeps nothing from it.

You can review or disconnect apps in Connected apps, and end ClackID sessions in Sessions. Disconnecting does not cancel subscriptions, delete data already received by an app or guarantee immediate sign-out from it. You can delete your account from your account page, or ask us to and we will delete it for you in exactly the same way. That removes the account records listed above after any required subscription cancellations and service disconnections have completed. When you delete your ClackID account, every app in the family you use with it erases what it holds about you too. If an app has something to settle first, such as a subscription it bills itself, it only disconnects you, and you can ask it for erasure from its own settings once that is settled. Deleting asks you to confirm it is you first.