Who it’s for · Companies using AI
Giving an AI tool access to data does not give you the right to use that data for that purpose. Purpose, legal basis, recipients and retention should be defined in your RoPA before data reaches the tool. GovernID helps you do that preparation and keep every AI use visible.
GovernID is a Privacy Management Automation platform: it makes the RoPA the single source for notices, consent, data subject requests, DPIAs and audit evidence, and records every data collection against it.
Access is not appropriate use
In most companies AI starts with a tool one team picks up. The questions come later: what purpose was this data collected for? What did we tell the individual? May the provider use the data to improve its own model? With Point Zero Privacy®, the answers are ready in the RoPA before data arrives.
Each record is created with its collection channel and data categories; special category data is flagged.
Each record is tied to the purpose and legal basis of its process. A new AI purpose means a new process.
The provider appears in the RoPA as a data recipient, with transfer country and retention period. If an existing system has an AI feature, the data storage location is marked that way too.
1
There is no separate data protection law for AI; GDPR and KVKK apply to AI use as they are. The table separates, for each obligation, what GovernID does and what stays with your company.
| Obligation | Basis | What GovernID does | What stays with your company |
|---|---|---|---|
| Specified, explicit purpose | GDPR 5(1)(b) KVKK 4(2)(c) | The AI use is defined as its own process in the RoPA; purpose, data categories and data subject groups are tied to it. | Deciding which task the AI is used for, with which data. |
| Legal basis | GDPR 6, 9 KVKK 5, 6 | The legal basis is selected in the process. Where consent is needed it is collected with the data; given and withdrawn dates stay on the record. | Choosing the right basis. Legitimate interest is not the default basis for AI; the balancing test is yours. |
| Using existing data for a new purpose | GDPR 6(4) KVKK 4(2)(c) | The new purpose enters the RoPA as a new process; because each record shows what it was collected for, the comparison can be made. | Carrying out the compatibility assessment. GovernID does not run this test automatically. |
| Transparency notice | GDPR 13, 14 KVKK 10 | The notice is generated from the process (9 languages); when the process changes, the updated text reaches your forms. | Where automated decisions exist, adding meaningful information about the logic and consequences (GDPR 13(2)(f)). |
| Automated decisions and objection | GDPR 21, 22 KVKK 11(1)(g) | In the Privacy Center individuals see their records, withdraw consent where processing relies on it, and flag a record that is not theirs with “This is not mine”; the request lands on your screen. | Offering a channel for objections and requests for human intervention, and reviewing the decision. |
| DPIA | GDPR 35 AI Act 26(9) | The DPIA is built on the process; with special category data the screen suggests a DPIA, a risk score is calculated, and it exports as PDF and JSON. | Assessing AI-specific risks (accuracy, discrimination, explainability). |
| Provider contract | GDPR 28 KVKK 3(1)(ğ), 12(2) | The provider appears as a data recipient in the process; with Third-party processor management it can reach your instructions for each record. | Making clear in the contract whether the provider may use your data to train its own models. |
| International transfer | GDPR 44–49 KVKK 9 | The transfer country is visible in the process; KVKK standard contracts and EU 2021 SCC clauses are ready. | Assessing the transfer, signing the contract, making any required notification. |
| Retention and deletion | GDPR 5(1)(e) KVKK 7 | Retention is defined in the process; records past their period are listed. | Making sure copies held by the provider are deleted. |
| Accountability | GDPR 5(2), 30 | The RoPA is versioned; who changed what and when is visible. Each record keeps the terms it was collected under. | Keeping records current and getting business units’ reviews on time. |
Obligations depend on the system’s risk class and your role. Classification and the obligations below stay with your company; GovernID supports their personal data side. Dates reflect Regulation (EU) 2026/1744 (Digital Omnibus on AI).
| Obligation | Article and application date | How GovernID helps | What stays with your company |
|---|---|---|---|
| AI literacy | Art. 4since 2 Feb 2025 | Out of scope | Taking measures to support staff AI literacy (reframed as a duty to take measures by 2026/1744). |
| Prohibited practices | Art. 5since 2 Feb 2025 | Out of scope | Checking that no system in use falls under a prohibition. |
| Transparency | Art. 50(3), 50(4)since 2 Aug 2026 | Partly Where emotion recognition or biometric categorisation is used, the information can be delivered with the process notice. | Disclosing AI-generated content (deepfakes); making sure information is given at first interaction. |
| Using a high-risk system | Art. 26Annex III: 2 Dec 2027 Annex I: 2 Aug 2028 | Partly The DPIA is built with the provider’s information (26(9)); workers and affected persons are informed through the notice (26(7), 26(11)). | Following instructions for use, assigning human oversight, input data relevance, monitoring, keeping logs for at least six months. |
| Fundamental rights impact assessment (FRIA) | Art. 27with Annex III: 2 Dec 2027 | Partly Under 2026/1744 a FRIA may cross-refer to or include parts of the DPIA (27(4)); the DPIA in GovernID can serve this. | Carrying out the FRIA. Applies to public bodies, private entities providing public services, and deployers using high-risk systems for creditworthiness or life/health insurance pricing. |
2
Four documents and one habit. All rest on the same record, the process in your RoPA; when one changes, the others follow from it.
Business units confirm their processes regularly through Process Owner Reviews: “Same as record” or “Different from record”. If a team has started using a new AI tool, this is where it shows up first.
Transparency in practice
These steps are good practice. Under the AI Act the duty to disclose interaction with AI sits with the system’s provider (Art. 50(1)); information is given at the latest at first interaction (Art. 50(5)). On the personal data side, GDPR Art. 13–14 applies in every case.
List every point where people meet the AI.
GovernID
Each touchpoint is a process in the RoPA; the service shows as a data recipient, a built-in feature on the storage location.
Your company
Identifying the touchpoints.
Tell people they are dealing with AI in the first message.
GovernID
The notice is shown at collection, in the form’s language.
Your company
The first message in the chat or interface.
Repeat it for complaints and money matters.
GovernID
In the Privacy Center individuals see their records, withdraw consent where processing relies on it, and flag a record that is not theirs.
Your company
Handing over to a person, re-informing, offering a channel to object.
A reviewer checks the answer and can stop it.
Out of scope
Your company
Human oversight and staff training (AI Act Art. 4; for high-risk, Art. 26(2)).
Recheck the notice and training when the use changes.
GovernID
Process Owner Reviews raise “Different from record”; the updated notice reaches your forms.
Your company
Assessing and approving the change.
3
Visibility comes from keeping records, not from watching network traffic. Once an AI use is recorded as a process in GovernID, five questions are answered on one screen. AI comes in two ways: as a separate service (data recipient) or inside a system you already use (data storage location).
| Process | Where the AI is | Country | Status |
|---|---|---|---|
| Pre-classification of customer requests | Data recipient: AI service A | IE | Same as record |
| Summarising candidate CVs | Data storage location: HR software (has AI feature) | US | Different from record |
| Transcribing call recordings | Data storage location: Contact centre software (has AI feature) | IE | Same as record |
Yes, if personal data is entered into it. That is a processing activity and should be recorded as a process with purpose, legal basis, recipient and transfer country (GDPR Art. 30). If no personal data may be entered, writing that down as a rule and confirming it through reviews is also a record.
Yes, where the output of the system is used in the EU, it applies to providers and deployers outside the EU too (Art. 2(1)(c)). Obligations depend on the risk class and your role; that assessment is made inside your company.
Yes. Regulation (EU) 2026/1744 set 2 December 2027 for Annex III high-risk systems and 2 August 2028 for systems tied to Annex I products. Prohibitions and AI literacy have applied since 2 February 2025, transparency obligations since 2 August 2026.
No, but they overlap. A DPIA assesses risks to personal data, a FRIA the impact on fundamental rights. Regulation 2026/1744 made it explicit that a FRIA may cross-refer to or include relevant parts of the DPIA (Art. 27(4)). The DPIA you build in GovernID can serve that.
Under GDPR it can be, but it is not the default. EDPB Opinion 28/2024 details the three-step test (legitimate interest, necessity, balancing) for AI models. The basis you choose is written into the process in GovernID and carried into the notice.
The Turkish law has no AI-specific provision; Law No. 6698 applies to AI use as it is. The authority published AI recommendations in 2021 and a 15-question guide on generative AI and personal data in November 2025. Türkiye’s Medium-Term Programme (2027–2029) targets the first quarter of 2027 for national AI rules aligned with the EU.
No. GovernID manages the personal data side of AI use: process record, legal basis, notice, consent, DPIA and data recipients. Model inventory, risk classification and bias monitoring are outside its scope.
Official sources: Regulation (EU) 2024/1689 (OJ L, 12.7.2024) · Regulation (EU) 2026/1744 (OJ L, 24.7.2026) · Regulation (EU) 2016/679 · Law No. 6698 (KVKK) · EDPB Opinion 28/2024 · KVKK Authority, Guide on Generative AI and Personal Data (Nov 2025)
In the demo we define one AI use as a process and show how the DPIA, notice and data recipient record come from the same place.