Email data retention

Kit retains email stats — opens, clicks, sends, bounces, unsubscribes, and complaints — for a rolling window across broadcasts and sequences. This policy took effect on October 15, 2026, as part of a move to a faster, more modern way to store and serve email data. This applies to email stats only. Subscriber records, tags, custom fields, purchases, and broadcast content are not affected. Broadcasts can always be viewed and duplicated, no matter how old; what changes is how long the performance stats behind them stay accessible.

​

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. Stats for emails sent more than 3 years ago stop updating: they reflect the email’s performance as of its three-year mark. Stats for emails sent more than 5 years ago are archived and are no longer returned. 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 are archived and are not available via the API, Kit MCP, or CSV export. If a creator needs them, they can contact Kit support, who will do their best to retrieve the data but cannot guarantee it. Requests need to come from the account owner, so apps should direct creators to support rather than contacting support on their behalf.