Sub-processors
Hetzner Online GmbH, as the network gateway in Helsinki, is involved in instance traffic on GPUwerk's own tiers; Cloudflare only for a model endpoint terminated on the gateway. For on-demand and reserved instances GPUwerk operates the hardware itself, in its own EU-Central data center in Hradec Králové, Czech Republic. An instance's SSH connections, and the traffic it sends to the internet, are forwarded through a gateway server that GPUwerk rents from Hetzner in Helsinki, Finland, inside WireGuard tunnels; see the Hetzner row below. No third party stores the content of a customer's instance or has access to its workspace. Some of these machines are owned by hosting customers who keep them in that data center; an owner has no access to its machine while someone else rents it, or to that renter's data, and has no local login or physical access to it. A GB10 machine may be an NVIDIA DGX Spark or an equivalent GB10 system, such as the ASUS Ascent GX10. The one exception is the Partner tier, which applies only if you choose it: its machines are owned and hosted by independent partners, listed as a category in the last row of the table and described under "Partner tier" below. The rest of the list covers the processors used for the website, sign-in, mail and billing side of the service, as described in our Privacy Policy, section 5, plus the error-reporting, analytics and marketing processors named in that same section. The rows marked consent-gated are only loaded, and only receive data, if you accept the corresponding category in the cookie banner; nothing is fetched from them beforehand.
| Sub-processor | Purpose | Entity and location | Data involved |
|---|---|---|---|
| Stripe | Payments and invoicing | Stripe Payments Europe, Limited, Dublin, Ireland | Card and billing data. Card details are entered on Stripe's own payment page and never reach GPUwerk's servers. |
| Veriff (until 7 November 2026) | Until 7 November 2026: identity verification of a partner's account owner before the first payout, including a face comparison with an identity document. GPUwerk no longer uses Veriff; it now verifies the account owner's identity itself (Platform Rules, rule R4.4). | Veriff OÜ, Tallinn, Estonia, with group companies including Veriff UK Ltd (United Kingdom) and Veriff Inc. (United States) | For checks made until 7 November 2026: the partner owner's identity document and face images, the data on the document, device and IP address. Veriff's decision, including the name read from the document, came back to GPUwerk; GPUwerk stored only the outcome. Veriff keeps the images and document data for the period set in its contract with GPUwerk and then deletes them. Partners only; no customer or instance data. Transfers outside the EEA: see the Privacy Policy, section 6. |
| Hetzner Online GmbH | Server hosting for the control plane, console, this website, and the account database; the mail server that sends our email, and the gateway through which instance network traffic (SSH, VNC if enabled, outbound internet) is forwarded | Germany (Hetzner Cloud servers in Helsinki, Finland, and Nuremberg, Germany) | Account and billing data, and the recipient address and content of the email we send. Instance traffic is forwarded, not stored: SSH and TLS are not terminated on the gateway and stay encrypted end to end, but traffic a workload sends unencrypted (plain HTTP) is readable there in transit. Workspaces and storage are not on the gateway. Inside the EU. |
| Cloudflare | DNS, network protection and delivery for gpuwerk.com, the console and the API | Cloudflare, Inc., San Francisco, California, United States (global network) | IP addresses and the HTTP requests and responses that pass through its network. It does not reach instance storage or SSH. A model preset's HTTPS endpoint that is terminated on the gateway (https_termination: gateway in the API) passes through Cloudflare decrypted, prompts and responses included; one terminated on the instance does not. This is a transfer to the United States under the EU–US Data Privacy Framework, with standard contractual clauses as a fallback; see Privacy Policy section 6. |
| Google Workspace | Email (Gmail): our support, privacy and abuse mailboxes and the mailboxes our staff write from | Google Ireland Limited, Dublin, Ireland; processing also by Google LLC, United States | Email address, whatever you write to us, and email a person at GPUwerk writes to you. This is a transfer to the United States under the EU–US Data Privacy Framework, with standard contractual clauses as a fallback; see Privacy Policy section 6. |
| Sentry | Error reporting: catches JavaScript errors on the website and console | EU region | No cookie set, no identifier stored; personal data collection, IP capture and session replay are all off. Legal basis is legitimate interest, Article 6(1)(f) GDPR, not consent, so this one is not gated by the cookie banner. |
| PostHog Consent-gated: analytics | Website analytics: which pages fail, in aggregate | PostHog, EU region | Session recording and autocapture off, IP discarded at ingest. Loaded and receives data only if you accept the analytics category in the cookie banner. Stays in the EU: no third-country transfer. |
| Google Analytics 4 Consent-gated: analytics | Website analytics: which pages fail, in aggregate | Google, United States | Loaded and receives data only if you accept the analytics category in the cookie banner; refusing means the script is never fetched. When accepted, this is a transfer to the United States under the EU–US Data Privacy Framework adequacy decision, or standard contractual clauses otherwise; see Privacy Policy section 6. |
| Google Ads Consent-gated: marketing | Marketing: attributing a signup to the advert that produced it | Google, United States | Loaded and receives data only if you accept the marketing category in the cookie banner. Events sent are page and product views, checkout steps, a submitted contact form, a sign-up and a purchase. No names or message contents. With a sign-up or purchase, Google receives a SHA-256 hash of your email address (enhanced conversions); details in the Cookie Policy. Transfer basis as above. |
| Meta pixel Consent-gated: marketing | Marketing: attributing a signup to the advert that produced it | Meta, United States | Loaded and receives data only if you accept the marketing category in the cookie banner. Events sent are page and product views, checkout steps, a submitted contact form, a sign-up and a purchase. No names or message contents. When a payment is confirmed our server also sends Meta a SHA-256 hash of your email address, the IP address and browser of the order request and your Meta cookie ids (Conversions API); these are cleared from our side after 45 days. Details in the Cookie Policy. When accepted, this is a transfer to the United States under the EU–US Data Privacy Framework adequacy decision, or standard contractual clauses otherwise; see Privacy Policy section 6. |
| Independent partner hosts Partner tier only | Hosting the DGX Spark a Partner-tier instance runs on: the machine itself, its physical custody, power and internet connection | Each partner, at its own premises. By default an EU member state, Iceland, Liechtenstein or Norway; any country not under EU sanctions if you choose "any location" when you deploy | The instance's workload runs on the partner's machine; its traffic crosses the partner's line inside an encrypted tunnel. The partner has no login and is not told who the renter is. Involved only if you choose the Partner tier. A machine outside the EEA is a transfer to a third country, under the European Commission's standard contractual clauses, module three, between GPUwerk and the partner; see Privacy Policy section 6. |
GitHub and Google are not sub-processors. If you sign in through one of them, they act as independent controllers for what happens on their side, governed by their own privacy policy. They learn that you have an account with GPUwerk; nothing more passes through this relationship. Signing in with an email address instead involves neither of them.
Full detail on legal basis, retention, and international transfers for each of these is in our Privacy Policy. Our Article 28 data processing agreement is at /legal/dpa.
Partner tier
The Partner tier, listed in the console as "DGX Spark 1× (Partner)", runs on a DGX Spark that an independent partner owns and hosts. GPUwerk vets each partner, and every partner signs GPUwerk's partner agreement before a machine can be paired. Enrolling a machine wipes it and installs GPUwerk's locked operating system, which GPUwerk operates remotely; the partner gets no login on it. In the agreement the partner undertakes not to tamper with the machine, its firmware or its operating system, and not to attempt to inspect, copy or interfere with any renter's workload or data, and a breach lets GPUwerk suspend the machine at once. The machine's TPM proves its boot state at registration and on every boot, and each instance's workspace is its own encrypted volume, whose key GPUwerk holds and deletes when the instance is terminated. One renter at a time gets the whole machine, and it is wiped between renters.
You choose where the machine may be when you deploy. By default your instance is placed only on a partner machine in the European Economic Area. With "any location" it may be placed in a country outside the EEA, which is a transfer to a third country under the standard contractual clauses in our partner terms; the console shows the machine's country.
The partner still has physical access to the machine, and the locked system deters casual access rather than stopping a determined owner. The Partner tier has no SLA. You may use any data on it, and you choose the location. The full description, including what is and is not encrypted, is in our Privacy Policy, section 5a, and clause 9 of the data processing agreement.
This list names the category, not individual partners, who join and leave as they list and unlist machines. If you never choose the Partner tier, no partner host is involved in your processing.
Changes
This list is updated at this address as sub-processors change. We give account holders at least 30 days' notice by email before a new sub-processor is engaged, so there is time to review it or object. Partner hosts joining or leaving the Partner-tier category are not notified individually: a partner host is involved only in a Partner-tier instance you chose.