Cookie Policy
This page lists everything GPUwerk stores in your browser. It is short, because there is not much, and the part that is optional is genuinely optional: nothing in the analytics or marketing categories is downloaded at all until you say yes.
The short version
- Necessary storage keeps you signed in and remembers your cookie choice. It cannot be switched off, and it is not used to profile you.
- Analytics and marketing are off by default. Not "loaded but disabled": not fetched at all.
- Marketing includes remarketing: with it on, Google and Meta may show you GPUwerk adverts after your visit.
- Refusing is one click, in the same place and the same size as accepting.
- You can change your mind at any time: . Turning a category off deletes the cookies it set.
- Your choice is remembered for twelve months, then we ask again.
- None of this touches your instances. Nothing on this page can see a workload, a model, a prompt or a file on a rented machine.
- A visit through an affiliate link (
?aff=) sets one first-party cookie,gpuwerk_aff, so that visit can be counted for the creator. It is separate from the analytics and marketing choice. Details are under “Affiliate attribution”.
Necessary
Set on the basis of Article 6(1)(f) GDPR and the corresponding national implementation of the ePrivacy Directive. These are what "strictly necessary" actually means: without them the thing you asked for does not work.
| Name | Purpose | Expires |
|---|---|---|
gpuwerk.consent.v1 | Your choice, covering gpuwerk.com and console.gpuwerk.com, so the banner does not ask again on every visit. Stored in local storage, not sent anywhere except once, as described under "Proving we asked" below. | 12 months |
gpuwerk_consent | Your cookie choice, as a cookie on gpuwerk.com and its subdomains, so the console honours the same decision. | 1 year |
gpuwerk.cid | A random string with no meaning outside our consent log. It exists so a withdrawal can be matched to the consent it withdraws. It is not an advertising identifier and is never joined to your account. | 12 months |
sb-…-auth-token | Keeps you signed in to the console after you authenticate, whether that was through GitHub, through Google, or with your email address. | Session |
sy.* | Console interface state: which view you had open, your saved preferences. Local storage, never transmitted, except sy.promo below. | Until cleared |
gpuwerk.promo, sy.promo | A promotional code you opened a link with (?promo=), kept so the free hours you clicked for reach the account you create. gpuwerk.promo is session storage on gpuwerk.com, used only to add the code to links into the console. sy.promo is local storage in the console, sent once to our server when you are signed in, then deleted. Neither is sent to Google, Meta or PostHog. | End of the tab session; 7 days at most |
Affiliate attribution
This cookie is set only when the address you opened contains ?aff=, the code a creator was given for the affiliate programme. Our own script sets it. No advertising network is involved, and the code is not sent to Google, Meta or PostHog. Those tools still load only if you accept analytics or marketing.
| Name | Purpose | Expires |
|---|---|---|
gpuwerk_aff | The creator's public code and the time you opened the link. Nothing else: no name, no email, no account id in the cookie. It is stored on gpuwerk.com and its subdomains, which is what lets the console see the same code. We count a page view on the page the link opened, and on the home page, pricing, the DGX Spark page, the GPU pages, the docs index, the benchmarks page, the console home and the console deploy view. We also count a click on a control that is already marked as a call to action (Create account, Deploy, Pricing and the same kind of control). A later visit through a different affiliate link replaces the cookie. Deleting it, or the gpuwerk.com entry in your browser, ends the attribution. | 90 days |
The 90 days are the cookie window in the terms on the affiliate page. Legal basis: Article 6(1)(f) GDPR, a legitimate interest in knowing which creator's link a visit came from, so a commission agreed with that creator can be calculated. The cookie is not required to rent a machine, and refusing analytics or marketing does not clear it. The server stores the code, the page path, whether the event was a view, a click or a sign-up, and the time. A sign-up also stores the account id. No IP address is stored with these events. This is separate from the referral credit a customer can share from the console.
Analytics: optional, off unless you accept
Article 6(1)(a) GDPR, your consent. We use this to find out which pages people actually read and where the documentation loses them. It is aggregate: we are looking at which page fails, not at who you are.
| Name | Set by | Purpose | Expires |
|---|---|---|---|
_ga, _ga_* | Google Analytics 4 | Distinguishes one visit from another so a session is counted once. IP anonymisation is on. | 2 years |
ph_* | PostHog (EU region) | Which pages a visit moved through, so a drop-off in signup can be located. Configured without session recording and without autocapture, and PostHog is told to discard the IP at ingest. | 12 months |
Marketing: optional, off unless you accept
Article 6(1)(a) GDPR, your consent. This category does two things. It attributes a signup back to the advert or link that produced it. And it lets Google and Meta add your browser to GPUwerk remarketing audiences, so that they can show you GPUwerk adverts on their services after your visit. We define those audiences by the pages you viewed and the steps you took here, such as a started sign-up or a host application; we do not see who is in them, and membership ends 180 days after your last visit that qualified. It is also the category that involves Google and Meta, and it is the one to leave off if you would rather they did not learn you were here or show you our adverts. Leaving it off has no effect on the service.
| Name | Set by | Purpose | Expires |
|---|---|---|---|
_fbp, _fbc | Meta pixel | Attributes a signup, an enquiry or a purchase to the Meta advert it came from, and adds your browser to GPUwerk remarketing audiences on Facebook and Instagram. Fires page views, product views, cart and checkout steps, enquiries, the first sign-in in the console and purchases with their value, never names or emails. | 3 months |
_gcl_* | Google Ads | Measures which Google advert led to a sign-up, an enquiry, a started checkout or a purchase (conversion tracking, with the order value). With a sign-up or a purchase, a one-way SHA-256 hash of your email address goes with the conversion (“enhanced conversions”) so Google can match it to an advert it showed you; the address itself is never sent. Google may also add your browser to GPUwerk remarketing audiences for its advertising services, and may set its own cookies for that on its own domains. Only present once Google Ads conversion tracking is switched on. | 3 months |
gpuwerk_ft | GPUwerk (first-party) | Remembers the first advert or link that brought your browser here: the campaign tags in that link (utm_*), the Google campaign id (gad_campaignid), the Google or Meta click id (gclid, gbraid, wbraid, fbclid), the page you landed on (without its query string), the site that linked to it, and when. It is read by nobody else. If you create an account within its lifetime, the console saves it with your account once, so we can see which campaign produced sign-ups and first payments. The Meta click id from it may be sent to Meta with your sign-up and purchases (Conversions API, see the Privacy Policy). If you apply to host a machine on GPUwerk Platform, the same values are sent with the application and kept with it, so we can see which campaign brought hosts; the click ids are deleted from the account after 90 days, the campaign tags are kept. Removed as soon as marketing is switched off. Without this cookie no earlier visit is remembered: only the campaign tags carried in the page addresses of the visit you sign up in are saved with a new account, with no cookie or other storage (see “Sign-up details” in the Privacy Policy). | 3 months |
Accepting this category is a transfer of personal data to the United States. Google and Meta are both established there. Our Privacy Policy sets out the Chapter V GDPR mechanism this rests on. Rejecting it means no such transfer happens, because the scripts are never fetched.
When you pay: the same choice, reported by our server
A purchase is easy to miss in the browser: the tab is closed after paying, a bank transfer arrives days later, and the checkout page loads Google Analytics at most. So when a payment is confirmed (a card payment, a matched bank transfer or a credit top-up), our server can report it too, to the same tools and only as far as the choice you had made when you placed the order allows. The browser and the server send the same order number, so each purchase is counted once.
- Google Analytics (Measurement Protocol), only if you allowed analytics: the order number, value, currency and products, with the random Google Analytics id from your
_gacookie. No email, name or IP address. - Meta (Conversions API), only if you allowed marketing: the order number, value, currency and products, a SHA-256 hash of your email address and of your account id, the IP address and browser of the request that placed the order, and your
_fbp/_fbccookies if present. The same applies to a new account created at the store checkout and to a GPUwerk Platform partner application and, once switched on, to the listing of a host’s first machine for rent (the consent is the one in force when the host applied or accepted the partner terms). Meta may also use these events for the remarketing audiences described above.
An account’s first credit top-up is reported once more, as a separate “first top-up” event with the same data and the same choice, because that is the result our adverts are measured on. A hardware order goes to Google Analytics only, never to Meta or Google Ads.
With analytics and marketing both off, nothing is reported and none of these identifiers is stored with your order. What is stored for this is kept with the order and its personal parts (the cookie ids, IP address and browser) are deleted after 45 days. Legal basis: Article 6(1)(a) GDPR, the consent you gave in the banner.
Error reporting, which is not a cookie
We run Sentry to catch JavaScript errors, so that a broken signup page is noticed by us rather than only by the person it broke for. It sets no cookie and stores no identifier in your browser, so there is no cookie choice attached to it. It is configured with personal data collection off, IP capture off and no session replay, and it runs in Sentry’s EU region. Legal basis: Article 6(1)(f) GDPR, our legitimate interest in a service that works.
What we deliberately do not do
- No data brokers, and no audience lists sold or bought. Remarketing, in the marketing category and only if you allow it, is the one way your visit here can change what you see on other sites.
- No email lists uploaded to advertising platforms, except our own account holders’ hashed addresses. That matching does not use cookies, so it is not part of this choice: it is described in our Privacy Policy, and the unsubscribe link in our marketing email stops it.
- No fingerprinting, and no attempt to identify you if you refuse cookies.
- No third-party fonts. The typeface on this page is served from our own servers precisely so that loading it does not tell anyone else you were here.
- No consent wall. Refusing gets you the entire site; there is no content behind an "accept to continue".
- Nothing in any category is applied to a rented instance. Cookies are a website matter and stop at the website.
Proving we asked
Article 7(1) GDPR requires us to be able to demonstrate that consent was given. A record that lives only in your own browser proves nothing, so when you make a choice here we store one copy on our server: the random gpuwerk.cid, the time, the version of this policy you were shown, and which categories you allowed. No name, no email address and no IP address is in that record. It is append-only, so a withdrawal is written as a new entry rather than by editing the old one.
Changing your mind
Use , here or in the footer of any page. Withdrawal takes effect immediately: the tools are silenced on the page you are on, and the cookies they set are deleted rather than left to expire. Withdrawal does not affect processing that already happened, which is why it is worth deciding before rather than after.
You can also block or delete cookies in your browser directly, and browser-level "do not track" or global privacy control signals are respected where your browser sends them.
FitLocally (fitlocally.com)
FitLocally, our model-and-hardware reference site, asks separately; a choice there does not apply here, or the other way round. It has one optional category, analytics, and no marketing. Its banner offers “No” and “Allow” at the same size, and Global Privacy Control or Do Not Track counts as “No”. Details are in section 5b of the Privacy Policy.
| Name | Type | Purpose | Expires |
|---|---|---|---|
fitlocally.consent.v1 | Local storage, necessary | Remembers your answer to the analytics question. Stays in your browser; no copy is sent to us. | Asked again after 12 months |
fitlocally-hw | Local storage, necessary | Remembers the machine you picked so other pages can show results for it. Never sent anywhere. | Until you clear it |
_ga, _ga_P15V25C67C | Cookie, Google Analytics 4, only after “Allow” | Distinguishes one visit from another so page views are counted once. Advertising storage and Google signals are off. Deleted if you later choose “No”. | 2 years |
Related documents
The full picture of what we process and why is in our Privacy Policy. Company details are in the Imprint, and the contract is the Terms of Service.