Privacy policy
2 Oct 2026
This policy explains what information DMCN LLC (“DMCN”, “we”, “us”) does and does not process when you use our encrypted email service. The short version: your mail is encrypted on your device, and we are built so there is as little to collect as possible.
1. Who we are
DMCN LLC created the DMCN protocol, maintains its open specification and reference implementation, and owns the DMCN name. It operates this service, meaning the apps, websites and relay infrastructure behind the addresses we issue, and is the controller responsible for the limited information described in this policy.
It does not own the DMCN network. The protocol is open and the server software is published under Apache-2.0, so anyone can run DMCN nodes on their own domain. This policy covers only what we operate: mail you exchange with an address on someone else’s DMCN domain is handled by that operator under their own practices, not ours.
Questions about this policy, or about the information we hold, can be sent to the privacy address printed at the foot of this page.
2. Our approach
We designed DMCN to minimise the data we hold. Where ordinary email providers can read your messages, we cannot: your mail is encrypted on your device and we only ever handle the encrypted version between DMCN inboxes.
3. What we can and can’t see
We cannot read the contents of your DMCN-to-DMCN mail, and we do not hold your encryption keys. We do process a limited amount of operational data needed to run the Service, such as your address and billing status.
Mail sent to or received from a regular email address is decrypted at the bridge to interoperate with standard email; it is protected in transit but is not end-to-end encrypted.
4. Information we process
Account data: your DMCN address and settings. Billing data: your plan and payment status (payments are handled by our payment processor; we do not store full card numbers). Operational logs: minimal metadata needed for reliability and abuse prevention, retained for a limited period.
5. No ads, no tracking
We do not use advertising, third-party trackers, or content scanning. We do not sell or rent your data. Remote images in mail are blocked by default to prevent tracking pixels.
We do count visits to our public marketing pages, in daily totals: how many pages were served, which campaign tag (if any) brought someone here, and the name of the website they came from, if their browser tells us. We keep only that website's name, never the page they were on. We count our sign-up link the same way each time it is followed, separately from the pages. When we compare two versions of our home page, its links say which version you saw, and we count which version the links people follow came from. Your browser picks the version at random each time the page loads and keeps no record of it. That count is aggregate: no cookies, no IP addresses, no profiles, and nothing that could identify a visitor or link two visits to the same person.
6. Demo addresses
The demo address offered on our website is created only when you ask for one, in a copy of our mail client kept for demo addresses on its own web address. Your browser generates its keys there and keeps them in that site’s local storage until the address expires or you end it, so the address survives a reload or a closed tab. The private keys never leave your browser. What the mail client keeps in a browser for any account, such as its search index, is kept there too, and cleared when the address ends.
We hold the address, its public keys and the mail sent to it, still encrypted, on a server used only for demo addresses. Its sent mail, the senders you choose to trust and its settings are stored on the same server, encrypted to the address’s own key, as they are for any account. Mail it sends to ordinary email passes through our bridge like any other account’s, and the bridge’s delivery log records the sender and recipient addresses, not the content. When the address expires, that server deletes the address and everything stored for it. Nothing links a demo address to you: we keep no account, no name and no email address for it.
Requests for a demo address are limited per network address. The count is kept in memory and not written down, though the network address of a refused request can appear in our operational logs.
7. Data retention
We keep operational data only as long as needed to provide the Service and meet legal obligations. When you delete your account, we delete associated data within a reasonable period, except where we must retain limited records by law.
8. Your rights and controls
Depending on where you live, you may have rights to access, correct, export or delete your personal data. You can export your mail from Settings as standard mbox files while your account is open, including during the grace period after a trial or plan ends, and an encrypted backup of your keys at any time. To have your account deleted, or to exercise any other right, contact us.
9. Third parties
We use a small number of processors (for example, payment and infrastructure providers) strictly to operate the Service. They are bound to handle data only on our instructions and cannot access the contents of your encrypted mail.
10. Changes to this policy
We may update this policy as the Service evolves. If we make material changes, we will notify you in the app or by email before they take effect.