privacy
Privacy and data protection - GDPR, CCPA, consent. Use when handling user data.
When & Why to Use This Skill
This Claude skill provides a robust framework for privacy and data protection, ensuring compliance with global standards like GDPR and CCPA. It acts as a safety guardrail by auditing user consent mechanisms, preventing PII (Personally Identifiable Information) leaks into logs or third-party tools, and verifying that data deletion requests are properly executed across the entire tech stack. It bridges the gap between legal privacy policies and actual code implementation to maintain user trust.
Use Cases
- Consent Enforcement Audit: Verifying that analytics (PostHog) and marketing tags (GTM) are strictly blocked until the user provides explicit consent.
- PII Leakage Prevention: Scanning application logs, Sentry reports, and observability data to ensure sensitive user information is not being accidentally exposed.
- Data Deletion Integrity: Ensuring that when a user deletes their account, the instruction correctly propagates to all third-party processors and internal databases.
- Policy-to-Code Alignment: Reviewing technical implementations to confirm they accurately reflect the promises made in the organization's public privacy policy.
- GDPR/CCPA Compliance Readiness: Using the driving questions to prepare for data subject access requests (DSAR) and minimize unnecessary data collection.
| name | privacy |
|---|---|
| description | Privacy and data protection - GDPR, CCPA, consent. Use when handling user data. |
Privacy Guideline
Tech Stack
- Analytics: PostHog
- Email: Resend
- Tag Management: GTM (marketing only)
- Observability: Sentry
Non-Negotiables
- Analytics and marketing must not fire before user consent
- PII must not leak into logs, Sentry, PostHog, or third-party services
- Account deletion must propagate to all third-party processors
- Marketing tags (GTM, Google Ads) must not load without consent
- Conversion tracking must be server-truth aligned, idempotent, and deduplicated
Context
Privacy isn't just compliance — it's trust. Users share data expecting it to be handled responsibly. Every log line, every analytics event, every third-party integration is a potential privacy leak.
The review should verify that actual behavior matches stated policy. If the privacy policy says "we don't track without consent," does the code actually enforce that? Mismatches are not just bugs — they're trust violations.
Driving Questions
- Does the consent implementation actually block tracking, or just record preference?
- Where does PII leak that we haven't noticed?
- If a user requests data deletion, what actually gets deleted vs. retained?
- Does the privacy policy accurately reflect what the code actually does?
- How would we handle a GDPR data subject access request today?
- What data are we collecting that we don't actually need?