Privacy
This is how the koven.chat reference instance handles your data. If you sign up on a different Koven server, that server's operator is responsible for their own policy.
What we store
- Account. An email address (used only to send you the 6-digit login code), a username, and a hashed display profile. No password.
- Messages. Public-room messages are stored on the homeserver in plaintext, the way Matrix works. Direct messages are end-to-end encrypted with megolm; we cannot read them.
- Governance events. Flags, votes, collapses, and censures are public Matrix events. They are visible to anyone in the federation forever, by design.
- Reputation. Per-account reputation scores, derived from on-protocol activity. Computed locally; not shared with third parties.
What we do not collect
- No analytics. No tracking pixels. No third-party advertising SDKs.
- No telemetry. The client and server do not phone home.
- No payment data. The koven.chat instance is free to use.
Federation
Koven federates with other Koven servers. When you post to a federated room, your message is replicated to every server that hosts a member of that room, and to the public audit log of governance events. This is how Matrix works. If you do not want a message to leave the koven.chat server, post it in a non-federated or end-to-end encrypted room.
Cookies
We use first-party storage to keep you signed in. We do not set cookies for advertising or cross-site tracking.
Deletion
You can delete your account from the client. Account deletion removes your profile and detaches your username from your messages. Because the audit log is append-only by design, governance events you signed in the past remain in the log under a redacted identifier. There is no way to retroactively remove a flag or a vote. This is the cost of having a public, tamper-evident record.
Contact
Questions? hello@gnosyslabs.xyz.