Neblla's sub-processors
Providers that process data of the apps' players on Neblla's behalf:
| Provider | What for | Where | Transfer outside the EEA |
|---|---|---|---|
| Render (Render Services, Inc.) | Neblla's server: connections, rooms, API | US (Oregon) | Yes: standard contractual clauses |
| MongoDB Atlas (MongoDB, Inc.), on AWS | The main database | EU (Frankfurt, Germany) | No |
| Turso (ChiselStrike, Inc.), on AWS | Database for the apps' data | EU (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 network | Yes: Privacy Framework / standard clauses |
| Stripe (Stripe Payments Europe, Ltd.) | Charging on the developer's behalf (Stripe Connect) | EU (Ireland), with processing in the US | Yes: Privacy Framework / standard clauses |
| Anthropic (Anthropic, PBC) | AI (neblla.ai), only when the call goes through Neblla | US | Yes: standard clauses |
| Google (Google LLC, Firebase) | Signing in with Google | US / global | Yes: Privacy Framework / standard clauses |
| Resend | Transactional emails (codes, confirmations, notices) | US | Yes: 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 too | Global (Dubai / Telegram servers) | Yes: the connecting person's consent and standard clauses |
What does not go through here:
- With their own database (BYODB), the app's data is stored in the developer's database, who chooses where.
- P2P messages travel directly between the players' devices and are not stored by Neblla.
- AI in browser mode (
userTokenMode: 'browser') goes straight from the browser to Anthropic, with the user's own key.
Last updated: 27 October 2026