Subprocessors
Last updated: March 1, 2025
We use the following subprocessors to provide and operate our services. This list may change over time. We will update this page when we add or remove subprocessors or make material changes. If you have entered into a Data Processing Addendum with us, we may notify you of material changes (e.g., by email) where required.
Email notification (optional)
If you would like to receive email notification when we add or change subprocessors in a material way, please contact us and we will add you to our notification list. (TODO: Founder to set up notification mechanism if desired.)
| Vendor | Service | Purpose | Data categories | Hosting / region |
|---|---|---|---|---|
| Clerk | Authentication and user management | Identity, sign-in, and account management | Account identifiers, email, profile data | United States (placeholder) |
| Supabase | Database and backend | Data storage, APIs, and real-time features | Customer data, usage data, application data | United States / EU (configurable) |
| Stripe | Payments and billing | Payment processing and subscription management | Billing contact, payment method metadata, transaction data | United States |
| Twilio | Voice and SMS | Calls, SMS, and communication APIs | Phone numbers, call/SMS metadata, message content | United States |
| Vercel | Hosting and edge | Application hosting, CDN, and serverless functions | Request data, logs, deployment metadata | Global edge |
| PostHog (or equivalent analytics) | Product analytics | Usage analytics and product insights (where consent applies) | Usage events, device/browser data, feature usage | United States / EU (placeholder) |