Data retention
How long Intempt keeps your data, what happens to backups and deleted projects, and how retention interacts with deletion requests.
Overview
Intempt keeps data no longer than it needs to.
Data is retained for a maximum of two years, after which it is deleted. Two years is the ceiling set by the Data Processing Addendum, not an entitlement. Within it, a paid organization chooses how long events stay.
Retention is applied automatically. There's nothing to schedule and no job to run.
Retention levels
Paid organizations pick one retention window. It applies to every project in the organization.
| Level | Window | |
|---|---|---|
| Weekly | 7 days | |
| Monthly | 30 days | |
| Quarterly | 90 days | |
| Standard | 13 months | Default |
| Compliance | 24 months |
Standard is 13 months rather than 12 so a year-over-year comparison has a prior period to compare against.
A shorter window is a volume choice, not a smaller product. At 7 days you hold a fraction of what you send, which is how a high-volume sender keeps retention cost flat as volume grows. A shorter window does mean a shorter reporting range: a segment, journey wait, or attribute-history lookup can only reach as far back as the window.
📘 Good to know
Retention is billed on what you are holding, not on what you send. A 13-month window holds thirteen times what a 30-day window holds, at one rate for every level, so the window does the pricing. Changing level takes effect from the next billing cycle.
Free tier
The Free tier holds data for 30 days, on the free event volume of 1,000,000 events a month and nothing beyond it. See Project Limits for every free cap.
The free window is not a purchasable level and does not appear in the table above. It also does not undercut the paid ladder: free retention is capped by the free event volume, while a paid window holds any volume.
Backups
Intempt keeps backups of customer data for 14 days, then deletes them as part of standard lifecycle procedures.
📘 Good to know
Deleting data doesn't reach into backups, and backups aren't edited to remove individual records. A backup ages out on its own within 14 days. If you're answering a deletion request from one of your users, that's the accurate thing to tell them: the live record is gone immediately, and any backup copy expires within two weeks.
Deleted projects
Deleting or resetting a project is recoverable for 30 days. During that window the data still exists and support can restore it. After 30 days it's permanently deleted and can't be recovered.
A separate 30-day window applies when an agreement ends or an organization is deleted: data stays in active systems for 30 days and is then deleted. See the Data Processing Addendum.
How retention interacts with deletion requests
| Erasure request | Removes that user's data immediately, ahead of any retention window |
| Retention expiry | Removes data at the two-year maximum regardless of requests |
| Backups | Expire within 14 days in both cases |
| Project deletion | Permanent after the 30-day recovery window |
Retention is not a substitute for handling deletion requests. A user who asks to be forgotten shouldn't wait for a retention window to pass. See Managing DSR.
Use cases
- Answer a procurement question about how long a vendor holds data.
- Confirm a reporting window is available before committing to a year-over-year analysis.
- Tell a user asking to be deleted exactly when the last backup copy expires.
- Recover a project a teammate deleted by mistake, within 30 days.
- Explain to an auditor why deletion requests are handled separately from retention.
- Check what happens to your data after a subscription ends, before renewal discussions.
Where to go next
Blocking unwanted traffic
Keeping bots, crawlers, and your own team's testing out of your analytics: what Intempt filters automatically, and how to exclude internal traffic yourself.
Privacy Settings Reference
Field reference for the Privacy tab on a user's profile: consent status, consent categories, and legitimate interest records.