Data Processing Agreement
This document is incorporated into our Terms of Service for business customers who process personal data on their instance. The version at this address is the one that applies, and it supersedes any earlier draft sent by email.
1. Parties and roles
This agreement is between PRINT IT! SE, Altajská 1568/2, Vršovice, 100 00 Praha 10, Czech Republic ("GPUwerk", "processor") and the customer named on the account ("controller"). It applies wherever the controller processes personal data on a GPUwerk instance. Where no such data is processed, this agreement has nothing to act on and imposes no obligation on either side.
2. Subject matter and duration
GPUwerk provides dedicated, single-tenant GPU compute, in one of the tiers listed on the pricing page (currently NVIDIA DGX Spark, with further tiers listed as they become available). The controller decides what runs on the instance, including whether it processes personal data at all. GPUwerk hosts the machine but does not access, read, copy, index, or analyse the content of the controller's instance. On the Partner tier, which the controller can choose instead and which clause 9 describes, an independent partner hosts the machine and GPUwerk operates it remotely. Processing under this agreement lasts for as long as the controller's account exists and continues only for the time needed to give effect to termination as described in clause 8.
3. Nature and purpose of processing
The nature of the processing is infrastructure hosting: storage on the instance's local NVMe while it runs or is stopped. GPUwerk keeps no other copy of the workspace. If the account's credit reaches zero or its monthly budget is reached, the instance is stopped and its node released for other customers to rent. The workspace is kept on that node for up to 48 hours, or until another customer rents the node, whichever comes first, and is then deleted unless the controller has started the instance again. The purpose is solely to make the controller's dedicated compute available and to preserve its state between stop and restart. GPUwerk does not process the content for any purpose of its own, including training, analytics, or marketing.
4. Categories of data subjects and personal data
The controller determines what it puts on the instance, so the categories of data subjects and personal data are whatever the controller chooses to process there, for example its own customers, employees, or end users, and whatever data types its workload handles. GPUwerk has no visibility into these categories and cannot enumerate them; the controller is best placed to record them in its own Article 30 records.
5. Documented instructions
GPUwerk processes personal data on the instance only by hosting the hardware it runs on, and only for as long as the account exists. GPUwerk does not otherwise access or act on the content, so there are no further instructions to give or receive at that layer, and none are needed. These terms, the controller's choice of tier and, on the Partner tier, of location when it deploys an instance, and the controller's actions in the console and API are its documented instructions, including with regard to any transfer of personal data to a third country. GPUwerk will not transfer the controller's personal data to a third country except on those instructions, or where Union or Member State law to which GPUwerk is subject requires it; in that case GPUwerk will inform the controller of that legal requirement before processing, unless that law prohibits such information on important grounds of public interest. If a documented instruction requires clarification, or GPUwerk considers an instruction would infringe the GDPR or another EU data protection provision, GPUwerk will inform the controller before carrying it out.
6. Confidentiality
GPUwerk ensures that persons authorised to access the platform's infrastructure have committed themselves to confidentiality, and access is limited to what their role requires, consistent with the access control measures described in our Privacy Policy, section 12.
7. Security of processing
GPUwerk applies the technical and organisational measures required by Article 32 GDPR. They are listed in Annex 1, which forms part of this agreement: among them a machine dedicated to a single customer, with no workload sharing between customers, SSH public key authentication with passwords disabled fleet-wide, deletion of a tenant's container and workspace before a node is offered to anyone else, and access control limiting staff access to what their role requires. Partner-tier instances have the different measures and limits set out in clause 9 and in section 5a of the Privacy Policy. GPUwerk may update the measures as technology develops, provided the overall level of protection does not fall.
8. Deletion on termination
On termination of an instance, GPUwerk deletes the container and its workspace volume from the node, as described in our Terms of Service, section 7. Before a node is allocated to another customer it is sanitised: every tenant container and volume is removed from it, and the node fails its readiness check and is not allocated while any remain. This is deletion at the filesystem level. GPUwerk does not currently operate self-encrypting drives or full-disk encryption on the nodes, and does not claim a cryptographic erase. The controller is responsible for exporting anything it needs before termination, since termination is not reversible. Exhaustion of credit or the monthly budget stops the instance as described in clause 3; termination and deletion follow when another customer rents the node, or 48 hours later at the latest, unless the controller has started the instance again before then.
GPUwerk keeps no backup or other copy of any workspace. The workspace exists only on the instance's node. Copies of workspaces made before 16 October 2026 may remain in GPUwerk's encrypted system backups until they roll off, by October 2027 at the latest; GPUwerk does not restore from them.
9. Sub-processors
GPUwerk's own tiers. On its own tiers, on-demand and reserved, GPUwerk engages Hetzner as network gateway for the processing described in this agreement, and Cloudflare only for a model endpoint that the controller uses through the gateway, both described next: those instances run on machines GPUwerk operates in its own EU-Central data center in Hradec Králové, Czech Republic, and the only other party in that path is Hetzner Online GmbH (Germany), described next. Some of those 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. Introducing the Partner tier changes nothing for them.
Hetzner (network gateway). GPUwerk engages Hetzner Online GmbH, Germany, as a sub-processor for the gateway server it rents in Helsinki, Finland, through which the network traffic of instances on its own tiers is forwarded: inbound SSH (and VNC where the controller enabled it) and the instance's outbound internet traffic, which leaves from the gateway's address. The instance, its workspace and its storage stay on GPUwerk's machines in Hradec Králové and are not on the gateway. Traffic between the gateway and the machine runs inside WireGuard tunnels. The gateway forwards connections at network level: it does not terminate SSH or TLS, and GPUwerk does not capture or log the content of forwarded traffic there. SSH and TLS sessions therefore stay encrypted end to end between the controller's or remote party's endpoint and the instance. Traffic that a workload sends or receives unencrypted, such as plain HTTP, is readable on the gateway while it passes. The gateway is inside the European Union.
Cloudflare (gateway-terminated model endpoints). A model preset can also have a public HTTPS endpoint, and the API reports where its TLS ends (https_termination). Where it ends on the instance itself (instance), the gateway forwards it encrypted, like SSH, and nothing above applies differently. Where it ends on the gateway (gateway), requests and responses to that endpoint pass through Cloudflare, Inc. (United States) and are decrypted by Cloudflare and by Caddy on the gateway, then forwarded to the machine inside the WireGuard tunnel. For that endpoint's traffic Cloudflare is a sub-processor; this is a transfer to the United States under the EU–US Data Privacy Framework, with the standard contractual clauses in Cloudflare's data processing addendum as a fallback. Sending requests to a gateway-terminated endpoint is the controller's choice and its authorisation for this; SSH, including port forwarding to the model, avoids it. A controller that never chooses the Partner tier and does not use a gateway-terminated endpoint has no sub-processor at the instance level other than Hetzner. The general sub-processor list for the website, billing and account side of the service, which does not touch instance content, is published at /legal/sub-processors. If GPUwerk ever engages a further sub-processor for instance-level processing on its own tiers, it will give the controller at least 30 days' notice by email before the change takes effect, and the controller may object on reasonable grounds relating to the protection of personal data within that period.
Partner tier. The Partner tier, listed in the console as "DGX Spark 1× (Partner)", runs on a DGX Spark that an independent, vetted partner owns and hosts at the partner's own premises. If the controller chooses that tier for an instance, the partner hosting the machine is a sub-processor for that instance only, and choosing the tier is the controller's authorisation for it. The following applies:
- Location. The machine is at the partner's premises, not necessarily in the Czech Republic. The controller chooses the location when it deploys the instance. By default the instance is placed only on a machine in an EU member state, Iceland, Liechtenstein or Norway, all in the European Economic Area. If the controller chooses "any location", the instance may be placed on a machine in a country outside the EEA, though never in a country under EU sanctions. The console shows the machine's country once the instance is placed.
- Transfers outside the EEA. Only where the controller chose "any location" and the instance is placed on a machine outside the EEA, processing on that instance is a transfer of personal data to a third country under Chapter V GDPR. For that transfer GPUwerk relies on the European Commission's standard contractual clauses (Implementing Decision (EU) 2021/914), module three, processor to processor, between GPUwerk and the partner hosting the machine, under Article 46(2)(c) GDPR. Those clauses form part of GPUwerk's partner terms, and GPUwerk has documented its assessment of the transfer under clause 14 of the clauses. Choosing "any location" is the controller's authorisation for that transfer.
- The partner's role. The partner provides the machine, its physical custody, and its power and internet connection. Instance traffic crosses the partner's line inside an encrypted WireGuard tunnel to GPUwerk, reaches the internet from GPUwerk's network, and cannot reach the partner's local network.
- No access by the partner. Enrolling the machine wipes it and installs GPUwerk's locked operating system, which GPUwerk operates remotely. The partner has no login: interactive accounts are locked, local console logins and the desktop are off, and SSH is limited to GPUwerk's operators over the tunnel with short-lived certificates. The partner is not told who the controller is.
- Partner agreement. Every partner signs GPUwerk's partner agreement before a machine can be paired. Its data processing annex, which every new partner accepts and which a partner must have accepted before GPUwerk places an instance on its machine outside the EEA, binds the partner, as GPUwerk's sub-processor, to the obligations of this agreement under Article 28(4) GDPR, including notifying GPUwerk of a personal data breach within 24 hours. In the agreement the partner also permits GPUwerk to install, update and remotely operate the operating system and to verify the machine's boot state by TPM attestation, and 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 workload or data. A breach allows GPUwerk to suspend the machine immediately.
- Attestation, encryption and wiping. The machine's TPM proves its boot state at registration and on every boot; its own secrets, such as its tunnel key, and its container storage are on encrypted volumes that open only after that check passes, and a change in the boot measurements suspends the machine. Unless the controller turns it off at deploy, the instance's workspace is its own encrypted volume, whose key GPUwerk's control plane holds and releases only to that machine, after a TPM check made for that instance; terminating the instance deletes the key, so the volume can no longer be opened. With workspace encryption turned off, the workspace is stored unencrypted on the machine's disk, is readable by whoever has physical access to the machine, and is deleted at filesystem level on termination. Choosing that is the controller's decision and its responsibility for the data it places there. One renter at a time gets the whole machine, and it is wiped between renters.
- Limits. The partner has physical access to the machine. Whoever holds a machine controls its firmware and install media, and the TPM measurements cover the boot chain, not everything that runs afterwards, so the locked system deters casual access but cannot stop a determined owner. The encryption protects the workspace while its volume is closed; while it is open, for example while the instance runs, its data is readable on the machine.
- Permitted data and location. The Partner tier is offered without an SLA. The controller may process any data on any tier, in any location, and decides the location of each instance. Choosing a location that meets the controller's own obligations, for example a location in the EEA where personal data must not leave it, is the controller's responsibility.
Individual partner hosts join and leave as partners list and unlist machines. The sub-processor list names the category, not the individual hosts, and GPUwerk does not send notice of changes within that category, because a controller's data reaches a partner host only through a Partner-tier instance the controller chose.
10. Assistance with data subject requests and Articles 32 to 36
Because GPUwerk cannot see the content of the controller's instance, it cannot itself locate or respond to a data subject request about that content. Where a data subject contacts GPUwerk directly about data on a customer's instance, GPUwerk will refer the request to the controller, since the controller alone can act on it. GPUwerk will otherwise give the controller reasonable assistance in responding to data subject requests, to the extent the request concerns the infrastructure layer GPUwerk operates. If GPUwerk becomes aware of a personal data breach affecting the controller's instance, it will notify the controller without undue delay, consistent with Article 33(2) GDPR, so the controller can meet its own 72-hour notification duty to its supervisory authority. The notice will describe, as far as GPUwerk knows it, the nature of the breach, the likely consequences and the measures taken or proposed, and GPUwerk will add further information as it becomes available.
Taking into account the nature of the processing and the information available to it, GPUwerk will also give the controller reasonable assistance with its obligations under Articles 32 to 36 GDPR: the security of processing, notifying a breach to the supervisory authority and communicating it to data subjects, data protection impact assessments, and prior consultation with the supervisory authority. In practice this means answering questions about the infrastructure and the measures in Annex 1, without charge for reasonable requests.
11. Audits
GPUwerk will make available to the controller all information necessary to demonstrate compliance with Article 28 GDPR and this agreement, and will allow for and contribute to audits, including inspections, conducted by the controller or an auditor it mandates. GPUwerk will first answer written questionnaires and provide documentation, which is usually enough for dedicated single-tenant hardware. Where the controller still considers an inspection necessary, it gives at least 30 days' written notice, the parties agree its scope and timing in good faith, the auditor is bound by confidentiality, and the inspection must not give access to other customers' data or machines. Each party bears its own costs, except that the controller pays GPUwerk's reasonable costs for more than one inspection in any twelve months unless the inspection follows a personal data breach or a supervisory authority's request. A supervisory authority's audit rights are not limited by this clause.
12. Governing law
This agreement is governed by the laws of the Czech Republic, on the same terms as clause 16 of our Terms of Service, which that clause sets out in full and which apply here without repetition.
13. Related documents
See also our Privacy Policy, Terms of Service, and Sub-processors.
Annex 1. Technical and organisational measures
| Area | Measures |
|---|---|
| Isolation | One customer per physical machine for the whole rental; no workload sharing between customers. The customer has root inside its container, not on the host. Each instance has its own network segment, and a host firewall blocks traffic between instances and to the management network. |
| Encryption in transit | Control-plane traffic to every machine runs inside WireGuard tunnels. The website, console and API use TLS. Customer SSH and VNC sessions are encrypted end to end by those protocols. Instance traffic is forwarded through the Helsinki gateway (clause 9); unencrypted traffic from a workload, such as plain HTTP, is readable there in transit. A model endpoint terminated on the gateway is decrypted by Cloudflare and on the gateway (clause 9); one terminated on the instance is not, and a model's own port is not reachable on the instance's public address without that endpoint's API key check. |
| Encryption at rest | Machines of GPUwerk's own tiers, in GPUwerk's datacenter: no encryption at rest at present; deletion is at filesystem level, with physical access to the datacenter limited to GPUwerk. Partner-tier machines: the machine's own secrets and its container storage are on encrypted volumes that open only after a TPM attestation of its boot state; each instance's workspace is its own encrypted volume, whose key GPUwerk's control plane holds and releases only to that machine after a TPM check made for that instance, and terminating the instance deletes the key, so the volume can no longer be opened. A controller may turn workspace encryption off for an instance at deploy; that instance's workspace is then not encrypted at rest. Core dumps are off on Partner-tier machines. |
| Access control | Operator access to machines is by SSH key or short-lived SSH certificate only; passwords are disabled. Partner-tier machines have no local logins, and partners have no access to the operating system. Hosting customers whose machines GPUwerk hosts have no access to them while someone else rents them. Administrative actions in the control plane are recorded in an audit log. Staff access is limited to what the role requires, and staff are bound to confidentiality. |
| Deletion and reuse | On termination the container and workspace are deleted; before a machine is offered to another customer every tenant container and volume is removed, and the machine is not allocated until that check passes. No copy of a workspace is kept anywhere (clause 8). |
| Physical security | Machines of GPUwerk's own tiers are in GPUwerk's datacenter in Hradec Králové, Czech Republic, with physical access limited to GPUwerk. Partner-tier machines are at the partner's premises; the partner agreement forbids tampering, and a change in the machine's boot measurements suspends it. |
| Availability and recovery | The control plane and account database are backed up every six hours, encrypted, to separate hardware. Customer workspaces are not backed up; the customer is responsible for its own copies. |
| Monitoring and incidents | Health checks every five minutes with alerting to the operator; a public status page; a written procedure for assessing personal data breaches and notifying controllers without undue delay. |
| Software and updates | Images are built from pinned, digest-verified sources. Security updates are applied to hosts and images; machine images and agent code are deployed only by GPUwerk. |