Privacy notice
Last updated 1 November 2026
Draft. These texts have not been reviewed by a lawyer yet, and the contact address will be added before public launch.
What we keep about you
Your email address, the time you confirmed it, and the time you confirmed you are 18 or older and accepted the terms.
For each passkey you add: its public key, an identifier, a usage counter and the dates it was added and last used. The private part of a passkey never leaves your device, and we cannot use the public key to sign in as you.
For each signed-in device: a SHA-256 hash of the session token and its expiry date (30 days). The token itself is only in your browser's cookie.
Payments
Creators who accept payments connect a view-only key for one Zcash wallet account. It goes to ZSocial's payment watcher, which keeps only the part that sees incoming shielded (Orchard) payments, encrypted. It cannot spend or move money, and it does not show what the creator sends or holds.
For each tip, membership and post unlock we keep who paid whom, for what, the amount, the one-time payment address, its status and its times. For a tip we also keep your message, which is never written on the blockchain.
For memberships we keep when each one started and when it ends; for unlocks, which posts you unlocked.
We do not record which wallet a payment came from. The money goes from wallet to wallet; we never hold it.
Notifications
We keep a list of notifications for your account: new followers, payments you received, a reminder three days before a membership of yours ends, decisions our moderators made about your posts or account, and the outcome of reports you sent, each with the time and whether you have read it.
A notification points to the record it is about, so a tip message or a post you delete is not kept in it. A decision about your post or account keeps what was decided, the moderator's reason and the report reasons; it never names the moderator or the people who reported you.
Short-lived security records
Sign-in codes are stored only as a keyed hash and stop working after 10 minutes or 5 wrong tries.
To slow down abuse we count requests per email address and per network address in 15-minute windows. The counter is stored under a keyed hash, never the address itself.
What we do not collect
No passwords, because the service does not use them. No advertising or analytics trackers, and no third-party scripts.
Cookies
Only cookies the service needs: your session (30 days), a passkey challenge (5 minutes) and an unfinished sign-up step (15 minutes). All are first-party and HttpOnly.
Sign-in codes are sent through an email delivery provider, which receives your address and the message to deliver it.
Your choices
You can remove passkeys and sign out in Settings. To have your account deleted, contact us at the address that will be listed here before launch.