sentry-data-handling

# Sentry Data Handling Configure PII scrubbing, GDPR compliance, data retention, and audit controls for Sentry. This skill covers client-side filtering with `beforeSend`, server-side scrubbing rules, data subject erasure via API, and SOC 2 compliance patterns. ## Overview Sentry captures error context that often contains personally identifiable information (PII) — emails in stack traces, credit card numbers in request bodies, IP addresses in headers. Production deployments must scrub this data at two layers: client-side via `beforeSend` hooks (before data leaves the application) and server-side via Sentry's built-in Data Scrubber (defense in depth). GDPR requires additional controls: consent-based initialization, data subject deletion endpoints, and a signed Data Processing Agreement. This skill implements all three layers with TypeScript and Python examples, plus verification tests to prove scrubbing works end-to-end. ## Prerequisites - Sentry SDK v8 installed and initialized (`@sentry/node` or `sentry-sdk`) - Sentry project with **Admin** or **Owner** role (required for Security & Privacy settings) - Compliance requirements documented (GDPR, HIPAA, PCI-DSS, or SOC 2) - Auth token with `project:write` and `org:admin` scopes for API operations - Data Processing Agreement signed at https://sentry.io/legal/dpa/ (GDPR requirement) ## Instructions ### Step 1 — Client-Side PII Scrubbing with beforeSend The first defense layer prevents PII from leaving your application. Con...