Set up your bannerConfigure Your ToolsMonitoring and Performance

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.

  1. Configure the third-party service.
  2. Map the selected configuration in the Consenter Manager.
  3. 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.

ConfigurationSummary
Configuration A — Lower riskError monitoring only; no Session Replay.
Configuration B — Medium riskSession Replay with default masking and blocking, after Consenter consent.
Configuration C — Higher riskSession 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 areaWhere to configure itConfiguration A — Lower riskConfiguration B — Medium riskConfiguration C — Higher risk
1Processing purposesOperator decisionImprove the serviceImprove the serviceImprove the service
2Session ReplaySentry.replayIntegrationNot addedAddedAdded
3MaskingmaskAllText, maskAllInputs, blockAllMedia—Defaults (true)maskAllText: false, blockAllMedia: false
4LoadingFront-endPer DPO assessmentAfter Consenter consentAfter Consenter consent

Step 2 — Map the configuration in the Consenter Manager

Processing location. Sentry is a US enterprise; list the United States.

Consenter Manager fieldConfiguration A — Lower riskConfiguration B — Medium riskConfiguration C — Higher risk
Entry neededPer DPO assessment (⚠)YesYes
Processing purposesImprove the serviceImprove the serviceImprove the service
Tracking methodNo trackingFirst party tracking (single session)First party tracking (single session)
IdentifierIP addressIP addressIP address
Data categoriesDevice characteristics, IP addressDevice characteristics, IP address, Browsing and interaction dataDevice characteristics, IP address, Browsing and interaction data, User-provided data
Legal role of data recipientProcessorProcessorProcessor
Personalisation modelNo personalisationNo personalisationNo personalisation
Maximum storage durationPer Sentry data retentionPer Sentry data retentionPer Sentry data retention
Processing locationPer account data region / United StatesPer account data region / United StatesPer 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

On this page