Privacy & data

Your ideas belong in the conversation. Your data does not.

Plain-language summary · Local test edition

What we collect

Public reading does not require an account. Contributors provide their name, email address, age confirmation and submitted content. The local audit trail stores timestamps and a one-way client fingerprint for security.

How it is used

Data is used to authenticate contributors, moderate discussions, maintain an editorial and security history, and prevent abuse. No third-party analytics is enabled in this local build.

Your rights

You can request access, correction, export or deletion. A published contribution may be anonymised when retaining the surrounding conversation is necessary.

Retention and security

Passwords and OTP codes are hashed. Database access uses prepared statements, forms use anti-forgery tokens, sessions use HTTP-only cookies, and repeated actions are rate-limited.