Legal

Sub-processors

Draft, pending legal review, not yet in effect

This list is a working draft. Items marked [to confirm] are not settled yet. It does not bind anyone until a final version is published here with an effective date.

Last updated: [Effective date]

[Company legal name] uses the third parties below to run Zaproo Search. Each one gets only the data it needs for its task, under a written agreement with data protection terms. We will announce a new sub-processor [30 days, to confirm] before it starts, and customers can object under the data processing agreement.

Infrastructure

Sub-processor	What it does	Data	Location
[Hosting provider, to confirm]	Runs the Kubernetes cluster with the API, the dashboard and the databases	All service data	[EU region, to confirm]
[Object storage provider, to confirm]	S3-compatible storage for uploaded document batches, database backups (30 days) and search index snapshots (14 days)	Catalog documents, backups of all service data	[EU region, to confirm]
[Email delivery provider, to confirm]	Sends account and service emails over SMTP	Customer email addresses, email content	[to confirm]
[Monitoring provider, if any, to confirm]	Receives traces and metrics when telemetry export is switched on	Request metadata [to confirm]	[to confirm]

PostgreSQL, Redis and OpenSearch run inside our own cluster at the hosting provider. They are not separate third parties.

AI model providers

These receive shopper messages, recent conversation history, the shop's assistant instructions and mapped catalog fields when a shop uses the AI assistant. What is sent and stored is described in How the AI assistant handles data with model providers. Only providers our staff have configured and switched on receive data.

Sub-processor	In use	Location	Zero data retention
Anthropic	[to confirm]	[United States, to confirm]	[to confirm]
OpenAI	[to confirm]	[United States, to confirm]	[to confirm]
[OpenAI-compatible provider, for example Ollama Cloud, to confirm]	[to confirm]	[to confirm]	[to confirm]