GDPR·Article Article 30·critical·Component: Chapter IV: Controller and Processor

What this control requires

Controllers and processors must keep written records of processing activities, including details on purposes, data categories, recipients, transfers, erasure timelines, and security measures, accessible to supervisory authorities, unless exempted for low-risk, small-scale processing. This control addresses Processing Records.
— GDPR, Article Article 30

In plain English

Controllers and processors must keep written records of processing activities, including details on purposes, data categories, recipients, transfers, erasure timelines, and security measures, accessible to supervisory authorities, unless exempted for low-risk, small-scale processing. In practice, this means you can prove you data controller-level controls on a defined cadence.

Why it matters

GDPR administrative fines reach the greater of €20 million or 4% of global annual turnover. The European Data Protection Board (EDPB) coordinates supervisory-authority enforcement across the EU/EEA, and DPAs publish enforcement decisions citing specific Articles.

This control is rated critical in the source catalogue. Treat gaps here as production incidents in the risk register, not housekeeping.

What an auditor looks for

A DPA or privacy auditor expects: a Records of Processing Activities (RoPA) entry, a documented lawful basis, evidence the Article's data-subject right is operationalised end-to-end, a named DPO contact (where required), and Article 30 records that match what the front-end actually does.

Within Chapter IV: Controller and Processor, the assessor will trace your implementation back to the catalogue reference (Article Article 30) and look for objective evidence on the latest two assessment cycles.

How to implement

Policy Management

Docs. Keep each policy in version-controlled Markdown alongside the code that implements it; ship a signed PDF snapshot at each annual review and link the SHA into the SoA.

Operational checklist

  • Data. Document the trigger, the owner and the cadence.
  • Processor. Document the trigger, the owner and the cadence.
  • Records. Document the trigger, the owner and the cadence.
  • Security. Document the trigger, the owner and the cadence.
  • Transfers. Document the trigger, the owner and the cadence.
  • Scope: controller, controllers, recipients, transfers, erasure timelines, security measures.

Evidence to collect

  • Policy Document. A signed and version-controlled policy / standard / procedure document.

Signed policy or standard documents the safeguard. Focus: Records of processing activities.

Common pitfalls

  • Policies that no engineer has read; the version in Confluence drifts from the version that's actually being enforced.

Related controls in GDPR

References

Topics: governance riskpolicy management