Privacy Policy
Last updated November 13, 2026
GhstMail forwards mail to you without reading it or storing it. To make that work we keep your email address, your aliases, and the address of whoever wrote to each alias, so your replies can find them. Our servers keep short-lived logs for running the service. We don't run analytics, ads or trackers, and we never sell or share your data.
What GhstMail does
GhstMail gives you email aliases: addresses you can hand out instead of your real one. Mail sent to an alias is forwarded to your real inbox, and when you reply, the reply goes out from the alias. The people you write to only ever see the alias.
What we store
Your account
- Email address: your login, and where your aliases forward to.
- Password, if you set one. It is stored only as a hash: scrypt, or bcrypt for passwords set before November 2026. We can't see your password.
- Google or GitHub sign-in, if you use it. The provider tells us your email address and confirms it's yours. We ask for nothing else, and we discard the name and photo the provider sends anyway. We keep the provider's ID for your account so it signs you in next time.
- Sign-in sessions: a session record with an expiry date (7 days), so it can be ended when you sign out or reset your password. We don't record your IP address or browser with it. It's held in a cookie on
api.ghstmail.space, used only to keep you signed in. - Email confirmation: whether you've confirmed your address, plus single-use codes for confirming it or resetting your password. Those codes expire within an hour.
Your aliases
- Each alias's address, label, on/off status, creation date, expiry, and running counts of messages received and forwarded.
- Filter rules: the domains you block or allow.
What makes replies work
- The sender's address for each message forwarded to you, so your reply can reach them without revealing your address. Not the message, not the subject.
- The
Message-IDof forwarded mail, an opaque identifier, so replies thread correctly in your mail client. - Both are kept while the alias exists and deleted when you delete it.
If you use the API
- API keys: the name, the permissions you granted, a short prefix so you can tell keys apart, and a SHA-256 hash. Never the key itself, which is why it's shown only once.
- Sending records: for mail sent through the API, which alias sent it, the recipient's domain (never their full address), the number of recipients and the time. This enforces the sending quota.
- Idempotency records: the response to a request sent with an
Idempotency-Key, kept 24 hours so a retry doesn't create a duplicate.
What passes through but is never stored
The content of your email: the body, attachments and subject line. A message is processed in memory on our server, forwarded, and discarded. It never touches our database or disk.
Server logs
Like any mail server, ours keeps operational logs so we can fix delivery problems and stop abuse:
- The mail server logs the sender and recipient addresses of each delivery, the IP address of the server that connected, and the results of standard anti-spam checks (SPF, DKIM and reverse DNS).
- The API logs the IP address and path of each request, not what was sent in it.
Logs never contain message content or subject lines. We're adding size limits to our logs, so that old entries are overwritten as new ones arrive.
Backups
We're setting up nightly backups of our database so a failure doesn't lose your aliases. They will stay on our own server and delete themselves after 30 days, so anything you delete from GhstMail will be gone from backups within that time.
What we never collect
- No analytics, tracking pixels, fingerprinting or telemetry, on the website, in the Chrome extension or in the CLI.
- No cookies for tracking or advertising. The only cookie is the sign-in one above.
- No browsing history or web activity.
- The CLI's update check asks the npm registry, not us.
Services we rely on
We don't sell, rent or share your data. Running GhstMail does mean these companies handle traffic on our behalf:
- DigitalOcean hosts our server and database.
- Cloudflare sits in front of
api.ghstmail.space, so it sees API requests in transit. - Vercel hosts this website, so it sees normal web requests to
ghstmail.space. - Google or GitHub, only if you choose to sign in with them.
Forwarded mail is delivered to your own email provider, and your replies to the sender's.
Chrome extension
- Stores your sign-in token in your browser (
chrome.storage.local). - Looks for email fields on pages to show the alias button, without collecting or sending any page content.
- Talks only to
api.ghstmail.space. - Runs no remote code.
Sending from an alias
If you send mail through the API or CLI, it goes out from our server, signed as your alias. The message isn't stored before or after sending; we keep only the sending record described above. Sending needs an API key that you explicitly gave the messages:send permission.
How long we keep things
- Account and aliases
- Until you delete them
- Sender addresses and Message-IDs
- Until the alias is deleted
- Sign-in sessions
- 7 days, sign-out, or a password reset
- Confirmation and reset codes
- 1 hour, or first use
- Idempotency records
- 24 hours
- Server logs
- Size limit being added
- Backups
- 30 days, once nightly backups are running
- Revoked API keys
- Kept and marked revoked, hash only
Your choices
- Delete an alias at any time from the dashboard. Its reply records go with it immediately.
- Delete your account by emailing support@ghstmail.space from your account's address. We delete it, with everything in it, within 7 days. Once backups are running, they age out within 30 days after that.
- Ask what we hold about you by emailing us, and we'll send it to you.
Security
- Passwords are hashed with scrypt, or bcrypt for older ones.
- API keys are stored only as hashes, and carry permissions so a key can do only what you allowed.
- Every connection to the website and API uses TLS, and our mail server accepts encrypted (STARTTLS) connections.
- Forwarded and sent mail is DKIM-signed.
Changes to this policy
When this policy changes, we update the date at the top. If a change lets us keep more about you, we'll email account holders before it takes effect.
Contact
Questions or requests: privacy@ghstmail.space