Your story. Your boundaries.
Privacy policy draft. Counsel review and operator contact details are required before public launch.
What the application stores.
We store your chosen alias, rules acceptance, optional verified recovery email, session tokens as hashes, profile details, drafts, stories, uploaded images, comments and replies, reactions, follows, blocks, votes, reports, notifications, and account requests. Email addresses, reports, blocks, and notification lists are private. Your display name, handle, bio, approved stories and comments, verified vote totals, and milestones are public. If you connect a wallet for voting, we retain its public address, chain, ownership verification and balance/price evidence privately. Wallet bindings and minimal vote evidence remain for campaign integrity and prevention of relinking abuse, including after deletion. We never ask for private keys, seed phrases or transfers.
Why we keep it.
Data supports sign-in, publishing, vote integrity, moderation, and campaign records. We keep a limited keyed hash of trusted network information for rate limits, rather than raw IP addresses in application logs. Rate-limit buckets expire. Magic links expire after 15 minutes, sessions after 30 days, and expired security state is cleaned by a scheduled job.
Your choices.
Use a nickname, keep private details out of stories and comments, change your display name and bio, edit or delete your own comments, withdraw stories, mute or block authors, unfollow stories, export your account data, or request deletion from your account. A moderator processes deletion requests. Personal profile data, public stories, and comment bodies are removed; blank thread placeholders, minimal pseudonymous audit records, and finalized campaign point records may be retained where needed for integrity and legal obligations.
Images and service providers.
Uploaded JPG, PNG, and WebP images are re-encoded to WebP, resized, and stripped of metadata. Images are private until a story is approved. Hosting, database, email, storage, and optional error-monitoring providers process data necessary to operate the service. The operator must disclose its selected providers, retention periods, legal basis, international transfer safeguards, and privacy contact before launch.
Cookies and retention.
The application uses an essential HttpOnly, SameSite session cookie. It does not include advertising trackers. Account deletion does not instantly erase disaster-recovery backups or immutable audit records. The operator must set and disclose a backup retention schedule, implement storage cleanup, and handle legal privacy requests before public launch.