GDPR: accountability you can demonstrate, in policies, records and training

For controllers, processors and DPOs that handle personal data of people in the EU and must show a supervisory authority how they meet the Regulation.

30-day trialUnlimited free viewersNo credit card required

GDPR at a glance

Checked against primary sources on 18 October 2026.

Who it applies to

Controllers and processors established in the EU, and those outside it that offer goods or services to, or monitor the behavior of, people in the EU.

Who checks

National data protection supervisory authorities, through complaints, breach notifications, investigations and audits; in the UK, the ICO under the UK GDPR.

How often

No fixed audit cycle; records of processing and other evidence must be produced on request, and breaches are documented as they occur

Current edition

Regulation (EU) 2016/679 as published in OJ L 119, 4.5.2016 (EUR-Lex shows no later consolidated version), 2016-04-27 (applies from 2018-05-25). Free to read.

Dates to know

Dates for GDPR
DateWhat happensStatus
2026-01-01Regulation (EU) 2025/2518 on GDPR cross-border enforcement procedure enters into forceDone
2026-06-19UK: ICO states all data protection provisions of the Data (Use and Access) Act 2025 are in forceDone
2027-04-02Regulation (EU) 2025/2518 appliesScheduled

What GDPR asks you to write down

Each one needs an owner, an approval, and proof it reached the people it covers.

Article 24(1) and 24(2)

Data protection policies

The controller implements measures to ensure and demonstrate compliance, including appropriate data protection policies where proportionate to the processing.

  • Approver, date and version in force
  • Reviews tied to processing changes

Article 30

Records of processing activities

Controllers and processors keep written records of processing, electronic form included, and make them available to the supervisory authority on request.

  • Purposes, categories, recipients and retention
  • Date the record was last updated

Article 32(1) and 32(4)

Security of processing and staff instructions

Appropriate technical and organizational measures protect personal data, and anyone acting under the controller's or processor's authority processes it only on instructions.

  • Security policy and staff instructions
  • Evidence staff received the instructions

Article 33(5)

Personal data breach documentation

Every personal data breach is documented with its facts, effects and remedial action, so the supervisory authority can verify compliance.

  • Facts, effects and remedial action
  • Date discovered and whether notified

Article 35

Data protection impact assessment

Before processing likely to result in high risk to individuals, the controller assesses its impact on the protection of personal data.

  • Assessment per high-risk processing activity
  • DPO advice and decision taken

Article 39(1)(b)

DPO monitoring, awareness and training

Where a DPO is designated, they monitor compliance with the GDPR and internal policies, including assignment of responsibilities, staff awareness and training, and related audits.

  • Training records for staff in processing roles
  • Responsibilities assigned under each policy

Citations are to the standard or regulation; wording is ours.

What gets asked for on the day

What reviewers sample about these documents and the people they cover.

Records of processing

Authorities typically ask for the Article 30 record first, then test whether it reflects actual processing, recipients, transfers and retention.

Policies behind accountability

Investigators request data protection policies and evidence they were approved, communicated and applied, under Articles 5(2) and 24.

Breach register

After an incident, authorities ask for the internal breach documentation required by Article 33(5), including breaches that were never notified.

Awareness and training

They ask how staff were told about policies and instructions, often through DPO monitoring records and training logs.

The policy and acknowledgment layer for GDPR.

Write each policy, send it through approval, and send it to the people it covers. Each acknowledgment is recorded by name, with the version, the date and the time.

When a policy changes, the new version is approved, its Editor sends it out again, and everyone it applies to is asked again. Export the record as a PDF or CSV, or give a reviewer Viewer access to the documents their tags allow.

  • Approved before it goes outUp to four steps, with any or all approvers.
  • Acknowledged by nameName, email, date, time and version on every record.
  • Asked again on every changeEach new version goes out again to everyone it applies to.
  • The record on requestA PDF or CSV export, or Viewer access to the documents their tags allow.

Bring your own rules

Your region’s laws, the standards your customers ask for, and your own house rules. Write each one as a policy, approve it, and send it to the people it covers.

  • Laws of every country and state you work in
  • Standards and certifications
  • Customer and contract requirements
  • Your own policies and procedures
See GDPR on Policy and ComplianceWho audits it, which consultants work with it, and what it requires, checked against primary sources.Open the page (opens in a new tab)

Questions

Does the under-250 exemption remove the Article 30 record?

Article 30(5) exempts organizations with fewer than 250 employees only where processing is occasional, unlikely to create risk and excludes special category or criminal offense data. Routine employee or customer processing usually falls outside it.

Is there a proposal to relax record keeping?

A 2025 Commission simplification proposal would widen the Article 30(5) exemption to organizations with fewer than 750 employees, except where processing is likely to be high risk. The EDPB and EDPS issued a joint opinion in July 2025, and the proposal was still in the legislative process as of October 2026.

What does Regulation (EU) 2025/2518 change?

It sets common procedural rules for how supervisory authorities handle cross-border complaints and investigations, including admissibility and the right to be heard. It applies from 2 April 2027 and works alongside the GDPR's existing documentation duties.

How does the UK GDPR differ on documentation?

The UK GDPR keeps the same accountability, records and security articles, read with the Data Protection Act 2018 as amended by the Data (Use and Access) Act 2025. The ICO states all DUAA data protection provisions were in force by 19 June 2026, including a duty to acknowledge data protection complaints within 30 days.

Does the GDPR require staff to sign policies?

The GDPR does not prescribe signatures. Controllers must be able to demonstrate compliance under Article 5(2), so dated records of who received which policy and training are a common form of evidence.

Sources, read 18 October 2026

Where this shows up

Industries that hear about GDPR most.

Try AllyMatter free for 30 days

  • No credit card needed
  • 30-day money-back guarantee
  • Free migration on yearly plans