Workhorse Subprocessors
- Revised
- SHA-256
- f04049e9c36d931f6efe25f7fb95db866453754b53ead1127bb37de054f67909
This is the current version.
WORKHORSE APPS SUBPROCESSOR LIST
Current at 14 October 2026
This list covers only providers that hold or process customer data for the Workhorse platform itself: its app, backend, billing, email, analytics and AI features. Customer data includes account information, communications and usage metadata. Each row states what the provider may receive; not every provider receives every customer's data.
Providers for systems we build for you are chosen per system, agreed as part of its build work and shown on that system's page in your account. We do not maintain a separate list or send separate provider-change notices for those systems. Providers you contract with directly are governed by your agreement with them.
We may change platform providers at any time, without advance notice, an objection right or change emails. We keep this page current. Our confidentiality, security and overseas handling duties continue to apply. Billing and sign-in providers may also act independently for their own legal, payment, fraud-prevention or account duties.
| Provider | Purpose | Location | Customer data handled |
|---|---|---|---|
| Convex (opens in a new tab) | Platform database, authentication and backend services | United States (Virginia). | Account and session information, platform records and usage metadata. |
| Cloudflare (opens in a new tab) | Network protection, request routing, usage ingestion and storage | Global network, including Australia and the United States; storage location depends on the service and bucket. | Yes: network requests and responses, associated technical information, and usage metadata. |
| Railway (opens in a new tab) | Platform app hosting | United States (Virginia). | App requests, responses and session traffic. |
| Stripe (opens in a new tab) | Payments, payment authorities, subscriptions and invoices | United States and other countries in Stripe's global operations. | Yes: billing contacts, payment information and transaction records; not customer application record contents. |
| Metronome (opens in a new tab) | Usage calculation and billing | United States and other countries under its privacy terms; a dedicated account storage or backup region is not promised. | Yes, limited: business account references and usage quantities; no person identifiers or customer record contents in usage events. |
| Resend (opens in a new tab) | Service email delivery | United States for stored email and logs; sending routes may differ. | Yes: recipients, message contents, delivery details and sign-in links. |
| PostHog (opens in a new tab) | Product analytics embedded in the product | United States. | Product interaction events and associated account, device and technical information. |
| Vercel (opens in a new tab) | Retained platform hosting and previews | Australia (Sydney) and global network processing. | Requests, responses and session traffic on retained platform deployments. |
| Anthropic (opens in a new tab) | Platform roadmap AI drafting, where enabled | United States; processing can also occur through provider infrastructure in other countries. | Roadmap prompts, task information and outputs, under non-training business terms. |
| Google (opens in a new tab) | Optional platform sign-in | United States and global processing. | Sign-in requests and the account information needed for authentication. |
| Outseta (opens in a new tab) | Previous platform billing during cutover and retained records | United States. | Historical account, contact and billing records; retained here while it holds that data. |
Locations describe the service, not a guarantee that all data, support access or backups stay in one country. We provide available details for your service on request. We apply the overseas safeguards in the DPA and Privacy Policy (opens in a new tab).
Contact support@workhorseapps.com for provider questions. Our AI Use Statement (opens in a new tab) explains AI safeguards.