
Gdpr Ccpa Privacy Auditor
- 353 installs
- 2 repo stars
- Updated January 25, 2026
- jorgealves/agent_skills
gdpr-ccpa-privacy-auditor is a compliance skill that compares declared privacy policies to actual cookie, tracker, and data-handling behavior for developers preparing GDPR and CCPA launch or procurement reviews.
About
gdpr-ccpa-privacy-auditor is a jorgealves/agent_skills transparency checker that compares public privacy policies to technical data collection on web applications. The skill scans for cookie usage, client-side tracking scripts, and user data handling patterns to flag discrepancies that create regulatory exposure under GDPR and CCPA. Developers reach for it during privacy impact assessments, marketing landing launches with new trackers, and M&A due diligence on public sites. Passive URL scanning behaves like a standard browser; optional source_code_path review stays local when configured securely. The skill does not audit physical security, organizational policy documents, or server-only trackers with no client script. It targets publicly reachable endpoints, not internal VPN-only apps without public surfaces.
- Maps controllers, processors, and subprocessors
- Checks consent granularity and opt-out parity
- Reviews retention, minimization, and cross-border transfers
- Surfaces missing DSAR and deletion workflows
- Produces prioritized remediation findings
Gdpr Ccpa Privacy Auditor by the numbers
- 353 all-time installs (skills.sh)
- +11 installs in the week ending Aug 2, 2026 (Skillselion tracking)
- Ranked #578 of 2,203 Security skills by installs in the Skillselion catalog
- Data as of Aug 2, 2026 (Skillselion catalog sync)
npx skills add https://github.com/jorgealves/agent_skills --skill gdpr-ccpa-privacy-auditorAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 353 |
|---|---|
| repo stars | ★ 2 |
| Last updated | January 25, 2026 |
| Repository | jorgealves/agent_skills ↗ |
How do you audit GDPR and CCPA privacy compliance?
Audit privacy policies, consent flows, data maps, and retention practices against GDPR and CCPA before public launch or enterprise procurement reviews.
Who is it for?
Developers and security reviewers validating public web apps before GDPR or CCPA launch, new marketing trackers, or acquisition due diligence.
Skip if: Internal-only apps behind VPN without public endpoints or teams needing full legal, physical-security, or organizational policy audits.
When should I use this skill?
A public site launch, privacy impact assessment, or procurement review needs policy-versus-implementation checks for GDPR and CCPA.
What you get
Privacy discrepancy report on cookies, tracking scripts, consent flows, and data maps versus declared policy text.
- privacy discrepancy report
- cookie and tracker inventory
Files
GDPR/CCPA Privacy Auditor
Purpose and Intent
The gdpr-ccpa-privacy-auditor is a transparency tool. It helps companies ensure that their public-facing privacy policies actually match their technical implementations, preventing "Privacy Washing" and reducing the risk of regulatory fines.
When to Use
- Privacy Impact Assessments (PIA): Run as part of a recurring privacy review.
- Marketing Launches: Check new landing pages to ensure new trackers haven't been added without updating the policy.
- Due Diligence: Audit a target company's website during a merger or acquisition.
When NOT to Use
- Internal Only Apps: Not designed for apps behind a firewall or VPN without public endpoints.
- Comprehensive Legal Audit: Only focuses on technical indicators (cookies, scripts, data models); does not audit physical security or organizational policies.
Error Conditions and Edge Cases
- Server-Side Tracking: Trackers that run purely on the server (no client-side script) cannot be detected via URL scanning.
- Dynamic Content: Some trackers may only load for specific regions or after specific user interactions (like clicking a button).
Security and Data-Handling Considerations
- Passive Scanning: When scanning URLs, it acts like a standard browser.
- Source Code Privacy: If providing
source_code_path, ensure the environment is secure and the code is not transmitted externally.
name: gdpr-ccpa-privacy-auditor
version: 1.0.0
description: Audits web applications to ensure declared privacy policies match actual technical data collection practices. Use to identify discrepancies in cookie usage, tracking scripts, and user data handling.
inputs:
website_url:
type: string
description: The public URL of the application to scan.
policy_text:
type: string
description: The text of the privacy policy to analyze.
source_code_path:
type: string
description: Path to source code for backend analysis.
outputs:
alignment_report:
type: object
properties:
discrepancies:
type: array
items:
type: string
detected_trackers:
type: array
items:
type: string
capabilities:
- Cookie and script crawling.
- Policy claim extraction via NLP.
- Cross-referencing technical behavior with legal claims.
constraints:
- Server-side tracking cannot be detected without source code.
- Reflects point-in-time compliance.
security:
- Scans public elements only.
- Does not bypass security or access user data.
examples:
- input:
website_url: "https://example.com"
policy_text: "No tracking cookies used."
output:
alignment_report:
discrepancies: ["Policy claims no tracking, but Google Analytics found."]
detected_trackers: ["Google Analytics"]Related skills
How it compares
Use gdpr-ccpa-privacy-auditor for policy-versus-implementation privacy gaps on public sites; pair with dedicated appsec scanners for exploit-focused security testing.
FAQ
What does gdpr-ccpa-privacy-auditor detect?
gdpr-ccpa-privacy-auditor compares declared privacy policies to technical indicators such as cookies, client-side tracking scripts, and data models. Server-only trackers without client scripts and organizational policies sit outside its scope.
Can gdpr-ccpa-privacy-auditor scan internal apps?
gdpr-ccpa-privacy-auditor targets publicly reachable web endpoints. Internal-only applications behind a firewall or VPN without public URLs are outside its design; use source_code_path review only in a secure local environment.