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

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

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:

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.