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

ServiceWhat it does for usWhat it handlesWhere
SupabaseDatabase, authentication, file storageEverything the platform stores: accounts, intake and screening transcripts, workspace chat, deal documents, billing records, audit traileu-central-2
VercelApplication hosting, serverless compute, Web AnalyticsAll request and response data in transit; function logs with request metadata; cookieless pageviews (Web Analytics)Functions in fra1
ResendTransactional and notification emailRecipient name and address, subject and body (can carry lead and buyer contact details and order context)Sending in AWS Ireland (eu-west-1)
AnthropicAI model provider (direct API)Whatever a user types or uploads into an AI surface: names, emails, company details, requirements, negotiated terms, document textUnited States
Google (Gemini API)AI model provider (direct API); emergency failover target for Anthropic surfacesSame categories as Anthropic for the tasks below; under AI_EMERGENCY_PROVIDER=google every Anthropic task is rerouted hereUnited States
KvK (Dutch Chamber of Commerce)Business register lookupKvK number and company name of a supplier or buyer organisation being verified (a sole trader’s name can be personal data)Netherlands
European Commission VIESEU VAT number validationVAT number and country code of an organisationEU institution
Google (Sign-In with Google)Identity provider for the sign-in buttonThe visitor’s browser contacts Google (IP, Google session) and Google returns an ID token with name and emailGoogle 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.