All other customer data can be classified as either transient or non-transient and it may either be stored in your location, for example, AWS, or by RudderStack for upto 7 days (or 30 days in case of Enterprise plan).
RudderStack’s data retention policy defines data as they pertain to the primary components of its service - the data plane and control plane.
Transient customer data
Transient customer data can be defined as all in-transit data, that is, stored for less than 3 hours, as an essential part of delivering the RudderStack product experience. This data includes:
Control plane: The in-transit data captured in the Live Events tab of the RudderStack dashboard.
Non-transient customer data
Non-transient customer data can be defined as data that can persist for more than 3 hours only if configured by the RudderStack user. This includes:
Data plane: This includes processing errors and gateway dumps.
Processing errors: Events 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 3 hours of retry attempts.
Gateway dumps: Raw data for every successfully-ingested event.
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.
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:
RudderStack’s data privacy options let you safeguard your customers’ privacy by controlling who has access to the raw event data containing PII(Personally Identifiable Information). You can allow anyone on your team to access the PII or restrict access only to a select list of members.
Only members with PII permissions can view the customers’ PII in the Live Events and errors logs in your destination’sEvents tab:
To set the PII permissions, follow these steps:
In your RudderStack dashboard, go to Settings > Workspace > Data Management and scroll down to the Data Privacy section.
Under Who can view restricted data?, select the appropriate option:
Anyone on your team: All the members in your workspace can view the raw event data containing PII.
Only people you select: Only specific members with access can view the raw data.
To allow specific members of your team to edit the object, click Only people you select, followed by Add member.
Finally, select the workspace members from the drop-down and click Add Members:
If the admins are removed from the access list, RudderStack will restrict them from viewing the PII.
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.