Data processing agreement

In force from 16 November 2026. For the personal data inside what you run here. It is part of the terms of service and applies without a signature.

1. When this applies, and who is who

It applies whenever the applications, databases, volumes, logs or project memory you keep on Gagarin contain personal data about other people, and European or UK data protection law (the GDPR, the UK GDPR) applies to you because of it. For that data you are the controller — or a processor for somebody who is — and we are your processor: IE VIKTOR ROZENKO, an individual entrepreneur registered in Georgia (no. 345782879), Lermontov St., Batumi, Georgia, who operates Gagarin.

It does not cover the data we hold about you as our customer — your account, your email address, your bill. For that we are the controller, and the privacy policy is the page.

If you would like a signed copy for your records, write to support@mail.gagarin.cloud. The text will be this one.

2. What the processing is

  • Subject matter and nature — hosting: running your container images, storing what they write, routing traffic to them, backing up the resource types the terms say are backed up, keeping their logs, and storing your project memory.
  • Purpose — providing the Service to you under the terms, and nothing else.
  • Duration — for as long as the data is on the Service, and until it has been deleted as §3(g) describes.
  • Kinds of personal data, and whose — whatever you choose to put here. We do not know and do not look. Typically: your own users and customers, and their names, contact details, identifiers and whatever your application records about them.
  • Special categories — the Service is not built for health data, data about criminal convictions, or the other categories the GDPR treats as special. If you put them here, protecting them adequately — encrypting them in your application before they reach a database, for instance — is yours to do.

3. What we undertake

  • (a) Only on your instructions. We process this data only as you instruct. Your instructions are these terms, and what you and your agents tell the Service to do — every deploy, every command, every API call. We do not use it for anything of our own: no analytics on it, no training on it, no reading it out of curiosity. If the law ever requires us to process it otherwise we tell you first, unless that law forbids telling you. If we think an instruction breaks data protection law we say so.
  • (b) Confidentiality. Anybody who can reach your data on our side is bound to keep it confidential. Today that is one person.
  • (c) Security. We keep the measures in Annex 2 in place, and may change them only for something no weaker.
  • (d) Sub-processors. You give us a general authorisation to use the sub-processors in Annex 1. Each is bound by a contract with data protection terms no weaker than these, and we remain answerable to you for what they do. We may add or replace one at any time. Annex 1 on this page is the list and is how you are informed: it is updated when a change is made, and we do not promise to tell you separately. If you object to a change you may leave, under the terms’ clause on switching, at no charge.
  • (e) Requests from the people the data is about. If somebody writes to us to exercise a right over data that is yours, we pass it to you and do not answer it ourselves. The Service already gives you the means to find, correct, export and delete what you keep here; where that is not enough, we help as far as we reasonably can.
  • (f) Breaches, and your other obligations. If we become aware of a breach of security that leads to your data being lost, altered, disclosed or accessed without authority, we tell you by email without undue delay and in any case within 72 hours, with what we know — what happened, what data, what we are doing about it — and keep telling you as we learn more. We also give you the information you reasonably need for your own security duties, impact assessments and dealings with a regulator.
  • (g) Deletion and return. You can export your data at any time, as the terms’ clause on switching sets out. Destroying a resource, a service or a project deletes its data; so does closing your account. Backups we took expire within fourteen days of that, and our own database backups within seven. We keep nothing after that unless EU or member-state law requires it, and we will tell you if it does.
  • (h) Showing our work. We give you the information needed to show these obligations are being met, and answer a reasonable written audit questionnaire once a year, or whenever there has been a breach or a regulator requires it. An inspection in person is possible where a questionnaire cannot answer what the law requires you to know: on 30 days’ notice, at your cost, under a confidentiality agreement, and not in a way that would expose another customer’s data. There is no data centre of ours to walk round — the machines are Scaleway’s, and its certifications and audit reports are what we pass on for that layer.

4. What you undertake

That you have the right to put the data here and to instruct us as you do — a legal basis for it, and whatever you owed the people concerned by way of notice. That you will keep credentials for the Service safe, configure what you run sensibly, and keep your own copy of anything on a resource the terms describe as not backed up. And that the address on your account is one somebody reads, because that is where a breach notice goes.

5. Where the data is, and transfers

Your data is stored and processed in France, in Scaleway’s fr-par region, and we do not move it anywhere else. The processor, though — the person who operates Gagarin — is established in Georgia, which the European Commission has not recognised as providing adequate protection, and administers the platform from there. Engaging us is therefore a transfer in the GDPR’s sense, and it needs a legal footing. This is it:

  • The standard contractual clauses annexed to Commission Implementing Decision (EU) 2021/914 are incorporated into this agreement and apply between us: Module Two where you are a controller, Module Three where you are a processor. You are the data exporter and we are the data importer.
  • In those clauses: the optional docking clause (7) does not apply; under clause 9, option 2 (general written authorisation) applies, and changes are notified by updating Annex 1 as §3(d) describes; the optional wording in clause 11 does not apply; under clause 17, option 1 applies and the governing law is that of France; under clause 18 the courts are those of France. Annex I is §§1 and 2 of this page, with the French data protection authority (CNIL) as the competent supervisory authority unless yours is another; Annex II is Annex 2 below; Annex III is Annex 1 below.
  • For data subject to the UK GDPR, the UK International Data Transfer Addendum to those clauses (version B1.0) applies as well, completed with the same information, and neither of us may end it under its section 19.
  • Where those clauses and the rest of this page conflict, the clauses win.

6. How this sits with the terms

This page is part of the terms. About personal data it takes priority over them, except that the limits on liability in the terms apply to this agreement too — as between you and us, and never so as to limit what either of us owes to the people the data is about or to a regulator. It ends when the last of your data has been deleted.

Annex 1 — Sub-processors

  • Scaleway SAS (France) — the machines, block and object storage, the managed database and the network your services, volumes, backups, logs and project memory are on. Location: fr-par, Paris. This is the only company that holds the data this agreement is about in the ordinary running of the Service.
  • OpenAI (United States) — only if you use the dashboard’s Agent tab. That tab reads your projects, logs and project memory on your behalf and passes what it reads through OpenAI. If your logs or memory hold personal data and you do not want it to leave the EU, do not use that tab; nothing else on the Service touches it.

The other companies named in the privacy policy — Vercel, PostHog, Resend, Dodo Payments and the rest — handle data about you as our customer. None of them receives what is inside your services, databases or volumes.

Annex 2 — Security measures

What is true of the platform today. We would rather list eight things that are real than thirty that are aspirations.

  • Location. All customer data is in one EU region, with one EU provider.
  • Encryption in transit. Every public address is served over TLS, with a certificate we issue and renew; the API, the dashboard and the MCP server are HTTPS only.
  • Encryption at rest. The platform’s own database, and object storage, are encrypted at rest by Scaleway. Your services’ environment variables are encrypted by us before they are stored and decrypted only to start your container. The title and body of project memory notes are encrypted before they are stored. We hold those keys.
  • Credentials. There are no account passwords. CLI and agent credentials are stored only as an irreversible hash, can be revoked individually, and take effect on the next request.
  • Isolation between customers. Each project is its own namespace. A service accepts no traffic from another service unless the dependency has been declared; the default is to refuse.
  • Destructive actions need a person. Deleting a service, destroying a resource, releasing an address or transferring a project cannot be done with an agent’s credential alone: the account owner confirms it, signed in to the dashboard.
  • Backups. Postgres, qdrant and iggy resources nightly, each kept fourteen days; the platform database daily, kept seven. Other resource types are not backed up, and the terms say so.
  • Abuse controls. Outbound mail ports are blocked for every service, and sustained resource use is measured and reviewed by a person.
  • Access. One person administers the platform. Access to the infrastructure provider is by individual credentials that expire and are rotated.
  • Logs. Service logs are kept seven days and then deleted. An audit trail records which credential did what to each project.