Docs
relyance.ai ↗
Browse docs

Overview and Implementation Guide

Updated November 4, 2026View as Markdown ↗

About this document set

This is the entry point to the Relyance Universal ROPA™ documentation. Start here, then branch out to the guide that matches your role:

Document Audience What's in it
Overview and Implementation Guide (this doc) Everyone What the Universal ROPA is, how Relyance predicts and maintains records, and a rollout plan
Admin Configuration Guide Privacy Managers and privacy operations teams Working the ROPA list, reviewing and editing records, grouped views, bulk actions, custom fields, and export
Legal and Compliance Guide Legal, compliance, and DPO teams How the record maps to GDPR Article 30 and what its sources and audit trail demonstrate - no UI steps
Audit Log and Reporting Compliance teams and auditors What's captured for every record, where to see it, and how to produce a ROPA report
FAQ: Universal ROPA Prospects, new customers, sales and CS Common questions in plain language

What is the Universal ROPA?

The Universal ROPA is your organization's Record of Processing Activities (ROPA), built and kept current by Relyance instead of by a spreadsheet. Relyance discovers the vendors and systems in your environment - in source code, infrastructure, vendor integrations, contracts, and websites - predicts the processing activity each one performs, and turns each into a record with its controller, processor, data subjects, data elements, legal basis, retention period, transfers, and the sources that back each value. Your privacy team reviews, enriches, and approves those records, and every change is logged.

You find it under Comply → Universal ROPA™. The page has two tabs: Processing Activities (the records) and Audit Logs (every change, across all records).

Note. The Universal ROPA is included with the Vendor Lifecycle Management & ROPAs and Internal Services & ROPAs licenses. If you don't see it in the navigation, ask your Relyance account team.

How records are built

One record per pairing. A ROPA record is a processing activity performed by a specific controller with a specific processor - for example, "Payroll processing" with your business entity as controller and your payroll provider as processor. The same processing activity carried out with three different processors is three records, which you can view together as a group (see Grouped views).

Discovered automatically. Relyance builds records from what it learns about each vendor and system in your inventory, and predicts what it can't observe directly. Records created this way start with the status Discovered, ready for your review. See How Relyance predicts your ROPA.

Added by hand. You can also add a processing activity yourself - for a process with no system for Relyance to scan, for example. See Adding a processing activity.

Your edits stick. When you remove a value that discovery added, Relyance remembers the removal and doesn't add the value back on the next run. Editing a record doesn't change the underlying vendor discovery.

Every value shows where it came from. Values carry a source, grouped as:

Source group What it covers
Operational Reality Observed in your environment - source code, infrastructure and APM, vendor integrations, and domain and mobile app scans
Contract Read from a DPA, DPA amendment, MSA, or other agreement ingested through a contract integration
Assessment Taken from an assessment's answers
Public Knowledge Relyance's catalogue of what a vendor is known to process, and AI predictions
Manually Added Entered by a person

How Relyance predicts your ROPA

Most of the effort in a ROPA goes into answering the same questions for every vendor: what does it do for us, who is the controller and who is the processor, and what personal data is involved. Relyance answers them from evidence, then keeps the answers current as your environment changes. Your team's job shifts from writing the ROPA to reviewing it.

  1. Find the vendors and systems. Integrations, source code analysis, infrastructure and APM, contract analysis, and website and mobile app scans tell Relyance which vendors and systems handle personal data, what data they receive, and where.
  2. Predict the processing activity. When a vendor is added to your inventory, Relyance uses AI to choose the single most relevant processing activity for it - "Payroll processing" for a payroll provider, for example. It picks from your organization's processing activities first and, if none fits, from Relyance's wider library, which then adds that activity to your list.
  3. Fill in the activity's details. The chosen activity brings its standard details from Relyance's processing activity library: legal basis, data subject categories, data recipient categories, conditions for processing special category data, and the nature and purpose of processing. The data elements, locations, and transfers come from what discovery actually observed.
  4. Assign the roles. Relyance works out whether your organization is the controller, a joint controller, or a processor for the activity, and who the processor and subprocessors are (see Controller and processor roles).
  5. Create the record for review. The result is a ROPA record with the status Discovered. Nothing is approved until a person approves it.
  6. Keep it current. Discovery keeps running, and the ROPA follows it (see Keeping the ROPA current).

What the predictions are based on

Input Where it comes from
Your business The name, description, and business model of your top-level business entity in Business Atlas
The vendor The vendor's name and description from Relyance's catalogue of third parties
How the vendor was found The discovery sources that detected it - for example, a source code repository, a vendor integration, or a website scan
Your processing activities The processing activities enabled for your organization, plus Relyance's wider library

Tip. Predictions are only as good as the business context they start from. Keep the description and business model of your top-level business entity accurate in Business Atlas.

Controller and processor roles

When a vendor acts as a processor for you, your business entity is the controller and the vendor is the processor. When you act as a processor for your own customers, the controller is shown as Your Customer, your business entity is the processor, and the vendor is listed as your subprocessor.

With AI prediction, Relyance reads your business context and the vendor's purpose to predict which of these applies - processor, joint controller, or subprocessor - and records the evidence. Hover over a controller, processor, or subprocessor to see the Role Prediction, with a Confidence percentage and the Evidence behind it. Without it, Relyance uses the vendor's data-handler role.

How predictions show in the record

Predicted values are labelled Machine Learning Prediction in a value's Data Sources, and belong to the Public Knowledge source group alongside Relyance's catalogue. Values observed in your environment are Operational Reality. Use Filter by Discovery Source on the ROPA list to separate observed values from predicted ones during review.

Guardrails

  • A person approves. Predicted records start as Discovered. Relyance never approves a record.
  • Your choices win. A processing activity you or a scan added to a vendor is never replaced by a prediction, and a record a person has edited keeps the edits.
  • Predictions are stable. Relyance keeps each vendor's prediction, so the same vendor doesn't get a different answer each time discovery runs.
  • Technology vendors are skipped. Tools that don't process personal data on your behalf get no processing activity and no ROPA record.

Note. AI prediction of processing activities and roles is enabled per organization. Without it, processing activities come from Relyance's catalogue of what each vendor is known to do, from website scans, and from what you add. Ask your Relyance account team to enable it.

Keeping the ROPA current

As discovery runs, Relyance updates the records it built:

  • New values found for a vendor - data elements, data subjects, locations, and so on - are merged into the record.
  • Subprocessors known for a vendor in Relyance's catalogue are added to the record's Subprocessors.
  • A discovered record that's no longer backed by any source is removed.
  • A value you removed stays removed. Relyance remembers the removal and doesn't add it back.

Every one of these changes is in the audit log under the user System, so you can see exactly what discovery changed and when. See Audit Log and Reporting.

Working with the records

Grouped views

Group the list by Processing Activity, Department, Processor, Controller, Status, or a dropdown custom field, and open a group to see everything its records have in common on one page. A group's values are the combined values of its records, and each value shows which records contributed it. You can edit a group in one step, and the change applies to every record in it. See Working with groups.

Statuses

Status Meaning
Discovered Created by discovery or added by hand, and not yet approved
Draft Work in progress. A Draft record can't be approved until you change its status
Approved Reviewed and signed off by your privacy team
Archived No longer active, kept for the record

Where the ROPA appears elsewhere

  • Assessments - create a DPIA or other assessment directly from one or more ROPA records, and see a record's assessments on its Articles tab. See the Assessments Admin Configuration Guide.
  • Vendor drawer - a vendor's Overview tab shows a Processing Activities card listing the ROPA records where it is processor or subprocessor.
  • Business Atlas - group and pivot the ROPA by business entity and internal product. See Business Atlas - Overview.
  • Consent Management - editing a consent purpose's display title doesn't change the processing activity name your ROPA uses. See the Consent Management Admin Configuration Guide.

Phase 1 - Connect your sources

Owner: Privacy Manager, with IT or engineering. The ROPA is only as complete as the systems Relyance can see. Connect your source code, cloud and APM, SaaS vendors, and contract systems. See the Source Code Integration, Infrastructure Integration, Vendor Integration, and Contract Integration guides.

Phase 2 - Organize the inventory

Owner: Privacy Manager. Map vendors and services to business entities and internal products in Business Atlas, so the ROPA's controllers and products reflect how your organization is structured. Make sure your top-level business entity has an accurate description and business model - Relyance uses them to predict processing activities and roles. See Business Atlas - Overview.

Phase 3 - Review the discovered records

Owner: Privacy Manager. Open Comply → Universal ROPA™, group by Processing Activity, and work through each group: confirm the controller and processor, fill in the required Description and Purpose of processing, and add legal basis, retention period, and security measures. Use Bulk Edit for values that apply across many records. See the Admin Configuration Guide.

Phase 4 - Fill the gaps by hand

Owner: Privacy Manager. Add processing activities that no system reveals - paper-based or offline processes, for example - with Add Processing Activity, and add any fields your regulators or internal policy require as custom fields.

Phase 5 - Approve and assess

Owner: Privacy Manager or DPO. Approve reviewed records, archive ones that no longer apply, and create assessments for high-risk activities straight from the list.

Phase 6 - Keep it current

Owner: Privacy Manager. Save views for recurring reviews (for example, Status = Discovered), check the Audit Logs tab for what discovery changed, and export the ROPA to Excel when a regulator, auditor, or customer asks for it. See Audit Log and Reporting.