Sub-processors.
last updated · version 1.1
PorchOps uses the following sub-processors to deliver the service. We don't share customer data with any party not on this list. The Privacy Policy at /legal/privacy Section 9 is the controlling source; this page mirrors it for link discoverability.
Who we use, what flows there.
| Vendor | What flows there | Region | Privacy page |
|---|---|---|---|
| Amazon Web Services (AWS) | Cloud hosting and infrastructure. Customer Data is processed in transit and held transiently during agent execution. | United States (us-east-1) | link |
| Anthropic | LLM inference (Claude API) for agent reasoning. Customer Data is sent at the time you generate an output; commercial API terms prohibit training on customer data; 30-day deletion window. | United States | link |
| Clerk | Authentication and identity management; user records. | United States | link |
| Cloudflare | DNS, CDN, and object storage (R2) for attachments and exports. | Global edge | link |
| GitHub | Source code repository and CI/CD. No Customer Data flows here; this is engineering infrastructure. | United States | link |
| Inngest | Background job and workflow orchestration. Job payloads may reference workspace IDs and Customer Data on a transient basis. | United States | link |
| Langfuse | LLM observability and tracing for quality monitoring. | United States | link |
| Neon | Managed PostgreSQL database for workspace and customer data. | United States | link |
| OpenAI | LLM inference for agent outputs. Commercial API terms prohibit training on customer data. | United States | link |
| Plausible Analytics | Privacy-respecting website analytics. No cookies, no persistent identifiers, no cross-site tracking. | European Union (Germany) | link |
| PostHog | Product analytics and session replay for the marketing site — funnels, conversion tracking, and anonymized session recordings. Input fields are masked in recordings; no product Customer Data flows here. | United States | link |
| Resend | Transactional email (welcome, receipts, notifications). Not a customer connector; agent drafts flow through your own Gmail. | United States | link |
| Sentry | Error tracking and application monitoring. Stack traces may include user-supplied input; sensitive fields are scrubbed before transmission. | United States | link |
| Stripe | Billing and payment processing. Card data is held by Stripe; we never see or store full card numbers. | United States | link |
| Upstash | Redis cache and rate limiting. | Global | link |
| Vercel | Web hosting, edge runtime, and deployment for porchops.com and app.porchops.com. | Global edge | link |
How we notify when this list changes.
When we add or remove a sub-processor, we update this page and notify customers in advance via the in-app changelog. Where applicable law or a Data Processing Addendum requires direct notice, we send that notice by email at least 30 days before activation.
Customers with sensitivity to a new sub-processor may object on reasonable grounds. If we can't accommodate the objection, the customer may terminate the Service for the affected workspaces as described in the Terms of Service.
Email [email protected] with questions, or [email protected] for data-protection-specific inquiries.
Date and version.
last updated may 30, 2026 · version 1.1