EU AI Act & AI Governance Toolkit — curated by Devseis
Collection
AI Act, GDPR/PII and LLM-security resources curated by Devseis, a Luxembourg AI governance & cybersecurity consultancy. Not legal advice. • 13 items • Updated
Datasets:
template_type stringclasses 5
values | section stringlengths 4 42 | field_or_question stringlengths 11 143 | description stringlengths 38 152 | gdpr_article stringlengths 7 56 | notes float64 |
|---|---|---|---|---|---|
ropa_controller | Identity | Controller name and contact details | Legal name, address, and contact point of the controller. | Art. 30(1) | null |
ropa_controller | Identity | Joint controller details (if applicable) | Name and contact details of any joint controller. | Art. 30(1) | null |
ropa_controller | Identity | Representative details (if applicable) | EU representative, if controller is not established in the EU (Art. 27). | Art. 30(1) | null |
ropa_controller | Identity | DPO contact details (if applicable) | Name and contact details of the Data Protection Officer, if one is designated (Art. 37). | Art. 30(1) | null |
ropa_controller | Purpose | Purposes of processing | Why the personal data is processed for this activity — should match the lawful basis relied on. | Art. 30(1) | null |
ropa_controller | Data | Categories of data subjects | Who the data is about, e.g. employees, customers, website visitors, job applicants. | Art. 30(1) | null |
ropa_controller | Data | Categories of personal data | What kinds of data, e.g. contact details, financial data, special-category data (Art. 9). | Art. 30(1) | null |
ropa_controller | Recipients | Categories of recipients | Who the data has been or will be disclosed to, including processors, other controllers, public authorities. | Art. 30(1) | null |
ropa_controller | International transfers | Third-country / international-org transfer — destination | Country or organisation the data is transferred to, if any. | Art. 30(1) | null |
ropa_controller | International transfers | Third-country / international-org transfer — safeguard | Legal mechanism used: adequacy decision, Standard Contractual Clauses, BCRs, or Art. 49 derogation. | Art. 30(1) | null |
ropa_controller | Retention | Envisaged erasure time limits | Retention period per category of data, or the criteria used to determine it, where a fixed period isn't possible. | Art. 30(1) | null |
ropa_controller | Security | General description of technical and organisational security measures | High-level summary of Art. 32(1) safeguards (e.g. encryption, access control) — the RoPA itself needn't detail the full security architecture. | Art. 30(1) | null |
ropa_processor | Identity | Processor name and contact details | Legal name, address, and contact point of the processor. | Art. 30(2) | null |
ropa_processor | Identity | Sub-processor details (if applicable) | Name and contact details of each sub-processor engaged. | Art. 30(2) | null |
ropa_processor | Identity | Representative details (if applicable) | EU representative, if processor is not established in the EU. | Art. 30(2) | null |
ropa_processor | Identity | DPO contact details (if applicable) | Name and contact details of the processor's DPO, if designated. | Art. 30(2) | null |
ropa_processor | Controllers | Each controller's name and contact details | For every controller the processor acts on behalf of. | Art. 30(2) | null |
ropa_processor | Processing | Categories of processing per controller | What processing activities are carried out on behalf of each controller. | Art. 30(2) | null |
ropa_processor | International transfers | Third-country / international-org transfer — destination and safeguard | Same structure as the controller RoPA, per Art. 30(2)(c). | Art. 30(2) | null |
ropa_processor | Security | General description of technical and organisational security measures | Art. 32(1) safeguards summary, as processor. | Art. 30(2) | null |
dpia_screening | Mandatory triggers (Art. 35(3)) | Systematic/extensive evaluation of personal aspects via automated processing (incl. profiling) producing legal or similarly significant effects | If YES on its own, a DPIA is required. | Art. 35(3)(a) | null |
dpia_screening | Mandatory triggers (Art. 35(3)) | Large-scale processing of special-category data (Art. 9) or criminal-conviction/offence data (Art. 10) | If YES on its own, a DPIA is required. | Art. 35(3)(b) | null |
dpia_screening | Mandatory triggers (Art. 35(3)) | Systematic monitoring of a publicly accessible area on a large scale | If YES on its own, a DPIA is required. | Art. 35(3)(c) | null |
dpia_screening | EDPB WP248 guidance criteria (non-binding) | Evaluation or scoring (incl. profiling and predicting) | General EDPB guidance: meeting 2 or more of these criteria is a strong indicator a DPIA is likely required, even outside the Art. 35(3) mandatory cases. | EDPB Guidelines WP248 rev.01 (not the Regulation itself) | null |
dpia_screening | EDPB WP248 guidance criteria (non-binding) | Automated decision-making with legal or similarly significant effect | General EDPB guidance: meeting 2 or more of these criteria is a strong indicator a DPIA is likely required, even outside the Art. 35(3) mandatory cases. | EDPB Guidelines WP248 rev.01 (not the Regulation itself) | null |
dpia_screening | EDPB WP248 guidance criteria (non-binding) | Systematic monitoring of individuals | General EDPB guidance: meeting 2 or more of these criteria is a strong indicator a DPIA is likely required, even outside the Art. 35(3) mandatory cases. | EDPB Guidelines WP248 rev.01 (not the Regulation itself) | null |
dpia_screening | EDPB WP248 guidance criteria (non-binding) | Sensitive data or data of a highly personal nature | General EDPB guidance: meeting 2 or more of these criteria is a strong indicator a DPIA is likely required, even outside the Art. 35(3) mandatory cases. | EDPB Guidelines WP248 rev.01 (not the Regulation itself) | null |
dpia_screening | EDPB WP248 guidance criteria (non-binding) | Data processed on a large scale | General EDPB guidance: meeting 2 or more of these criteria is a strong indicator a DPIA is likely required, even outside the Art. 35(3) mandatory cases. | EDPB Guidelines WP248 rev.01 (not the Regulation itself) | null |
dpia_screening | EDPB WP248 guidance criteria (non-binding) | Matching or combining datasets | General EDPB guidance: meeting 2 or more of these criteria is a strong indicator a DPIA is likely required, even outside the Art. 35(3) mandatory cases. | EDPB Guidelines WP248 rev.01 (not the Regulation itself) | null |
dpia_screening | EDPB WP248 guidance criteria (non-binding) | Data concerning vulnerable data subjects (children, employees, patients, the elderly) | General EDPB guidance: meeting 2 or more of these criteria is a strong indicator a DPIA is likely required, even outside the Art. 35(3) mandatory cases. | EDPB Guidelines WP248 rev.01 (not the Regulation itself) | null |
dpia_screening | EDPB WP248 guidance criteria (non-binding) | Innovative use or applying new technological or organisational solutions | General EDPB guidance: meeting 2 or more of these criteria is a strong indicator a DPIA is likely required, even outside the Art. 35(3) mandatory cases. | EDPB Guidelines WP248 rev.01 (not the Regulation itself) | null |
dpia_screening | EDPB WP248 guidance criteria (non-binding) | Processing that prevents data subjects from exercising a right or using a service/contract | General EDPB guidance: meeting 2 or more of these criteria is a strong indicator a DPIA is likely required, even outside the Art. 35(3) mandatory cases. | EDPB Guidelines WP248 rev.01 (not the Regulation itself) | null |
dpia_assessment | Description | Systematic description of the envisaged processing operations | What is actually being done with the data, end to end. | Art. 35(7)(a) | null |
dpia_assessment | Description | Purposes of the processing, including legitimate interest pursued (if relevant) | Why the processing is being carried out. | Art. 35(7)(a) | null |
dpia_assessment | Necessity & proportionality | Assessment of necessity and proportionality of the processing in relation to the purposes | Could the same purpose be achieved with less data, or a less intrusive method? | Art. 35(7)(b) | null |
dpia_assessment | Risk assessment | Assessment of risks to the rights and freedoms of data subjects | Identify sources of risk (technical, organisational, human) and their likelihood and severity. | Art. 35(7)(c) | null |
dpia_assessment | Risk treatment | Measures envisaged to address the identified risks | Technical and organisational safeguards, including security measures. | Art. 35(7)(d) | null |
dpia_assessment | Risk treatment | Mechanisms to ensure the protection of personal data and demonstrate compliance | Evidence/documentation that the safeguards are actually applied and effective. | Art. 35(7)(d) | null |
dpia_governance | Consultation | Seek the views of data subjects or their representatives, where appropriate | Not always required/practical, but must be considered and the decision documented either way. | Art. 35(9) | null |
dpia_governance | Consultation | DPO opinion | Where a DPO is designated, their advice on the DPIA must be sought and recorded. | Art. 35(2) | null |
dpia_governance | Residual risk | Determine whether residual risk (after mitigation) remains high | If yes, prior consultation with the supervisory authority is required before processing starts. | Art. 36 | null |
dpia_governance | Residual risk | Prior consultation with the supervisory authority (e.g. CNPD in Luxembourg) | Required only if residual risk is still high after mitigation measures. | Art. 36 | null |
dpia_governance | Sign-off | Formal approval and sign-off record | Who approved the DPIA and when — accountability evidence under Art. 5(2). | Art. 5(2), 24 | null |
dpia_governance | Review | Review trigger / re-assessment schedule | DPIA should be reviewed when the risk changes (new tech, new data types, incident) — not treated as a one-off document. | Art. 35(11) | null |
GDPR RoPA & DPIA Template Pack
A structured field/section template for two of the most common GDPR deliverables: the Record of Processing Activities (RoPA, Article 30 — controller and processor versions) and the Data Protection Impact Assessment (DPIA, Article 35 — screening, assessment content, and governance steps).
Compiled by Devseis, a Luxembourg cybersecurity, data protection and AI governance consultancy, from GDPR's own text (Articles 5, 24, 27, 30, 32, 35, 36, 37) and the EDPB's WP248 rev.01 guidelines on DPIA (for the non-binding "likely high risk" screening criteria, clearly marked as guidance rather than the Regulation itself).
⚠️ Not legal advice
This is a field/section template, not a filled-in example and not a compliance determination. It tells you what a RoPA or DPIA needs to contain, not the right answer for your specific processing activity. Always verify against the current GDPR text and, where relevant, your national supervisory authority's guidance (e.g. Luxembourg's CNPD) before relying on it.
Columns
| Column | Description |
|---|---|
template_type |
ropa_controller / ropa_processor / dpia_screening / dpia_assessment / dpia_governance |
section |
Grouping within that template (e.g. Identity, Recipients, Risk assessment) |
field_or_question |
The specific field to fill in, or question to answer |
description |
What it means / how to fill it in |
gdpr_article |
Article citation (or EDPB guidance reference for the non-binding screening criteria) |
notes |
Extra context where useful |
License
CC-BY-4.0 — compiled from public regulatory and EDPB guidance text.
- Downloads last month
- 30