Skip to main content

Built for Chief Privacy Officers

Keep the request, review and decision together.

On a busy morning, a rights response and an incident assessment can both have near-term deadlines. ScrubMetadata Professional brings recorded deadlines into one view and connects the underlying DSAR, DPIA, RoPA, incident and DPO work. Your team still judges consequence from each case.

What needs attention before a review or decision?

Before a decision, the team needs the source record, the response owner and any evidence still missing or disputed. Professional keeps the request, assessment and incident records described below, with their review history.

GDPR accountability

The handoff between teams

At the weekly review, the request owner, file reviewer and decision-maker should reconcile the same receipt date and evidence history. If one file finding also informs a DPIA or RoPA record, check the source link before repeating its status in another report.

Decision boundary: Applicability and legal conclusions remain customer-owned

GDPR Art. 15

A deadline starts before the record is tidy

Rights requests require intake, identity review, evidence gathering, disclosure-file safety, deadlines, accountable completion, and a defensible audit trail.

Decision boundary: Response obligations depend on the request and applicable law

GDPR Art. 35

A DPIA decision after the DPO opinion

A final assessment can hide which version the DPO reviewed, what conditions remained open and who decided whether processing could proceed.

GDPR Art. 30

A register with missing source records

A loaded RoPA page is not the full register. The team must reconcile the recorded population and check whether the Article 30 fields are complete enough for its own activities.

What evidence can the team check?

Records and exports give the reviewer the information available in the selected organisation. Source versions, open conditions and any missing evidence still matter when judging the case.

EU privacy-office dashboard

Review owners, deadlines and evidence across the six Professional workflows. Open the case record before judging the next action or its consequences.

  • Selected organisation
  • Evidence and completeness state
  • Deadline and task calendar
  • Accountable decision boundaries

Rights requests and disclosure review

Assign a request owner, track the deadline, collect scoped evidence and record completion for review. Work in external systems remains manual; third-party integrations are outside Professional.

  • Receipt date and request type
  • Identity and disclosure-file review checkpoints
  • Extension and refusal reasoning records
  • Deadline, response and export evidence

DPIA opinion and decision history

Review the assessment version, DPO opinion, open conditions and controller decision as separate events. A completed status does not settle the legal question.

  • Processing and risk context
  • DPO opinion and review history
  • Named conditions and follow-up
  • Separate controller decision

RoPA and data-inventory review

Review processing activities for the selected organisation and export the mapped Article 30 fields. Your team still checks the source counts and whether those records are substantively complete.

  • Organisation-scoped processing records
  • Nine mapped Article 30 field groups
  • Processor and transfer references where recorded
  • Export population and review gaps

What does Professional include?

Professional supports 6 privacy-office workflows for 1 EU organisation and accepts 17 file extensions on the supported local-processing paths. The seat limit is 20, including pending invitations.

6

DPO workflows

in Professional

17

Accepted extensions

10 format families

1

Organisation

Professional

20

Allocated seats

pending invitations count

How does the privacy team review its work?

Review rights requests, DPIAs, processing records and breach work alongside the operational queue. Open the relevant case to check its owner, dates, source evidence and unresolved conditions before judging the next action. A dashboard summary supports review; it does not make a legal decision for your team.

Illustrative Chief Privacy Officer workspace preview using example data

6

DPO workflows

17

Accepted extensions

1

Organisation

20

Allocated seats

What should you check before requesting access?

Professional access starts with an application review. The pricing page sets out the included workflows and seat allocation; the format pages and provider disclosures state their limits. ScrubMetadata records the work. The controller remains responsible for the processing decision.

Read the PDF metadata removal limits and Word document metadata removal limits for files your office shares. The Professional access, evidence and team FAQ explains the main buying and workspace questions.

Privacy workflows for heads of privacy · ScrubMetadata