/privacy

[pseudonymous · anon when you want] this is the formal policy. The short version lives at /about.

Privacy is the foundation, not a feature.

You should be able to share research, code and opinions without being profiled. This page lists exactly what we store, what we never store, and — just as important — the limits of what we can promise.

$ what_we_store

01.

Username — chosen by you, public

02.

Password — as a bcrypt hash only — the password itself is unrecoverable

03.

What you write — posts, comments, votes, the flags you raise

04.

Account facts — when you joined, when you last signed in, your karma and role

05.

Who invited you — shown on your profile — the invite tree is how the community vouches for itself

06.

Your inbox — replies to you; read ones are deleted after 90 days

$ what_we_never_store

[✗]Email — we never ask for one

[✗]IP addresses on disk or in logs — an IP lives in server memory for at most an hour, only to rate-limit sign-ups and logins

[✗]Image files — pictures are dithered into text on your device; the file never reaches us

[✗]Third-party requests from your browser — pages load nothing from anywhere else: no analytics, fonts or images; remote images in posts show as links

[✗]Device fingerprints, tracking cookies, advertising data

[✗]Anything sold or shared with third parties

$ anon_posts

>Other people never see who wrote an anon post or comment: not on it, not on your profile, not in your karma.
>Your anon ID (anon#…) is different in every thread, so your anon posts can't be linked to each other.
>The server does know — that's how bans work. Moderators can ban the author of an anon post without ever seeing who it is.
>The operator has database access. Don't post anything that could get you in legal trouble.

$ sessions

You stay signed in with a signed token in an httpOnly cookie — no session records in the database. It lasts 30 days or until you log out. Changing your password signs out every other session at once.

$ your_rights

You can, any time and without asking anyone:

>Edit or delete any post or comment you wrote
>Change your password or delete your account at /settings/account
>Post as anon whenever you like
>Use the site over Tor: at the onion mirror http://rnnrnetypaxce6b5pdsznau2sjcqjfjtyhue426joyfglxbmndrmjtad.onion, or through exit nodes, which aren't blocked

$ data_retention

>Your writing stays as long as your account does. Deleting a post or comment clears its content; an empty [deleted] shell keeps the thread in shape.
>Deleting your account is immediate. You choose: anonymize your writing (it stays, signed [deleted]) or wipe it. Votes, flags, invites and inbox go with the account either way.
>Read inbox notifications are deleted after 90 days.
>The database is backed up daily and encrypted on our server before it leaves — the storage provider (Backblaze, EU) only ever sees ciphertext. Backups are kept for 30 days, so whatever you delete is gone from the site at once and from every backup within 30 days.

$ security_posture

>Passwords hashed with bcrypt (cost factor 12)
>Database reachable only from the app, never from the internet
>HTTPS everywhere; HSTS, a strict CSP, no X-Powered-By
>Rate limits on sign-up, login and password checks
>Every input validated server-side; markdown sanitized before it renders
>Moderation: content three users flag is hidden until a sysop reviews it
>Traffic reaches us through Cloudflare (TLS, DDoS protection). Like any network in between, it sees your IP address; we keep its analytics, error reporting and script injection off and don't export or keep its logs. The onion mirror doesn't go through Cloudflare at all

Last updated: 2026-10-04

This policy is short because the data model is short. The best privacy policy is one where there is nothing to report.

loading…