Trust / Data retention
How long we keep things, and why.
We hold minimal data and keep it only as long as it serves you. Here is the schedule, by data type.
At a glance
How long each kind of data lives.
Last updated 2026-06-22.
| Data type | Retention | Notes |
|---|---|---|
| Client account details | Deleted on offboarding | Account and configuration data is removed when you leave; we do not keep it "just in case." |
| Hosted mailboxes | Deleted on offboarding | The mailbox and its access are removed immediately when you offboard. |
| Mailbox contents | Up to ~1 month | Message storage exists only to run the mailbox while active; residual copies and backups roll off within about a month of deletion. We never read content. |
| Delivery / webhook event data | 2 years | Delivery, bounce, deferral, and suppression events (metadata, not message bodies) are retained for up to two years for reporting and troubleshooting. |
| Message bodies (for delivery) | Not stored | We do not store message bodies for delivery; they pass through and are not retained. |
| Suppression entries | Retained while needed | Unsubscribes, complaints, and hard bounces are kept as long as needed to keep honoring them, which protects you and the recipient. |
| Payments, invoicing, banking | Held by providers | Stored by Stripe, Intuit QuickBooks, and Mercury under their terms and statutory accounting requirements; we do not separately store card data. |
Principles
What this reflects.
The shape of this schedule is deliberate: delete what we do not need, keep what protects you. Mailboxes and account data go when you go. Message content is never read and is not kept beyond running the mailbox. Delivery metadata sticks around long enough to be useful for reporting and disputes, then expires. Suppression data is the one thing we keep deliberately, because forgetting an unsubscribe or a complaint would harm both you and the recipient.
You remain the controller of your data. On request we will export or delete your data per your terms, and we can confirm deletion. If your review needs specific retention or deletion commitments in writing, those live in an Order or SOW. See also sub-processors and the Privacy Policy.
Need a retention commitment in writing?
Tell us what your policy or regulator requires. We will tell you plainly what we can sign.