goSprinto/compliance-skills / gdpr-compliance-checker
gdpr-compliance-checker
VerifiedAutonomous 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.
| File | Kind | Size |
|---|---|---|
| README.md | markdown | 7.5 KB |
| SKILL.md | skill md | 34.0 KB |
| references/access-governance-checklist.md | markdown | 9.0 KB |
| references/ai-vendor-checklist.md | markdown | 12.5 KB |
| references/breach-response-pack.md | markdown | 12.5 KB |
| references/consent-audit.md | markdown | 8.1 KB |
| references/dpa-template.md | markdown | 10.5 KB |
| references/dpia-template.md | markdown | 8.8 KB |
| references/eprivacy-checklist.md | markdown | 9.2 KB |
| references/gdpr-articles.md | markdown | 14.5 KB |
| references/lia-template.md | markdown | 7.2 KB |
| references/member-state-supplements.md | markdown | 15.2 KB |
| references/pii-patterns.md | markdown | 7.8 KB |
| references/ropa-template.md | markdown | 5.6 KB |
| references/sector-overlays.md | markdown | 12.9 KB |
| references/subprocessor-notification-template.md | markdown | 8.2 KB |
| references/supervisory-authorities.md | markdown | 8.0 KB |
| references/training-awareness-template.md | markdown | 9.5 KB |
| sample/gdpr-gap-analysis-acme-2025-05-25.docx | binary | 38.0 KB |
references/ropa-template.md
View on GitHub# Record of Processing Activities (ROPA) Template
## What is a ROPA?
Required under Article 30 GDPR for:
- Organisations with 250+ employees, OR
- Organisations whose processing is likely to result in a risk to data subjects' rights, OR
- Organisations processing special category data, OR
- Organisations processing criminal conviction data
Best practice: maintain one regardless of size.
Controllers and processors must maintain separate ROPAs. This template covers the **controller** ROPA (Art. 30(1)).
---
## How to populate this ROPA
Each row = one **processing activity** (a distinct purpose for which data is used).
Typical activities to identify from a codebase scan:
- User account registration and management
- Customer order processing and fulfilment
- Marketing email campaigns
- Analytics and product improvement
- Customer support
- Payment processing
- Session management / security logging
- Employee HR processing (if applicable)
- Third-party data sharing / advertising
---
## ROPA — Controller Record
**Organisation name:** {{ORGANISATION_NAME}}
**Organisation address:** {{ORGANISATION_ADDRESS}}
**Data Protection Officer (if applicable):** {{DPO_NAME_AND_CONTACT}}
**Date last updated:** {{DATE}}
**Version:** {{VERSION}}
---
### Processing Activities
---
#### Activity 1: {{ACTIVITY_NAME}}
| Field | Detail |
|-------|--------|
| **Activity name** | {{ACTIVITY_NAME}} |
| **Business function / department** | {{DEPARTMENT}} |
| **Description of processing** | {{DESCRIPTION}} |
| **Purpose(s) of processing** | {{PURPOSE}} |
| **Legal basis (Art. 6)** | {{LEGAL_BASIS}} — e.g. Consent (Art. 6(1)(a)) / Contract (Art. 6(1)(b)) / Legal obligation (Art. 6(1)(c)) / Legitimate interests (Art. 6(1)(f)) |
| **Legitimate interest assessment (if Art. 6(1)(f))** | {{LIA_REFERENCE_OR_N/A}} |
| **Special category data? (Art. 9)** | Yes / No — if Yes: {{SPECIAL_CATEGORY_TYPE}} and legal basis under Art. 9(2): {{ART_9_BASIS}} |
| **Categories of data subjects** | {{DATA_SUBJECT_CATEGORIES}} |
| **Categories of personal data** | {{DATA_CATEGORIES}} |
| **Source of personal data** | {{DATA_SOURCE}} — e.g. Directly from data subject / Third party: {{SOURCE_NAME}} |
| **Recipients / disclosures** | {{RECIPIENTS}} — include internal teams and external processors/controllers |
| **Processors used** | {{PROCESSORS}} — list with DPA reference |
| **Retention period** | {{RETENTION_PERIOD}} — e.g. 2 years from last login / 7 years for financial records |
| **Retention basis** | {{RETENTION_BASIS}} — e.g. Legal obligation (tax records) / Business need / Contract term |
| **Deletion method** | {{DELETION_METHOD}} — e.g. Automated purge job / Manual deletion / Anonymisation |
| **International transfers?** | Yes / No — if Yes: destination country {{TRANSFER_DESTINATION}}, transfer mechanism {{TRANSFER_MECHANISM}} |
| **Technical security measures** | {{TECH_MEASURES}} — e.g. Encryption at rest (AES-256), TLS 1.2+, access controls |
| **Organisational security measures** | {{ORG_MEASURES}} — e.g. Staff training, need-to-know access, DPA with processor |
| **DPIA required?** | Yes / No — if Yes: DPIA reference {{DPIA_REF}} |
| **Notes / Risk flags** | {{NOTES}} |
---
#### Activity 2: {{ACTIVITY_NAME}}
*(Copy the table above for each processing activity. Typical activities below — add, remove, or rename as appropriate to what the codebase reveals.)*
---
### Common Activities Starter List
Use this to seed the ROPA — confirm and populate each from the codebase scan:
| # | Activity | Likely Legal Basis | Likely Data |
|---|----------|--------------------|-------------|
| 1 | User registration & account management | Contract | Name, email, password hash |
| 2 | Order / transaction processing | Contract | Name, address, payment ref |
| 3 | Marketing emails | Consent | Email, name, preferences |
| 4 | Product analytics | Legitimate interests | IP, device ID, behaviour events |
| 5 | Customer support | Contract / Legitimate interests | Name, email, support history |
| 6 | Payment processing | Contract | Payment card data (via processor) |
| 7 | Session management & security logging | Legitimate interests | IP, session ID, timestamps |
| 8 | Fraud prevention | Legitimate interests / Legal obligation | IP, device fingerprint, transaction patterns |
| 9 | Legal compliance / record keeping | Legal obligation | Various — as required by law |
| 10 | Employee data (if applicable) | Contract / Legal obligation | Name, salary, bank details, NI/SSN |
| 11 | Cookie tracking / advertising | Consent | Cookie ID, browsing behaviour |
| 12 | Third-party data sharing (partners) | Consent / Legitimate interests | As agreed |
---
## Processor ROPA (Art. 30(2))
If this organisation also acts as a **processor** for other controllers, maintain a separate record:
| Field | Detail |
|-------|--------|
| **Controller name and contact** | {{CONTROLLER_NAME_AND_CONTACT}} |
| **Processor (this org) name and contact** | {{PROCESSOR_NAME_AND_CONTACT}} |
| **DPO contact** | {{DPO_CONTACT}} |
| **Categories of processing carried out for controller** | {{PROCESSING_CATEGORIES}} |
| **Transfers to third countries** | {{TRANSFER_DETAILS}} |
| **Security measures** | {{SECURITY_MEASURES}} |
---
## ROPA Maintenance
- Review and update this ROPA: **at least annually**, and whenever a new processing activity is introduced or materially changed.
- Owner: {{ROPA_OWNER_ROLE}}
- Review date: {{NEXT_REVIEW_DATE}}
- Approved by: {{APPROVER}}
---
*This template is based on Article 30 GDPR requirements. It is a starting point — legal review is recommended before relying on this as your organisation's official ROPA.*
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 472k | Updated | Claude CodeCodex | Verified | Install |
| 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: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |