gagarinDocuments

Privacy policy

In force from 17 September 2026.

1. What this covers

This policy covers gagarin.cloud — the website, the CLI (gg) and the dashboard at my.gagarin.cloud. Together we call all of that the Service. “We” is gagarin; “you” is whoever is using it.

Using the Service means accepting this policy. If you do not accept it, stop using the Service.

2. What we collect

Only what the Service needs to work:

  • Who you are at GitHub or Google — you sign in through one of them, and it tells us your account’s id there and the email address it has verified. From GitHub we also keep your username and the date your GitHub account was created, because we turn away accounts younger than thirty days. Google’s sign-in shows us your name and picture as well; we do not keep them. We store no passwords, because there are none, and we keep no GitHub or Google token: the access they give us is used only while you sign in, to read the details above.
  • Your email address — the one GitHub or Google verified, which is where we write to you.
  • Technical details — IP address, browser, device, operating system — whenever you reach the website or the API.
  • Cookies for analytics, through Pager, which is our own analytics server and is open source. No ad networks and no third-party trackers touch this site. You cannot turn these off one at a time; we say so on your first visit rather than burying it here.
  • What you did and when — which projects, services and resources you created, which commands ran, and under whose name (“Claude Code on viktor-mbp”, for instance).
  • How your services are configured — image, port, environment variables. Environment variables are stored encrypted and are never read outside of starting your container.

We do not ask you for identity documents, photographs, or anything else beyond the minimum the Service needs to run.

3. What we use it for

  • Running the product — deploying, routing, and billing you for what you used.
  • Getting hold of you — approval requests, notifications, support.
  • Writing to you about the Service. When your account is created — the first time you sign in with GitHub or Google — your address goes on our customer list, and we may write to it about changes to the Service, incidents, and what is new. Every such message carries an unsubscribe link, and leaving the list changes nothing else: approval emails are how the Service works, not a mailing, and keep arriving.
  • Asking before anything irreversible. Deleting a service, destroying a resource, removing an address or handing over a project sends a button to the email address on the account concerned. The button does nothing by itself: it is pressed by somebody signed in to the dashboard as that account, so a forwarded or intercepted email approves nothing.
  • Working out what to fix next.

4. Who else sees it

Nobody, unless one of these applies:

  • the law requires it;
  • we cannot do our job without it — our payment provider, GitHub or Google for signing you in, the cloud provider whose machines your service physically runs on, or our email provider, Resend, which delivers every email we send and holds the customer list described above;
  • you told us to.

5. How it is kept

We keep data for as long as the purposes above require, including whatever period accounting and settlement records have to survive after an account is deleted. Account passwords are not kept at all — signing in goes through GitHub or Google. Machine secrets (your CLI credentials) are stored as an irreversible hash. Service environment variables are stored encrypted.

We take reasonable measures to protect all of it. Nobody can promise that anything sent over the internet is absolutely safe, and we are not going to be the first.

6. What we cannot promise

Sending anything over the internet carries risk, and you accept that by using the Service. We are not liable for data lost, stolen or exposed through somebody else’s doing or your own — losing your CLI credentials, for instance.

7. Changes to this policy

We may change it. The current version lives on this page with its date on it. Carrying on using the Service after a change means you accept the new version.

8. Getting in touch

Anything about your data: support@mail.gagarin.cloud.