Subprocessor List
Current subprocessors and service providers used by Cap Orbit.
This Subprocessor List is referenced by the Cap Orbit Data Processing Addendum (the "DPA") and the Cap Orbit Privacy Policy, and forms part of the DPA where the DPA incorporates it. Capitalized terms used but not defined here have the meanings given to them in the DPA, the Cap Orbit Terms of Service, or the Privacy Policy. In this document, "Cap Orbit", "we", "us", and "our" mean Cap Orbit, Inc., a Delaware corporation, the operator of the Service, and "Customer", "you", and "your" mean the organization that subscribes to the Service and its Authorized Users.
1. About this list
A "Subprocessor" is a third party Cap Orbit engages to process Customer Content in providing the Service.
This list identifies providers Cap Orbit uses to deliver the Service. Amazon Web Services (AWS) Processes Customer Content for the Cap Orbit-hosted Service. Anthropic Processes Customer Content only when the Customer's configuration uses Claude Platform rather than Amazon Bedrock. Mapbox Processes property addresses when a Customer uses the map features. Where a Customer supplies its own API keys for Anthropic, OpenAI, or xAI, those providers Process Customer Content under the Customer's own agreement with them. We also disclose providers that process account and identity data (WorkOS), billing data (Stripe), Usage Data (Metronome), and account and product email (Loops), together with the providers that host our public websites and process no Customer Content (Vercel, Cloudflare). This document uses "Subprocessors and service providers" when referring collectively to these categories.
Each provider identified in this list is engaged as a service provider, contractor, processor, or other vendor as appropriate for the function it performs. Where a provider processes Personal Information on Cap Orbit's behalf, Cap Orbit uses contractual restrictions intended to limit the provider's use of that Personal Information to the services it provides to Cap Orbit and to prohibit the provider from selling or using it for targeted advertising.
Before a Subprocessor receives Customer Content, Cap Orbit enters into a written agreement that flows down data-protection obligations equivalent in substance to those Cap Orbit owes to the Customer under the DPA, including obligations limiting the Subprocessor to the documented processing purposes, requiring confidentiality, requiring reasonable security measures, and prohibiting any use of Customer Content to train, fine-tune, or otherwise improve any AI or machine-learning model unless the Customer has opted into that use. Cap Orbit remains responsible to the Customer for the performance of each Subprocessor's obligations.
You can subscribe to advance notice of changes to this list. See Section 5 (Changes and notification) for how to subscribe and how we provide notice before a new Subprocessor begins processing Customer Content.
2. Current Subprocessors and service providers
The following table lists the providers Cap Orbit currently engages. A provider marked as configuration-specific Processes Customer Content only when that configuration is selected. As used here, "Usage Data" has the meaning given in the DPA and Privacy Policy (metadata about use of the Service, excluding Customer Content).
Location entries identify the primary region or configuration currently used for the Service. They are not a general data-residency commitment unless the applicable Order expressly says otherwise.
| Provider | Purpose | Data Processed | Primary location / configuration |
|---|---|---|---|
| Amazon Web Services (AWS) | Cloud hosting, storage, database, content delivery, OCR, voice dictation, agent web search and browsing, and AI model inference through Amazon Bedrock | Customer Content, and account and Usage Data | Hosting and storage in the United States (us-east-1); Bedrock inference may use AWS cross-region inference profiles (see Section 3) |
| Anthropic | AI model inference through Claude Platform on AWS; applies only when that provider is selected | Inputs, Outputs, and related request data | Anthropic-operated processing through the configured AWS region |
| Anthropic, OpenAI, xAI | AI model inference using API keys the Customer supplies; applies only when the Customer configures its own keys | Inputs, Outputs, and related request data | Under the Customer's own agreement with the provider; see Section 3 |
| Mapbox | Geocoding and static map rendering for the map features | Property and comparable addresses the Customer asks to map; no documents | United States |
| WorkOS | Identity, authentication, single sign-on, organization and seat membership, and storage of authorization tokens for data-room connectors the Customer links | User identifiers, name, email address, organization data, and connector authorization tokens | United States |
| Stripe | Payment processing and subscription billing | Billing contact email, payment method data, and Stripe customer and subscription identifiers | United States |
| Metronome | Usage metering and billing | Usage Data (metadata only, no Customer Content) | United States |
| Loops | Account, product, and marketing email | Name, email address, organization name, and account lifecycle stage; no Customer Content | United States |
| Vercel | Hosting of the public marketing and documentation websites | Website visitor server logs (IP address, user agent, referrer); no Customer Content | United States |
| Cloudflare | Bot protection (Turnstile) on the marketing website's contact form | Visitor IP address and challenge token; no Customer Content | United States |
3. Configuration-specific AI processing
Cap Orbit supports more than one AI-inference configuration:
- Amazon Bedrock (default). For sessions configured to use Amazon Bedrock, AWS operates the inference service and is the Subprocessor. This covers every model offered through Bedrock, including models developed by Anthropic, OpenAI, xAI, and Amazon. AWS states that Amazon Bedrock does not share customer inputs or outputs with model providers or use them to train foundation models. Current AWS service terms and documentation govern that processing. Cap Orbit stores Customer Content in the United States (us-east-1). Some models run on AWS cross-region inference profiles, under which AWS may route an individual inference request to another AWS commercial region to serve it. A Customer that needs inference held to a specific region can use its own provider keys (below) or a Customer-controlled deployment (Section 4), where the Customer's own provider configuration sets the region.
- Claude Platform on AWS. For sessions configured to use Claude Platform on AWS, Anthropic operates the inference service and Processes Inputs, Outputs, and related request data as a Subprocessor. This processing is outside the Amazon Bedrock service boundary. Anthropic's standard commercial API retention is up to 30 days for Inputs and Outputs, subject to exceptions in Anthropic's current terms and documentation, including longer retention for certain features, safety and usage-policy enforcement, legal requirements, or a different written retention arrangement.
- Customer-supplied keys. A Customer administrator may configure the Service to use the Customer's own API keys for Anthropic, OpenAI, or xAI. In that configuration, Inputs, Outputs, and related request data are sent directly to that provider under the Customer's own agreement with it, and the Customer is responsible for that provider's retention and training terms. Cap Orbit does not store Customer Content with those providers on its own account.
Cap Orbit does not use, or authorize either provider to use, Customer Content to train or fine-tune generalized models unless the Customer expressly opts in or gives a documented instruction permitting that use. Provider documentation may change, so this list describes Cap Orbit's current configuration and links to the providers' current terms rather than incorporating provider statements into the Terms of Service. See the [Amazon Bedrock documentation](https://aws.amazon.com/bedrock/faqs/) and [Anthropic commercial retention information](https://privacy.claude.com/en/articles/7996866-how-long-do-you-store-my-organization-s-data).
4. Customer-controlled deployments
Where the Service is deployed into infrastructure the Customer owns or controls, that infrastructure provider is not a Cap Orbit Subprocessor for the Customer-controlled Processing. The Customer is responsible for the configuration, access controls, logging, retention, deletion, and revocation of its infrastructure. A provider Cap Orbit separately engages to Process Customer Content, including a configuration-specific AI provider, remains a Subprocessor and is listed above.
The following continue to apply as Cap Orbit service providers in a Customer-controlled deployment because they support identity and billing rather than the hosting of Customer Content:
- WorkOS, for identity, authentication, single sign-on, and organization and seat membership.
- Stripe, for payment processing and subscription billing.
- Metronome, for usage metering and billing (Usage Data only, no Customer Content).
- Loops, for account and product email (no Customer Content).
- Mapbox, for the map features, where the Customer uses them.
Vercel and Cloudflare serve the public websites only and do not process Customer Content.
Data-room connectors. Where a Customer links a Microsoft 365, Dropbox, Box, or Datasite account, the Service reads files from that account on the Customer's instruction. Those providers are the Customer's own vendors and are not Cap Orbit Subprocessors; WorkOS stores the connector authorization tokens, as listed above.
5. Changes and notification
Effective date: June 18, 2026. Last updated: October 20, 2026.
Cap Orbit may add to or change its Subprocessors from time to time. Before a new Subprocessor begins processing Customer Content, Cap Orbit will update this list and provide at least ten (10) business days' advance notice to Customers who have subscribed to Subprocessor change notifications. Customers may object to a new Subprocessor as set out in the DPA. To subscribe to notifications, or to ask a question about this list, contact us at privacy@cap-orbit.com.
This list is maintained in connection with the DPA, the Privacy Policy, and the Cap Orbit Terms of Service. If there is a conflict between this list and the DPA as to the processing of Customer Content, the DPA controls.
(c) 2026 Cap Orbit