Manage your event data with our data retention options.
This guide explains RudderStack’s data retention policy and your options for opting in or out of data storage.
RudderStack’s default policy is not to store your event data, but there are times when it may be useful for you to access or replay recent event data. Refer to the Event Replay guide for more details on this feature.
RudderStack provides 3 options for retaining your event data:
Choose one of the 3 data storage options in the Data retention section:
The following sections explain the data retention options in detail.
1. Do not store event data
If you choose this option, RudderStack will not store any of your event data. This is the default setting.
2. Store event data in your own cloud storage (Recommended)
This is the recommended event storage option, and available in the Starter, Growth, and Enterprise plans. Selecting this option will bring up a modal allowing you to connect a storage bucket with your RudderStack data.
RudderStack supports storage via AWS, GCS, Azure, and MinIO if you select this option.
When connecting your cloud storage provider to RudderStack, you will first need to create a storage bucket and configure the credentials for RudderStack to access the datastore. Follow the steps listed below depending on your cloud provider:
Connect your storage provider in the RudderStack dashboard.
3. Store event data in RudderStack cloud storage
Choosing this option allows RudderStack to store and delete your event data on a rolling 30-day basis.
Sample event data
When the Sample event data setting is enabled, RudderStack stores and deletes sample events and responses on a rolling 30-day basis. This data may be helpful for debugging your events.
RudderStack does not consider the event name or event type to be Personally Identifiable Information (PII).
Based on your plan, RudderStack provides different options for event storage, giving you the ability to enable or disable retention for the following kinds of data:
Sample events and responses: As mentioned above, RudderStack will store and delete sample events and responses on a rolling 30-day basis.
Processing errors: These correspond to the events that are rejected at various stages of the data pipeline, including errors from user transformation, destination transformation (internal to RudderStack), and events rejected by the destination after three hours of retry attempts.
Gateway dumps: These correspond to the raw data for every successfully-ingested event.
cookies, the cookies that are categorized as necessary are stored on your browser as they are as
for the working of basic functionalities of the website. We also use third-party cookies that
analyze and understand how you use this website. These cookies will be stored in your browser
consent. You also have the option to opt-out of these cookies. But opting out of some of these
have an effect on your browsing experience.
Necessary cookies are absolutely essential for the website to function properly. This
category only includes cookies that ensures basic functionalities and security
features of the website. These cookies do not store any personal information.
learn more about cookies and why we use them, visit our cookie
policy. We'll assume you're ok with this, but you can opt-out if you wish Cookie Settings.