Privacy policy

1. Who we are

anturno is operated by Anturno ("we"). We are the controller of the account, usage and marketing data described below. For the content your company brings to the service we are a processor: your company decides what goes in, and we handle it on its behalf. Questions go to hello@anturno.cloud.

2. What we collect

Account data: the name, email address, GitHub login and profile picture of the people on your workspace.

Content: the repositories, tickets, documents and pages you connect, and the plans, diffs, pull requests, transcripts and traces a run produces. So that a session can resume on another machine, its uncommitted work is also saved to a hidden ref (refs/anturno/wip/) in your own repository. You control what is connected and can disconnect it at any time.

Usage data: for each call to the public API and the MCP server, the token, the person, the route, the status, the IP address and the user agent. Run counts, durations, model token use and cost. Server logs of requests and errors.

Support: what you write to us, including the reply address you give.

Marketing data: if you book a demo on the site, your name, email address, company, team size and what you wrote, which reach us by email through Resend and stay in our inbox. If you subscribe to the newsletter, your email address, which reaches our inbox and is kept as a contact in Resend. You can unsubscribe from any issue; to have the address deleted, write to us.

3. Why we use it

To run the service you asked for: to start a run, to build the change, to write back a status and to keep the trace in your workspace. To support you when you write to us. To keep the service secure, which includes detecting abuse and keeping an audit log. To answer a demo request and send the newsletter you subscribed to.

We do not use your content to train models. We do not sell personal data, and we do not share it with advertisers.

A run sends prompts, which include parts of your code, to the model provider your workspace uses. What that provider keeps, and whether it may train on it, is set by the terms of the key or subscription you connect. The run reports and wiki checks the engine writes itself go to that provider too. If a workspace turns on the optional model pass of inbound screening, the engine also sends the outside text it screens, such as an issue body or a comment, to the same provider on the same terms.

4. How long we keep it

Each session runs in its own microVM. The microVM and its disk are kept between the session's runs so work can resume, and are deleted when the session's work ends. On a paired device, the checkout stays on your own machine.

Traces, plans, diffs and transcripts stay for the life of the workspace. Some records are pruned sooner: live event streams after 3 to 30 days depending on the kind, verification logs after 14 days, the raw payloads of incoming webhooks after 14 days, and the API request log after 90 days.

Deleting a factory in Settings stops its runs and hides its boards, and its sessions' microVMs are deleted within minutes. The rest of its data stays so a member can restore it by installing the anturno GitHub App again, and backups keep copying it until it is erased.

To erase a workspace permanently, a member writes to hello@anturno.cloud. We erase its data, backups included, within thirty days of the request and confirm by email. Erasure does not reach what we wrote into your own repositories and accounts, such as branches, pull requests and the hidden refs, which you can delete there, or the checkouts on a device you paired.

5. Who else touches it

The services that process data for us, the model providers you choose and the services you connect are listed on the subprocessor list, with what each does, which of your data it touches and where. We post a new subprocessor there at least thirty days before it starts processing customer data. What a model provider or a connected service does with your data is set by your own agreement with it.

6. Where it lives

The engine and the volume that holds workspace data run on Railway in the United States. Cloud sessions run in Vercel Sandbox. The subprocessor list gives the country each subprocessor is based in, which is not a data region. A paired device runs sessions, with their checkout and commands, on your own machine. For transfers out of the EEA, the UK and Switzerland, standard contractual clauses are available through our data processing agreement, which we offer on request.

7. Your rights

You can ask for a copy of your personal data, for a correction, for deletion, or for us to stop a particular use. Write to hello@anturno.cloud and we will answer within thirty days. Where your data is in your company's workspace, we act on your company's instructions and may pass your request to it. In the workspace, a member can remove another member or delete a factory, which hides it as section 4 says rather than erasing it.

If you are in the EEA or the UK you can also complain to your supervisory authority.

8. Cookies and analytics

The site at anturno.cloud uses PostHog to count page views, clicks, form submissions and errors, and to record visits so we can replay them and see where the site gets in the way. A recording holds the pages you see, your mouse movements, clicks and scrolling, and browser console messages. It does not hold what you type: the value of every form field is masked in your browser before anything is sent. Recordings are kept for 30 days. PostHog sets no cookie and stores nothing in your browser, so the identifier it uses, and the recording, end when you close or reload the page. PostHog receives your IP address, derives an approximate location from it, and may record the address. There is no advertising or cross-site tracking.

The app at app.anturno.cloud sets only the cookies it needs to work: the ones that keep you signed in, one that remembers which workspace you last opened, and ones that carry a sign-up or a GitHub App installation through to your workspace.

9. Contact and changes

Questions and requests go to hello@anturno.cloud. Reports of a security vulnerability go to security@anturno.cloud; the vulnerability disclosure policy says what to include and what to expect. We will tell you here, and by email, before this policy changes in a material way.