Version 2.6 · effective 2026-10-25
Subprocessors and Providers — FizzUp
1. How to read this registry
FizzUp uses technology providers only to the extent required for an active function. Not every technically approved integration is active for every user, market or module.
The registry describes integrations and conditions for admission to a feature. It does not declare that a listed provider processes a particular person’s data. Before activation, we confirm entity, role, region, contract/DPA, transfer mechanism and training restrictions; for Entrusted Data we provide the required DPA notice. The recipient selected for an operation is identified before transfer; a recipient change requires an updated notice and the required acknowledgement.
2. Registry
| Provider / group | Function | Typical data | Functional status | Safeguards |
|---|---|---|---|---|
| Railway | API, database and backend infrastructure hosting | account data, progress, transcripts, logs | production / environment-dependent | contract and DPA; production region and transfer must match the deployed configuration |
| Google Cloud / Google Gemini | AI models, Live conversation, speech functions, Google login, Firebase/push depending on configuration | Live audio, text, transcript, session/device identifiers, email for login | feature-dependent integration; transfer only after admission and identification of the recipient before the operation | DPA and an appropriate transfer mechanism, e.g. adequacy/DPF or SCCs |
| Resend | transactional email (sign-in, invitations, notifications, billing) and marketing email (only with the recipient's prior consent) | email address, name, message content, delivery data | scope depends on the email service used; the actual recipient and role must match delivery configuration | AWS servers in Ireland (region eu-west-1); contract/DPA and an appropriate transfer mechanism for any access from outside the EEA |
| Hostinger | FizzUp mailboxes (e.g. hello@, privacy@, support@) and domain | correspondence sent to and from FizzUp, email addresses | scope depends on the email service used; the actual recipient and role must match delivery configuration | contract/DPA; region and transfer in line with the service configuration |
| Stripe | web payments, B2B billing and future web B2C/Family billing | customer ID, transaction and billing data; card data handled by Stripe under its service | active for web billing | DPA/payment terms and appropriate transfer mechanism |
| Apple | iOS distribution, Sign in with Apple, push and consumer purchases if activated | account/device identifiers, purchases, platform data | active depending on platform | platform terms and applicable safeguards |
| Google Play / Google Identity | Android distribution, authentication and consumer purchases if activated | account/device identifiers, purchases, platform data | active depending on platform | platform terms and applicable safeguards |
| Microsoft (Azure Speech) | pronunciation assessment in selected exercises, if activated | recording of the answer in the exercise and its text | feature-dependent integration; transfer only after admission and identification of the recipient before the operation | activation only after confirming contract/DPA, region and transfer mechanism |
| Meta (WhatsApp Business) | WhatsApp messages with FizzUp, if the user uses this channel | phone number and message content | optional | activation only after confirming contract/DPA and transfer mechanism |
| Sentry | error/stability diagnostics if activated | technical data, event identifiers, redacted error context | optional | before activation: confirm entity, DPA, content minimization and transfer mechanism |
| OpenAI | selected voice-conversation sessions and additional language models depending on configuration | Live audio, text, transcript and session identifier needed for the feature | feature-dependent integration; transfer only after admission and identification of the recipient before the operation | current contract/DPA, settings restricting training use and an appropriate transfer mechanism are required |
| Anthropic | additional language models if activated | text and context needed for the function | feature-dependent integration; transfer only after admission and identification of the recipient before the operation | before activation: contract/DPA, no-training setting, transfer mechanism |
| OpenRouter | routing to additional models if activated | text and limited function context | feature-dependent integration; transfer only after admission and identification of the recipient before the operation | activation only after privacy, security, contract and transfer review |
| z.ai | additional language model if activated | text and limited function context | feature-dependent integration; transfer only after admission and identification of the recipient before the operation | activation only after privacy, security, contract and transfer review |
3. No-training principle
For Private Coaching Layer data, FizzUp uses service configurations and terms that, under the relevant contract and provider capabilities, exclude use of transferred data for training the provider's general/public models.
4. Provider changes
FizzUp may change a provider or model for quality, availability, security, compliance or cost reasons. A change requiring notice or objection under the DPA is communicated to the B2B customer within the specified notice period.
Material public-registry changes are reflected in the Legal Center.
5. Transfers
Where processing occurs outside the EEA, we use an appropriate GDPR transfer mechanism, including an adequacy decision, the EU-US Data Privacy Framework for an eligible recipient, or SCCs together with a transfer assessment and supplementary measures where required.
Contact: privacy@fizzup.ai.
The Polish version is the reference version. This English text is a translation; in case of an unintended difference, the Polish version prevails.