Skip to content

goSprinto/compliance-skills / gdpr-compliance-checker

gdpr-compliance-checker

Verified

Autonomous GDPR compliance auditor that scans a codebase to identify PII collection, storage, and sharing, then produces an article-by-article gap analysis, a pre-filled Data Processing Agreement (DPA), and a ROPA (Record of Processing Activities) starter kit — all exported as downloadable files (.docx recommended). Use this skill whenever the user mentions GDPR, data privacy audit, DPA, ROPA, EU compliance, PII scan, data protection, ICO, CNIL, or asks whether their codebase or product is compliant with data protection law. Trigger even for casual phrasings like "are we GDPR compliant?", "I need to check our data privacy", or "help me get audit-ready." The skill runs autonomously — it reads the codebase, researches third-party processors, and produces final deliverables without the user needing to provide structured input.

references/dpa-template.md

View on GitHub
# Data Processing Agreement (DPA) Template

Fill all `{{PLACEHOLDER}}` values from codebase context, web research, and user input before generating the final document.

---

# DATA PROCESSING AGREEMENT

**Between:**

**{{CONTROLLER_NAME}}**
Registered address: {{CONTROLLER_ADDRESS}}
Company number: {{CONTROLLER_COMPANY_NUMBER}}
("Controller")

**And:**

**{{PROCESSOR_NAME}}**
Registered address: {{PROCESSOR_ADDRESS}}
Company number: {{PROCESSOR_COMPANY_NUMBER}}
("Processor")

Together referred to as "the Parties."

---

## 1. Background

1.1 The Controller is a company providing {{CONTROLLER_SERVICE_DESCRIPTION}}.

1.2 The Processor provides {{PROCESSOR_SERVICE_DESCRIPTION}} to the Controller under a separate services agreement dated {{SERVICES_AGREEMENT_DATE}} ("the Principal Agreement").

1.3 In the course of providing those services, the Processor will process personal data on behalf of the Controller. The Parties enter into this Agreement to ensure that such processing complies with the UK/EU General Data Protection Regulation ("GDPR") and applicable data protection laws.

---

## 2. Definitions

2.1 In this Agreement, capitalised terms have the meanings given in GDPR Article 4 unless otherwise defined. In particular:

- **"Personal Data"** means any information relating to an identified or identifiable natural person.
- **"Processing"** has the meaning given in Article 4(2) GDPR.
- **"Data Subject"** means the natural person to whom Personal Data relates.
- **"Supervisory Authority"** means {{LEAD_SUPERVISORY_AUTHORITY}} (e.g. the Information Commissioner's Office (ICO) for UK, or the relevant EU lead authority).

---

## 3. Details of Processing (Schedule 1)

| Item | Detail |
|------|--------|
| **Subject matter** | {{PROCESSING_SUBJECT_MATTER}} |
| **Duration** | For the term of the Principal Agreement plus {{RETENTION_PERIOD_POST_TERMINATION}} |
| **Nature of processing** | {{PROCESSING_NATURE}} (e.g. collection, storage, retrieval, transmission, erasure) |
| **Purpose of processing** | {{PROCESSING_PURPOSE}} |
| **Types of Personal Data** | {{DATA_TYPES}} (e.g. name, email, IP address, payment data) |
| **Categories of Data Subjects** | {{DATA_SUBJECT_CATEGORIES}} (e.g. customers, employees, website visitors) |

---

## 4. Controller's Obligations

4.1 The Controller shall:

(a) Ensure it has a lawful basis for the processing described in Schedule 1, in accordance with Article 6 GDPR (and Article 9 GDPR where applicable);

(b) Provide data subjects with privacy information as required by Articles 13 and 14 GDPR;

(c) Ensure that its instructions to the Processor are lawful and comply with applicable data protection laws;

(d) Respond to requests from data subjects exercising their rights under Chapter III GDPR.

---

## 5. Processor's Obligations

5.1 The Processor shall:

(a) **Process only on instructions.** Process Personal Data only on documented instructions from the Controller, including with regard to international transfers, unless required to do so by applicable law; in such a case, the Processor shall inform the Controller before processing, unless prohibited by law on important grounds of public interest.

(b) **Confidentiality.** Ensure that persons authorised to process Personal Data have committed to confidentiality or are under an appropriate statutory obligation.

(c) **Security.** Implement appropriate technical and organisational measures to ensure a level of security appropriate to the risk, including as appropriate:
   - Pseudonymisation and encryption of Personal Data;
   - The ability to ensure ongoing confidentiality, integrity, availability and resilience of processing systems;
   - The ability to restore the availability and access to Personal Data in a timely manner in the event of an incident;
   - A process for regularly testing, assessing and evaluating the effectiveness of technical and organisational measures.

(d) **Sub-processors.** Not engage another processor without prior specific or general written authorisation of the Controller. Where general authorisation is given, the Processor shall inform the Controller of any intended changes and give the Controller the opportunity to object.

(e) **Data subject rights.** Assist the Controller by appropriate technical and organisational measures in fulfilling its obligations to respond to requests for exercising data subjects' rights under Chapter III GDPR.

(f) **Assistance.** Assist the Controller in ensuring compliance with Articles 32–36 GDPR (security, breach notification, DPIA, prior consultation).

(g) **Deletion or return.** At the choice of the Controller, delete or return all Personal Data after the end of the provision of services, and delete existing copies unless applicable law requires storage.

(h) **Audit.** Make available to the Controller all information necessary to demonstrate compliance with Article 28 GDPR, and allow for and contribute to audits, including inspections, conducted by the Controller or an auditor mandated by the Controller.

(i) **Notification.** Immediately inform the Controller if, in the Processor's opinion, an instruction infringes GDPR or other applicable data protection provisions.

---

## 6. Sub-Processors

6.1 The Controller provides general authorisation for the Processor to engage sub-processors. The current list of sub-processors is set out in Schedule 2.

6.2 The Processor shall notify the Controller of any intended changes (additions or replacements) to Schedule 2 with at least {{SUB_PROCESSOR_NOTICE_PERIOD}} days' notice.

6.3 The Controller may object to such changes within {{CONTROLLER_OBJECTION_PERIOD}} days. If the Parties cannot resolve the objection, either party may terminate the Principal Agreement on {{TERMINATION_NOTICE}} days' written notice.

6.4 The Processor shall impose data protection obligations on sub-processors that are equivalent to those in this Agreement.

---

## 7. Security

7.1 The Processor shall implement and maintain the technical and organisational security measures described in Schedule 3.

7.2 The Processor shall conduct a risk assessment of its processing operations at least {{SECURITY_REVIEW_FREQUENCY}} and update its security measures accordingly.

---

## 8. Personal Data Breaches

8.1 The Processor shall notify the Controller without undue delay, and in any event within **{{BREACH_NOTIFICATION_TO_CONTROLLER_HOURS}} hours**, after becoming aware of a Personal Data Breach affecting Controller data.

8.2 The notification shall include:
- The nature of the breach (categories and approximate number of data subjects and records affected);
- The likely consequences of the breach;
- Measures taken or proposed to address the breach.

8.3 The Controller is responsible for notifying the Supervisory Authority within 72 hours (Article 33 GDPR) and data subjects where required (Article 34 GDPR).

---

## 9. International Transfers

9.1 The Processor shall not transfer Personal Data outside the UK/EEA without the Controller's prior written authorisation and without ensuring an appropriate transfer mechanism is in place, including:

- An adequacy decision (Article 45 GDPR);
- Standard Contractual Clauses (SCCs) as approved by the European Commission (June 2021);
- Binding Corporate Rules (Article 47 GDPR);
- UK International Data Transfer Agreement (IDTA) where applicable.

9.2 Where SCCs apply, they are incorporated into this Agreement by reference. The applicable module is: **{{SCC_MODULE}}** (Module 2: Controller-to-Processor / Module 3: Processor-to-Processor / Module 4: Processor-to-Controller).

---

## 10. Term and Termination

10.1 This Agreement commences on {{EFFECTIVE_DATE}} and continues for the duration of the Principal Agreement.

10.2 Either party may terminate this Agreement on written notice if the other party materially breaches this Agreement and (where the breach is capable of remedy) fails to remedy it within {{REMEDY_PERIOD}} days of written notice.

10.3 On termination, Clause 5.1(g) (deletion or return) applies.

---

## 11. Liability

11.1 Each party's liability under this Agreement is subject to the limitations set out in the Principal Agreement, except:

(a) A party's liability to data subjects under Article 82 GDPR shall not be limited;

(b) Nothing limits liability for fraud or wilful misconduct.

---

## 12. Governing Law and Jurisdiction

12.1 This Agreement is governed by the laws of {{GOVERNING_LAW_JURISDICTION}} (e.g. England and Wales / Republic of Ireland / Germany).

12.2 The Parties submit to the exclusive jurisdiction of the courts of {{COURT_JURISDICTION}}.

---

## Signatures

| Controller | Processor |
|-----------|-----------|
| Signed: _________________________ | Signed: _________________________ |
| Name: {{CONTROLLER_SIGNATORY_NAME}} | Name: {{PROCESSOR_SIGNATORY_NAME}} |
| Title: {{CONTROLLER_SIGNATORY_TITLE}} | Title: {{PROCESSOR_SIGNATORY_TITLE}} |
| Date: {{SIGNATURE_DATE}} | Date: {{SIGNATURE_DATE}} |

---

## Schedule 1 — Details of Processing
*(See Clause 3 table above — reproduce here for standalone schedule)*

---

## Schedule 2 — Approved Sub-Processors

| Sub-Processor | Location | Processing Activity | Transfer Mechanism |
|--------------|----------|--------------------|--------------------|
| {{SUB_PROCESSOR_1_NAME}} | {{SUB_PROCESSOR_1_LOCATION}} | {{SUB_PROCESSOR_1_PURPOSE}} | {{SUB_PROCESSOR_1_TRANSFER_MECHANISM}} |
| {{SUB_PROCESSOR_2_NAME}} | {{SUB_PROCESSOR_2_LOCATION}} | {{SUB_PROCESSOR_2_PURPOSE}} | {{SUB_PROCESSOR_2_TRANSFER_MECHANISM}} |

*(Add rows for each processor found in codebase scan)*

---

## Schedule 3 — Technical and Organisational Security Measures

The Processor shall maintain, at minimum, the following measures:

| Measure | Description |
|---------|-------------|
| Encryption in transit | TLS 1.2 or higher for all data in transit |
| Encryption at rest | AES-256 or equivalent for stored Personal Data |
| Access control | Role-based access control; principle of least privilege |
| Authentication | Multi-factor authentication for systems accessing Personal Data |
| Logging & monitoring | Audit logs retained for {{LOG_RETENTION_PERIOD}}; anomaly alerting in place |
| Vulnerability management | Patches applied within {{PATCH_SLA}} of release; annual penetration testing |
| Backup & recovery | Daily backups; RTO of {{RTO}}; RPO of {{RPO}} |
| Employee training | Annual data protection training for staff with access to Personal Data |
| Incident response | Written incident response plan; breach notification within {{BREACH_NOTIFICATION_TO_CONTROLLER_HOURS}} hours to Controller |

---

*This template is provided for informational purposes. It should be reviewed by qualified legal counsel before execution. This skill does not provide legal advice.*
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 196kUpdated Claude CodeCodexVerifiedInstall