Who we are
AOSplane is operated by Voxasphere Software Inc., a Delaware corporation (“AOSplane”, “we”, “us”). If you have a question about this policy or your data, write to privacy@aosplane.io.
This policy covers aosplane.com, the AOSplane console at app.aosplane.io, the mobile app, the API and the command-line tools (together, the “Service”). Our Terms of Service govern your use of the Service.
Two kinds of data, two roles
Account data is information about you and how you use the Service: your name and email, your organization’s settings, billing and usage records, and security logs. We decide how it is used, so for this data we are the controller.
Customer Content is the work itself: repository code, task descriptions, prompts, agent messages and transcripts, command output, diffs, workspace snapshots, attachments, pull requests, and issues pulled in from connected tools. We process Customer Content on behalf of the organization that owns the workspace, and only to provide the Service to it. For this data the organization is the controller and we are its processor (or “service provider”). If you are a member of someone else’s workspace, questions about its content go to that organization’s admin. Customers who need a data processing agreement can request one at legal@aosplane.io.
What we collect
Information you give us
- Account details. Your name, email address and profile picture, received from our sign-in provider when you sign up or sign in, including through single sign-on.
- Organization settings. Organization and project names, members and roles, agent definitions, budgets, approval rules and the integrations you turn on.
- Credentials you connect. Model-provider API keys and access tokens for GitHub, Linear, Jira and Slack. These are encrypted before they are stored (see Security).
- Billing information. Your plan, billing contact, invoices and credit balance. Card payments are handled by Stripe; we do not receive or store your full card number.
- Support messages. What you send us when you contact support or sales.
Customer Content
When a run starts, the repository you attach is cloned into that run’s sandbox. Everything the run works with and produces is Customer Content: the code, your instructions, the agent’s messages and tool calls, the commands it runs and their output, the resulting diff, any workspace snapshot, the pull request it opens, and any files you attach.
Information collected automatically
- Usage and metering. Runs started, run time, sandbox size and duration, storage, and budget reservations. We use these to enforce your limits and to bill platform usage.
- Audit and security records. Who did what and when: tasks created, budgets reserved, permissions requested and decided, pull requests published. For console and API actions we also record the IP address, the browser or client (user agent), the acting user’s email, and a partial identifier of the API key used.
- Sandbox network records. When network controls are on for a run, we record where traffic leaving the sandbox went: the destination host and port, connection counts, bytes sent and received, and whether it was allowed or blocked. We do not record what that traffic contained.
- Mobile device token. If you turn on notifications in the mobile app, we store its push token so we can reach that device.
- Diagnostics. When something fails, our services send error reports and performance traces to our error-monitoring provider. Before traces leave our systems we strip authentication headers, cookies, URLs, database queries, user and organization IDs, and model prompts and completions. We configure error reports to exclude credentials and Customer Content.
On this website
aosplane.com has no analytics, advertising or tracking scripts and sets no cookies. It remembers only whether you chose the light or dark theme, in your own browser’s storage. Like any website, the service that delivers it processes standard request data, such as your IP address and browser, to serve the page and protect it from abuse.
How we use information
- To run the Service: start runs in sandboxes, call your model provider with the credential you connected, publish pull requests, and sync with the tools you connect.
- To enforce budgets, plan limits and approval gates, and to keep the audit trail your organization relies on.
- To bill you, collect payment and prevent fraud.
- To keep the Service and its users secure: detect abuse, investigate incidents and enforce our Terms.
- To communicate with you: service, security and billing notices, replies to support requests, and the email and push notifications you turn on. If we send product news, every message has a way to opt out.
- To find and fix errors and keep the Service reliable.
- To comply with the law.
We do not sell personal information, and we do not use it for targeted advertising.
AI models and your code
Your agents call your provider. When an agent runs on AOSplane, it sends requests to the model provider you connected, such as Anthropic or OpenAI, using your credential. What that provider does with the data is governed by your agreement with it.
Some features use our models. A few features run on AOSplane’s own model account, such as automated code review, task planning, and the assistant in connected chat tools. When you use one, the content it needs (for example a pull request’s diff and the repository’s agent instructions) is sent to a model provider we contract with, listed below. We use these providers only on terms that do not allow them to train their models on your content.
No training on your content. We do not use Customer Content to train AI models.
How we share information
- Subprocessors. Companies that run parts of the Service for us, listed below. They may use the data only to provide their service to us.
- Services you connect. GitHub, Linear, Jira, Slack and your model providers receive data when you direct it, for example when a run opens a pull request. Their own privacy policies apply.
- Your organization. Admins and members of a workspace can see its runs, transcripts, audit records and usage, according to their role.
- Legal reasons. When the law requires it, or to protect the rights and safety of our users, the public or AOSplane. Where the law allows, we tell a customer before handing over its Customer Content.
- Business transfers. If AOSplane is part of a merger, acquisition or sale of assets, data may transfer as part of that deal, under this policy or with notice to you.
- With your consent. In any other case, only when you ask us to.
Subprocessors
| Provider | What they do for us | Data involved |
|---|---|---|
| Google Cloud | Hosts the AOSplane service, its databases and the sandboxes runs work in. Provides Gemini models for features AOSplane runs itself. | All service data, including Customer Content |
| Amazon Web Services | Encryption keys, file storage, notification email, Amazon Bedrock models for features AOSplane runs itself, and hosting for this website. | Encrypted credentials, attachments, audit records, notification emails, content sent to AOSplane’s AI features, website request data |
| WorkOS | Sign-in, single sign-on and organization membership. | Name, email address, profile picture, organization membership |
| Stripe | Payments, subscriptions and invoices. | Billing contact details, payment card details, invoices |
| Sentry | Error monitoring and performance traces. | Error reports and scrubbed traces (see below) |
| Apple and Google (Firebase Cloud Messaging) | Push notifications to the AOSplane mobile app. | Device push token, notification text such as a run title and project name |
We update this list before a new subprocessor starts handling data.
Where data is stored
We store and process data in the United States. Where we offer a regional data location, such as India, and your workspace uses it, that workspace’s run data stays in that region; account, sign-in and billing data are kept in the United States for every customer. Diagnostics and some subprocessors may process data in other countries. When we transfer personal data out of the European Economic Area, the United Kingdom or Switzerland, we rely on safeguards the law recognizes, such as the European Commission’s Standard Contractual Clauses.
How long we keep it
- Account and organization data: for as long as your account is open.
- Audit events in the console: for the period your plan includes: 7 days on Free, 30 on Starter, 90 on Team, and 365 or as agreed on Enterprise.
- Detailed run activity, where your plan includes it: for the period your plan includes.
- Attachments: 30 days.
- Conversations captured from connected chat tools: 30 days.
- Run transcripts, diffs and workspace snapshots: until you delete them or close your workspace.
- Billing records: as long as tax and accounting law requires.
When you close your account, we delete or anonymize your data within a reasonable period. Copies in backups expire on their normal schedule, and we keep what the law requires us to keep.
Security
- Every run works in its own isolated sandbox.
- Credentials you connect are encrypted before they are stored.
- API keys are stored only in a form we cannot reverse. We cannot recover a key once it is issued.
- Data is encrypted at rest, and in transit whenever it crosses a public network.
- Audit records are tamper-evident, so changes show.
- Staff access is limited to the people who need it.
Our Security page has more detail. No system is perfectly secure. If a breach affects your data, we will notify you as the law requires.
Your rights and choices
Depending on where you live, you may have the right to access the personal data we hold about you, correct it, delete it, receive a copy in a portable format, object to or restrict how we use it, and withdraw consent you have given. To use any of these rights, write to privacy@aosplane.io. We will confirm your identity before acting and reply within the time the law sets. We will not treat you differently for using your rights.
For Customer Content in a workspace you do not own, contact that organization’s admin; we will help them respond. You can turn email and push notifications off in the console and the mobile app.
European Economic Area, United Kingdom and Switzerland
We process personal data to perform our contract with you, for our legitimate interests in running, securing and improving the Service and in communicating with business customers, to meet legal obligations, and with your consent where we ask for it. You can complain to your local data protection authority.
California
In the past 12 months we have collected identifiers (such as name, email and IP address), commercial information (such as plan and billing history), internet activity (such as audit and usage records) and professional information (such as your organization and role), for the purposes described above. We do not sell or share personal information for cross-context behavioral advertising. You may use the rights described above, including through an authorized agent.
India
Under the Digital Personal Data Protection Act, 2023, you can ask to access, correct and erase your personal data and to have a grievance addressed. Send these requests to privacy@aosplane.io.
Cookies
The console uses only the cookies it needs to work: a session cookie that keeps you signed in, cookies our sign-in provider sets during sign-in, and short-lived cookies that hold state while you connect GitHub or another tool. It also keeps your last active project in your browser’s local storage. Neither the console nor this website uses analytics or advertising cookies.
Children
The Service is for people 18 and over, and is not directed at children. If we learn that we hold a child’s personal data, we delete it.
Changes to this policy
We update this page when our practices change and change the date at the top. If a change is material, we tell you by email or in the console before it takes effect.
Contact
Voxasphere Software Inc., privacy@aosplane.io.