mChat · document
What the server sees, and what it cannot
This page was written by reading the code, not from memory. Every claim matches a line of mChat you can go and check.
What is written to disk
Your username, your two public keys, the date you joined, and optionally a profile picture and a phone number if you use one to sign back in. Your key vault is there too, but encrypted by your passcode: the server stores it without being able to open it.
What a stranger can read
The directory is public by necessity: without it nobody can write to you in an encrypted way. It exposes your username, your public keys, and your picture if you set one. It exposes neither your phone number nor your vault. Verified by querying the live directory, not by reading the code.
What is never written
The content of your messages. The server relays opaque blocks: it sees who to whom in order to route, and nothing else. It holds no private key, so it cannot decrypt, now or later.
What dies on restart
Who is online, codes sent by SMS, and the queue of messages waiting for an offline recipient. That queue is written to disk so it survives a restart: these are your encrypted blocks, which the server can no more open on disk than in memory. Uncollected after 30 days, it is dropped.
Deleting your account
There is no button yet. Write to support@medtra.ca from the address or number attached to the account and it is removed from the directory by hand, vault included. A self serve button is still to be built, and until it exists this page will not pretend otherwise.
No tracking, no third parties
No tracker, no ad network, no font loaded from anywhere else. The page you are reading contacts only this domain. The only counter that exists is a total of relayed bytes, with no who and no what.
Quebec Law 25 and GDPR: data controller, Medtra Inc. For access, correction or erasure, support@medtra.ca.