mcpField
G
gdpr-ccpa-privacy-auditor

gdpr-ccpa-privacy-auditor

github.com/jorgealvesSecurity2408 installsUpdated 2d ago
Repository

About gdpr-ccpa-privacy-auditor

gdpr-ccpa-privacy-auditor is a transparency tool for comparing public privacy policies with technical indicators on websites, such as cookies, scripts, and data models. It is intended for recurring privacy reviews, launch checks, and due diligence, but does not cover organizational practices or server-only tracking.

Key features

  1. 01Compare policies with technical indicators
  2. 02Scan public website URLs
  3. 03Inspect cookies and scripts
  4. 04Support privacy reviews and launch checks
  5. 05Flag limits of client-side scanning

Use cases

  1. 01Run a recurring privacy impact review
  2. 02Check a landing page before launch
  3. 03Review a public website for due diligence

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/jorgealves/agent_skills --skill gdpr-ccpa-privacy-auditor

After installing, type/gdpr-ccpa-privacy-auditorin Claude Code to confirm it loaded.

Bundled filesskill.yaml

Details

From the project README

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.

Comments

Markdown supported