16 rules read your privacy.md the way Articles 13 and 14 read it
It 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.
[readystack_gdpr_privacy_notice_lint]. In the block editor, use a Shortcode block.Each finding names the rule it breaks and the fix. Correct the flagged lines, paste the file again, and keep the clean result as a dated record of the check for your checklist, ticket or client report.
The tool runs in the browser of whoever opens the page. The plugin makes no external requests, sets no cookies, adds no tracking and stores nothing in your database. It has no settings screen.
The JavaScript and CSS files in the plugin’s assets folder are the complete, human-readable source. There is no build step: nothing is compiled, bundled or minified, so what you read is what runs.
The free tool on this page is complete for one pasted file at a time: every finding is listed with the rule it breaks and the fix. Nothing in this plugin is locked or time-limited. A separate paid version for teams is sold on our website, not inside this plugin. Full version: https://getreadystack.com/tools/gdpr-privacy-notice-lint?ref=wporg