Subprocessors

Working draft ยท Last updated 6 July 2026

Working draft. Under legal review. We will notify connected customers' admins by email at least 14 days before adding a subprocessor.

Infrastructure and tooling

These providers process data on our behalf for every customer:

Provider Purpose What it can touch Location
Render Application hosting: API, background workers, database, cache All service data (encrypted at rest; tokens additionally app-layer encrypted) US
Vercel Web app and website hosting Static assets and web traffic; no customer database access US/global edge
Anthropic AI explanations Error text, matched configuration excerpt, component labels (see Privacy ยง5); no training on customer data US
PostHog Product analytics Anonymous usage events with enumerated properties only US
Sentry Error monitoring Application error reports, scrubbed of tokens and user content US
Resend Transactional email (sign-in links, notifications) Recipient email addresses and message content US
UptimeRobot External uptime monitoring Public endpoint URLs and response status only โ€” no customer data EU

Customer-elected destinations

These providers receive data only if your organization connects them as a ticket destination โ€” and then only the tickets your users choose to file. If you never connect them, they never see your data.

Provider Purpose What it receives
Atlassian (Jira Cloud) Ticket destination Ticket title, body, step labels, masked screenshot โ€” per ticket filed
Linear Ticket destination Ticket title, body, step labels, masked screenshot โ€” per ticket filed

Salesforce Cases, the third destination, are created inside your own Salesforce org โ€” no third party is involved.

Questions about this list: hello@rootcase.io.