Where your code goes, and what’s kept.
AoTwin has to read your code to do a ticket. This page says where that happens, who else handles it, how long it stays, and what we don’t offer yet.
Where the work happens
Each ticket runs in its own isolated sandbox hosted by Anthropic, using Claude models. The repositories AoTwin needs for that ticket are copied into the sandbox for the job.
- The sandbox holds a read-only GitHub token. AoTwin’s own service opens the pull request from the change the sandbox hands back.
- The sandbox’s network is limited to package registries and a short list of allowed hosts.
- AoTwin refuses to write to your default branch, and merging and closing pull requests are blocked. Your engineers approve every change.
Your account, tickets, comments, attachments and connection details are stored on Cloudflare. We don’t offer a choice of region, so your data may be processed outside your country, including in the United States.
What’s kept, and for how long
- The record of each job. Anthropic keeps it until it’s deleted, and it can include parts of your code. We don’t delete these automatically today. Ask and we’ll delete yours.
- Files sent to the sandbox. Deleted when the job ends, and they expire after 30 days if that fails.
- Content Anthropic’s safety systems flag. Anthropic may keep it for up to 2 years, or longer where the law requires.
- Tickets, comments and attachments. Kept while your account is open. Ask us to close it and we’ll delete them.
- Backups. Taken daily and kept for 35 days.
Anthropic publishes its rules in API and data retention.
Whether it trains models
AoTwin doesn’t train models on your code or tickets. Anthropic says that by default it doesn’t use inputs or outputs from its commercial products, including its API, for training. AoTwin uses that API. Read Anthropic’s page on training.
Who handles your data
- Anthropic: does the work on your tickets, answers Ask AoTwin and reads Slack reports.
- Cloudflare: hosts AoTwin and stores its data.
- GitHub: holds your code and the pull requests AoTwin opens.
- Stripe: takes payments. We don’t see or store your full card number.
- An email delivery provider: sends AoTwin’s email.
- Google: holds the email you send us.
- Atlassian, Linear and Slack: only if you connect them.
How access is protected
- GitHub access uses short-lived tokens limited to the repositories you connect.
- Linear, Jira and Slack tokens are encrypted before they’re stored.
- Sign-in uses a one-time link sent to your email, so there’s no AoTwin password to steal.
What we don’t offer yet
- A SOC 2 or ISO 27001 report.
- Zero data retention. It isn’t available for this work.
- A HIPAA agreement. AoTwin isn’t for health data.
- A choice of data region.
If you need one of these, tell us before you connect your code.
Report a problem
Found a security issue? Write to aous@aotwin.io. How your personal data is handled is covered in the privacy policy.
Updated 30 October 2026