Sub-processors & AI providers
Effective date October 18, 2026
Orbital, a product of Constructr, Inc., uses the third parties below to deliver the platform. Each one processes customer data only on our instructions and under a written contract that holds it to data-protection obligations no less protective than the ones we give you in our Data Processing Addendum.
This page is the list referred to in clause 7.2 of the DPA.
How we notify you of changes
Before a new sub-processor starts processing customer personal information, we update this page and give customers at least 30 days' notice. We send that notice by email to each customer's account owners.
If you object to a new sub-processor on reasonable data-protection grounds within the notice period, write to privacy@withorbital.ai and we will discuss it with you. Clause 7.4 of the DPA sets out what happens if we cannot resolve the objection.
Platform sub-processors
These process customer data as part of delivering the platform.
| Sub-processor | Legal entity | Registered address | Purpose | Data categories | Processing location | Notes |
|---|---|---|---|---|---|---|
| Amazon Web Services | Amazon Web Services, Inc. | 410 Terry Avenue North, Seattle, WA 98109, United States | Hosting and running the platform; storage of customer data and backups | All categories of customer data the platform processes | United States; European Union for customers who select an EU region on an enterprise plan | Encrypted in transit and at rest |
| Cloudflare | Cloudflare, Inc. | 101 Townsend Street, San Francisco, CA 94107, United States | Content delivery, DNS and network protection for our websites and apps; sending account, sign-in and service emails | Request metadata, including IP addresses, for traffic passing through its network; the addresses and contents of service emails | Global edge network operated by a United States company | Named in our Cookie Policy. Cloudflare Web Analytics is not used |
| Neon | Neon, Inc. | 209 Orange Street, Wilmington, DE 19801, United States | Managed Postgres databases for the platform | Account and workspace records and customer data stored in the platform database | United States; European Union for customers who select an EU region on an enterprise plan | Encrypted in transit and at rest |
| Composio | Sampark, Inc., trading as Composio | 2 Bryant Street, Suite 220, San Francisco, CA 94105, United States | Connector authentication and tool access: brokers the OAuth connection to the systems you connect and relays agents' requests to and responses from them | Connector credentials (OAuth tokens and API keys), and the data agents read from or write to connected systems | United States | Credentials are encrypted at rest. Composio does not use payload data to train models and deletes data within 30 days of the end of service; its execution logs may be retained for up to one year under its standard terms |
Model and AI providers
These receive the content of agent tasks in order to produce the output needed to perform the task.
| Provider | Legal entity | Registered address | Purpose | Data categories | Processing location | Training | Zero retention | Notes |
|---|---|---|---|---|---|---|---|---|
| Anthropic | Anthropic, PBC | 548 Market Street, PMB 90375, San Francisco, CA 94104, United States | Model inference for agent tasks (Claude models, including through Claude Code) | Prompts, context and connected-system data sent for inference; model outputs | United States | Contractually prohibited under Anthropic's commercial API terms | Not enabled on Orbital's account; Anthropic retains inputs and outputs for up to 30 days under its standard terms | Standard commercial API |
| OpenAI | OpenAI, L.L.C. | 3180 18th Street, San Francisco, CA 94110, United States | Model inference for agent tasks (GPT and Codex models) | Prompts, context and connected-system data sent for inference; model outputs | United States | Contractually prohibited under OpenAI's business terms; API content is not used for training by default | Not enabled on Orbital's account; OpenAI retains API inputs and outputs for up to 30 days for abuse monitoring | Standard commercial API |
| Google LLC | 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States | Model inference for agent tasks (Gemini models, including through Antigravity) | Prompts, context and connected-system data sent for inference; model outputs | United States | Contractually prohibited under the paid Gemini API terms | Not enabled on Orbital's account; Google retains paid-tier prompts and responses for up to 55 days for abuse monitoring | Standard commercial API |
How we hold these providers to our training commitment. Every provider in the serving path is engaged under paid, commercial API terms that contractually prohibit the provider from using your content to train or improve its own models, and we disable provider settings that would allow your content to be used for model improvement. We have not yet enabled zero data retention on our own provider accounts, so each provider retains content for the limited period shown in the Zero retention column, under its standard terms and typically for abuse monitoring. We will update this table when that changes.
If you bring your own provider account or key. Most customers run agents on their own Claude Code, Codex or Antigravity accounts. In that case the provider processes your content under your agreement with it, and any zero-retention arrangement is one you hold with the provider directly; the rows above describe traffic through Orbital's own accounts.
Our full data-use position, including the three cases in which we do and do not use customer data, is in our AI & Agent Terms and in clause 3.4 of the DPA.
Business and support sub-processors
These process personal information about customer personnel - not the content of agent tasks.
| Sub-processor | Legal entity | Registered address | Purpose | Data categories | Processing location | Notes |
|---|---|---|---|---|---|---|
| PostHog | PostHog, Inc. | 2261 Market Street #4008, San Francisco, CA 94114, United States | Product analytics and error tracking - understanding which features are used, where people get stuck, and where the product fails | Pseudonymous identifier, usage events, device and browser information, IP address; error reports with request metadata | United States (PostHog US Cloud) | Named in our Cookie Policy; website analytics load only after you accept analytics cookies. Not used for advertising. Identifier retained up to 12 months; identifiable event data up to 14 months |
| Crisp | Crisp IM SAS | 2 Boulevard de Launay, 44100 Nantes, France | Live chat support on the website | Conversation content, session identifier, page context, and whatever a visitor types | European Union (Netherlands and Germany) | Named in our Cookie Policy; loads only after you accept support cookies or open the chat. Session identifier up to 6 months; conversations retained up to 12 months after the request is resolved |
| Stripe | Stripe, Inc. | 354 Oyster Point Boulevard, South San Francisco, CA 94080, United States | Payment processing | Billing contact, invoice details, payment card data | United States | Named in our Privacy Policy. Orbital does not store full card numbers |
Not sub-processors
For completeness, two third parties appear on Orbital surfaces without processing customer data on our behalf:
cdn.brandfetch.io, operated by Brandfetch Sàrl, andlogos.composio.dev, Composio's logo service, serve integration logos on our marketing pages. Composio's connector service is a platform sub-processor, listed above; its logo host processes no customer data. Neither sets a cookie, but a visitor's browser connects to them and discloses an IP address; see Section 4 of our Cookie Policy.- Systems you connect yourself. When you authorise an agent to work in one of your own systems, that system is not an Orbital sub-processor and your own agreement with that provider governs it.