agentleFS
zsrrica-pixelzsrrica-pixel/gdpr-compliance-plugin/skills/privacy-policy-review/SKILL.md

privacy-policy-review

Skill1 starsChanged 43 days agoMITView on GitHub

Review a privacy policy or notice against GDPR Arts. 12-14 transparency requirements. Use when the user shares a privacy policy, website, or notice to check.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Check the document for each Art.

    line 8

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Privacy policy review

Check the document for each Art. 13/14 element and mark Present / Weak / Missing:

  • Controller identity and contact, DPO contact
  • Purposes and lawful basis for each purpose; legitimate interests explained
  • Recipients or categories of recipients
  • International transfers and safeguards
  • Retention periods (or criteria)
  • Data subject rights (access, rectification, erasure, restriction, portability, objection, withdraw consent) and right to complain to a supervisory authority
  • Whether providing data is mandatory; consequences of not providing
  • Automated decision-making/profiling information
  • Source of data (if not collected from the subject)

Also check plain language, easy accessibility, cookie/tracking disclosures, and date/version. Output a findings table and suggested replacement wording for each gap.

Method and format

  • Read the verbatim text. For a URL use a browser tool and read the page text (not a summarising fetch); if only a summary is available, say so and treat every "Missing" as "verify on the live page".
  • Status: Present = element stated clearly. Weak = stated but vague, wrong basis, or incomplete (e.g. legitimate interest named but not explained). Missing = absent.
  • Also check ePrivacy/cookie disclosures (cookie-by-cookie table, withdrawal route) and cross-check the policy against what the site actually loads (see cookie-tracker-audit) and what it sells or collects (payments, forms, AI tools).
  • Output: table (element, status, finding, priority High/Medium/Low), then replacement wording per gap with [placeholders] only where a fact is unknown.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.