Data & Moderation Transparency
Last updated: · A plain-language account of what SecureChat stores, keeps, deletes, and moderates — and how.
1. What data is stored, and where
| Data | Where | Who can read it |
|---|---|---|
| Email, display name, birth year | users/{uid} | You, and MSS's system administrator |
| Public encryption key (per device) | mssUsers/{uid} | Anyone signed in — this is not secret, it's needed for others to encrypt data to you |
| Workspace & room metadata (names, members, timestamps) | mssCompanies, mssRooms | Members of that workspace/room; workspace admins |
| Message ciphertext | mssChats/{roomId}/messages | Stored for everyone with read access to the room doc, but only decryptable by members holding that room's key |
| Wrapped (encrypted) room keys | mssRooms/{id}/keys/{uid} | Only the specific member it belongs to |
| Reports | reports | The reporter, and admins of the relevant workspace |
2. What we can and can't see
We cannot read message content, ever — not MSS staff, not workspace admins who aren't members of a given room, not anyone without that room's decryption key. This is enforced by the encryption itself (see §5), not just by policy. What we can see is metadata: who's a member of what, when a message was sent, its encrypted size, and who sent it.
3. Retention rules
- Messages are retained until deleted by their sender, a workspace moderator with delete permission, or as part of account deletion.
- Account data is retained for as long as the account exists.
- Reports are retained so moderation history is auditable, even after the reported message itself is deleted.
- Key backups you export yourself are never stored by us — they exist only as a file on your own device.
4. Deletion rules
Using "Delete My Account & Data" in your SecureChat profile deletes, in order:
- Every message you've authored, across every workspace.
- Every room you created (freeing up that workspace's room quota).
- Your membership in every workspace you don't own.
- Your SecureChat profile.
- Your base MSS account (email/auth identity).
One known limitation: if you own a workspace outright, it isn't auto-deleted (ownership transfer isn't supported yet) — you'll be prompted to delete or hand off owned workspaces first. Deleting a room or leaving a workspace does not retroactively delete messages you sent there before the room's key was known to have been compromised — deletion is immediate and forward-looking, not a guarantee against a copy someone already has (this is inherent to any messaging system, encrypted or not).
5. How the encryption actually works
Each device generates an ECDH (P-256) key pair; the private key never leaves the browser. Each room has a random AES-256-GCM key, generated once and "wrapped" (encrypted) individually for every member using a key derived from ECDH between the wrapper's private key and each recipient's public key. Messages are encrypted with the room's key, with a fresh random IV per message, before ever being sent to Firestore. None of this requires — or uses — a server-side decryption step at any point.
6. How moderation works
Any member can report a message via the flag icon. Because content is end-to-end encrypted, a report is only ever as informative as what the reporter chooses to include (their own decrypted view of the message) — we have no way to inspect message content independently. Reports appear in the reporting workspace's Admin Panel → Reports tab, visible to members with the admin permission in that workspace.
7. How reports are handled
- A workspace admin reviews the report (reason, and whatever the reporter quoted).
- The admin can mark it resolved once handled.
- The admin can ban the reported member from sending further messages in that workspace — this doesn't delete their past messages or remove them from other workspaces. The workspace owner can never be banned this way.
- For content suggesting illegal activity or harm to a minor, MSS may act at the account level independent of the workspace's own decision — see our Community Guidelines.
8. Permissions model
SecureChat uses named, assignable roles per workspace (visible in Admin Panel → Roles). Each role grants a combination of: creating rooms, deleting messages, managing rooms, managing members, and admin panel access. The workspace owner always has every permission and can't be edited or banned.
9. Free-tier limits
Currently: up to 3 workspaces owned per account, and up to 10 rooms per workspace. These are enforced server-side (Firestore security rules), not just in the interface.