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, model inference through Amazon Bedrock, 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, operational reporting, and agent cloud machine traces and logs | Usage events, operational metadata, product telemetry, machine service logs | 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 |
| Hatchet | Workflow orchestration and background job execution | Workflow metadata, task state, queued event data, operational metadata | United States and other regions as configured |
| Latitude.sh | Bare-metal hosting and object storage for agent cloud machines | Repository checkouts, files, commands, logs, environment configuration, machine snapshots | United States |
| Backblaze | Archive storage for dormant machine snapshots | Machine snapshots, including repository checkouts and files | United States |
| turbopuffer | Search indexing for threads, pull requests, and issues | Message text, thread and task titles, pull request and issue text | United States |
| Revyl | Cloud phones, mobile app builds, and device sessions | Repository source archives, app builds, device sessions, organization name, owner email | United States and other regions as configured |
| Grafana Labs | Infrastructure metrics for agent cloud machines | Machine and team identifiers, host metrics | United States |
| 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 |
| Customer.io | Transactional email, lifecycle email, customer messaging, and email engagement | Names, emails, organization data, email events, message metadata | 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 |
| Vercel AI Gateway | Model routing with zero data retention | Prompts, code context, files, tool output, generated Output | Used for selected routed open 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 |
| Cerebras | Model hosting and inference | Prompts, code context, files, tool output, generated Output | Used for selected open models where available |
| Inception | Language model inference | Prompts, code context, files, tool output, generated Output | Used for Mercury models |
| Moonshot AI | Language model inference | Prompts, code context, files, tool output, generated Output | Used for Kimi models, routed through OpenRouter or Vercel AI Gateway |
| Alibaba Cloud | Language model inference and model hosting | Prompts, code context, files, tool output, generated Output | Used for Qwen and selected DeepSeek models, routed through OpenRouter or Vercel AI Gateway |
| Tencent | Language model inference | Prompts, code context, files, tool output, generated Output | Used for Hunyuan models, routed through OpenRouter |
| Meta | Language model inference | Prompts, code context, files, tool output, generated Output | Used for Muse Spark models, routed through Vercel AI Gateway |
| Particle | Language model inference | Prompts, code context, files, tool output, generated Output | Used for Particle models, routed through Vercel AI Gateway |
| DeepInfra | Model hosting and inference | Prompts, code context, files, tool output, generated Output | Used for selected open models, routed through OpenRouter |
| Atlas Cloud | Model hosting and inference | Prompts, code context, files, tool output, generated Output | Used for selected open models, routed through OpenRouter |
| Novita AI | Model hosting and inference | Prompts, code context, files, tool output, generated Output | Used for selected open models, routed through OpenRouter |
| Exa | Web search and retrieval features | Search queries, retrieved snippets, task context needed for search | Used when web search/research tools are available |
| Firecrawl | Web search and retrieval features | Search queries, URLs, retrieved page content | Used alongside Exa when web search/research tools are available |
| ElevenLabs | Speech-to-text transcription | Audio recordings, transcripts | Used for composer dictation and for transcripts of attached voice messages |
| 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, ChatGPT/Codex, or SuperGrok 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 |
| Promptwatch | Marketing-site visitor analytics, including AI search referral traffic | Pageviews, referrer, location, device and browser data |
| Customer.io | Email delivery and engagement | Email address, message metadata, opens/clicks |
| Resend | CRM email campaigns and reply handling | Email address, name, message content, replies |
| Context.dev | CRM company enrichment from email domains | Email domains, company details |
| Exa | CRM research on business contacts and companies | Names, email addresses, company details |
| X | Social outreach from our CRM | X handles, direct messages, engagement data |
| TypeSafe | CRM data enrichment and scoring of business contacts and companies | Names, job titles, company details, public profile data |
| Unipile | LinkedIn messages and connection requests for sales outreach | LinkedIn profile identifiers, messages, connection status |
| 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. Each change is listed under Changes below and in the subprocessor RSS feed, so you can subscribe to be notified. 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."
Changes
- October 30, 2026: Added speech, search, mobile, monitoring, and model providers. ElevenLabs transcribes composer dictation and attached voice messages. Firecrawl serves web search and retrieval alongside Exa. turbopuffer indexes threads, pull requests, and issues for search. Revyl runs cloud phones and mobile app builds. Grafana Labs receives infrastructure metrics for agent cloud machines, and ClickHouse also stores their traces and logs. Added Vercel AI Gateway, Moonshot AI, Alibaba Cloud, Tencent, Meta, Particle, DeepInfra, Atlas Cloud, and Novita AI as model providers.
- October 30, 2026: Added Resend, Context.dev, Exa, and X as marketing providers. Resend sends CRM email campaigns and handles replies. Context.dev enriches companies from email domains. Exa researches business contacts and companies. X carries social outreach from our CRM.
- October 15, 2026: Updated infrastructure and model providers. Hatchet replaces Temporal for workflow orchestration. Latitude.sh replaces Daytona as the host for agent cloud machines, and Backblaze stores archived machine snapshots. Added Cerebras and Inception as model providers, and Amazon Bedrock model inference under Amazon Web Services.
- October 15, 2026: Added TypeSafe and Unipile as marketing providers. TypeSafe enriches and scores business contacts and companies in our CRM. Unipile sends LinkedIn messages and connection requests for sales outreach. Neither processes Customer Content.
- October 15, 2026: Removed PostHog and Sentry as app subprocessors. The Capy app no longer sends data to PostHog or Sentry. PostHog remains a marketing-site analytics provider, and Sentry remains a customer-directed integration.




