Security architecture
Separate raw-file custody from workspace security.
Professional processes supported raw files in your browser. The platform stores account, subscription, compliance and audit records on managed infrastructure. The measures below explain local processing, transport, access, application encryption and audit controls. Review each measure's scope and the separate limits for provider configuration and independent assurance before procurement.
Read the DPA security scheduleWhich data stays on the device?
Supported raw files, extracted raw metadata and cleaned outputs stay on the browser processing path. Account, subscription, compliance and audit records use managed infrastructure, and minimised file-workflow evidence can reach the workspace. Inspect a synthetic file’s Network requests to check that session; review the provider register for stored-record boundaries.
On your device
Supported input files, extracted raw metadata and cleaned output stay in the browser workflow. Open the browser developer tools and inspect Network requests for raw file bytes or extracted raw metadata.
In your workspace
Account, subscription, compliance and audit records use managed infrastructure. Only minimised evidence from the supported file workflow can be saved to the workspace.
Which technical measures are described here?
The controls below describe storage, transport, local file processing, application encryption, access and audit integrity. Each control has a stated scope. A control present in the source does not establish current provider configuration, complete route coverage or independent assurance; check those separate limits when assessing the service for your organisation.
Infrastructure
Managed hosting, database and transport.
- Managed storage boundary
- Compliance records use managed-infrastructure storage. The provider register describes the known configuration and the limits of that evidence.
- Transport protection
- HTTPS/TLS protects application transport. The exact negotiated protocol and cipher are not asserted here.
Application
Browser-local processing and scoped field encryption.
- Browser-local file processing
- On supported Professional paths, raw files and extracted raw metadata stay in the browser workflow.
- Application encryption scope
- AES-256-GCM protects explicitly wired integration credentials and selected sensitive fields. It does not cover every compliance record at the application layer.
Access
Authentication and privilege boundaries.
- Privileged-access controls
- Magic-link, step-up, session and device controls are implemented. Universal MFA or privileged-access enforcement is not claimed.
- Organisation scope
- For organisation-scoped requests, the shared API boundary checks signed-in membership before the handler proceeds. A copied record link does not grant membership.
Audit
Accountable writes and verifiable record links.
- Audit integrity scope
- Canonical audit writes include SHA-256 hash-chain controls. Complete route coverage and retention, legal-hold, backup and restore assurance are not claimed.
Where are the security measures recorded?
The published DPA records the security measures for local-file processing, access, transport, audit, monitoring and incident response. Read the full security schedule when assessing the supplier. An accepted agreement preserves its document version and hash in Billing, so your team can check which text it accepted.
Read the full security scheduleIs independent security assurance claimed?
No SOC 2 or ISO certification or independent penetration-test opinion is claimed. The descriptions above explain implemented controls and their contractual scope. Assess them against your organisation’s requirements, alongside provider locations and agreements; a control description is not independent assurance or a determination of legal compliance.
For data location and supplier contract details, review the provider register. For a security issue, use the contact on the trust centre.