Regulation · European Union and EEA
GDPR
At a glance
- Jurisdiction
- European Union and EEA
- Supervisory authority
- National data protection authorities, coordinated by the EDPB
- In force
- Applies since 25 May 2018
- Official name
- Regulation (EU) 2016/679
What the GDPR asks of you, article by article
How GovernID fits: The GDPR asks you to know your processing, explain it to people and prove it. GovernID builds that proof into collection. Your RoPA follows Art. 30, privacy notices are generated from it, and each record collected through GovernID carries the notice, consent, legal basis and retention period that applied on the day it arrived. Companies registered in the EU use GovernID’s servers in the EU.
Recent developments: The GDPR’s obligations have not changed since 2016. Regulation (EU) 2025/2518 adds procedural rules for cross-border cases between authorities and applies from 2 April 2027. The European Commission’s Digital Omnibus proposal would amend parts of the GDPR, and is still in the legislative process.
| Requirement | Article | What GovernID does | What stays with you |
|---|---|---|---|
| Principles and accountability. Process lawfully, fairly and transparently, for specified purposes, with only the data needed, kept accurate and no longer than necessary, and be able to show it. | Art. 5(1), 5(2) | Each processing activity in your RoPA records its purpose, data categories, legal basis and retention period. Every field is classified before the first record arrives, and each record keeps the terms it was collected under, so you can show compliance record by record. | Deciding purposes and judging what is necessary. |
| Lawful basis. Every processing needs one of six bases: consent, contract, legal obligation, vital interests, public task or legitimate interests. | Art. 6 | Legal bases come ready in the Privacy Taxonomy. Each activity records its basis, and each record keeps the basis that applied on the day it arrived. | The legal assessment, including the balancing test for legitimate interests. |
| Conditions for consent. You must be able to show that consent was given, the request must be clear and separate from other matters, and withdrawing must be as easy as giving it. | Art. 7, Art. 4(11) | The approved consent text is shown at collection, one purpose per box, never pre-ticked, separate from the privacy notice. GovernID keeps the version on the record with the dates consent was given and withdrawn. People withdraw in the Privacy Center, and the request is tracked until handled. | Deciding when consent is the right basis, and approving the text. |
| Special categories of data. Processing is prohibited unless one of the listed exceptions applies. | Art. 9 | Special category fields are marked in the RoPA and at collection, and GovernID recommends a DPIA for activities that use them. | Choosing the exception and the safeguards. |
| Transparency. Give people concise, clear information about the controller, purposes, legal basis, recipients, transfers, retention and their rights, at the time data is collected. | Art. 12(1), Art. 13, Art. 14 | Privacy notices are generated from the RoPA with these items, in nine languages, and served as a link at the moment of collection. Each record keeps the notice version the person saw. | Approving the notice and keeping it accurate. |
| Data subject rights. Access, rectification, erasure, restriction, portability, objection and safeguards around automated decisions. | Art. 15–22 | In the Privacy Center, people see the records that contain their verified contact details, withdraw consent, object to processing and get an instant preliminary report. DSAR Automation finds every record of a person across connected collection points, and recipients are recorded for each activity (Art. 19). | Handling access, rectification, erasure, restriction and portability requests, and requests made through other channels. |
| Response time. Reply to requests without undue delay and within one month, extendable by two further months where needed. | Art. 12(3) | Requests made in the Privacy Center reach your team at once and consent withdrawals are tracked until handled. | Deciding on each request and replying in time. |
| Data protection by design and by default. Build data protection into how processing is designed, and collect only what each purpose needs. | Art. 25 | Forms connect to GovernID so the notice, consent and classification are set before collection starts. Each field is linked to a data category approved for that activity. | Designing systems and limiting data beyond the forms connected to GovernID. |
| Processors. Use processors that give sufficient guarantees, under a contract with the terms the GDPR lists. | Art. 28 | Processors and other recipients are recorded in each activity and shown as processing flows. | Choosing processors and signing the contracts. |
| Records of processing activities. Keep a written record of each activity with the details Art. 30 lists, and make it available to the authority on request. | Art. 30 | The RoPA is modelled on Art. 30. Process owners confirm their activities and every confirmation is logged. Compliance Reporting exports the record with its version history. | Keeping the record complete for processing outside GovernID. |
| Security of processing. Apply technical and organisational measures appropriate to the risk. | Art. 32 | Safeguards are recorded for each activity and storage location, and Corporate Privacy Memory keeps how each activity looked on any past date. | Implementing and testing the measures. |
| Breach notification. Notify the supervisory authority within 72 hours where feasible, inform people when the risk to them is high, and document every breach. | Art. 33, Art. 34 | Breach Impact Analysis shows which activities used the affected system, which data was kept there and which safeguards applied. | Assessing the breach, notifying and documenting it. |
| DPIA. Assess processing likely to result in a high risk before it starts, and consult the authority when risk remains high. | Art. 35, Art. 36 | GovernID recommends a DPIA for activities with special category data or transfers abroad. The assessment opens with the facts from your RoPA, ends with a risk map and report, and can be exported as PDF and JSON. | The risk judgement and any prior consultation. |
| Data protection officer. Appoint a DPO where the GDPR requires it. | Art. 37–39 | Your DPO works from one RoPA, sees which activities are confirmed and which have changed, and can export reports for management. | Appointing the DPO. |
| Transfers outside the EEA. Transfer only under an adequacy decision, appropriate safeguards such as standard contractual clauses or binding corporate rules, or a listed derogation. | Art. 44–49 | Transfers are recorded in each activity, GovernID recommends a DPIA when data is sent abroad, and Legal Text Management generates the European Commission's standard contractual clauses from the activity. | Choosing the transfer tool and signing it. |
| Storage limitation and erasure. Keep data no longer than needed and erase it when the grounds end. | Art. 5(1)(e), Art. 17 | Retention periods are set in the RoPA. Each record gets its own end date, records past it can be listed at any time, and GovernID's own copy is marked for destruction when its period ends. | Deleting the data in your own systems. |
This page summarises the law to show where GovernID supports your work. It is not legal advice; your legal counsel decides how the law applies to your company.
Right of access: what a response must include
Under Article 15 GDPR, an individual can ask whether you process their personal data and, if you do, receive a copy and specific information about that processing.
| The response must include | Article |
|---|---|
| Confirmation that personal data is or is not being processed | Art. 15(1) |
| A copy of the personal data | Art. 15(3) |
| Purposes of processing | Art. 15(1)(a) |
| Categories of personal data | Art. 15(1)(b) |
| Recipients or categories of recipients, especially in third countries | Art. 15(1)(c) |
| Retention period, or the criteria used to set it | Art. 15(1)(d) |
| Rights to rectification, erasure, restriction and objection | Art. 15(1)(e) |
| Right to lodge a complaint with a supervisory authority | Art. 15(1)(f) |
| Source of the data, if not collected from the individual | Art. 15(1)(g) |
| Automated decision-making, including profiling: the logic, significance and consequences | Art. 15(1)(h) |
| Safeguards for transfers to third countries | Art. 15(2) |
Deadline: without undue delay and within one month. Extension: two further months for complex or numerous requests, notified within the first month (Art. 12(3)). Fee: free; a reasonable fee for further copies or manifestly unfounded or excessive requests (Art. 12(5), 15(3)).
What GovernID does: Every record collected through GovernID is stored with its purpose, legal basis, the notice version shown, consent scope, retention end date and collection point. These are the answers an access response has to give. In the Privacy Center, the individual sees their records instantly as a preliminary report and can export it, and your team finds a person's records across every GovernID collection point with PII Search. Recipients are recorded per processing activity in the RoPA, so you can name them, as the Court of Justice requires in C-154/21.
What stays with you: Data held in systems outside GovernID and a copy of it, the formal response letter, identity checks beyond the verified e-mail, redaction of third-party data, and tracking the deadline.
Rectification, erasure and objection are separate rights and are handled separately; this section covers access only.
What manual handling costs: Gartner estimates that manually fulfilling a single subject rights request costs organisations around US$1,500 (Market Guide for Subject Rights Request Automation, 2021).
Frequently asked questions
Does the GDPR apply to companies outside the EU?
Yes, when they offer goods or services to people in the EEA or monitor their behaviour there (Art. 3(2)). Such companies usually need an EU representative (Art. 27).
Is the RoPA mandatory for every company?
Art. 30(5) gives a limited exemption to organisations with fewer than 250 employees, but it does not apply when processing is not occasional, involves special category data or is likely to result in a risk. In practice most companies keep one.
Where is our data hosted?
Companies registered in the EU use GovernID’s servers in the EU, and backups stay in the EU too.
Can we use the same GovernID setup for KVKK and the GDPR?
Each company works under the law of the country it is registered in. A group with companies in Turkey and the EU uses a separate portal for each.
Is this page legal advice?
No. It summarises the regulation to show where GovernID supports your work. Your legal counsel decides how it applies to your company.
The law and its regulations: official sources
Links go to the issuing authority's own website. Some government sites restrict access from outside their country.
- Regulation (EU) 2016/679 – EUR-Lex, all EU languages
- Regulation (EU) 2025/2518: procedural rules for cross-border GDPR enforcement (applies from 2 April 2027) – EUR-Lex, all EU languages