legal
Privacy policy
Last updated: 3 November 2026
GPU Zero ("we") runs machine-learning training on cloud GPUs that you connect, and shows its runs, metrics and logs in a console. This page says which personal data that involves and what you can do about it.
Who is responsible
The data controller is Jonathan Vecchione, a natural person based in Italy. For anything about your data, write to hello@gpuzero.dev.
What we process
- Your account. When you sign in we receive, from our sign-in provider, your email address, your name and an identifier that stays the same across sign-ins. If you sign in with Google, these come from your Google account. We never see or store a password.
- Your workspace. What you put into GPU Zero to run training: projects (a repository address and branch), the GitHub accounts you connect and their names, jobs, runs with their configuration and parameters, metrics, the list of checkpoints, and the output your training scripts print. Run output may contain personal data if your scripts print it.
- Credentials you give us. Tokens and keys for your cloud, your storage bucket or your repositories. They are stored encrypted, are never shown back, and are only handed to the jobs launched with them, on the machines those jobs run on.
- Checkpoints. Model weights and training state are written by the training process itself, to the storage bucket your workspace connects, or, if it connects none, to a bucket we operate on Cloudflare R2. Our servers do not hold them.
- Technical data. Your IP address and request details pass through Cloudflare, which serves and protects our sites, and may appear in our server logs.
- Usage events. Our server records some of what a workspace does, as it happens: that it signed up, made a machine token, reported its first run, resumed, forked or exported a run, connected a cloud provider, queued a job, and that a machine was rented, taken back by its provider or given back and why. Each record holds the workspace, you if you did it, the kind of event and a few identifiers such as the run. Never your code, your keys or what your scripts print. We count them to know which parts of the product work for people; nothing is sent from your browser or from Ravex, Moonclip or the agent.
Signing in sets one cookie, on our API's address: your session, which no script on the page can read, and which is needed for the console to work. The console keeps your theme choice in your browser's local storage. We use no analytics, advertising or tracking cookies or scripts. Our sign-in provider sets the cookies its sign-in page needs, on its own domain.
Why, and on what basis
- To provide the service you sign up for - signing you in, running your jobs, showing their results: performance of a contract (GDPR art. 6(1)(b)).
- To keep the service secure and working - limits, abuse prevention, logs to fix faults: our legitimate interest (art. 6(1)(f)).
- To learn which parts of the product people use and where they stop, from the usage events above: our legitimate interest in improving it (art. 6(1)(f)). You can object by writing to us.
We do not sell your data, use it for advertising, or make automated decisions about you that have legal or similarly significant effects.
Who else handles it
These providers process data on our behalf, each only for its part:
- Auth0 (Okta) - sign-in.
- Google - only if you choose to sign in with Google.
- Hetzner Online GmbH, Germany - the server and database that hold your account and workspace.
- Cloudflare - delivery of our sites, the connection to our server, the default checkpoint storage, and the database's backups.
- Cloudflare Email Routing and Google (Gmail) - email you send to an @gpuzero.dev address is forwarded to a mailbox at Google.
- Resend, in the EU (Ireland) region - it sends the email we write from an @gpuzero.dev address, so it handles the recipient's address and the message.
- GitHub - only if you connect it, to read the repositories you choose.
- Amazon Web Services - only if you connect an AWS account, to obtain short-lived access to it.
- The GPU cloud providers your jobs run on, with your own account - they receive your code, the credentials your job needs and the data your training reads. On a marketplace such as vast.ai the machine belongs to a third party chosen by the marketplace, who can read what a job is given.
Some of them are based in, or transfer data to, countries outside the European Economic Area, such as the United States. Those transfers rely on the providers' Standard Contractual Clauses or the EU-US Data Privacy Framework.
People we contact about GPU Zero
If you work at an organisation that has written in public about a problem GPU Zero addresses - in a GitHub issue, say, or on its website - we may write to you once, at an address your organisation publishes for that purpose, or answer you where you wrote. We keep your name or your organisation's, that address, the public page where we found the problem, and whether you answered. We do not buy lists or collect personal addresses. The basis is our legitimate interest in telling people about a project relevant to their work (art. 6(1)(f)); we do not write where the law asks for your consent first. You can object at any time, by replying "no" or writing to hello@gpuzero.dev: we then stop, and keep only what we need so as not to write again. We delete the rest twelve months after our last exchange.
How long we keep it
Your account, as long as it exists. A run - its metrics, logs, history and the jobs that ran it - for six months: it is deleted on the first day of the seventh month after its experiment began, together with the runs forked from it, and its page says so from a month before, with a button to export it. Usage events are kept for the same six months. The checkpoints of a run stay in its bucket until you delete them. You can delete your account yourself, in Settings: it goes at once, with every workspace that is yours alone and the bucket we keep for it. If you ask us by email instead, we do it within 30 days. Checkpoints in a bucket of your own stay yours to delete.
We keep encrypted backups of the database, so that a failure does not lose your work: one a day for a week, one a week for a month, and one a month for six months. Data you or we delete stays in those backups until they expire, at most six months later, and nobody reads it there. If we ever restore one, we delete again what had been deleted since it was made.
Your rights
You can ask to access, correct, delete or export your data, to restrict its processing, or object to it, by writing to hello@gpuzero.dev. We answer within one month. You can also complain to the Italian data protection authority, the Garante per la protezione dei dati personali, or the authority where you live.
Children
GPU Zero is not meant for anyone under 14, and we do not knowingly hold their data.
Changes
When this policy changes, the date at the top changes with it. If a change affects what we do with data we already hold, we will tell you by email before it applies.