Neblla's sub-processors

Providers that process data of the apps' players on Neblla's behalf:

ProviderWhat forWhereTransfer outside the EEA
Render (Render Services, Inc.)Neblla's server: connections, rooms, APIUS (Oregon)Yes: standard contractual clauses
MongoDB Atlas (MongoDB, Inc.), on AWSThe main databaseEU (Frankfurt, Germany)No
Turso (ChiselStrike, Inc.), on AWSDatabase for the apps' dataEU (Ireland)No
Cloudflare (Cloudflare, Inc.)Serving the apps' public files (CDN), the relay for connections between players (TURN), Server in the cloud (Workers) and the encrypted backups (R2)Global networkYes: Privacy Framework / standard clauses
Stripe (Stripe Payments Europe, Ltd.)Charging on the developer's behalf (Stripe Connect)EU (Ireland), with processing in the USYes: Privacy Framework / standard clauses
Anthropic (Anthropic, PBC)AI (neblla.ai), only when the call goes through NebllaUSYes: standard clauses
Google (Google LLC, Firebase)Signing in with GoogleUS / globalYes: Privacy Framework / standard clauses
ResendTransactional emails (codes, confirmations, notices)USYes: standard clauses
Telegram (Telegram FZ-LLC)Alerts to the developer and their team on Telegram, only if the person connects it: by default the type of alert, the app and a button, no user text; with the full text switched on by the developer, that text tooGlobal (Dubai / Telegram servers)Yes: the connecting person's consent and standard clauses

What does not go through here:

Last updated: 27 October 2026