A DPA template prepared for pilot review.

Security measures

• Authentication through the managed authentication service, with email and password or Google sign-in; passwords are not stored by us in readable form.
• Database-level row security policies scope every supplier record, case and report to a single workspace.
• Role-based permissions inside a workspace: owner, compliance lead, investigator and read-only reviewer.
• An append-only activity log of material actions — supplier added or removed, import, case opened or closed, report exported, role changed — exportable for an auditor.
• Worker narratives are not surfaced in the management console, in exports or in the case layer.
• HTTPS/TLS for the site and the data API; encryption at rest and backups are provided by the infrastructure sub-processors.
• Synthetic demo content is rendered from a fixed fictional dataset in the application and never written to customer data.

Sub-processors

Deletion and return

A workspace owner can delete supplier records from the console at any time. On written request at the end of an engagement we delete the workspace and its linked records, or provide an export first. The exact schedule is fixed in the signed DPA.

Incidents and cooperation

We notify the customer contact without undue delay after becoming aware of a personal data breach affecting their workspace, with what we know at that point, and we cooperate with the customer's own regulatory obligations, data-subject requests and reasonable audit or questionnaire requests. A specific notification window is agreed in the signed DPA; we do not publish an hour count we have not committed to.