Retention policy

The number

Message and event history is kept for the days on your plan, then deleted. Starter keeps 30, Pro 90, Scale 180; Free keeps 7 days — that is also the fallback the purge job uses when a plan is unknown. This page reads that number from the same constant the purge job falls back to, and /retention.json publishes it in machine-readable form.

What is covered

Deleted on your plan's window today, on every account, with no switch to turn on:

• Messages: envelope, headers, subject and body.
• Message events: accepted, delivered, bounced, complained, and opens and clicks if you turned tracking on.
• Webhook deliveries: the signed body, each attempt, and a delivery that has finished failing. One that is still waiting to be tried again stays until it finishes.
• API request logs, kept 30 days on every plan.

Counted on the same schedule, but not yet deleted on it — every run counts these rows, and we turn deletion on for them once the backup and restore process behind it is in place:

• Mail sent to your own domain — not open to customers yet, so nothing is stored under this category today; once it opens, it will follow the same counted-not-yet-deleted rule as the rest of this list.
• Business events (the kind an automation listens for) and the automation runs they started.
• Agent actions waiting on an approval, once they are no longer pending.
• Notifications, once you have read or resolved them.
• A contact you deleted: the address stays, hidden from every ordinary list, only so an unsubscribe link already sent keeps working; it is due to go 60 days after the delete.

/retention.json publishes both lists as objects, the same list the purge job walks.

What a purge does

It deletes the rows. Messages and their events live in one store, nothing is copied to a colder store first, and there is no archive to request data back from afterwards. The Metrics screen counts from those same events, so its figures for a purged period go with them.

What is kept longer, and why

• The audit log of account changes stays while the account is open, and is due to go only once a closed account itself is removed (see "Closing the account" below) — it is not on the message-retention window.
• Suppressions are kept indefinitely. An address that unsubscribed, hard-bounced or complained stays suppressed; forgetting it after ninety days would mean mailing it again, which is the opposite of what the person asked for.
• Account records — who the account is, what plan, which domains — live as long as the account does.

Before it goes

GET /account/export returns a zip of every store on the account: the messages still inside the window with their full body, delivery events, mail you received, contacts with their properties, templates, webhooks, this account's own suppressions, domains, support requests, the audit log and the team, with a manifest that counts every file. Export before you need it, not after.

Closing the account

DELETE /account stops your keys immediately. Messages and their events keep ageing out on your plan's window exactly as above, whether the account is open or closed. Everything else on a closed account — contacts, templates, webhooks, the team, the audit log — is not yet removed on a schedule: we are installing the backups that make that safe to automate first (see "What is covered" above). Until it ships, write to hello@agentisend.com after closing and tell us to remove the rest; we do it by hand and confirm it. A single message on an account that stays open is yours to remove yourself, any time: DELETE /emails/:id (a message still on its way to being sent is cancelled first).

If you are a recipient rather than a customer, the unsubscribe link in the message stops that sender. To have your address removed from our systems, write to hello@agentisend.com; we tell the sender, who decides about their own records, and we delete or redact the copies we hold within 30 days and confirm.