DPO Radio

A Record of Processing Activity drifts from current operations the moment a processing activity changes. A new recipient is added; a retention period shifts; a lawful basis is reclassified. If the RoPA is not updated, the next audit surfaces the gap and the privacy team scrambles to reconstruct what changed and when.
The RoPA hygiene auto-fix workflow runs against the organisation's RoPA registry and surfaces per-entry gaps against four completeness frameworks. They are the PDPL controller duties applied to records of processing, GDPR Article 30 records of processing, Vietnamese Decree 165 implementing requirements, and ISO 27701 privacy information management. Each gap carries a citation and a deep-link Fix button that opens the activity editor at the missing field.
The workflow does not auto-fix. The DPO reviews each suggested fix per gap and applies through the standard editor. The audit trail records the suggestion, the operator decision, and the resulting state change.
The workflow runs across the active RoPA entries. Each entry is checked against the four completeness rule sets — required fields, required relationships, required attestation cadence.
Each gap surfaced carries an inline citation naming the framework requirement that anchors the field. A missing retention period cites the relevant article; a stale attestation cites the cadence rule; an unmapped data category cites the classification requirement.
Every gap row carries a Fix button that opens the underlying processing-activity editor with the missing field highlighted. The operator fills the field, saves through the standard editor, and the gap closes.
Where Forseti can suggest the missing value (e.g. inferred from the activity description or from a linked DPIA), the suggestion ships with the gap row. The operator accepts the suggestion through the standard editor or overrides with the correct value.
A missing lawful basis is the exception. Choosing a basis is the organisation's legal determination, so Forseti suggests none. The suggested fix lists the bases the installed frameworks declare, each with its article. The operator chooses one, or records the ground in their own words with the article it rests on.
Each gap surfaced emits three audit events — gap identified, suggestion drafted (if applicable), operator action recorded. The audit trail walks the hygiene pass end to end.
The workflow can be scheduled — typically monthly or quarterly — so the hygiene pass runs on a consistent cadence. Each scheduled run is a separate run in the audit trail.



Every gap citation is grounded against the four-framework registry. Suggestions without grounding ship with a "no grounding" marker rather than fabricated authority.

Fixes apply through the standard activity editor. The workflow does not mutate RoPA entries autonomously. Operator decisions are recorded in the audit trail.

The audit trail walks any RoPA-touched record back through the hygiene pass that surfaced the gap and the operator action that resolved it.
| Framework | How RoPA Hygiene Supports It |
|---|---|
| Vietnam Personal Data Protection Law | Checks RoPA entries against the PDPL controller duties (Law 91 Article 37) applied to records of processing. |
| EU GDPR | Checks RoPA entries against GDPR Article 30 records of processing requirements. |

Use RoPA sufficiency to review completeness and support. The hygiene workflow prepares changes to individual entries. See Privacy Workflows.
Ready to see a RoPA registry walked in three minutes with per-gap citation and deep-link Fix buttons? Request a personalised demo.


Run RoPA hygiene auto-fix monthly against your registry for one quarter. Measure how much audit drift is removed by proactive hygiene.

Talk to our team about how RoPA hygiene fits into your existing attestation cadence.
Four: the PDPL controller duties (Law 91 Article 37), GDPR Article 30, Vietnamese Decree 165 implementing requirements, and ISO 27701 privacy information management. The registry covers required fields, required relationships, and required attestation cadence per framework.
No. The workflow surfaces gaps and suggests fixes where possible. The operator applies the fix through the standard activity editor. The audit trail records the suggestion and the operator action.
Yes. Scheduled runs typically run monthly or quarterly. Each scheduled run is a separate run in the audit trail. Schedule changes are explicit operator actions.
The gap is surfaced with the citation; the suggested fix is omitted. The operator opens the activity editor through the Fix button and fills the field manually. The platform records the operator action.
Yes. Each run sends requests to the AI provider your organisation has configured, and your provider bills your organisation for them directly. A run is never refused because a Forseti allowance ran out, and the Usage page reports what each feature consumed.