Solution skill
Workflow: the three-layer data scrubbing stack
Complete solution
Shows how to fix workflow: the three-layer data scrubbing stack. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
Use Safe Fields for the rare key that must stay (a field literally named token that holds a non-secret), and additional sensitive fields for your own keynames.
When to use
You are seeing this: No single layer catches everything. Use this skill when you run into "Workflow: the three-layer data scrubbing stack".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.
No single layer catches everything. Scrub in the SDK, on the server, and with custom rules, in that order of preference.
Layer 1: beforeSend in the SDK
Scrub before data leaves the host. This is the only layer that guarantees sensitive data never reaches Sentry's servers:
Sentry.init({
beforeSend(event) {
if (event.user) delete event.user.email;
return event;
},
});Use it for the secrets you know about: API keys in headers, tokens in query strings, PII in user context. Keep the callback fast and total; a throwing beforeSend drops the event.
Layer 2: server-side defaults
Server-side scrubbing is on by default and catches credit-card-shaped values plus keynames like password, secret, api_key, token, and bearer. Leave it on. Configure at the org level for consistency, knowing org settings override project settings. Use Safe Fields for the rare key that must stay (a field literally named token that holds a non-secret), and additional sensitive fields for your own keynames.
Layer 3: advanced rules
For patterns only your app produces, write Advanced Data Scrubbing rules. Each rule has a method (Remove, Mask, Hash, Replace), a data type (what to look for, including custom regex), and a source (which part of the event to search):
[Mask] [custom regex for internal account IDs] from [extra.account_id]Sources let you test conservatively: scope a rule to one event attribute first, then widen. Note the precedence: advanced rules apply even to fields in Safe Fields.
Rollout order
- beforeSend for known secrets (deploy with the app).
- Server-side defaults review: confirm they are on, add your keynames.
- Advanced rules for the leftovers, tested narrow first.
Verify
Send test events containing each secret type through all three layers and confirm redaction in the stored event. Re-audit quarterly: new features add new secret shapes, and scrubbing rules do not write themselves.
Evidence
Researched against live Sentry docs 2026-09-26. Advanced Data Scrubbing (docs.sentry.io/security-legal-pii/scrubbing/advanced-datascrubbing/): methods Remove/Mask/Hash/Replace, sources restrict which event parts rules touch, advanced rules take precedence over other server-side settings including Safe Fields. Server-Side Scrubbing (docs.sentry.io/security-legal-pii/scrubbing/server-side-scrubbing/): enabled by default, org-wide or per-project, scrubs credit cards and keynames like password/secret/api_key/token/bearer, org settings override project settings. The JS filtering page (docs.sentry.io/platforms/javascript/configuration/filtering/) documents beforeSend.
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_2OZQgy7mHdBi-QZlsIgMMA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Workflow: the three-layer data scrubbing stack <span>— Vectle</span></a>