Professional
What Professional covers for your privacy office
Professional supports six privacy-office workflows for one EU organisation. Supported raw files stay in your browser; minimised workflow records can be stored by the service. Use the scope table to check what your team can review and which decisions remain with the responsible people.
What is included in Professional?
Professional covers one EU privacy office with up to 20 allocated seats, including pending invitations. The table separates supported records and file processing from legal decisions, external systems and future scope. Compare each row with your team’s requirements before relying on a feature or output.
| Dimension | Professional | Explicit boundary |
|---|---|---|
| Buyer and organisation | One EU privacy office with up to 20 allocated seats, including pending invitations | Multi-client vDPO services, additional organisations, future tiers and supplier administration are outside this offer |
| Privacy-office work | Six privacy-office workflows with decisions retained by your team | Legal conclusions and independent assurance stay with your counsel and auditors |
| File formats | 17 accepted extensions across ten format families | Unsupported and deferred formats must be rejected before processing |
| Raw-file custody | Supported raw files and raw metadata are processed in your browser | Minimised workflow records are stored by the service. Provider data boundaries are disclosed separately. |
| Team access | Role-correct DPO, CPO, owner, admin, and member policies | Actions remain subject to role, tenant, and four-eyes checks |
| Value and price | USD 999/month plus applicable tax | Savings, replacement, time, payment, and renewal outcomes require measured customer evidence |
Which privacy-office jobs can the team manage?
The six workflows cover file safety, rights requests, DPIAs, processing records, breach work and DPO operations. Start with the record for the task you need to complete. Check its owner, evidence and review state before using a summary or export; the responsible people retain the decisions.
How can I check that supported files stay local?
Supported raw files and their raw metadata stay on the browser processing path. Account and minimised workflow records can still reach the service. Use a synthetic supported file, inspect the request bodies in the Network panel and compare what you observe with the processing report and evidence manifest.
- Open your browser developer tools and select the Network tab.
- Process a supported file in your workspace.
- Inspect the outbound requests for raw file bytes or extracted raw metadata. Account and minimised workflow records can still be sent.
- Compare the recorded evidence with what you saw: counts, categories, status, timestamps and hashes.
Which evidence can I export?
Eligible file reports show the recorded removals, independent residual-check result and file hashes. You can retain an evidence package for your archive and export Article 30 supporting evidence in the listed formats. Check the report’s source, scope and verification state; it does not replace a complete processing record.
- When the file report is eligible for export, review its recorded removals, residual-check result and SHA-256 hashes of the original and processed file.
- An evidence package (ZIP) for your own archive.
- Article 30 supporting evidence as PDF, JSON, CSV or text. It supports your processing records and is not a complete record.
What should I check before relying on an export?
Check which source records an export contains, whether its evidence is verified and which conditions remain open. A file report, workflow status or management summary supports review within its stated scope. Your team must assess the underlying facts and make the legal, disclosure or notification decision.
The platform does not determine legal compliance, provide independent assurance, or submit reports to authorities.
NIS2, DORA, SOC 2, ISO 27001, EU AI Act, US State Privacy, HIPAA, PCI DSS, SEC Cyber, and NYDFS are not included in the controlled Professional offer; any availability requires separate scope, entitlement, applicability review, and current certification evidence.
How should we assess whether Professional fits?
Choose one recurring privacy task and identify the source records, reviewers and handoffs it needs. Compare those requirements with the six included workflows, file-format limits and export boundaries. Record your current effort before assessing any improvement; savings and customer outcomes need measurements from your own work.
Request access