Documentation

Privacy

Own your data — everything lives on your server, and the tooling to honor your users' rights is built in.

Your server, your data

Every message, file, and account sits in your database and volumes on your host. There is no vendor cloud, no telemetry, and no third-party analytics in the product — the server talks to the outside world only where you configure it to (your SMTP relay, Let's Encrypt for certificates, browser push services for Web Push, and image pulls from the GitHub registry).

User rights, built in

• Export — every user can request a full JSON export of their data from Preferences.
• Deletion — account deletion with a grace period, then anonymization in place.
• Consent & terms — registration consent and legal documents are first-class server settings.
• Retention — messages, notifications and attachments can expire automatically.
• Reports & appeals — DSA-style content reporting with an appeal flow, handled in the admin panel.

Who can see what

• Direct messages are strictly participant-only — no admin read access through the API.
• Private channels and communities are invisible to non-members; search and permalinks respect the same boundaries.
• Media is served through signed, expiring URLs — no public bucket.
• Voice media is encrypted in transport (DTLS-SRTP).