Subprocessors
Last updated October 12, 2026
These companies process personal data or Customer Content for RelayDev. They are the sub-processors authorised under the Data Processing Agreement. We notify account owners by email at least 30 days before we add or replace one, and update this page at the same time.
Current subprocessors
| Provider | What they do for RelayDev | Data they handle | Location |
|---|---|---|---|
| Vercel | Hosts the RelayDev web app, its cron jobs and the workflow runtime. Runs cloud agent work in Vercel Sandbox microVMs. | Everything that passes through the web app. Repository contents cloned into cloud sandboxes during a run. Run output. Request logs and IP addresses. | United States and other countries where Vercel operates |
| Supabase | Hosts the Postgres database and Supabase Auth (sign-up, log-in and sessions). | Account details. All application data: projects, tasks, run events and the audit log. Provider credentials, encrypted. | Region set by RelayDev for its Supabase project |
| Anthropic | Runs the Claude models that power agents, through the Claude Messages API with the customer's own API key. The Admin API is read-only and only used for usage reports. | For cloud runs: task descriptions, repository code and tool output sent as prompts. Usage and cost metadata. | United States |
| GitHub | Gives the RelayDev GitHub App access to the repositories you choose. Agents read code, RelayDev pushes run branches, and opens and merges pull requests. | GitHub account and installation identifiers, repository names and contents, and pull request data. | United States and other countries where GitHub operates |
| Sentry (Functional Software, Inc.) | Error and crash reporting for the web app, its workflows and the desktop app. | Error messages and stack traces, the page or API route involved, browser or operating system version, and run and project ids. Request bodies, cookies, console output and run logs are removed before sending. | United States |
| Better Stack | Uptime monitoring and the public status page. Checks that RelayDev's public pages and health endpoint respond. | None about you: it only requests public URLs and records whether they answered. Status page subscribers' email addresses, if you subscribe. | European Union and United States |
| Stripe | Payment processing and subscription billing for paid plans. Receives billing data once paid plans are switched on. | Name, email, billing address, invoices and payment details. Card data goes straight to Stripe and is not stored by RelayDev. | United States and other countries where Stripe operates |
Desktop app
Local runs happen on your own computer with your own Claude Code login, so the content of those runs is sent to Anthropic under your agreement with Anthropic, not through RelayDev. RelayDev still stores tasks and run records, through the subprocessors above.