Home / Sub-processors
Sub-processors
Questions: [email protected]. This page has not yet been reviewed by a lawyer.
Last updated: 17 November 2026
Sub-processors in use today
| Name | Purpose | Data involved | Location | When used |
|---|---|---|---|---|
| Cloudflare (network, tunnel and Turnstile) | Carries traffic to our hardware through a tunnel, ends the TLS connection, and runs the spam check on our forms | IP address and request details; the content of requests while in transit; spam-check signals | See Cloudflare’s documentation | Always, for the website and the platform |
| Cloudflare (Workers and Email Routing) | Receives an invite, estimate or application form and delivers it to us as an email | Your name, email, company, message and the answers you gave on the form | See Cloudflare’s documentation | When you send a form on this website, or request an invite through the chat assistant |
| The founder’s mailbox provider | Stores the emails that Cloudflare forwards, and the founder’s replies to you | The same form details, and any email you exchange with us | [Owner to fill: mailbox provider name and location] | When you send a form or email us |
| Mailgun (Mailgun Technologies, Inc.) | Sends our account emails, such as email confirmation, password reset, invitations and service notices, from mg.sundersystems.com | The recipient’s email address, and the subject and body of that email; delivery events | [Owner to fill: Mailgun account region, US or EU]. See Mailgun’s documentation | When the platform sends you an account email |
| OpenRouter | The gateway that routes AI requests to an open-weight model | The prompt and context of that request | See OpenRouter’s documentation | When a workspace’s AI requests are sent through OpenRouter |
| The upstream provider OpenRouter routes to | Runs the model and generates the response | The prompt and context of that request | Depends on the provider. OpenRouter lists the providers for each model. OpenRouter is told to use only providers that do not collect or train on prompts, that take every parameter we send, and that charge no more than $0.30 in and $1.20 out per million tokens. We have not limited the countries they may be in | Whenever a request goes through OpenRouter |
Hosting of the platform, your hosted desktop, your workspace data and any model trained for you is on our own hardware in the Philippines. It is not a third-party sub-processor. The chat assistant on this website also runs on that hardware.
The tools we run on that hardware are not sub-processors either: GlitchTip for error reports (it receives no request bodies, cookies or headers), Uptime Kuma for monitoring, and Gitea, which holds our source code only.
Our own mail log keeps, for each account email, the template, a keyed hash of the recipient address, the recipient’s domain, the delivery status and Mailgun’s message id. It holds no address and no content, and it is deleted after 90 days.
If you message us on WhatsApp or Viber, that provider handles the conversation under its own terms. It is a channel you choose, not a service we send your data to.
Planned, not handling client data yet
- Xendit, for card, GCash and Maya payments into the prepaid wallet and for subscriptions. We have chosen it, but online payment is not open yet. The app runs in test mode, and today clients pay by invoice. When it opens, Xendit will see payment details, billing name and email, and card data will not touch our servers.
- Google, Apple and Facebook sign-in. Built but not switched on. If one is switched on, that provider learns that you signed in with it and shares your name and email with us.
Only if you choose it
- Your own provider key. If your workspace adds its own OpenRouter or DeepSeek key, its calls go to that provider under your own agreement with it. That provider is your provider, not ours.
- Services you connect to your own desktop, such as your mailboxes and social accounts, are your own providers.
How we tell you about changes
We update this page before adding or replacing a sub-processor and aim to tell platform clients at least 30 days ahead where the change affects their data, in the app and, once our account email service is running, by email. If you object on reasonable data protection grounds, write to [email protected] within that period and we will work with you; see our data processing addendum.