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).

What your own browser or app loads is limited too. Images and video previews hosted on other websites are not fetched unless you allow them, so reading a message doesn't reveal your address to a site you never chose; you decide per site, or switch it off entirely, under Remote content. Message links point at your own server, and the desktop app only reads previews from servers you've added.

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.

None of this is imposed on your server. Registration consent, legal documents and retention periods are off until you configure them, moderation reasons are optional, and what you do with reports and appeals is your call. Operators outside the EU can ignore all of it; operators inside it have what they need without a paid add-on.

Who can see what

  • Direct messages are participant-only — no admin access to message lists, search or reads. The message edit-history endpoint is the one documented exception, reserved for global admins investigating abuse.
  • 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).
Note

Honesty clause: whoever operates the server administers its database — self-hosting means trusting your own operator, not a vendor's. Pick your host accordingly.