Privacy

What we store

When you sign in with Bluesky, we store your account's DID, your current handle, your display name, your avatar URL and the bluesky.bot handle you claim. We need them to serve your handle on the AT Protocol network.

We never ask for your Bluesky password: sign-in goes through Bluesky's own OAuth page.

To keep you signed in, we also store the OAuth session that Bluesky issues to Bluesky.bot: access and refresh tokens and the matching key. You can revoke it at any time from your Bluesky settings.

We only ask Bluesky for the permissions we use: proving who you are when you sign in, and, for a bot you add, changing its handle to the one you claim. These permissions do not let us read your email or your private messages, nor post on your behalf. Sessions opened before October 2026 had broader permissions: we never use them beyond signing you in, and they expire on their own.

Cookies

We set one cookie, named sid, which keeps you signed in for up to 7 days. It is encrypted, strictly necessary, and never used for tracking. "Sign out everywhere" on your dashboard ends it on all your devices at once.

While you sign in or add a bot, a second cookie, named oauth_binding, proves that the sign-in finishes in the browser that started it, so nobody can sign you in to their account with a link. It holds a random value, is only sent to our sign-in page, and is deleted when you come back from Bluesky, or after one hour.

A third cookie, named NEXT_LOCALE, remembers the language of the last page you read, for up to one year, so that your dashboard speaks it; without it, the dashboard follows your browser's language. It never changes the language of a page, which only depends on its address. It holds only a language code and is never used for tracking.

When you sign in, a cookie named signed_in, set to 1, tells the header to show "My bots" instead of "Sign in". It is not encrypted because it holds nothing: it does not sign you in, lasts as long as your session and is deleted when you sign out.

When you claim a name from the home page, a cookie named picked_handle remembers that name for 30 minutes, so your dashboard can suggest it once you are signed in. It holds only the name and is deleted as soon as you claim a handle or dismiss the suggestion.

Analytics set no cookie at all, which is why there is no consent banner.

Your choice of light or dark theme is saved in your browser's local storage, under the key "theme". It never leaves your browser: we keep no copy of it and never use it for tracking.

When your browser prefers another of our languages, a small banner offers the page in it. Closing or following it is saved in your browser's local storage, under the key "language-suggestion", so that it does not come back. It never leaves your browser.

Analytics

We use Umami, a privacy-friendly analytics tool hosted on our own server, to count page views and a few anonymous actions (for example "sign-in started" or "handle claimed"). Visitors are not identified: there is no cookie, no fingerprinting across sites, and the IP address is not stored.

When something breaks, an error report (the page, the browser and the error message, never your session or your IP address) is sent to an error tracker hosted on our own server, so that we can fix it.

No event contains your handle, your DID or anything you typed.

Contact form

When you use the contact form, your name (if you give one), your email address, the topic and your message are sent by email to our mailbox through Resend, our email provider, so we can answer you. We do not store them on our servers.

To limit spam, we count messages per visitor with a salted hash of your IP address, never the address itself, for one hour.

Hosting

The site and its database are hosted on a server operated by Bluesky.bot, behind the Cloudflare network. Your handle and DID are public by design: anyone can resolve name.bluesky.bot to your DID.

Your choices

Anyone can report a bot from its page. A report is anonymous: we store the reason, the details you type and a salted hash of your IP address (never the address itself), only to limit spam and duplicate reports. Reports are deleted with the bot.

You can sign out, or release a bot's bluesky.bot handle, at any time from your dashboard. Releasing switches the bot back to its previous Bluesky handle when Bluesky allows it; otherwise pick another handle in the bot's Bluesky settings.

You can delete your account from your dashboard. We then delete your account, your bots, their OAuth sessions and every record that identifies you, and revoke the sessions with Bluesky. Moderation records keep only an anonymous reference. A freed handle stays blocked for others for a few days, so nobody can impersonate your bots right away.