How Minket handles keys, content and access
Nothing about your mail is kept longer than it needs to be, or shown to anyone it does not belong to.
Keys
Copy this key now
minket_live_<shown once>
| Name | Key | Scope |
|---|---|---|
| ci-deploy | minket_live, k9Qz | sending_access |
Content is gone after 30 days
Each kind of data has its own clock, and nothing outlives it.
| What | Kept |
|---|---|
| Bodies, attachments, received mail | 30 days |
| Subjects and custom headers | 30 days |
| Addresses and events | 13 months |
| Request logs, never a body | 30 days |
A key is shown once
Minket keeps only its SHA-256 hash, so no one can read it back.
- Shown
- the prefix and the last four characters
- Revoked
- at once, in the console or the API
Every secret encrypted, none of it logged
Encrypted at rest and never written to a log.
- Webhook signing secrets
- Mailbox tokens and passwords
- SMTP passwords and OAuth client secrets
Another organization's data answers 404
To your keys and your people, anything that is not yours does not exist.
GET /v1/emails/019a2b3c-4d5e-7f60-8a9b-0c1d2e3f4a5e 404 not_found
Only people you invite reach the console
Each has a role, checked on every request, and every change lands in the audit log.
- Invitedan admin added a developer09:02
- Rotateda webhook's signing secret11:40
- Revokedthe key ci-deploy16:15
Roles, keys and the team
Questions
Are the links in my mail signed?
Yes: unsubscribe, preference and tracking links carry signed tokens that name an id, never an address or a URL.
Can a webhook reach my network?
No. Private, loopback and cloud metadata addresses are refused, after every redirect too.
Are backups kept longer?
Nightly exports expire 30 days after they are written.