We limit what a fooled agent can do.
An agent reads mail from strangers, and no filter can promise it won't be fooled. So the server checks what any one agent can reach on every call, and the big decisions stay with a person.
What this doesn't do.
You should know where the edges are before you hand an agent an inbox.
Drin Airlock doesn't catch everything.
An approved wake keeps firing.
An app's key doesn't wait.
An open desk doesn't wait either.
Your agent's other tools are yours.
The rest of the locks.
The plain things a mail provider should get right.
Keys
We keep a hash, a prefix and the last four characters. A key can't be read back.
Set 1 to 3,650 days. After that, 401 key_expired.
A key can only make keys inside its own scopes, project, inboxes and lifetime.
A project key works only in its project. Other projects' ids answer 404.
Data
Wake-target tokens and integration OAuth tokens are sealed with AES-256-GCM.
The audit log keeps who did what for 90 days. The request log keeps writes and failed calls for 14.
One call exports the workspace as a JSON file, never secrets.
Closing revokes every key at once. Records are purged 30 days later.
SMTP and IMAP logins need TLS. A login without it is refused.
3 failed logins a connection, 10 an address per 10 minutes.
SPF, DKIM and DMARC on every message. Mail failing a p=reject policy is refused. Through the API, MCP and wakes, every message says whether its sender was verified.
Every delivery is signed, so your app can check it came from Drin.
Found something? Tell us first.
We'll acknowledge your report and keep you updated, and we won't pursue good-faith researchers.
Report a problem
Email security@drin.run with details and steps to reproduce. Machine-readable at /.well-known/security.txt. For spam or abuse from mail sent through Drin, write to abuse@drin.run.
What we can't show you yet
We hold no security certifications today. When that changes, this page will say so. Who handles your data is in our Privacy Policy.