Sub-processors
Every third party that processes data on our behalf, what they do, and where.
We tell you who our sub-processors are before you have to ask. If we add one, we will update this page and notify customers before the new sub-processor starts processing, as our Data Processing Agreement requires. To be told when this page changes, email privacy@veridatum.co.uk.
| Sub-processor | What they do | Where | What they process | Transfer basis |
|---|---|---|---|---|
| Render Services, Inc. Website and demo |
Application hosting for the public website and the anonymised demo | Origin in Frankfurt, Germany (EEA). Requests are served through Render's own content delivery network, which terminates the connection at an edge location — in the United Kingdom for UK visitors. | No client documents and no client personal data. Server logs containing visitor IP addresses, and the throwaway per-visitor demo databases, which contain anonymised sample content only. | The origin and its stored data are in the EEA. The content delivery network in front of it is operated by Render's own sub-processor and handles connection metadata such as IP addresses at the edge; it is covered by Render's data processing addendum. Render is US-incorporated, so its support staff may access infrastructure from outside the UK under the UK Addendum to the EU Standard Contractual Clauses in that addendum. |
Not yet in service
The Veridatum platform is not yet hosting client data. The sub-processors below will be engaged when it launches, and this page will be completed and dated before any client document is processed through them. They are listed now so that the direction of travel is visible rather than discovered.
| Sub-processor | What they will do | Where | What they would process |
|---|---|---|---|
| To be confirmed Platform |
Application hosting, database and document storage for the Veridatum platform | To be confirmed | Client documents, the extracted record, user accounts and the audit trail. |
| Anthropic PBC Platform (reading engine only) |
Large language model used for document classification, attribute extraction and conflict comparison | United States | Passages of client documents sent for reading, and page images where a document has no text layer. Whole corpora are never transmitted, and no account or billing data is sent. |
| To be confirmed Platform |
Transactional email — invitations, password resets and service notices | To be confirmed | Recipient name and email address, and the content of the notice. No client documents. |
What we do not use
Error monitoring. No third-party error monitoring service is enabled. Application errors are written to the host's own logs. If this changes it will be added here first.
Analytics. No analytics or advertising service is used on this site.
Payment processing. Invoicing is handled outside the platform. No card data is collected or stored.