Subprocessors
Updated July 27, 2026
These are the third parties that process data on our behalf so ValorBrain can run. It is the list your legal team will ask for alongside the DPA, so it lives here, in public, instead of in an annex nobody can find.
What stays on our own infrastructure
Your documents, the vectors built from them and the Postgres database sit on our own hardware in Santa Catarina, Brazil. Embedding, reranking and entity extraction run on that machine's GPU — none of those steps leaves it. Error monitoring is self-hosted too.
The international transfer that does happen
One thing leaves the country: answer generation. The language model that writes the answer is a cloud service, and every question sends it the question plus the retrieved passages. Searching your memory sends nothing; only a generated answer does. If you cannot have that, run ValorBrain entirely in your own environment — optional on the Empresa plan, included on Enterprise.
The list
| Who | What for | What they receive | Where |
|---|---|---|---|
| Cloudflare, Inc. | Network edge: DNS, TLS termination and the tunnel that publishes the service. | All HTTPS traffic passes through it, request and response bodies included. Content is in transit, not stored. | United States and global network |
| OpenCode Zen (opencode.ai) | Router for the language model that writes the answer. | The question and the passages retrieved to answer it. No credentials, and never the whole index. | United States |
| Provedor de inferência do modelo (DeepSeek V4 Flash, via roteador) | Runs the model that generates the answer text. | The same content sent to the router. Our contract is with the router, not with the inference provider — anyone who needs a direct contractual chain runs on-premise (optional on Empresa, included on Enterprise). | Determined by the router; outside Brazil |
| Stripe | Subscription billing, card and boleto. | Name, email, billing details and invoice history. No indexed content is sent, and we never store card numbers. | United States and Ireland |
| Google LLC | Google sign-in (optional) and reading the sources you connect. | At sign-in: name, email, avatar. On connectors: whatever the authorized Drive, Gmail or Calendar scope allows us to read. | United States |
| Hostinger International Ltd. | Host of the transactional mail server we operate (verification, notices, invoices). | Recipient address and the content of the message we send. | São Paulo, Brazil |
| Telegram FZ-LLC | Operational alert channel for our on-call team. | Technical identifiers and error messages (account, route, code). Not a channel for document content. | United Arab Emirates and global network |
Sources you connect
Google Drive, Gmail, Calendar, Notion, GitHub and Slack only enter the path once you authorize the connection, and they read only what the OAuth scope allows. Revoke any of them in Settings → Connectors. Until you connect one, it sees nothing.
What we do not do
- We do not train models on your workspace content.
- We do not sell or share your data.
- We use no advertising analytics and no tracking cookies.
Changes to this list
Before adding a subprocessor that touches customer content we give 30 days' notice by email to the account's admin contact. If the addition does not work for you, you may terminate without penalty within that window — it is in the data processing agreement.
Contact
Data Protection Officer: Gustavo Iucksh Santos · [email protected]