Concept: juridische controle vereist
This is a working draft prepared for legal review. It is not yet final and does not constitute legal advice. The final text is fixed by the operator’s legal counsel before launch.
Sub-processors
The services that process personal data on behalf of ZoraMatch to run the platform. This list is generated from the platform's own code and shows only the services that are switched on.
Last updated 16 October 2026
The list
| Service | What it does for us | What it handles | Where |
|---|---|---|---|
| Supabase | Database, authentication, file storage | Everything the platform stores: accounts, intake and screening transcripts, workspace chat, deal documents, billing records, audit trail | eu-central-2 |
| Vercel | Application hosting, serverless compute, Web Analytics | All request and response data in transit; function logs with request metadata; cookieless pageviews (Web Analytics) | Functions in fra1 |
| Resend | Transactional and notification email | Recipient name and address, subject and body (can carry lead and buyer contact details and order context) | Sending in AWS Ireland (eu-west-1) |
| Anthropic | AI model provider (direct API) | Whatever a user types or uploads into an AI surface: names, emails, company details, requirements, negotiated terms, document text | United States |
| Google (Gemini API) | AI model provider (direct API); emergency failover target for Anthropic surfaces | Same categories as Anthropic for the tasks below; under AI_EMERGENCY_PROVIDER=google every Anthropic task is rerouted here | United States |
| KvK (Dutch Chamber of Commerce) | Business register lookup | KvK number and company name of a supplier or buyer organisation being verified (a sole trader’s name can be personal data) | Netherlands |
| European Commission VIES | EU VAT number validation | VAT number and country code of an organisation | EU institution |
| Google (Sign-In with Google) | Identity provider for the sign-in button | The visitor’s browser contacts Google (IP, Google session) and Google returns an ID token with name and email | Google global |
How this list stays current
Every service the platform talks to is recorded in a register that is generated from the code itself. A change that adds a new service without recording it stops before it can be released. This page reads that register, so it changes when the platform changes.
Questions about how your data is handled: see our privacy policy.