Data Collected
See what data is collected by the Sentry SDK.
Sentry takes data privacy very seriously and has default settings in place that prioritize data safety, especially when it comes to personally identifiable information (PII) data. When you add the Sentry SDK to your application, you allow it to collect data and send it to Sentry during the runtime of your application.
The category types and amount of data collected vary, depending on the integrations you've enabled in the Sentry SDK. This page lists data categories that the Sentry Android SDK collects.
Many of the categories listed here require you to enable the sendDefaultPii option.
By default, the Sentry SDK doesn't send any HTTP response or request headers.
To start sending HTTP headers, set sendDefaultPii: true.
By default, the Sentry SDK doesn't send cookies. Sentry tries to remove any cookies that contain sensitive information, such as the Session ID and CSRF Token cookies in Django.
If you want to send cookies, set sendDefaultPii: true in the Sentry.init() call. This will send the cookie headers Cookie and Set-Cookie from fetch and XHR requests.
By default, the Sentry SDK doesn't send any information about the logged-in user, such as email address, user ID, or username. Even if enabled, the type of logged-in user information you'll be able to send depends on the integrations you enable in Sentry's SDK. Most integrations won't send any user information. Some will only set the user ID, but there are a few (e.g. User Feedback) that will set the user ID, username, and email address.
To start sending logged-in user information, set sendDefaultPii: true in your Sentry.init({}) config.
By default, the Sentry SDK doesn't send the user's IP address.
To enable sending the user's IP address and infer the location, set sendDefaultPii: true. In some integrations such as handleRequest in Astro, you can send the user's IP address by enabling trackClientIp.
If sending the IP address is enabled we will try to infer the IP address or use the IP address provided by ip_address in Sentry.setUser(). If you set ip_address: null, the IP address won't be inferred.
The full request URL of outgoing and incoming HTTP requests is always sent to Sentry. Depending on your application, this could contain PII data. For example, a URL like /users/1234/details, where 1234 is a user id (which may be considered PII).
The full request query string of outgoing and incoming HTTP requests is always sent to Sentry. Depending on your application, this could contain PII data.
- The type of the request body:
- JSON and HTML Form bodies are sent
- The size of the request body: There's a maxRequestBodySize option that's set to
NONEby default. This means by default no request body is sent to Sentry.
By default, the Sentry SDK doesn't send the content of response bodies. By default, the SDK will send the response body size based on the content-length header.
By default, using the Sentry CLI Wizard will enable uploading source maps to Sentry.
To disable source map upload, see the Source Maps documentation.
By default, the Sentry SDK will not send local variables in the error stack trace in client-side JavaScript SDKs.
By default, the Sentry SDK sends information about the device and runtime to Sentry.
In browser environments, this information is obtained by the User Agent string. The User Agent string contains information about the browser, operating system, and device type.
In server-side environments, the Sentry SDK uses the os module to get information about the operating system and architecture.
By default, the Sentry SDK sends the referrer URL to Sentry. This is the URL of the page that linked to the current page.
By default, our Session Replay SDK masks all text content, images, web views, and user input. This helps ensure that no sensitive data is exposed. You can find more details in the Session Replay documentation.
By default, the Sentry SDK sends JS console logs to Sentry which may contain PII data.
To disable sending console messages, set console: false in your Sentry.breadcrumbsIntegration config, see the Breadcrumbs documentation.
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) or suggesting an update ("yeah, this would be better").