Regulation · Privacy · EU law
GDPR compliance: principles, rights and accountability requirements
The General Data Protection Regulation (EU) 2016/679 is the EU law on personal data, applying since 25 May 2018 to organisations in the EU and to those outside it that target or monitor people in the EU. It sets 7 principles, 6 lawful bases and 8 rights, with fines of up to €20 million or 4% of global turnover.
What you need to know about GDPR
Who needs to comply with GDPR?
GDPR is law, so the question is whether it applies to you.
QULDEX helps here first: the readiness check shows where you stand before you commit budget.
What does GDPR require?
GDPR requires you to process personal data under the seven principles, with a lawful basis, while respecting individuals' rights, securing the data and proving all of it. Controllers carry most duties; processors have their own.
7 principles
Lawfulness, purpose limitation, minimisation, accuracy, storage limitation, security, accountability.
In QULDEX: Each principle mapped to evidenceLawful basis
Six bases, consent conditions, children and special categories.
In QULDEX: Lawful basis per processing activity8 rights
Information, access, rectification, erasure, restriction, portability, objection, automated decisions.
In QULDEX: Request log with deadlinesAccountability
By design, processors, ROPA, security, breaches, DPIAs, DPO.
In QULDEX: ROPA and DPIAs linkedInternational transfers
Adequacy, SCCs, BCRs and derogations.
In QULDEX: Transfer register with TIAsEnforcement
Complaints, compensation and fines.
In QULDEX: Audit trail ready for regulatorsCertification
Approved schemes can demonstrate compliance.
In QULDEX: Evidence reused for ISO 27701Which GDPR articles matter most?
GDPR has 99 articles. These 36 carry the obligations most organisations work on day to day, grouped by theme. Select any article to see what it requires, typical evidence and the matching DPDP Act section.
Showing up to 6 per group. Search, filter, or open a group to see all 36.
Principles 7
Art. 5(1)(a)Lawfulness, fairness and transparencyProcess personal data lawfully, fairly and in a transparent way.
In QULDEXQULDEX gives this obligation an owner, a review cycle and an evidence request, and reuses it for ISO 27701 and DPDP.
Art. 5(1)(b)Purpose limitationCollect data for specified, explicit and legitimate purposes and don't reuse it incompatibly.
In QULDEXQULDEX gives this obligation an owner, a review cycle and an evidence request, and reuses it for ISO 27701 and DPDP.
Art. 5(1)(c)Data minimisationKeep personal data adequate, relevant and limited to what the purpose needs.
In QULDEXQULDEX gives this obligation an owner, a review cycle and an evidence request, and reuses it for ISO 27701 and DPDP.
Art. 5(1)(d)AccuracyKeep personal data accurate and up to date.
In QULDEXQULDEX gives this obligation an owner, a review cycle and an evidence request, and reuses it for ISO 27701 and DPDP.
Art. 5(1)(e)Storage limitationKeep data in identifiable form no longer than necessary.
In QULDEXQULDEX gives this obligation an owner, a review cycle and an evidence request, and reuses it for ISO 27701 and DPDP.
- Typical evidence
- Retention schedule
Art. 5(1)(f)Integrity and confidentialityProtect personal data with appropriate security.
In QULDEXQULDEX gives this obligation an owner, a review cycle and an evidence request, and reuses it for ISO 27701 and DPDP.
- Maps to
- ISO 27001 A.5.34
Art. 5(2)AccountabilityBe able to demonstrate compliance with all the principles.
In QULDEXEvery obligation has an owner and evidence, so accountability is provable.
- Typical evidence
- Records of processing, policies
Lawful basis 4
Art. 6Lawful basis for processingRely on one of six lawful bases: consent, contract, legal obligation, vital interests, public task or legitimate interests.
In QULDEXEach processing activity records its lawful basis.
- Typical evidence
- Lawful basis register, legitimate interests assessments
- Maps to
- DPDP Sec. 4
Art. 7Conditions for consentConsent must be freely given, specific, informed and unambiguous, and as easy to withdraw as to give.
In QULDEXQULDEX gives this obligation an owner, a review cycle and an evidence request, and reuses it for ISO 27701 and DPDP.
- Typical evidence
- Consent records
- Maps to
- DPDP Sec. 6
Art. 8Children's consent onlineGet parental consent for information society services offered to children below the national age (13–16).
In QULDEXQULDEX gives this obligation an owner, a review cycle and an evidence request, and reuses it for ISO 27701 and DPDP.
- Maps to
- DPDP Sec. 9
Art. 9Special category dataProcessing health, biometric, religious and other special data needs an extra condition.
In QULDEXQULDEX gives this obligation an owner, a review cycle and an evidence request, and reuses it for ISO 27701 and DPDP.
- Typical evidence
- Special category register
Individual rights 8
Art. 12–14Transparency and privacy noticesTell people what you process, why, how long and their rights, in clear language.
In QULDEXQULDEX gives this obligation an owner, a review cycle and an evidence request, and reuses it for ISO 27701 and DPDP.
- Typical evidence
- Privacy notices
- Maps to
- DPDP Sec. 5
Art. 15Right of accessGive people a copy of their data and information about processing, usually within one month.
In QULDEXRequests are logged with deadlines and response evidence.
- Typical evidence
- Request log
- Maps to
- DPDP Sec. 11
Art. 16Right to rectificationCorrect inaccurate personal data on request.
In QULDEXQULDEX gives this obligation an owner, a review cycle and an evidence request, and reuses it for ISO 27701 and DPDP.
- Maps to
- DPDP Sec. 12
Art. 17Right to erasureErase data when grounds apply, such as withdrawn consent or no longer needed.
In QULDEXQULDEX gives this obligation an owner, a review cycle and an evidence request, and reuses it for ISO 27701 and DPDP.
- Typical evidence
- Deletion records
- Maps to
- DPDP Sec. 12
Art. 18Right to restrictionRestrict processing while accuracy or objections are checked.
In QULDEXQULDEX gives this obligation an owner, a review cycle and an evidence request, and reuses it for ISO 27701 and DPDP.
Art. 20Right to data portabilityGive people their data in a structured, machine-readable format.
In QULDEXQULDEX gives this obligation an owner, a review cycle and an evidence request, and reuses it for ISO 27701 and DPDP.
Art. 21Right to objectStop processing based on legitimate interests or for direct marketing when people object.
In QULDEXQULDEX gives this obligation an owner, a review cycle and an evidence request, and reuses it for ISO 27701 and DPDP.
Art. 22Automated decision-makingPeople can refuse solely automated decisions with legal or similar significant effects, with exceptions.
In QULDEXQULDEX gives this obligation an owner, a review cycle and an evidence request, and reuses it for ISO 27701 and DPDP.
- Maps to
- ISO 42001 A.9
Accountability 9
Art. 24Responsibility of the controllerPut appropriate measures in place and be able to show them.
In QULDEXQULDEX gives this obligation an owner, a review cycle and an evidence request, and reuses it for ISO 27701 and DPDP.
Art. 25Data protection by design and by defaultBuild privacy into systems and default to the least data needed.
In QULDEXQULDEX gives this obligation an owner, a review cycle and an evidence request, and reuses it for ISO 27701 and DPDP.
- Typical evidence
- Design reviews
- Maps to
- ISO 27001 A.8.25
Art. 28ProcessorsUse only processors with sufficient guarantees, under a contract with required terms.
In QULDEXEach processor record links its DPA and assessment.
- Typical evidence
- Data processing agreements
- Maps to
- DPDP Sec. 8(2)SOC 2 P6.4
Art. 30Records of processing activitiesKeep written records of processing (ROPA).
In QULDEXROPA entries link to systems, vendors and transfers.
- Typical evidence
- ROPA
- Maps to
- ISO 27001 A.5.9
Art. 32Security of processingApply appropriate technical and organisational security measures.
In QULDEXSecurity controls are reused from ISO 27001 when you run one.
- Typical evidence
- Security controls evidence
- Maps to
- ISO 27001 Annex ADPDP Sec. 8(5)
Art. 33Breach notification to the authorityNotify the supervisory authority within 72 hours of becoming aware of a reportable breach.
In QULDEXBreaches are logged with the 72-hour clock and decisions.
- Typical evidence
- Breach register
- Maps to
- DPDP Sec. 8(6)
Art. 34Breach communication to individualsTell affected people without undue delay when the breach is high risk.
In QULDEXQULDEX gives this obligation an owner, a review cycle and an evidence request, and reuses it for ISO 27701 and DPDP.
- Typical evidence
- Notification records
Art. 35Data protection impact assessmentAssess high-risk processing before it starts.
In QULDEXDPIAs are templated, versioned and linked to processing activities.
- Typical evidence
- DPIAs
- Maps to
- DPDP Sec. 10
Art. 37–39Data protection officerAppoint a DPO when required and support their independence.
In QULDEXQULDEX gives this obligation an owner, a review cycle and an evidence request, and reuses it for ISO 27701 and DPDP.
- Typical evidence
- DPO appointment record
International transfers 5
Art. 44General principle for transfersTransfer personal data outside the EEA only under Chapter V conditions.
In QULDEXQULDEX gives this obligation an owner, a review cycle and an evidence request, and reuses it for ISO 27701 and DPDP.
- Maps to
- DPDP Sec. 16
Art. 45Adequacy decisionsTransfer freely to countries the Commission has found adequate.
In QULDEXQULDEX gives this obligation an owner, a review cycle and an evidence request, and reuses it for ISO 27701 and DPDP.
Art. 46Appropriate safeguardsUse safeguards such as Standard Contractual Clauses, with a transfer impact assessment.
In QULDEXTransfers record their mechanism and assessment.
- Typical evidence
- SCCs, transfer impact assessments
Art. 47Binding corporate rulesUse approved BCRs for transfers within a group.
In QULDEXQULDEX gives this obligation an owner, a review cycle and an evidence request, and reuses it for ISO 27701 and DPDP.
Art. 49DerogationsRely on narrow exceptions, such as explicit consent, only when no other mechanism applies.
In QULDEXQULDEX gives this obligation an owner, a review cycle and an evidence request, and reuses it for ISO 27701 and DPDP.
Enforcement 3
Art. 77Right to lodge a complaintPeople can complain to a supervisory authority.
In QULDEXQULDEX gives this obligation an owner, a review cycle and an evidence request, and reuses it for ISO 27701 and DPDP.
Art. 82Right to compensationPeople can claim compensation for damage caused by infringements.
In QULDEXQULDEX gives this obligation an owner, a review cycle and an evidence request, and reuses it for ISO 27701 and DPDP.
Art. 83Administrative finesFines of up to €20 million or 4% of worldwide annual turnover, whichever is higher, for the most serious infringements.
In QULDEXQULDEX gives this obligation an owner, a review cycle and an evidence request, and reuses it for ISO 27701 and DPDP.
Nothing matches that search.
Article numbers follow Regulation (EU) 2016/679. Summaries are QULDEX paraphrases, not legal advice; the official text on EUR-Lex is the authority.
How do you become GDPR compliant?
There is no GDPR certificate to obtain. You map your data, put the legal basis, rights and security processes in place, and keep evidence that they work. A first programme usually takes 3 to 9 months.
Map personal data and build your ROPA
List processing activities, data categories, systems, recipients and retention for each.
Set lawful bases and update notices
Record the lawful basis per purpose, fix consent where needed, and rewrite privacy notices.
Build rights request handling
Set up intake, identity checks, deadlines and response templates for all eight rights.
Fix processor contracts and transfers
Sign DPAs with every processor, and put SCCs and transfer impact assessments in place.
Secure data and prepare for breaches
Apply Article 32 security and a breach process that can meet the 72-hour deadline.
DPIAs and privacy by design
Run DPIAs for high-risk processing and build privacy reviews into projects.
Monitor and audit
MonthlyRights requests and breach log reviewYearlyROPA and notice refreshYearlyInternal or DPO audit
Durations are typical planning ranges from QULDEX delivery, not legal requirements.
Which documents does GDPR expect?
Regulators ask for these first when they investigate. Together they show accountability under Article 5(2).
| Document or record | Article | Where it lives in QULDEX |
|---|---|---|
| Records of processing activities (ROPA) | Art. 30 | Evidence vault |
| Privacy notices | Art. 13–14 | Evidence vault · policy library |
| Lawful basis register and legitimate interests assessments | Art. 6 | Risk register |
| Consent records | Art. 7 | Evidence vault |
| Data protection impact assessments | Art. 35 | Risk register |
| Data processing agreements | Art. 28 | Vendor register |
| Transfer mechanisms and impact assessments | Art. 44–49 | Vendor register |
| Breach register (including non-reported breaches) | Art. 33(5) | CAPA automation |
| Rights request log | Art. 12–22 | Evidence vault |
| DPO appointment and reports | Art. 37–39 | Program setup |
Article references point to the main source of each duty; others may also apply.
How long does GDPR compliance take and what drives the effort?
A first programme usually takes 3 to 9 months, then it runs continuously. Effort grows with the number of processing activities, vendors, transfers and high-risk uses.
Where the time goes
Bars show the upper end of each range on one scale (6 months = full width).
What changes the effort
- Processing activities: each one needs a ROPA entry, basis and notice
- Vendors: every processor needs a DPA and assessment
- Transfers: non-EEA transfers need SCCs and impact assessments
- High-risk processing: DPIAs for profiling, health or large-scale monitoring
- Existing ISO 27701: a privacy management system covers much of the work
How ready are you for a GDPR review?
Regulators and enterprise customers check these eight things first. Nothing you enter leaves this page.
How GDPR maps to India's DPDP Act, ISO 27701 and SOC 2
GDPR, the DPDP Act and ISO 27701 share most building blocks, so one documented process often serves all three. QULDEX keeps this mapping in its control library.
GDPR vs India's DPDP Act at a glance
| GDPR | DPDP Act 2023 | |
|---|---|---|
| Scope | Personal data, digital and paper | Digital personal data only |
| Lawful grounds | Six lawful bases | Consent or specified legitimate uses |
| Special categories | Extra rules for sensitive data | No separate category |
| Breach reporting | 72 hours to the authority, if reportable | Every breach to the Board and affected people |
| Maximum penalty | €20m or 4% of global turnover | Up to ₹250 crore per breach |
| Regulator | National supervisory authorities | Data Protection Board of India |
| In QULDEX | QULDEX maps each process to both laws, so global companies run one privacy programme. | |
Privacy crosswalk
| GDPR | ISO 27701 | DPDP Act 2023 | SOC 2 Privacy | Shared evidence |
|---|---|---|---|---|
| Art. 13–14 Notices | Controller notices | Sec. 5 | P1.1 | Privacy notices |
| Art. 6–7 Basis and consent | Lawful basis, consent | Sec. 4, 6 | P2.1 | Consent records |
| Art. 15–22 Rights | Rights of PII principals | Sec. 11–14 | P5.1–P5.2 | Request log |
| Art. 25 By design | Privacy by design | Sec. 8 | — | Design reviews |
| Art. 28 Processors | Contracts with processors | Sec. 8(2) | P6.4 | DPAs |
| Art. 30 ROPA | Records of processing | — | — | ROPA |
| Art. 32 Security | Security for PII | Sec. 8(5) | CC6 | Security evidence |
| Art. 33–34 Breaches | Breach notification | Sec. 8(6) | P6.6 | Breach register |
| Art. 35 DPIA | Impact assessment | Sec. 10 | — | DPIAs |
| Art. 44–49 Transfers | Transfers | Sec. 16 | — | Transfer register |
Indicative mapping for planning, not legal advice. The full crosswalk is in the QULDEX control library.
How QULDEX runs GDPR compliance from data map to audit
QULDEX is GDPR compliance and audit management software built from EGV Group's audit delivery, used by the organisation, its DPO and the auditors who test the programme. Pick your role to see who does what.
For organisations running a GDPR programme.
- Data mapBuild the ROPAROPA linked to systems, vendors and transfers
- Basis and noticesSet lawful basesBasis per purpose with review dates
- RightsAnswer requestsRequest log with deadlines and evidence
- VendorsSign DPAs and SCCsVendor register with contracts and TIAs
- BreachesMeet 72 hoursBreach log with a running clock
- AuditProve accountabilityControlled, logged evidence for regulators and customers
For DPOs and privacy consultants.
- Data mapRun the gap assessmentA reusable GDPR gap template
- Basis and noticesAdvise on basesLIAs and DPIAs as templates
- RightsOversee requestsDashboards across request types
- VendorsReview contractsDPA status per vendor
- BreachesDecide on notificationDecision records per breach
- AuditReport to the boardDPO reports from live data
For internal audit and external privacy auditors.
- PlanningAgree scopeScope and ROPA in a standard format
- FieldworkReview evidenceView-only evidence access with download control and an access log
- TestingSample requests and DPAsSampling per obligation
- FindingsRecord gapsFindings per article
- ReportReport resultsTraceable workpapers
- Follow-upTrack fixesFindings into CAPA
Pre-mapped control library
Requirements with owners, test steps and the crosswalk to 50+ frameworks.
Explore →EvidenceSecure evidence vault
Evidence linked to controls and findings, with upload, review and approval history.
Explore →RiskRisk register
Risk assessment and treatment, with decisions traced to the controls they drive.
Explore →FindingsCAPA remediation
Findings from internal and external audits tracked to closure with due dates.
Explore →GDPR questions people ask
Does GDPR apply to companies outside the EU?
Yes, when they offer goods or services to people in the EU or monitor their behaviour, under Article 3(2).
What are the 7 GDPR principles?
Lawfulness, fairness and transparency; purpose limitation; data minimisation; accuracy; storage limitation; integrity and confidentiality; and accountability.
What are the 6 lawful bases under GDPR?
Consent, contract, legal obligation, vital interests, public task and legitimate interests.
How quickly must a GDPR breach be reported?
Within 72 hours of becoming aware of it, to the supervisory authority, unless it is unlikely to result in a risk to people. High-risk breaches must also be communicated to the people affected.
What are the GDPR fines?
Up to €20 million or 4% of worldwide annual turnover, whichever is higher, for the most serious infringements, and up to €10 million or 2% for others.
Is there a GDPR certification?
There is no mandatory certificate. Article 42 allows approved certification schemes, and ISO 27701 is often used to show a governed privacy programme.
Can QULDEX run GDPR alongside DPDP and ISO 27701?
Yes. Processes and evidence are mapped once, and each law or standard keeps its own reporting.
Go deeper on GDPR
DPDP Rules 2025: the compliance timeline
How India's rules compare with GDPR obligations.
blog.quldex.comData privacy topic hub
Every privacy article in one place.
blog.quldex.comEU regulation topic hub
GDPR, NIS2, DORA and AI Act coverage.
blog.quldex.comAudit evidence naming convention
A file-naming scheme that lets auditors sample without asking.
References
- Regulation (EU) 2016/679 (General Data Protection Regulation), official text. eur-lex.europa.eu
- European Data Protection Board guidelines (breach notification, DPIA, transfers). edpb.europa.eu
- European Commission, Standard Contractual Clauses (2021/914). commission.europa.eu
- Digital Personal Data Protection Act, 2023 (India). meity.gov.in
- ISO/IEC 27701:2025. iso.org
Reviewed by
Page history
- : Rebuilt with article explorer, compliance path, GDPR vs DPDP table and readiness check
- : Page first published
Find your GDPR gaps in 15 minutes
Answer a short readiness check and get a gap summary by obligation. No sales call needed to see the result.