Data retention
Use this page to understand when Lettermint deletes sent email data and analytics data.
Retention periods
Lettermint deletes each item automatically and permanently when its retention period ends.
| Data | Retention period |
|---|---|
| Message content and attachments that Lettermint stored | 28 days after the message is created |
| Recipient addresses, message metadata, and the message events shown in Email Activity and returned by the message endpoints of the Team API | 28 days after the message is created |
| From address and subject in analytics | Until the retention period of the message ends |
| Delivery and engagement events in analytics, and the hourly and daily totals calculated from them | 90 days after the event. Until 8 November 2026, this period is 28 days. |
| Raw tracking signals: exact IP addresses, user agents, and request headers | 28 days. After that, Lettermint keeps only IP hashes and classification data. |
| Webhook delivery logs and payloads | 7 days after the delivery |
A scheduled email is an exception. Lettermint keeps it until it is released for sending, canceled, or its release fails. Its 28 days start at that moment, not when the message is created.
From 8 November 2026, analytics history starts with events from 12 October 2026.
When you delete a team, Lettermint deletes all of its analytics data.
Deleting this data from Lettermint does not remove a delivered email from a recipient's inbox.
You can resend an email only while Lettermint stores its content.
Recipients in analytics
Analytics do not store recipient email addresses. For each recipient, analytics store an HMAC-SHA256 hash of the message ID and the email address, and the domain of the address, such as gmail.com.
Lettermint keeps the secret key for this hash. The hash does not show the address. Lettermint can match a hash to an address that it still holds, for example an address on your suppression list.
Content redaction
Content redaction can prevent Lettermint from retaining supported message content. If your team has access to this setting, configure it on the project or route before sending sensitive email. Metadata, delivery events, and analytics still follow the retention periods above.
Data protection responsibilities
A short retention period can support data-minimization requirements. It does not replace your responsibilities as a data controller. Apply the required retention and deletion rules in your own systems and in every other processor that you use.
The Data Processing Agreement sets out the retention periods for message data and analytics. If your privacy notice or records of processing list how long Lettermint keeps data, include the analytics period.
Contact Lettermint support if a valid request requires deletion before the normal retention period ends.
Limits
- You cannot configure these retention periods.
- A deletion cannot recall email from a recipient.
- Some operational records can be subject to separate legal or security retention requirements.
Next steps
- Security - Review account and team access controls.
- Email activity - Search data that is still within the retention period.
- Routes - Review content-redaction settings.