Subprocessors
Last updated September 29, 2026
This page lists third-party subprocessors Crevio, Inc. may use to deliver the Service. Actual usage depends on enabled product features, account settings, and environment configuration. For background on how we share personal data, see our Privacy Policy.
Current Subprocessors
| Vendor | Primary purpose | Typical data categories |
|---|---|---|
| Hetzner (managed via Hatchbox) | Application servers, background workers, and Redis (United States) | All application data processed by the Service |
| PlanetScale | Primary PostgreSQL database (AWS, US East) | All application data processed by the Service |
| Cloudflare | DNS, CDN, custom domains, bot protection (Turnstile), AI Gateway routing, Workers and Durable Objects running the AI agent runtime and chat history, and R2 object storage for uploaded files, generated media, and exports | Request metadata, IP address, user agent, chat messages, routed AI request payloads, uploaded and generated files |
| Vercel | Isolated cloud computers (sandboxes) for the AI agent and site previews | Workspace files, code, synced Slack channel history, environment variables, execution logs |
| Stripe | Payments, subscriptions, merchant payouts via Stripe Connect | Billing data, payment method identifiers, transaction records, payout account identifiers |
| OpenAI | AI model inference | Prompts, completions, related metadata |
| Anthropic | AI model inference (Claude) for text generation and agent execution | Prompts, completions, related metadata |
| Google (Gemini, Cloud) | AI model inference, Google sign-in, and supporting cloud services | Prompts, completions, OAuth identifiers, related metadata |
| OpenRouter | Routing layer for AI model inference to model providers such as Z.AI | Prompts, completions, related metadata |
| fal.ai | AI media generation (images, video, audio) | Generation prompts, reference media, generated outputs |
| Vapi | AI voice calls and phone numbers | Phone numbers, call audio, call transcripts |
| Sapiom | Metered access to third-party tools the AI agent calls | Tool call inputs and outputs |
| Pipedream | Connections to third-party apps you authorize | OAuth tokens, configuration data, payloads routed through the integration |
| GitHub | Source-of-truth for sandbox repositories and tenant code | Code, commit metadata, integration tokens |
| Zernio | Publishing to connected social media accounts | Post content and media, social account identifiers |
| Firecrawl | Web crawling for research and content workflows | Target URLs, scraped content |
| Hunter.io | Email verification for outbound flows | Email addresses |
| X (Twitter) API | Searching public posts and verifying X accounts | Search queries, public X handles |
| ScreenshotOne | Screenshots of published pages | Page URLs, rendered page images |
| doola | Business formation and company services | Founder name, contact details, address, company details |
| Resend | Transactional email delivery and inbound email | Email address, recipient name, message content, delivery metadata |
| Loops | Product and marketing email sequences | Email address, subscription list membership, engagement metadata |
| Expo | Push notifications to the Crevio mobile app | Device push tokens, notification content |
| Slack | Slack app integration | Workspace, channel, member, and message data from workspaces that install Crevio |
| Discord | OAuth sign-in and bot integration | OAuth identifiers, Discord profile data, server metadata |
| Telegram | OAuth sign-in and bot integration | OAuth identifiers, Telegram profile data, chat metadata |
| PostHog | Product analytics (consent-gated where required) | Event data, user identifiers, page context |
| ClickHouse Cloud | Analytics for storefronts and hosted sites (AWS, US East) | Page views, device and referrer data, approximate location |
| Axiom | Application logs, metrics, and traces | Request logs and diagnostic data, which may include user identifiers and IP addresses |
| Sentry | Error monitoring and performance tracing | Error stack traces, request context, user identifiers in error reports |
| Linear | Internal tracking of bug reports and product feedback | Feedback content, account and user identifiers |
| Cal.com | Scheduling user research calls | Name, email address, booking details |
| Dub | Referral and affiliate attribution | Account identifiers, signup and conversion events |
| Meta | Advertising measurement and conversion tracking (server-side CAPI) | Hashed email or user identifiers, conversion event metadata |
| Google Ads / Tag Manager | Advertising measurement and tag delivery (consent-gated where required) | Conversion events, page context |
| Open Exchange Rates | Currency conversion data | None (rates only) |
Hosting infrastructure. Crevio's application servers, background workers, and Redis run on Hetzner in the United States, managed via Hatchbox. The primary database runs on PlanetScale in AWS US East. The AI agent runtime runs on Cloudflare, and each account's agent computer runs on Vercel.
Updates to This List
We may update this list as vendors or service architecture changes. Material updates are reflected by updating the effective date at the top of this page.
Related Notices
For questions about subprocessors, contact [email protected].