Draft — reviewed by the owner; not yet legal advice. Have a professional review before public launch.
Subprocessors
The providers Cluvia uses to run the service, what each one does, and the data it handles. See the Privacy page for the full picture.
| Provider | What it does for Cluvia | Data it handles | Where |
|---|---|---|---|
| AWS (Amazon Web Services) | Hosts the company database — PostgreSQL (RDS). | Company data: agents, tasks, outputs, chats and activity. | UK (London), encrypted at rest. |
| Cloudflare | Network and security, database access (Hyperdrive), file storage (R2), and hosting for published websites. | Files and uploads, site files, published-site traffic and visitor data, requests in transit. | Global network. |
| Cloudflare Turnstile | Bot check at sign-up and sign-in, to stop automated sign-ups. | Your IP address and technical details of your browser and connection, during the check. Cloudflare also uses these signals, as a separate controller, to improve its bot detection. | Global network. |
| Supabase | Authentication. | Your email address and session tokens. | Cloud service (region set by our project). |
| Whop (Whop, Inc.) | Checkout and payments for paid plans and top-ups, including renewals and refunds. Whop is the merchant of record for the payment at checkout. | Your Cluvia account ID and what you buy, and the records Whop sends us about your payments, refunds and disputes. Your payment details, billing email and country, which you give Whop at checkout and Whop handles under its own privacy policy. | United States. |
| OpenRouter | AI model gateway: text sent to generate deliverables, and the natural voice that speaks replies. | Task text, and reply text for the natural voice. | Cloud service. |
| Uman | DeepSeek models via its API, for planning and hard reasoning. | Task text sent for those calls. | Cloud service. |
| TypeSafe (Jev) | Quick-decision model. | Task text sent for those calls. | Cloud service. |
What is not a subprocessor
- Tools you connect yourself (GitHub, Google Workspace, Slack, Discord, MCP servers): requests go to those platforms under your own account and their terms. You choose what to connect, and disconnect it at any time.
- On-device processing: the fallback speech model runs in your browser, and your browser's own speech service (where you use it) is governed by that browser's terms — not by us.
How they are bound
Each provider processes data under contract, only for the purposes above. Two exceptions are named in the table: Cloudflare also uses Turnstile signals to improve its bot detection, and Whop handles what you enter at its checkout under its own privacy policy. Where a provider processes data outside the UK/EEA, the transfer relies on appropriate safeguards such as the UK International Data Transfer Addendum or standard contractual clauses. If we change this list, we will update this page. Last updated: 7 October 2026.