Subprocessors
Version 2026-08-03 · effective
Draft for owner and legal review. The routing, versioning, and acceptance mechanics around this document are production code. The prose is not legal advice and has not been reviewed by counsel.
These are the companies currently configured to process data on PpcGPT's behalf. We publish a dated entry here and email account owners 30 days before adding one.
| Provider | Purpose | Data category | Region |
|---|---|---|---|
| Vercel | Application hosting | Request metadata | United States |
| Supabase (on AWS) | Authentication, database, file storage | Account data, Amazon business data, uploaded invoices | United States |
| GitHub | Source control and continuous delivery | No customer data | United States |
Corrections
2026-08-03 — Launch inventory corrected. The 2026-07-31 draft listed Trigger.dev, Anthropic, Resend, and Better Stack as if they were active. The public-site-first deployment does not configure those services, so they are not current subprocessors. Each will be added through a new dated version and the notice process above before it receives customer data.
2026-07-31 — Sentry removed. An earlier draft listed Sentry as an error-monitoring subprocessor. No Sentry integration was deployed and no data was sent to it. PostHog is also not configured; error telemetry currently has no third-party destination.
Not currently subprocessors
Railway is not on this list. It appears in our architecture notes for a keyword-research experiment that is disabled and not provisioned. If that experiment is activated, Railway will be disclosed before deployment and will receive no Amazon data or tenant credentials.
Contact
Questions: privacy@ppcgpt.ai.