Partner Renter Terms Annex (Summary)
This is the text GPUwerk Platform partners accept in the partner console, which records the version each partner accepted.
Partner terms: Partner Agreement (version 6) · Self-billing Agreement (version 2) · Partner Data Processing Annex (version 3) · Partner Renter Terms Annex (version 3)
Changed from version 2: clause 5.1. Renters may use any data on Partner capacity in any location; the public or synthetic data limit for Partner capacity outside the EEA is removed. Renters choose the location.
This summary tells the Partner what GPUwerk promises renters of Partner capacity, so the Partner knows what its Nodes are held to. The binding renter terms are GPUwerk's customer terms plus the Partner-tier annex published to renters. This annex covers Partner-premises Nodes. A Hosted Machine (Partner Agreement, Schedule A) and a Sent-in Machine (Schedule B) are rented under GPUwerk's ordinary customer terms, like GPUwerk's own DGX Spark machines, and this annex does not apply to them.
1. What renters buy
1.1 Renters choose a Partner Node as a location of DGX Spark 1x when they deploy: each free Partner Node is shown as "Partner node" with its country, at the Partner price, next to GPUwerk's own machines. A renter who allows any location gets GPUwerk's own machine first and a Partner Node only while GPUwerk's own are all in use. The instance then runs as the Partner tier ("DGX Spark 1x (Partner)").
1.2 Renters are told that a Partner Node is operated by an independent partner at the partner's premises, reached over a residential or business internet connection, and located in the country shown in the listing.
2. What renters are not promised
2.1 No service-level agreement, no uptime guarantee and no benchmark result.
2.2 No Czech data-residency promise: the Node is in the country shown in the listing, which need not be the Partner's own country.
2.3 No on-premises delivery and no air-gapping.
3. Isolation and privacy
3.1 A renter's workload runs in an isolated instance. The Partner never learns the renter's identity and never has access to the renter's workload or data.
3.2 The instance's network traffic leaves through GPUwerk's network, not the Partner's local network, and cannot reach the Partner's local network.
3.3 The machine is wiped between renters.
4. Interruptions
4.1 If a Partner Node goes offline during a rental, the renter is not charged for the offline time.
4.2 A Partner may withdraw a Node at any time, without notice. Renters are told this before they rent.
4.3 If the Node is withdrawn during a rental, is unreachable for more than 15 consecutive minutes, or is suspended or removed by GPUwerk and the renter has to be moved off, the rental ends and is no longer charged, and GPUwerk credits the renter everything that rental was charged. The Partner loses the earnings of the last 24 hours of it (Partner Agreement 5.4).
4.4 After a withdrawal or an outage, the renter's workspace stays on the Node for 24 hours, unbilled, so the renter can reconnect and copy data off if the Node is reachable; then it is wiped. After a suspension or removal it may be wiped at once (Partner Agreement 5.5).
5. Data a renter may use
5.1 Renters may use any data on Partner capacity, in the European Economic Area and outside it. Renters choose the location of each instance; choosing a location suited to their data, for example one in the EEA where their data must stay there, is the renter's responsibility.