Reads the privacy notice in your repo against 16 rules from GDPR Articles 13 and 14, flags template placeholders, and tells you when the notice itself has gone stale. Runs entirely in your browser — nothing is uploaded.
Sweep the whole workspace and keep the report — $29 once
$29 once · one licence key per person or CI seat · 7-day full refund. Counsel reviewing one notice bills about €250 an hour.
Same engine as the VS Code extension, byte for byte.
This page is the working piece. The full pack has everything below.
16 rules read your privacy.md the way Articles 13 and 14 read it
A law firm reading one privacy notice against Articles 13 and 14 bills about €250 an hour; this runs in about a second.
Buy the full version — $29It reads a privacy notice in your repository and checks it against 16 rules drawn from GDPR Articles 13, 14, 22, 46 and 77. Each missing disclosure appears in the Problems panel with its article number and a line. On the assistant-written fixture shipped with it, the engine returns 17 findings: 11 errors and 6 warnings.
Solo founders and small engineering teams shipping a SaaS, app or docs site to EU users, who keep privacy.md in the repository beside the code. It is for the person who pasted an assistant-written policy into that file two years ago and has not opened Article 13 since.
A chatbot rewrites the prose. It does not count the six rights that Article 13(2)(b) requires, and it cannot compare the date in your header to today, so it will not tell you a notice is 2020 days old. These 16 rules are deterministic: same file, same findings, with article numbers attached.
Checking the notice open in your editor is free forever: all 16 rules, every finding, no key and no run limit. The licensed command works on a different axis, scope and ownership. It sweeps every notice in the workspace in one pass and writes a dated evidence report you keep, for $29 once.
A law firm reading one notice against Articles 13 and 14 bills at counsel's hourly rate, about €250 an hour, and gives you an answer for that one version of that one file. The exposure behind it is Article 83(5): up to €20 million or 4% of total worldwide annual turnover.
One question, answered by the person who built it. Your email only if you want the answer sent.