Privacy Policy

Last updated: July 2026

This policy describes what data the hosted Atrium service at chat.useatrium.xyz collects, why, and what your choices are. It is written to be read, not to hide anything.

What we collect

Account data — username, optional email address, display name, and a scrypt-hashed password (never plaintext).
Content you create — messages, files you upload, channels, workspaces, statuses, and reactions.
Technical data — session tokens (login state), timestamps, and standard server logs used to keep the service running and prevent abuse.

Cookies

We use two functional cookies: a session token that keeps you signed in, and a signed_in flag that lets the marketing site personalize its call-to-action. Neither tracks you, and there is no analytics or advertising on this service.

How your data is stored

Everything lives in a single SQLite database and an uploads directory on one rented server in the EU (Falkenstein, Germany). Data is not sold, shared, or mined. Backups, when made, are encrypted copies of the same files.

Federation

Atrium servers can connect to each other. If your workspace shares a channel or a DM with a workspace on another server, the content of that channel or DM — and basic profile fields (username, display name, avatar) — is relayed to that server and stored there too. Only the conversations explicitly shared ever leave this server.

What we don't do

No advertising, no trackers, no third-party analytics.
No sale or rental of your data to anyone, ever.
No reading of your private conversations. Server administrators can technically access the database but only touch it for operational reasons (abuse response, legal obligation).

Retention and deletion

Your data stays as long as your account does. To delete your account or specific content, open an issue at github.com/atree0/atrium/issues from the account in question, and it will be handled manually. Deleted messages are soft-deleted and purged on the next backup rotation.

Your alternatives

Atrium is open source (MIT). If you want complete control of your data, you can run your own server — your data then never touches ours. See the deployment guide.

Changes

If this policy changes, the updated version will be posted on this page with a new date.

This service is operated as a private, non-commercial project. Contact is only possible via GitHub issues. No personal data of the operator is published on this site.