Sub-processors
Sphere Consulting Group LLC — published sub-processor list.
Last updated: 28 October 2026. Changes are announced at least 30 days before they take effect, per clause 3.5 of the Data Processing Agreement.
This list is aligned to the deployment as built. An out-of-date sub-processor list is worse than a short one, so every row names what that party actually does, not what a category of vendor usually does.
| Sub-processor | Purpose | Data it can access | Location |
|---|---|---|---|
| Hetzner Online GmbH | Compute host for the API and the storefront | All data in transit and at rest on the host | EU - Falkenstein or Helsinki; the datacentre is named when the server is created |
| Cloudflare, Inc. | DNS only. The records are not proxied; TLS is terminated on our own host by Caddy with an ACME certificate. | DNS query metadata only. No request or response content, and no TLS keys. The records are created DNS-only; a proxied record would put Cloudflare in the request path and this row would become false, so it is checked at deployment. | Global anycast, DNS only |
Two rows, and that is the whole list. The service is one host, a DNS provider that never sees a request, and nothing else. There is no CI service, no CDN in the request path, no logging SaaS and no queue.
Not a sub-processor, listed for transparency
GitHub, Inc. hosts the source code. No customer data is processed there: images come from the vendors' own registries and the site is built and deployed from the operator's machine, so GitHub is not in the request path and holds nothing about a customer.
Paddle.com Market Limited — merchant of record. Paddle is the seller of record: the customer's contract for the purchase is with Paddle, Paddle handles the payment, the invoice, and the sales tax, and Paddle pays us. A merchant of record is not a processor acting on the Controller's instructions, which is why it is not in the table above. It sees billing contact details and invoice amounts. Nothing of the request path - no text, no audio - passes through it.
Skydo receives payouts from the merchant of record into the company's account. It sees payout and banking data, never customer content or request metadata.
What is deliberately not on this list
No analytics, no error-tracking SaaS, no customer-support platform, no email marketing, and no LLM provider. Every one of those would be a sub-processor with access to either content or behavioural data, and none is necessary to run the service. Keeping the list short is a feature, and it is the reason the compliance commitment in the DPA is credible rather than aspirational.
If any of those are added later, the 30-day notice applies and this page changes first.