Pitchesto // LEGAL SPECIFICATION
Subprocessors
1. Introduction
Pitchesto uses carefully selected third-party companies to help deliver the Service (“subprocessors”). This page lists categories and typical providers. Actual processing depends on which features you use and which environment variables / integrations are enabled. Read with our Privacy Policy.
2. Core subprocessors
| Provider | Role | Typical data | Region (typical) |
|---|---|---|---|
| Vercel | Application hosting, edge/network delivery, deployments | Request metadata, application content in transit/at rest per hosting config, logs | Global / US-centric edge |
| Neon (PostgreSQL) | Primary application database | Workspace, prospect, project, billing metadata, research records | Provider-configured (commonly US) |
| Google Firebase Authentication | User authentication and session verification | Email, auth identifiers, session tokens | Google Cloud regions |
| Stripe | Platform subscriptions and Stripe Connect client payments | Customer and payment metadata; card data handled by Stripe | Global / US |
| OpenAI | LLM / vision / web-search powered discovery, research, generation, analysis | Prompts, business research context, screenshots/page text as provided by features | Per OpenAI service regions |
3. Optional or configuration-dependent processors
These may process data only when the related integration is turned on:
| Provider | Role | When used |
|---|---|---|
| OpenRouter / model gateways | Alternate model routing (for example legacy Jev paths) | When explicitly configured |
| Vercel AI Gateway / model hosts | Website generation models | When AI generation keys/models are configured |
| Firecrawl (legacy) | Page crawling / extraction | Only if legacy Firecrawl flag/key enabled |
| Google PageSpeed Insights API | Performance signals | When PageSpeed key configured |
| Resend or similar email | Transactional email | When email delivery is configured |
| Object storage (for example Azure Blob / S3-compatible) | File and asset storage | When storage integration is configured |
| Inngest or job runners | Background jobs / orchestration | When durable workflows are enabled |
| Playwright / browser workers | Screenshot capture for research/QA | On hosts configured for browser capture (not all serverless environments) |
4. Updates to this list
We may add or replace subprocessors as the product evolves. Material changes will be reflected on this page with an updated effective date. Enterprise customers with a DPA may receive additional notice rights as specified in that agreement.
5. Contact
Questions about subprocessors or DPA requests: privacy@pitchesto.com