Make your website GDPR compliant today — Cookiebot automates cookie consent, scanning, and compliance so you don't have to. Try Cookiebot Free
Article 30

Records of processing activities

1. Each controller and, where applicable, the controller's representative, shall maintain a record of processing activities under its responsibility. That record shall contain all of the following information:

(a) the name and contact details of the controller and, where applicable, the joint controller, the controller's representative and the data protection officer;

(b) the purposes of the processing;

(c) a description of the categories of data subjects and of the categories of personal data;

(d) the categories of recipients to whom the personal data have been or will be disclosed including recipients in third countries or international organisations;

(e) where applicable, transfers of personal data to a third country or an international organisation, including the identification of that third country or international organisation and, in the case of transfers referred to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;

(f) where possible, the envisaged time limits for erasure of the different categories of data;

(g) where possible, a general description of the technical and organisational security measures referred to in Article 32(1).

2. Each processor and, where applicable, the processor's representative shall maintain a record of all categories of processing activities carried out on behalf of a controller, containing:

(a) the name and contact details of the processor or processors and of each controller on behalf of which the processor is acting, and, where applicable, of the controller's or the processor's representative, and the data protection officer;

(b) the categories of processing carried out on behalf of each controller;

(c) where applicable, transfers of personal data to a third country or an international organisation, including the identification of that third country or international organisation and, in the case of transfers referred to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;

(d) where possible, a general description of the technical and organisational security measures referred to in Article 32(1).

3. The records referred to in paragraphs 1 and 2 shall be in writing, including in electronic form.

4. The controller or the processor and, where applicable, the controller's or the processor's representative, shall make the record available to the supervisory authority on request.

5. The obligations referred to in paragraphs 1 and 2 shall not apply to an enterprise or an organisation employing fewer than 250 persons unless the processing it carries out is likely to result in a risk to the rights and freedoms of data subjects, the processing is not occasional, or the processing includes special categories of data as referred to in Article 9(1) or personal data relating to criminal convictions and offences referred to in Article 10.

Understanding This Article

Article 30 requires comprehensive documentation of processing activities - often called 'Records of Processing Activities' (ROPA) or 'Article 30 records.' This is a core accountability tool enabling controllers and supervisory authorities to understand what processing occurs.

Paragraph 1 - Controller Records Must Include:

  1. (a) Identity: Names and contacts of controller, joint controllers (if any), representative (if any), and DPO (if any)
  2. (b) Purposes: Why data is processed (all purposes)
  3. (c) Categories: Types of data subjects (customers, employees, etc.) and personal data (names, addresses, health data, etc.)
  4. (d) Recipients: Who receives data (processors, third parties, public authorities)
  5. (e) Transfers: Any transfers outside EU/EEA, including safeguards used
  6. (f) Retention: How long data is kept (where possible)
  7. (g) Security: General description of technical and organizational security measures (where possible)

Paragraph 2 - Processor Records Must Include:

  1. (a) Identity: Names and contacts of processor(s), controllers they serve, representatives, and DPOs
  2. (b) Processing categories: Types of processing conducted for each controller
  3. (c) Transfers: International transfers and safeguards
  4. (d) Security: General description of security measures

Paragraph 3 - Format: Written, including electronic (spreadsheet, database, software tools)

Paragraph 4 - Availability: Must provide to supervisory authority on request

Paragraph 5 - Small Enterprise Exemption:

Organizations with fewer than 250 employees are exempt UNLESS:

  • Processing likely to risk rights and freedoms, OR
  • Processing is not occasional (regular/core business), OR
  • Processing includes special category or criminal data

In practice, exemption rarely applies - most organizations must maintain records.

Key Points

  • Controllers and processors must maintain written records of processing activities (ROPA)
  • Controller records: identity, purposes, data categories, recipients, transfers, retention, security
  • Processor records: identity, processing categories, transfers, security
  • Must be available to supervisory authority on request
  • Small enterprise exemption (<250 employees) with three important exceptions
  • Electronic format acceptable

Practical Application

ROPA Template - Controller Entry Example:

FieldExample Content
Processing Activity NameCustomer Relationship Management
ControllerAcme Corp, DPO: John Smith, dpo@acme.com
PurposeManaging customer relationships, sales, support
Legal BasisContract performance (Art. 6(1)(b)), Legitimate interests (Art. 6(1)(f))
Data SubjectsCustomers, prospects, former customers
Data CategoriesName, email, phone, address, purchase history, interaction notes
RecipientsSales staff, customer support, CRM processor (Salesforce), email provider
TransfersYes - Salesforce (US) via Standard Contractual Clauses
RetentionActive customers: duration of relationship + 3 years
Prospects: 2 years from last interaction
SecurityEncryption in transit/rest, role-based access, 2FA, audit logs, annual penetration testing

Common Processing Activities to Document:

  • Customer/client database
  • Employee HR records
  • Marketing and communications
  • Website analytics
  • Supplier/vendor management
  • Financial records
  • Security systems (CCTV, access logs)
  • IT systems and logs

Granularity Level:

Don't create hundreds of micro-entries. Group similar processing:

  • Good: "HR Management" covering all employee processing
  • Too granular: Separate entries for each form or field
  • Too broad: "All business operations" with no details

Maintaining ROPA:

  1. Initial Creation:
    • Workshop with departments
    • Interview process owners
    • Review systems and databases
    • Document each processing activity
  2. Regular Updates:
    • Review quarterly or semi-annually
    • Update when new processing starts
    • Revise when processing changes
    • Remove obsolete entries
  3. Assign Ownership:
    • DPO or privacy team owns overall ROPA
    • Department heads own their entries
    • Process for notification of changes

ROPA Tools:

  • Spreadsheets (Excel/Google Sheets) - simple, free
  • Dedicated ROPA software (OneTrust, TrustArc, etc.) - sophisticated, integrated
  • GRC platforms - part of broader compliance
  • Custom databases

Link to Other Requirements:

Article 30 records support:

  • Accountability (Article 5(2), 24)
  • DPIAs (Article 35) - identify high-risk processing
  • Data subject requests - locate data quickly
  • Breach response - understand data involved
  • Audits and assessments
  • Supervisory authority inquiries

Small Enterprise Exemption - When It Doesn't Apply:

Company has 200 employees but processes:

  • Customer data regularly (not occasional) = No exemption
  • Employee health data (special category) = No exemption
  • Background checks (criminal data) = No exemption

In practice, exemption mainly benefits very small, low-risk businesses doing occasional processing.

Common Mistakes:

  • Not maintaining ROPA at all
  • Creating ROPA once and never updating
  • Too vague ("we process customer data")
  • Not documenting legal basis
  • Forgetting processor activities
  • Not making available to supervisory authority when requested