Sub-processors
The companies that process personal data from Linguiqo on our behalf, under the data processing addendum.
| Sub-processor | Purpose | Location | Safeguard for transfers outside the EU |
|---|---|---|---|
| Google Cloud | Application hosting, database, files and backups | EU – Belgium (europe-west1) | Data stored in the EU. Any access from the US: EU-US Data Privacy Framework and standard contractual clauses |
| Stripe | Payments and invoicing (payer details) | EU (Ireland) and US | EU-US Data Privacy Framework and standard contractual clauses |
| Brevo | Transactional email: invitations, account verification, notifications | EU | Not needed, the data stays in the EU |
Planned changes
No changes are planned.
How changes are announced
We publish every addition or replacement of a sub-processor here at least 30 days before it takes effect. If you have a reasonable objection, write to hello@linguiqo.com; what happens next is in article 6 of the addendum.
Not sub-processors
Machine translation (for example OpenAI or DeepL) runs on your own API key, git hosting (for example GitHub, GitLab or Azure DevOps) on your token, webhooks go to addresses you set, and signing in with Google or Microsoft uses your account with them. These are your relationships with those providers, governed by your agreement with them, so they are not our sub-processors. Data reaches them only when your team asks for it.