Sentry
How to configure Sentry at different risk levels and map it in the Consenter Manager.
This work is licensed under CC BY-SA 4.0
Typical processing purposes: Improve the service
Overview
This guide explains how to implement different privacy configurations for the Sentry browser SDK (error monitoring and Session Replay) and how to reflect them in the Consenter Manager.
- Configure the third-party service.
- Map the selected configuration in the Consenter Manager.
- Update your privacy policy to reflect the actual implementation.
The configurations are comparative examples, not guarantees of legal compliance. Verify that the guide matches your product edition, implementation, and current provider documentation.
At a glance
Scope. Sentry JavaScript browser SDK.
What the service does in this scope. Session Replay records user sessions; by default it masks all text with * and blocks media elements on the client before sending. maskAllText, maskAllInputs and blockAllMedia default to true. Disabling masking is only intended for sites with no sensitive data.
Configurations included.
| Configuration | Summary |
|---|---|
| Configuration A — Lower risk | Error monitoring only; no Session Replay. |
| Configuration B — Medium risk | Session Replay with default masking and blocking, after Consenter consent. |
| Configuration C — Higher risk | Session Replay with maskAllText: false / blockAllMedia: false, after consent. |
⚠ Recommendation. Whether error monitoring in A can run without consent depends on what data your events carry. Have your DPO confirm the legal basis before running A without a consent entry.
Step 1 — Configure Sentry
| # | Configuration area | Where to configure it | Configuration A — Lower risk | Configuration B — Medium risk | Configuration C — Higher risk |
|---|---|---|---|---|---|
| 1 | Processing purposes | Operator decision | Improve the service | Improve the service | Improve the service |
| 2 | Session Replay | Sentry.replayIntegration | Not added | Added | Added |
| 3 | Masking | maskAllText, maskAllInputs, blockAllMedia | — | Defaults (true) | maskAllText: false, blockAllMedia: false |
| 4 | Loading | Front-end | Per DPO assessment | After Consenter consent | After Consenter consent |
Step 2 — Map the configuration in the Consenter Manager
Processing location. Sentry is a US enterprise; list the United States.
| Consenter Manager field | Configuration A — Lower risk | Configuration B — Medium risk | Configuration C — Higher risk |
|---|---|---|---|
| Entry needed | Per DPO assessment (⚠) | Yes | Yes |
| Processing purposes | Improve the service | Improve the service | Improve the service |
| Tracking method | No tracking | First party tracking (single session) | First party tracking (single session) |
| Identifier | IP address | IP address | IP address |
| Data categories | Device characteristics, IP address | Device characteristics, IP address, Browsing and interaction data | Device characteristics, IP address, Browsing and interaction data, User-provided data |
| Legal role of data recipient | Processor | Processor | Processor |
| Personalisation model | No personalisation | No personalisation | No personalisation |
| Maximum storage duration | Per Sentry data retention | Per Sentry data retention | Per Sentry data retention |
| Processing location | Per account data region / United States | Per account data region / United States | Per account data region / United States |
How is this guide?
Shape Consenter Together
Consenter is built on an open and participatory process that grows through community collaboration. Whether you share feedback, improve the documentation, or contribute to the Risk Configuration Guides or Technical Integration Guides, your expertise helps make Consenter more privacy-friendly, interoperable, and useful for everyone—including your own users and services: Get finally your benefits and control the risks when sharing personal data.
Need Help?
Last updated on