Data retention
Knock applies a retention policy to some of the data within your account. Once data exceeds its retention period, it will no longer be accessible in the Knock Dashboard, the Management API, or the public API. Knock will eventually prune data that has aged out of its retention period.
Data retention policies
Some Knock data is subject to a retention policy based on your account plan. These policies are:
- Enterprise plans: 90 days
- All other plans: 30 days
Knock applies this plan-based retention policy to the following data:
- Audit logs
- Message log data
- Outbound webhook delivery logs
- Source event and action logs
- Workflow run logs
Additionally, Knock applies a universal, 30-day retention policy to the following data:
Message log data retention details
Message log data subject to your account's retention policy includes both the message log itself and associated metadata, including:
- Message contents
- Message events
- Delivery logs
- Activities
However, this does not mean that the associated notification has been completely removed from Knock's systems. Your recipients can still interact with these older notifications, and you can still take some specific actions on them.
- In-app feed notifications are available indefinitely. Even after your message log data has expired, you can still fetch the associated
FeedItemdata from the Show feed endpoint to deliver in-app notifications to your recipients. - Message status updates are allowed indefinitely. You can still call the Update message status, Remove message status, and Batch change message status endpoints to update the status of an older message, either directly or via a Knock SDK. These status updates will still generate new message events and trigger your outbound webhooks, even though you will not be able to view the message in the Knock Dashboard any longer.
- Tracking behavior will persist. Your recipients can still click tracked-links, and Knock will still register read events for your notifications using email-open tracking.