Skip to main content

Why didn’t Additional Sensitive Fields redact my data?

Issue

I want to know why adding fields (for example email) under Additional Sensitive Fields still leaves that data visible in events, and what to do next.

Applies To

  • All SaaS Customers and Self-Hosted Users

  • Data Scrubbing

  • Security & PrivacyAll customers

Resolution

Additional Sensitive Fields only scrub certain parts of an event (see Event PII Fields). Values that appear in exception messages, log messages, breadcrumbs, or other parts of the event often require a more specific rule.

Use Advanced Data Scrubbing

  1. Go to Organization Settings → Security & Privacy → Advanced Data Scrubbing, or the same section under the project.

  2. Click Add Rule.

  3. Choose a Method (Remove, Mask, Hash, or Replace).

  4. For emails, set Data Type to Email Addresses (or use a custom regex).

  5. Set Source to where the value appears (for example, $error.value, $message, or extra.**). You can paste an event ID above Source to automatically complete the fields based on a real event.

  6. Save the rule. Rules apply to new events going forward — events that are already stored remain unchanged.

For more details on the available rules and selectors, see Advanced Data Scrubbing.

If it still must not leave the client

Scrub the data in the SDK using beforeSend (or the platform equivalent), or use Relay. For an overview, see What are Sentry's data scrubbing options?

Did this answer your question?