Overview
This page identifies service providers and customer-directed integration providers that may process Customer Content or personal information in connection with Capy. It supplements our Privacy Policy, Terms of Service, and Data Processing Addendum.
Not every provider is used for every customer, plan, feature, model, integration, or region. Data processed depends on your configuration, selected models, connected repositories, enabled integrations, support requests, billing setup, and instructions to agents.
Core subprocessors
These providers may process personal information or Customer Content on Capy’s behalf to operate the Services.
| Provider | Purpose | Example data | Processing location |
|---|---|---|---|
| Amazon Web Services | Cloud infrastructure, storage, encryption, networking, and related services | Customer Content, files, logs, artifacts, operational metadata | United States and other AWS regions as configured |
| Cloudflare | Network, security, edge, DNS, and web-deployment routing services | IP address, request metadata, deployment routing metadata | Global |
| Vercel | Website and web application hosting, edge delivery, preview/deployment infrastructure, analytics | IP address, browser/device data, request metadata, page/app usage | Global |
| PlanetScale | Production database infrastructure | Account, organization, project, task, billing, integration, and application data | United States and other regions as configured |
| ClickHouse | Telemetry, product analytics, usage analytics, and operational reporting | Usage events, operational metadata, product telemetry | United States and other regions as configured |
| Upstash | Redis-compatible caching, queues, rate limits, realtime state, and operational coordination | Session metadata, cache entries, queue metadata, operational data | United States and other regions as configured |
| Temporal Technologies | Workflow orchestration and background job execution | Workflow metadata, task state, operational metadata | United States and other regions as configured |
| Daytona | Cloud development environments and agent VM infrastructure | Repository checkouts, files, commands, logs, environment configuration, artifacts | United States and other regions as configured |
| Clerk | Authentication, account management, sessions, and organization identity | Names, emails, user IDs, session data, organization membership | United States and other regions as configured |
| Stripe | Payment processing, invoices, subscriptions, taxes, fraud prevention, and disputes | Billing contact, payment metadata, invoices, transaction IDs, tax data | Global |
| Autumn | Subscription management, entitlements, credits, usage-based billing, and billing state | Organization IDs, plan, credits, usage records, subscription metadata | United States and other regions as configured |
| PostHog | Product analytics, feature usage, attribution, and product improvement | Pageviews, product events, account IDs, organization IDs, device data, UTM data | United States |
| Customer.io | Transactional email, lifecycle email, customer messaging, and email engagement | Names, emails, organization data, email events, message metadata | United States |
| Sentry | Error monitoring, performance diagnostics, and reliability | Error reports, stack traces, user IDs, URLs, device/browser data, diagnostic context | United States |
| Pylon | Customer support, security reports, and issue-management workflows | Support messages, contact information, issue metadata, security-report context | United States and other regions as configured |
| Ashby | Careers pages, recruiting workflows, job applications, and referral handling | Candidate names, emails, resumes, application materials, referral data | United States |
| Slack | Internal alerting and recruiting referral notifications | Referral form data, operational alerts, support or security notifications | United States and other Slack regions |
AI and model providers
Capy routes prompts, code context, files, logs, images, screenshots, tool output, and generated Output to model providers only as needed to provide the selected AI features. Model availability and routing can change over time.
| Provider | Purpose | Example data | Notes |
|---|---|---|---|
| Anthropic | Language model inference | Prompts, code context, files, tool output, generated Output | Used for Claude models |
| OpenAI | Language model inference and external subscription features | Prompts, code context, files, tool output, generated Output | Used for GPT/Codex models and related features |
| OpenRouter | Model routing and custom model-provider access | Prompts, code context, files, tool output, generated Output | Used for selected routed and customer-configured models |
| Google / Google Cloud / Vertex AI | Language model inference and model hosting | Prompts, code context, files, tool output, generated Output | Used for Gemini and Vertex-hosted models |
| xAI | Language model inference | Prompts, code context, files, tool output, generated Output | Used for Grok models where available |
| Fireworks AI | Model hosting and inference | Prompts, code context, files, tool output, generated Output | Used for selected open and hosted models |
| Z.AI | Language model inference | Prompts, code context, files, tool output, generated Output | Used for selected GLM models where available |
| DeepSeek model hosts | Language model inference where routed through supported providers | Prompts, code context, files, tool output, generated Output | Used for selected DeepSeek models where available |
| Exa | Web search and retrieval features | Search queries, retrieved snippets, task context needed for search | Used when web search/research tools are available |
| fal.ai | Media or image generation features where available | Image prompts, reference images, generated media | Used only for media-generation features where enabled |
Capy does not use non-public Customer Content to train models that Capy develops or controls unless you explicitly opt in or otherwise agree in writing. Third-party model-provider processing is subject to the applicable provider’s terms, policies, configurations, and data-processing commitments.
When you use BYOK, external subscriptions, customer-provided model credentials, or customer-directed model providers, that provider may process data under your own agreement with that provider rather than as Capy’s subprocessor.
Customer-directed integrations
These providers process data when you connect or instruct Capy to interact with them. They may act as independent controllers, processors for you, or service providers under their own terms.
| Provider | Purpose | Example data |
|---|---|---|
| GitHub | Repository access, branch creation, commits, PRs, issues, comments, checks, reviews, and webhooks | Repository contents, commit metadata, PR/issue data, comments, user identifiers, installation metadata |
| Slack | Slack-originated tasks, thread sync, message search/read tools, notifications, and file attachments | Workspace metadata, channel/thread messages, files, user IDs, permissions, reactions |
| Linear | Issue delegation, context sync, team mappings, project routing, and task updates | Issue text, comments, team/project metadata, user identifiers |
| Sentry | Error/issue context, automation triggers, and issue investigation | Issue metadata, stack traces, event data, project metadata |
| Vercel | Preview deployment detection and deployment context | Deployment URLs, PR comments, project/deployment metadata |
| GitHub Copilot or ChatGPT/Codex external subscriptions | Customer-directed model access using the customer’s own subscription | Prompts, code context, generated Output, subscription status |
| MCP servers and custom tools | Customer-directed tool access and context retrieval | Data exposed by the configured server or tool |
| Cal.com | Sales/demo scheduling | Name, email, company, scheduling metadata |
| YC Bookface, Solo Founders, and partner portals | Partner credit eligibility and redemption flows | Email, company, eligibility metadata submitted through partner workflows |
You control whether these integrations are enabled and what permissions are granted. Review each provider’s permissions, privacy policy, and terms before connecting it to Capy.
Recruiting and marketing providers
Our marketing site and careers workflows may use additional providers for job listings, applications, referrals, scheduling, analytics, and communications.
| Provider | Purpose | Example data |
|---|---|---|
| Ashby | Job listings, application forms, application submission, recruiting workflows | Candidate data, resumes, applications |
| Cal.com | Sales/demo scheduling | Name, email, company, meeting metadata |
| PostHog | Marketing and product analytics | Pageviews, UTM data, referral data, browser/device data |
| Customer.io | Email delivery and engagement | Email address, message metadata, opens/clicks |
| Slack | Internal referral and operational notifications | Referral form content, alert metadata |
How updates work
We may update this page at any time in our sole discretion, including when providers are added, removed, replaced, renamed, or used for new purposes. If a new material Subprocessor is added for Customer Personal Data under the Data Processing Addendum, customers may object as described in that DPA or their applicable agreement.
Questions or objections may be sent to support@capy.ai with the subject line "Subprocessors."