BuzzioDocs

Subprocessors (reference)

Providers that process data to operate Buzzio. Buzzio does not sell personal data to them.

Processors acting for Buzzio

Provider Role Typical data
Google Firebase / Google Cloud Auth, RTDB, Firestore, Storage, Functions, FCM, App Check, Remote Config, Analytics Account/ops data; E2EE ciphertext; analytics events
Cloudflare Workers, R2, D1/history APIs, developer-site edge, Realtime TURN Plaintext shared-room history/objects; bot/developer ops; TURN IP/port/timing and encrypted WebRTC packets
Bunny Media CDN / storage Plaintext OHG / Community / Broadcast bytes; client-encrypted Stories, Vault, and backup objects

Independent controllers under their own terms

Provider Role Typical data
Google Play / Apple App Store Distribution and billing Store account/payment data; Buzzio receives entitlement status
Google / GitHub OAuth Optional developer-console sign-in OAuth identity and email supplied to the developer site
GIPHY GIF/sticker search Search/request data under GIPHY's policy
Blockstream Esplora (or similar) Optional wallet chain queries Public chain queries when wallet is enabled
CoinGecko (or similar) Optional fiat estimates Price API requests

Privacy contact: See Contact and support · https://buzzio.dev

“Processor” and “independent controller” describe different legal roles; they are not interchangeable. When vendors change, update this page, the Privacy Policy third-party table, and store Data Safety forms together.

Related: Threat model · FAQ