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.

Key takeaways

What you need to know about GDPR

ExtraterritorialIt applies outside the EU when you offer goods or services to, or monitor, people in the EU.
AccountabilityYou must be able to prove compliance, not only comply.
Lawful basisEvery processing activity needs one of six lawful bases.
72 hoursReportable breaches go to the authority within 72 hours.
OverlapISO 27701 and India's DPDP Act cover much of the same ground.

Who needs to comply with GDPR?

GDPR is law, so the question is whether it applies to you.

Organisations established in the EUAny processing of personal data in the context of an EU establishment.
Non-EU companies selling to the EUOffering goods or services to people in the EU.
Companies tracking EU usersMonitoring behaviour, such as analytics or ad targeting.
Processors for EU clientsSaaS and service providers processing on a controller's behalf.
Groups with EU subsidiariesIntra-group transfers need Chapter V safeguards.

QULDEX helps here first: the readiness check shows where you stand before you commit budget.

What the law requires

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.

Art. 5 Principles

7 principles

Lawfulness, purpose limitation, minimisation, accuracy, storage limitation, security, accountability.

In QULDEX: Each principle mapped to evidence
Art. 6–9 Basis

Lawful basis

Six bases, consent conditions, children and special categories.

In QULDEX: Lawful basis per processing activity
Art. 12–22 Rights

8 rights

Information, access, rectification, erasure, restriction, portability, objection, automated decisions.

In QULDEX: Request log with deadlines
Art. 24–39 Duties

Accountability

By design, processors, ROPA, security, breaches, DPIAs, DPO.

In QULDEX: ROPA and DPIAs linked
Art. 44–49 Transfers

International transfers

Adequacy, SCCs, BCRs and derogations.

In QULDEX: Transfer register with TIAs
Art. 77–84 Remedies

Enforcement

Complaints, compensation and fines.

In QULDEX: Audit trail ready for regulators
Art. 42 Optional

Certification

Approved schemes can demonstrate compliance.

In QULDEX: Evidence reused for ISO 27701
Article explorer

Which 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.

99articles in 11 chapters
7principles
8individual rights
72 hbreach notification

Showing up to 6 per group. Search, filter, or open a group to see all 36.

Principles 7

  1. Art. 5(1)(a)Lawfulness, fairness and transparency

    Process 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.

  2. Art. 5(1)(b)Purpose limitation

    Collect 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.

  3. Art. 5(1)(c)Data minimisation

    Keep 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.

  4. Art. 5(1)(d)Accuracy

    Keep 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.

  5. Art. 5(1)(e)Storage limitation

    Keep 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

  6. Art. 5(1)(f)Integrity and confidentiality

    Protect 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

  7. Art. 5(2)Accountability

    Be 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

  1. Art. 6Lawful basis for processing

    Rely 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

  2. Art. 7Conditions for consent

    Consent 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

  3. Art. 8Children's consent online

    Get 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

  4. Art. 9Special category data

    Processing 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

  1. Art. 12–14Transparency and privacy notices

    Tell 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

  2. Art. 15Right of access

    Give 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

  3. Art. 16Right to rectification

    Correct 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

  4. Art. 17Right to erasure

    Erase 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

  5. Art. 18Right to restriction

    Restrict 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.

  6. Art. 20Right to data portability

    Give 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.

  7. Art. 21Right to object

    Stop 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.

  8. Art. 22Automated decision-making

    People 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

  1. Art. 24Responsibility of the controller

    Put 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.

  2. Art. 25Data protection by design and by default

    Build 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

  3. Art. 28Processors

    Use 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

  4. Art. 30Records of processing activities

    Keep written records of processing (ROPA).

    In QULDEXROPA entries link to systems, vendors and transfers.

    Typical evidence
    ROPA
    Maps to
    ISO 27001 A.5.9

  5. Art. 32Security of processing

    Apply 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)

  6. Art. 33Breach notification to the authority

    Notify 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)

  7. Art. 34Breach communication to individuals

    Tell 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

  8. Art. 35Data protection impact assessment

    Assess high-risk processing before it starts.

    In QULDEXDPIAs are templated, versioned and linked to processing activities.

    Typical evidence
    DPIAs
    Maps to
    DPDP Sec. 10

  9. Art. 37–39Data protection officer

    Appoint 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

  1. Art. 44General principle for transfers

    Transfer 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

  2. Art. 45Adequacy decisions

    Transfer 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.

  3. Art. 46Appropriate safeguards

    Use safeguards such as Standard Contractual Clauses, with a transfer impact assessment.

    In QULDEXTransfers record their mechanism and assessment.

    Typical evidence
    SCCs, transfer impact assessments

  4. Art. 47Binding corporate rules

    Use 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.

  5. Art. 49Derogations

    Rely 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

  1. Art. 77Right to lodge a complaint

    People 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.

  2. Art. 82Right to compensation

    People 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.

  3. Art. 83Administrative fines

    Fines 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.

Article numbers follow Regulation (EU) 2016/679. Summaries are QULDEX paraphrases, not legal advice; the official text on EUR-Lex is the authority.

Compliance path

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.

  1. Map personal data and build your ROPA

    List processing activities, data categories, systems, recipients and retention for each.

  2. Set lawful bases and update notices

    Record the lawful basis per purpose, fix consent where needed, and rewrite privacy notices.

  3. Build rights request handling

    Set up intake, identity checks, deadlines and response templates for all eight rights.

  4. Fix processor contracts and transfers

    Sign DPAs with every processor, and put SCCs and transfer impact assessments in place.

    1–3 monthsRisk register →
  5. Secure data and prepare for breaches

    Apply Article 32 security and a breach process that can meet the 72-hour deadline.

  6. DPIAs and privacy by design

    Run DPIAs for high-risk processing and build privacy reviews into projects.

  7. Monitor and audit

    MonthlyRights requests and breach log review
    YearlyROPA and notice refresh
    YearlyInternal or DPO audit

Durations are typical planning ranges from QULDEX delivery, not legal requirements.

Accountability records

Which documents does GDPR expect?

Regulators ask for these first when they investigate. Together they show accountability under Article 5(2).

Document or recordArticleWhere it lives in QULDEX
Records of processing activities (ROPA)Art. 30Evidence vault
Privacy noticesArt. 13–14Evidence vault · policy library
Lawful basis register and legitimate interests assessmentsArt. 6Risk register
Consent recordsArt. 7Evidence vault
Data protection impact assessmentsArt. 35Risk register
Data processing agreementsArt. 28Vendor register
Transfer mechanisms and impact assessmentsArt. 44–49Vendor register
Breach register (including non-reported breaches)Art. 33(5)CAPA automation
Rights request logArt. 12–22Evidence vault
DPO appointment and reportsArt. 37–39Program setup

Article references point to the main source of each duty; others may also apply.

Time and cost

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

Data mapping and ROPA3–6 wk
Bases and notices2–4 wk
Rights handling2–4 wk
Contracts and transfers1–3 mo
Security and breach1–3 mo

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
Readiness check · 2 minutes

How ready are you for a GDPR review?

Regulators and enterprise customers check these eight things first. Nothing you enter leaves this page.

Art. 30Do you have a current record of processing activities?
Art. 6Is a lawful basis recorded for every purpose?
Art. 13Are privacy notices complete and up to date?
Art. 15Can you answer access requests within one month?
Art. 28Do all processors have signed DPAs?
Art. 46Are non-EEA transfers covered by SCCs or adequacy?
Art. 33Can you notify a breach within 72 hours?
Art. 35Have you run DPIAs for high-risk processing?
Crosswalk

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

GDPRDPDP Act 2023
ScopePersonal data, digital and paperDigital personal data only
Lawful groundsSix lawful basesConsent or specified legitimate uses
Special categoriesExtra rules for sensitive dataNo separate category
Breach reporting72 hours to the authority, if reportableEvery breach to the Board and affected people
Maximum penalty€20m or 4% of global turnoverUp to ₹250 crore per breach
RegulatorNational supervisory authoritiesData Protection Board of India
In QULDEXQULDEX maps each process to both laws, so global companies run one privacy programme.

Privacy crosswalk

GDPRISO 27701DPDP Act 2023SOC 2 PrivacyShared evidence
Art. 13–14 NoticesController noticesSec. 5P1.1Privacy notices
Art. 6–7 Basis and consentLawful basis, consentSec. 4, 6P2.1Consent records
Art. 15–22 RightsRights of PII principalsSec. 11–14P5.1–P5.2Request log
Art. 25 By designPrivacy by designSec. 8—Design reviews
Art. 28 ProcessorsContracts with processorsSec. 8(2)P6.4DPAs
Art. 30 ROPARecords of processing——ROPA
Art. 32 SecuritySecurity for PIISec. 8(5)CC6Security evidence
Art. 33–34 BreachesBreach notificationSec. 8(6)P6.6Breach register
Art. 35 DPIAImpact assessmentSec. 10—DPIAs
Art. 44–49 TransfersTransfersSec. 16—Transfer register

Indicative mapping for planning, not legal advice. The full crosswalk is in the QULDEX control library.

Where QULDEX fits

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.

  1. Data mapBuild the ROPAROPA linked to systems, vendors and transfers
  2. Basis and noticesSet lawful basesBasis per purpose with review dates
  3. RightsAnswer requestsRequest log with deadlines and evidence
  4. VendorsSign DPAs and SCCsVendor register with contracts and TIAs
  5. BreachesMeet 72 hoursBreach log with a running clock
  6. AuditProve accountabilityControlled, logged evidence for regulators and customers
Without one systemWith QULDEX
ROPA in a spreadsheet nobody updatesROPA linked to systems and vendors
Rights requests in shared inboxesLogged requests with deadlines
DPAs scattered across drivesContracts linked to each processor
Separate work for GDPR, DPDP and ISO 27701One programme mapped to all three
10+years of audit delivery500+audits deliveredBoth sidesof the audit on one platformRBACand a full audit trail on every action
FAQ

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.

Sources

References

  1. Regulation (EU) 2016/679 (General Data Protection Regulation), official text. eur-lex.europa.eu
  2. European Data Protection Board guidelines (breach notification, DPIA, transfers). edpb.europa.eu
  3. European Commission, Standard Contractual Clauses (2021/914). commission.europa.eu
  4. Digital Personal Data Protection Act, 2023 (India). meity.gov.in
  5. ISO/IEC 27701:2025. iso.org

Reviewed by

Manisha Dubey

Framework reviewer · QULDEX

Reviewed this page against Regulation (EU) 2016/679 and EDPB guidance: principles, rights, accountability records and the privacy crosswalk.

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.

Schedule
Book a Demo