Legal

Privacy policy

How Mbox handles merchant account data, device registration, and the minimum notification signals needed for soundbox detection and sync.

Last updated: 28 October 2026

What we process

Mbox processes the minimum notification data required to detect eligible payment notifications, announce amounts locally, and synchronize merchant-owned event records.

  • Account identity needed to sign in and manage shops or devices
  • Device registration metadata for authorized soundbox phones
  • Parsed payment-event fields used for announcements and dashboard sync
  • Billing and subscription status for plan entitlements

What we avoid by default

Raw notification bodies are not stored by default. Device secrets are stored hashed on the server. Merchants may request a data export from account settings.

Merchant control

Merchants remain in control of which Android device holds notification access. You can revoke device access, manage team members from the dashboard, and contact support for export or deletion requests.

Related reading: detection limitations and the terms of service.