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 covers the per-seat, Cap Orbit-hosted Pro deployment model, in which Customer Content is hosted in Cap Orbit-operated AWS infrastructure in a United States region. Of the providers identified below, only Amazon Web Services (AWS) processes Customer Content and is therefore a Subprocessor in the strict sense of that defined term. For transparency, we also disclose the providers that process account and identity data (WorkOS), billing data (Stripe), and Usage Data (Metronome), together with the provider that hosts our public marketing website and processes no Customer Content (Vercel). This document uses "Subprocessors and service providers" when referring collectively to both 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 (Pro / hosted)
The following table lists the providers Cap Orbit currently engages in providing the hosted (Pro) Service. Only AWS processes Customer Content; the other providers process account and identity data, billing data, or Usage Data, or (in Vercel's case) no Customer Content, as indicated in the Data Processed column. 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, and AI model inference via Amazon Bedrock | Customer Content, and account and Usage Data | United States |
| WorkOS | Identity, authentication, single sign-on, and organization and seat membership | User identifiers, name, email address, and organization data | United States |
| Stripe | Payment processing and subscription billing | 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 |
| Vercel | Hosting of the public marketing website only | Website visitor server logs (IP address, user agent, referrer); no Customer Content | United States |
3. Amazon Bedrock and Anthropic (Claude models)
Anthropic is not a separate Subprocessor of Cap Orbit. The Claude models that power the Service's AI capabilities are accessed exclusively through Amazon Bedrock, the AI model inference service operated by AWS. Amazon Bedrock is the contractual boundary for AI inference: Customer Content is processed within Amazon Bedrock and is not provided to Anthropic as an independent processor.
AWS documentation for Amazon Bedrock states that AWS and third-party model providers do not use inputs to or outputs from Amazon Bedrock to train Amazon's models or any third-party models, and that a customer's inputs and model outputs are not shared with model providers (see the AWS Bedrock FAQ at https://aws.amazon.com/bedrock/faqs/ and the AWS Bedrock security and privacy page at https://aws.amazon.com/bedrock/security-privacy-responsible-ai/). AWS documentation also states that model providers operate in separate model deployment accounts that AWS owns and operates, and that model providers do not have access to Amazon Bedrock logs or to customer prompts and completions (see the AWS Bedrock User Guide, Data protection, at https://docs.aws.amazon.com/bedrock/latest/userguide/data-protection.html). These are AWS service-level commitments for Amazon Bedrock and are separate from Cap Orbit's own commitment, stated in the Terms of Service and Privacy Policy, that Cap Orbit does not use Customer Content, Inputs, or Outputs to train, fine-tune, or otherwise improve any AI or machine-learning model except where the Customer expressly opts in or instructs that use.
4. Enterprise / BYOC deployments
Where the Service is deployed under the Enterprise model ("bring your own cloud", or "BYOC") into infrastructure the Customer owns (the Customer's own AWS account, in the Customer's region), the AWS infrastructure that hosts and processes Customer Content is the Customer's own infrastructure and is not a Cap Orbit Subprocessor for Customer Content. In that model, Customer Content stays in the Customer's cloud, Cap Orbit does not take possession of Customer Content, Cap Orbit does not hold credentials that can write into the Customer's infrastructure, cross-account access is trigger-only, and the Customer controls its own retention, deletion, encryption keys, audit logs, and access revocation.
The following continue to apply as Cap Orbit service providers in the Enterprise / BYOC model 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).
Vercel hosts the public marketing website only and does not process Customer Content under either deployment model.
5. Changes and notification
Effective date: June 18, 2026.
Cap Orbit may add to or change its Subprocessors from time to time. Before a new Subprocessor begins processing Customer Content in the hosted (Pro) Service, 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