Skip to content
FRVR SDK

Privacy requirements

YouTube Playables and China layer extras on top.

Section titled “Consent”
  • MUST integrate FRVR.consent and wait for it to resolve before personalized ads, identifying analytics, or device‑fingerprinting SDKs.
  • MUST respect the channel’s consent surface (ATT on iOS, channel CMP on Web). FRVR.consent adapts to whichever applies.
  • MUST NOT ship a custom cookies banner.

Privacy policy

Section titled “Privacy policy”
  • FRVR’s Privacy Policy and GDPR addendum are shown to players. The game MUST be compliant with them by default. Variations (extra collection, different retention) MUST be registered with FRVR before submission.

External calls

Section titled “External calls”
  • MUST route analytics through FRVR.tracker.
  • ByteBrew and GameAnalytics are approved third‑party providers where the channel permits (YouTube Playables disallows external calls, so neither works there). Enabling either MUST be discussed with FRVR, and the provider’s deletion webhooks MUST be configured with FRVR before going live.
  • MUST NOT call URLs not declared in the data manifest.
  • MUST NOT load remote JavaScript (<script src>, eval of fetched code).

Clipboard

Section titled “Clipboard”
  • MUST NOT read the clipboard except in direct response to an explicit paste action.
  • Writing requires an explicit user action (e.g. “copy invite link” tap).

Identifiers

Section titled “Identifiers”
  • MUST NOT generate or persist a device fingerprint. Use the player ID from FRVR.auth.
  • MUST NOT read OS / device identifiers (IMEI, MAC, advertising ID) directly.