Encryption
In transit
The dashboard, the REST API and the MCP server are served only over HTTPS. When we deliver your mail to another provider, we encrypt the connection with TLS whenever the receiving server supports it, and we require it for any domain that publishes an MTA-STS or DANE policy.
At rest
Credentials are encrypted with AES-256-GCM before they are stored: mailbox passwords, DKIM signing keys, OAuth refresh tokens and the DNS provider tokens you connect. We use two separate keys with different reach. The key the dashboard can use only opens mailbox passwords, which you need to export to other tools. The signing keys and tokens are encrypted with a key that only our back-end mail workers hold, so the dashboard has no way to read them.
The message bodies we store for your inbox are encrypted with a key derived for your account alone, and each encrypted body is bound to the record it belongs to. A body copied to another account or another record fails to decrypt instead of being shown.
Your account
- Sign in with email and password, or with Google. Sessions are kept in HTTP-only cookies, which scripts running in the page cannot read.
- Turn on two-factor authentication with any authenticator app from your account settings.
- Invite your team with one of three roles: owner, admin or member. Each workspace’s data stays inside that workspace.
- Every export of mailbox credentials and list results is recorded with who made it and when, and listed on your Exports page.
Keeping accounts apart
EmailPal is a shared platform, so separation between customers is enforced in the database itself: row-level security is switched on for every table, and each request can only reach the rows of the workspaces its user belongs to. On top of that, stored mail is encrypted per account, so even if a bug handed one account’s stored messages to another, they could not be decrypted.
API, MCP and webhooks
- API keys are shown to you once. We keep only a SHA-256 hash of each key, so a copy of our database would not contain a working key. Keys carry read, write or admin scope and can be revoked at any time.
- AI assistants such as Claude, ChatGPT and Cursor can connect to the MCP server through OAuth: you approve access in your browser instead of pasting a key into the assistant.
- Webhooks are signed with HMAC-SHA256. Each delivery carries an
EmailPal-Signatureheader with a timestamp, so you can check that it came from us and reject old payloads that are replayed. The signing secret is shown once, when you create the endpoint. See the API documentation for verification code.
Infrastructure and backups
Our infrastructure runs in the United States and the European Union. The main database is a managed PostgreSQL service in the United States, with daily backups kept for seven days. Mail is sent and received by mail servers we operate ourselves. Their data is backed up every night to separate off-site storage, encrypted before it leaves the server, and we keep a written, tested procedure for restoring a server from those backups.
Our analytics store records delivery events with recipient addresses replaced by a one-way hash, so the event history used for reporting is not a copy of anyone’s contact list.
Sending safely
Protecting your domains’ reputation is part of security too.
- Every sending domain gets its own 2048-bit DKIM key. Where we manage a domain’s DNS, we publish its SPF, DKIM and DMARC records for you.
- Cold sending pauses automatically when a mailbox reaches a 5% hard-bounce rate, before a bad list can damage a domain.
- Unsubscribes are honoured automatically: a lead who opts out is not mailed again from your account. A person who asks to be removed from our lead data is suppressed across the whole platform.
- A sample of outbound mail is scanned automatically for violations of our acceptable use policy. Abuse reports go to abuse@emailpal.io.
Your data
How we collect, use and share personal data, for customers and for the people who receive mail sent through EmailPal, is set out in our privacy policy. Questions about your data go to privacy@emailpal.io.
Reporting a vulnerability
If you think you have found a security problem in EmailPal, please email hello@emailpal.iowith “Security report” in the subject. Tell us what you found, how to reproduce it and what an attacker could do with it. A person on our team reads every report.
While you investigate, please:
- use only accounts you own, and stop as soon as you can see another customer’s data;
- not send mail to people who have not agreed to it, or test against our deliverability;
- not run denial-of-service tests or automated scans that degrade the service;
- give us a reasonable chance to fix the problem before telling anyone else.
We will not take action against anyone who reports a problem in good faith and follows these guidelines.