Skip to content

Operational registers

Bring RoPA, DPIA, DSAR and breaches into one scope.

GDPR workflows do not stay static templates: they become registers with responsibility, deadlines, links to processing activities and available evidence.

Illustration of per-tenant data isolation with separate databases and encryption.
Per-tenant data isolation
Separate databases per tenant and encryption underpin how privacy data is handled.

What it includes

Record of processing activities

Document purpose, legal basis, categories, transfers, security and retention for each processing activity.

DPIA and approvals

Link impact assessments to processing activities and make the approval step visible.

Requests and breaches

Manage DSARs with deadlines and record privacy breaches in the same operational incident register.

Operationally connected

RoPA, DPIA, DSAR and breaches stay connected to controls, suppliers and evidence, not isolated in separate modules.

How it works

Document processing activities

Fill in the RoPA with purpose, legal basis, categories and transfers.

Assess the impact

Link the DPIA to processing activities and track the approval step.

Manage requests

Track DSARs against their deadlines.

Record breaches

Track data breaches in the same operational incident register, with a GDPR profile.

Available with

Modules: Privacy operations

Frameworks: GDPR

AuditReady supports compliance work; it does not replace the customer’s assessments, obligations, or decisions.

Frequently asked questions

Are DPIA and RoPA linked?

Yes, every DPIA references one or more processing activities from the RoPA.

Do privacy breaches have a dedicated register?

They share the operational incident register, with a GDPR profile, so they stay in the same management scope.

Can I link a DSAR to a piece of evidence?

Yes, you can link the relevant evidence to support handling the request.