Subprocessors
Last updated
On this page
These are the companies we use to run CrewOS. Each one handles only what it needs for its job, under a contract that limits how it can use your data. The tools you connect yourself, such as Gmail or QuickBooks, work under your own agreements with them.
Infrastructure
Where CrewOS runs and where your data is stored.
| Name | Purpose | Data | Location |
|---|---|---|---|
| Microsoft Azure | Hosting for the CrewOS service and teammate runtime | All service data, including thread history and audit logs | United States (US East) |
| Neon | Database | Account, workspace, thread history, approvals, audit logs, usage | United States |
| Cloudflare | Website hosting, DNS, and edge network | Website requests, IP addresses | Global edge network |
Accounts and billing
Who handles sign-in and payments.
| Name | Purpose | Data | Location |
|---|---|---|---|
| WorkOS | Sign-in and single sign-on | Name, work email, company, sign-in events | United States |
| Stripe | Billing and payments | Billing contact, plan, invoices, payment details | United States |
AI models
Teammates send the parts of a conversation they need to one of these providers to write a reply. Our agreements with them do not allow training on your content.
| Name | Purpose | Data | Location |
|---|---|---|---|
| Anthropic | AI models | Message content and tool data needed for the reply | United States |
| OpenAI | AI models | Message content and tool data needed for the reply | United States |
| AI models | Message content and tool data needed for the reply | United States |
Where teammates work
The places a teammate reads and posts. You choose to connect them.
| Name | Purpose | Data | Location |
|---|---|---|---|
| Slack | Where teammates read threads and post replies | Messages, channel and member details in channels a teammate is added to | United States |
| GitHub | Where the code reviewer reads and comments on pull requests | Repository content, pull requests, issues, comments | United States |
Changes and notice
When we add or replace a subprocessor, we update this page and change the date at the top. Enterprise customers can ask to be emailed 30 days before a new subprocessor starts handling their data. To ask a question or sign up for notices, email [email protected].