Subprocessors
Last updated October 25, 2026
These companies process personal data for Camelus. Each one gets only what its job needs. We'll update this page at least 30 days before adding a subprocessor that receives feedback data; subscribe to changes by writing to hello@camelus.si.
| Subprocessor | What it does | What it receives | Where |
|---|---|---|---|
| Server hosting | Runs the Camelus servers and stores all data and backups | Everything stored in Camelus, encrypted in transit and at rest | Listed here before launch |
| OpenAI | Reads each feedback message once to summarize, translate and classify it, and embeds summaries for grouping | Feedback text and product descriptions; requests are sent with storage turned off and aren't used for training | United States |
| Resend | Sends Camelus emails (digests, alerts, invites, loop messages) and receives forwarded feedback emails | Recipient addresses, email content, forwarded emails | United States |
| Polar | Payments, invoices and tax for Camelus plans | The workspace owner's email and billing details. Polar is the merchant of record | United States |
| Sign-in with Google; Google Analytics on the website, only after consent | Name, email and photo at sign-in; analytics events with a pseudonymous id | United States |
Data sent to the United States is covered by the EU-US Data Privacy Framework where the provider is certified, and by the European Commission's standard contractual clauses otherwise.
If you connect your own Polar organization or set up destinations (Slack, Discord, n8n, Zapier, Make, Vicunia or your own endpoint), you choose to send data to those services. They aren't Camelus subprocessors: they work for you.