GDPR compliance coverage

We scan SaaS codebases against 10 custom Semgrep rules across 6 GDPR articles. Each article below maps to the specific code-level checks we run.

Art.51 rule

Principles relating to processing of personal data

The foundational principles — data minimization, purpose limitation, accuracy, and integrity — that govern all lawful personal-data processing.

Art.61 rule

Lawfulness of processing

Requires a valid lawful basis (consent, contract, legitimate interest, etc.) before any personal data is processed.

Art.71 rule

Conditions for consent

Defines what constitutes valid consent — freely given, specific, informed, unambiguous — and that pre-ticked boxes do not count.

Art.171 rule

Right to erasure ('right to be forgotten')

Data subjects can request deletion of their personal data. A SaaS without a working deletion path is a compliance defect.

Art.281 rule

Processor obligations

When a SaaS shares user data with third-party processors (analytics, email, payments), a written Data Processing Agreement is required.

Art.325 rules

Security of processing

Mandates appropriate technical and organizational measures — encryption, access control, secrets management — proportional to risk.

Run a scan on your repo

See all 10 rules evaluated against your actual code in 3 minutes.

Try the demo scan