Skip to main content
This page is a placeholder. The authoritative MusterBox privacy policy is maintained in the MusterBox legal center; this page will link to the canonical URL once published.

​
Developer-facing privacy notes

The following is a plain-language summary of what the SDK transmits, so you can reason about player privacy in your own privacy policy:
  • Identity: the SDK sends the player’s identifier and password to the MusterBox backend to authenticate. The backend is the identity owner.
  • Device metadata: login may carry device_id, device_name, device_os, and location, plus an x-device-id header. Configure these defaults consciously.
  • Gameplay events: only what your game submits via submitEvent is transmitted. Keep payloads minimal and never put PII into event payloads unless required — they feed analytics and audit.
  • Purchase data: item, amount (decimal string), destination address, and an idempotency key are sent only through the SDK-mediated purchase client.
  • Diagnostics: SDK diagnostics are redacted by default (URLs, tokens, key material). Your own logs should follow the same rule.

​
Your obligations

  • Disclose data handling to your players in your own privacy policy.
  • Do not log tokens, PINs, wallet material, or raw gameKey values.
  • Obey applicable law when collecting any additional personal data in your events.
Contact the MusterBox team for the full privacy policy text.
Last modified on September 10, 2026