Legal
Sub-processors
Last updated: · DPA v1.2.1
Every third party that processes customer data on Sageio's behalf, with its purpose and processing location. This page mirrors the table in our Data Processing Agreement and is updated whenever the list changes.
SUB-PROCESSORS
The full chain of custody.
| Sub-processor | Purpose | Processing location |
|---|---|---|
| Amazon Web Services | Cloud hosting, object storage, encryption key management. | Customer-selected region (default: Singapore, Asia-Pacific). EU and US on Enterprise plans. |
| Neon | Managed PostgreSQL database for application data. | Region matched to Customer's primary AWS region. |
| Vercel | Hosting for marketing site and customer-facing web application. | Global edge network. Origin: customer-selected region. |
| Clerk | Authentication, single sign-on, and identity management. | United States. |
| Deepgram | Speech-to-text transcription of meeting audio. | United States. |
| OpenAI | Real-time speech-to-text transcription of meeting audio (default engine for new workspaces) and transcription of uploaded audio files. | United States. |
| DeepL | Translation of interim transcript segments and final translation for selected target languages. | Germany (EU). |
| Google (Gemini API) | Translation refinement of finalized transcript segments; AI-generated summaries and action items. | United States. Data not used to train Google models per paid-tier Gemini API terms. |
| Resend | Transactional email delivery (account and service notices; meeting-summary emails sent at the user's request). | United States. |
Lemon Squeezy (a Stripe company) is not a sub-processor: as Merchant of Record it determines its own purposes for payment, tax, and invoicing, and acts as an independent data controller under its own privacy policy.
Plausible (cookieless website analytics) operates only on our marketing site and does not process platform personal data under this DPA; it is disclosed in the Privacy Policy.
Changes to this list follow the sub-processor change mechanism in our DPA; each change is recorded in the DPA version history.