Email data retention

Starting October 15, 2026, Kit is changing how far back email stats — opens, clicks, sends, bounces, and unsubscribes — are directly accessible across broadcasts and sequences. We’re investing in a faster, more modern way to store and serve this data, which lets us build more robust reporting tools going forward. This applies to email stats only. Subscriber records, tags, custom fields, purchases, and broadcast content are not affected. Nothing is deleted — a creator’s data remains theirs; what changes is how older stats are accessed.

​

What the API returns

The API returns email stats for the last 5 years (60 months): Note that the Kit app UI shows the last 3 years, so the API, Kit MCP, and exports give you access to a longer history (5 years) than creators see in the app. How the 5-year window surfaces varies by endpoint:

• Requesting stats for a specific broadcast sent before the window returns a 400 error.
• Explicit date-range parameters that fall outside the window return a 400 error indicating the earliest available date.
• List and filter endpoints omit out-of-window broadcasts from results, or clamp date ranges to the window.

​

Affected endpoints

• Get stats for a broadcast — returns a 400 error for broadcasts sent before the window
• Get stats for a list of broadcasts — broadcasts sent before the window are omitted from results
• Get link clicks for a broadcast — click data for broadcasts older than the window is no longer available
• List stats for a subscriber — date params are clamped to the window; dates outside it return a 400 error
• Filter subscribers by engagement — engagement-condition date bounds are clamped to the window; a stats include range outside it returns a 400 error

​

Need data older than 5 years?

Stats older than 5 years will be archived and will no longer be accessible. If a creator needs their email stats that are older than 5 years, you have until October 15th, 2026 to export them directly from Kit or contact Kit support. Requests need to come from the account owner, so apps should direct creators to support rather than contacting support on their behalf.