Docs
relyance.ai ↗
Browse docs

Legal and Compliance Guide

Updated November 4, 2026View as Markdown ↗

Audience: legal, compliance, and DPO teams. This guide describes what the Universal ROPA records and demonstrates. For UI steps, see the Admin Configuration Guide.

Note. This guide explains how the Universal ROPA supports your record-keeping obligations. It isn't legal advice. Your legal team decides what your records must contain and whether they meet the laws that apply to you.

The record-keeping obligation

Article 30 of the GDPR (and the UK GDPR) requires controllers and processors to keep a written record of their processing activities and make it available to the supervisory authority on request. Other regimes ask for similar inventories - for example, data maps that support privacy notices, data protection assessments, and responses to rights requests under US state privacy laws.

The usual difficulty isn't the format of the record but keeping it true. A ROPA compiled from interviews and spreadsheets describes systems as they were at the last review. The Universal ROPA is generated from what Relyance observes in your code, infrastructure, vendors, and contracts, and it records where each value came from.

How the record maps to Article 30

Article 30(1) - records kept by a controller

Article 30(1) requirement Where it's recorded
(a) Name and contact details of the controller, any joint controller, the controller's representative, and the DPO Controller and Joint Controller, each with Address and DPO Email. Add a representative as a custom field if you need one
(b) Purposes of the processing Purpose of processing (required on every record), with Description
(c) Categories of data subjects and categories of personal data Data Subject and Data Elements, plus Special Categories of Personal Data
(d) Categories of recipients, including recipients in third countries or international organizations Data Recipient Category, Processor, and Subprocessors
(e) Transfers to a third country or international organization, and the safeguards for them Transfers (destination countries) and Locations of Processing. Record transfer mechanisms such as SCCs as a custom field if you need them in the record
(f) Envisaged time limits for erasure Retention Period
(g) General description of technical and organizational security measures Security Measures

Article 30(2) - records kept by a processor

Where your organization processes data on behalf of its customers, the record shows the controller as Your Customer and your business entity as the processor, with the vendors you engage listed as Subprocessors. The same fields cover the processor's record: the name and contact details of the processor and controller, the categories of processing, transfers, and security measures.

Lawful basis

Article 30 doesn't require the lawful basis in the record, but most supervisory authorities recommend it, and you need it for privacy notices and DPIAs. The record keeps it in Legal Basis.

What the record demonstrates

Provenance. Each value carries its source: Operational Reality (observed in code, infrastructure, vendor integrations, or website and mobile app scans), Contract (read from a DPA, MSA, or other agreement), Assessment, Public Knowledge, or Manually Added. When an authority or auditor asks how you know a vendor receives a category of data, you can show the source rather than an interview note.

Review and sign-off. Records move from Discovered to Approved when your privacy team signs off, and to Archived when they no longer apply. Draft records can't be approved until their status is changed.

Accountability. Every change - by a person or by discovery - is logged with who made it, when, and the before and after values. Changes made by discovery are attributed to System. See Audit Log and Reporting.

Availability on request. The record can be exported to Excel at any time, filtered to the scope requested.

Supporting other obligations

  • DPIAs (Article 35). Create a DPIA directly from a processing activity, so the assessment starts from the record's facts. See the Assessments Legal and Compliance Guide.
  • Transparency (Articles 13 and 14). Purposes, recipients, retention periods, and transfers in the ROPA are the inputs for your privacy notice.
  • Processor due diligence (Article 28). Each processor and subprocessor in the ROPA links to its vendor record, where contracts and assessments are kept.
  • Data subject requests. The data elements and systems in the ROPA show where a data subject's data is held. See Data Subject Requests.

Your responsibilities

The Universal ROPA automates discovery and record keeping. It doesn't decide for you:

  • Whether a role assignment (controller, joint controller, or processor) is legally correct - review any role Relyance predicts.
  • Which lawful basis applies to an activity.
  • Whether a retention period or security measure is adequate.
  • Whether a transfer has a valid safeguard.

Records Relyance discovers start as Discovered so that a person reviews them before approval.