Skip to content

Sentry & Consent

Last updated: February 9, 2026

This page explains how Sentry is used, which consents exist, and how you can control them.

What Sentry is

Sentry is a technical monitoring tool used for error diagnostics and stability.

  • Optional error reporting.
  • Optional session replay, controlled separately.
  • Optional feedback widget for issue reports.

Important

Sentry is only active with your explicit consent (opt-in).

Where Sentry is active

  • Not on public start/login paths.
  • On authenticated app areas when consent is granted.

Consent types

1) Error reporting (Sentry)

  • Controls technical error telemetry.
  • Without this consent, Sentry remains disabled.

2) Session replay (optional, separate)

  • Only relevant when error reporting is enabled.
  • Can be toggled independently as an additional option.

How opt-in works

  1. After login, a Sentry consent dialog is shown (if no decision exists yet).
  2. You can enable or decline.
  3. You can optionally enable replay at the same time.
  4. Your choice is applied immediately.

How opt-out works

  1. Open Account > Privacy and disable error reporting.
  2. This disables Sentry for your session.
  3. Replay can also be disabled there.

Without consent

If you do not opt in, error telemetry stays off. Core app functionality is unchanged.

Privacy and technical boundaries

  • Sentry runs with default PII sending disabled.
  • Server/Edge events without consent cookie are dropped.
  • Request data is minimized (for example URL reduced to path; sensitive headers removed).
  • Replay is masked (text inputs/on-screen content/media are protected).

Where your choice is stored

  • evk-sentry-consent (error reporting consent)
  • evk-sentry-replay-consent (replay consent)
  • Also mirrored in session storage for runtime behavior.

For more details, see Privacy settings and the Privacy Policy.

Contact support

Questions about Sentry or consent settings: support@evoklar.de