Account data
We store your login email, a one-way password hash, account timestamps and short-lived security tokens. Passwords are never stored in plain text. Login sessions expire after seven days.
Privacy and data
A clear view of what MXDuck keeps.
MXDuck exists to reduce how often you expose your everyday email. This page explains the data needed to make that work during the private beta.
Incoming mail
We store the original message, sender, recipient, subject, plain-text body and attachments so you can read and download them. The inbox displays plain text rather than remote HTML content.
Address lifetimes
Expiry stops an address receiving new mail; it does not currently erase messages already received. During the beta, saved mail remains available while the account exists. We will explain any future retention schedule before applying it.
Service limits
- 10 MiB maximum per incoming message
- 500 messages per address
- 250 MiB stored mail per workspace
- 50 active addresses per workspace
New mail is rejected when a limit is reached. MXDuck does not silently delete existing mail to make room.
Infrastructure
MXDuck runs on Cloudflare Workers, D1 and R2. Essential infrastructure logs may include request metadata such as IP address, browser details and timestamps for reliability and abuse prevention.
What we do not do
MXDuck does not sell account or message data, use message contents for advertising, load remote tracking pixels in the inbox, or forward incoming messages to your everyday address.
Account security
Login-email verification and one-hour password reset links use single-use, hashed tokens. Resetting a password invalidates existing sessions.
Beta changes
This is a developing private beta. Material changes to storage, retention or data use will be reflected here. Last updated 1 November 2026.