Privacy Policy
What personal data Isolation collects, why, where it goes, how long it is kept, and your rights.
Version 1.0 — 11 October 2026
This policy explains what personal data Isolation Labs S.r.l. ("Isolation", "we") collects when you use Isolation Cloud (the website, the API, the isolation command, our apps for Slack and Microsoft Teams, and the software we distribute to run it), why, where it goes, how long we keep it, and what you can do about it. It is written for the General Data Protection Regulation (GDPR); where your country gives you more rights, those apply too.
Controller. Isolation Labs S.r.l., Italy. Contact: privacy@isolation.cloud.
Two roles. For your account, your sign-in, billing and our operation of the Service we are the controller. For what your organization puts into the Service — code, files, environment values, conversations with agents, what agents produce — the organization is the controller and we are its processor: we handle that content only to provide the Service as configured, under the Terms of Service and our Data Processing Agreement (isolation.cloud/legal/dpa), which applies to every organization and is part of every Enterprise contract.
1. What we collect, and why
| data | where it comes from | why | legal basis |
|---|---|---|---|
| Account: email address, display name, an avatar if you connect GitHub, the organizations you belong to and your role in each | you, when you sign in and when you are invited | to run your account and your organizations | contract |
| Sign-in: one-time login codes sent by email, session cookies, a bot check (Cloudflare Turnstile) on the login form | the login flow | to sign you in and keep abuse off the login form | contract; legitimate interest (security) |
Tokens you create for apps, MCP clients and the isolation command: their label, scopes, organization, dates of creation, last use and revocation | you, when you connect something | to let those tools act as you, and to let you revoke them | contract |
| Billing: your organization's balance, ledger, invoices, receipts, plan; a Stripe customer id | you and Stripe | to bill and to keep the accounts the law requires | contract; legal obligation |
| Customer Content (as processor): repositories and files in workspaces, environment values and secrets, credentials you store (AI keys and subscriptions, Git tokens, SSH keys), agents' prompts, conversations and memory, what sandboxes produce | you, your members and your agents | to run sandboxes and keep your work between them | the organization's instructions, under the Data Processing Agreement |
| Usage and metering: sandbox start/stop/pause times, server size and price, bytes of egress, tokens counted for the credentials you use through the Service, server capacity reports | the Service and your servers | to bill per second and to show usage | contract |
| Activity log: which member (or agent, and which member launched it) did which action, through which door (website, command, MCP, terminal, agent), when | the Service | so your organization can audit itself; security | legitimate interest (the organization's audit and our security) |
| Chat messages addressed to Isolation in Slack or Teams: the text is routed to the agent or command you addressed; we store a hash of the text, its length, and what was decided — not the text | the chat app | to route your message; to evaluate the interpreter | contract; legitimate interest |
| Interpreted text: a sentence you type on the website, in the terminal or in a chat that is not an exact command is sent to our interpreter provider (TypeSafe) to be turned into a command | you | to understand what you asked | contract |
| Voice (push-to-talk): the audio clip is sent to our transcription provider (Groq) and the text comes back; we keep neither the audio nor the transcript beyond the request | you, when you hold the microphone | to transcribe your instruction | consent (you press the button) |
| Connected servers: the machine's name, a machine id, software version and capacity, and the connection it opens to us | isolation-server on the machine | to pair, monitor and reach the server | contract |
| Technical logs: request logs at our hosting provider (IP address, user agent, timestamps, the path called) | your browser and tools | to keep the Service running and secure | legitimate interest |
Error reports (through Sentry): when something breaks in the website, the Service, our apps, the isolation command or the software that runs sandboxes and servers — the error, where in our code it happened, the software version, the operating system and device model. Before a report leaves, we remove web addresses' secret parts, tokens, sign-in codes, cookies, request bodies, environment values, your name and home folder, and never send the text of terminals, agents or chats, screenshots or screen recordings | our software | to find and fix what breaks | legitimate interest; the isolation command and the desktop apps stop sending with DO_NOT_TRACK=1 |
| Emails we send: login codes, invitations, receipts and invoices, plan changes, alerts | the Service | to sign you in and to tell you what your organization needs to know | contract |
| Product emails: onboarding tips, reminders and a monthly usage summary, sent through Loops. Loops receives your email address, first name, account and plan attributes and product-usage events (for example "launched a first sandbox"), and records whether an email was opened and which link was clicked | the Service | to help you get started and get the most out of the Service | legitimate interest (you are our customer, and the emails are about the service you signed up for); turn them off in your account settings or with the unsubscribe link in every product email. Login codes, invoices and alerts are always sent |
We do not collect data for advertising, we do not sell personal data, and we do not train AI models on your data.
2. Where your data is processed — our sub-processors
The Service runs on the providers below. The current list, with each provider's location, is kept at isolation.cloud/legal/subprocessors; we tell organizations' owners by email before adding one.
- Cloudflare — the application, its database and file storage, the connections sandboxes and servers keep to us, the login form's bot check (Turnstile). Customer Content in file storage is encrypted with a key per workspace before it is written.
- Amazon Web Services — the machines Cloud Sandboxes run on, in the region your organization chose (Europe or the United States). A sandbox's files exist on its machine while it runs and are saved back to our storage at the documented points.
- Fly.io — the relay that forwards your agents' ChatGPT/Codex subscription requests to OpenAI from an address that is not Cloudflare's: the request passes through it (your ChatGPT sign-in token included) and nothing is stored.
- Stripe — payments; your card details go to Stripe and never to us.
- Resend — sends our transactional emails (login codes, invitations, receipts, alerts).
- Loops — sends our product emails, unless you turn them off (§1).
- Sentry (Functional Software, Inc., United States) — error and crash reports from the website, the Service, our apps and the
isolationcommand, scrubbed as described in §1, so we can fix what breaks. - TypeSafe — the interpreter: receives the sentence you typed and the names of the things it could refer to (your workspaces, sandboxes, agents), returns a command.
- Groq — transcription of push-to-talk audio.
- GitHub, Slack, Microsoft — when you connect them: the tokens they issue us, and the messages and events they deliver for the things you connected.
- Your own AI providers — an agent you run talks to the provider of the credential you gave it (Anthropic, OpenAI, or another) under your agreement with that provider; what the agent sends them is your prompt and your code, from inside your sandbox, not through us.
Some of these providers are in the United States. Where personal data leaves the European Economic Area we rely on the EU–US Data Privacy Framework where the provider is certified, and otherwise on the European Commission's Standard Contractual Clauses.
3. How long we keep it
| data | kept |
|---|---|
| Account, organizations, memberships, tokens | until you delete them, or your account; a revoked or expired token is deleted 30 days after |
| Login codes and session cookies | until they expire (a code within minutes; a session as set at sign-in), then deleted |
| Invitations | until accepted (the acceptance record stays with the membership) or 30 days after expiry |
| Customer Content | until your organization deletes the workspace, the agent or the organization; a deleted organization's content is removed within 30 days |
| Usage and metering, ledger, invoices | as long as the law requires for accounting (10 years in Italy) |
| Activity log | 90 days |
| Chat routing records (hash, length, decision) | 90 days |
| Voice audio and transcripts | not stored |
| Technical logs | up to 30 days at the hosting provider |
| Error reports at Sentry | up to 90 days |
| Product-email contact at Loops | until you delete your account (unsubscribing stops the emails; the contact is deleted with the account) |
| Acceptance of the Terms (who, when, which version) | as long as the account or organization exists, then as part of the accounting record |
4. Your rights
You can see and change your account data on the Account page, export a workspace (its files and its agents' memory) from the Workspace page, revoke any token from the Account page, leave an organization, and delete your account. Beyond that, under the GDPR you may ask us to access, correct, erase or port your personal data, to restrict or object to its processing, and to withdraw a consent you gave. Write to privacy@isolation.cloud; we answer within one month. You may also complain to your data protection authority — in Italy, the Garante per la protezione dei dati personali (garanteprivacy.it).
For Customer Content, where we are the processor, ask your organization's owners: they control it, and we act on their instructions, as the Data Processing Agreement (isolation.cloud/legal/dpa) sets out.
5. Security
Credentials, secrets and workspace content are encrypted at rest; secrets travel to a sandbox sealed for that sandbox alone and are never written to logs, URLs or repositories. Every action is logged with who did it. Our staff reach Customer Content only to provide the Service or when you ask us to help. Sandboxes are isolated from each other and from us at the machine or container level. More at isolation.cloud/docs/servers and isolation.cloud/docs/credentials.
6. Cookies
The website uses one cookie, the session that keeps you signed in, and the Turnstile bot check on the login form. There are no advertising or analytics cookies. The isolation command and other tools you connect keep their own token on your machine, not a cookie.
7. Children
The Service is not for children under 16, and we do not knowingly collect their data.
8. Changes
We will publish changes at isolation.cloud/legal/privacy with a new version and date, and email organizations' owners before a material change takes effect.