App: Dice! Publisher: Matthew Sawrey

This page explains how to delete the personal data the Dice! mobile app processes about you. The app has no server of its own and no user accounts, so almost all deletion is self-service — you do not have to contact us, and we do not hold any data on your behalf.

For the full list of what data is processed and why, see the Privacy Policy.

1. Data stored on your device

Everything you create inside the app — dice collections, roll history, settings, campaigns and the bag customisation — is stored only on your device. It never leaves your phone. Two ways to delete it:

  • In the app: open Settings → Reset all data. This permanently wipes every collection, history entry, campaign and preference.
  • Uninstall the app. This also permanently removes all on-device data.

Either action is instant. There is no server-side copy to delete.

2. Data processed by third-party SDKs

The app uses Firebase Analytics, Firebase Crashlytics and Google Mobile Ads (AdMob) to keep the free tier running. These SDKs collect diagnostic and advertising data described in the Privacy Policy (Section 5). None of it is linked to your name, email or any direct identifier — it is keyed to pseudonymous device-scoped IDs (a Firebase installation ID, and the mobile advertising ID if you granted ATT/UMP consent).

You can delete or sever the link to this data yourself, without contacting us, in any of the following ways:

  • iOS: Settings → Privacy & Security → Tracking → Dice! — turn off “Allow tracking”. This revokes ATT and stops personalised advertising data collection.
  • Android: Settings → Google → Ads — turn on Delete advertising ID. This breaks the link between AdMob’s data and your device permanently.
  • In-app: if a consent prompt (UMP) is shown on Android, decline it — the app will fall back to non-personalised ads.

b) Uninstall the app

Uninstalling generates a new Firebase installation ID on any future re-install, so existing analytics/crash data can no longer be associated with you.

c) Wait for automatic expiry

Data collected by these SDKs is not retained forever. Google’s default retention periods are:

  • Firebase Analytics event data — up to 14 months, then auto-deleted by Google.
  • Crashlytics crash reports — up to 90 days, then auto-deleted.
  • AdMob ad-serving logs — typically 60 days for serving data, up to 26 months for aggregate reporting.

Combined with advertising-ID reset or uninstall, these retention windows mean any data that identifies you will be gone within months even if you do nothing.

3. Requests we cannot automate

Because the app has no backend, we do not run a database of user accounts. This means there is no per-user record we can delete on our side in response to a request — the data is scattered across Google’s own infrastructure and keyed to identifiers we do not hold. In practice, using the self-service options in Section 1 and Section 2 above is faster and more complete than any request we could action for you.

If you believe you have a specific UK GDPR right that the self-service tools cannot address (for example, a formal Article 17 erasure request from a named individual, or a complaint about how we have described our processing), see the contact details on the Privacy Policy page. We respond within the 30-day limit set by UK GDPR Article 12(3).

4. Questions

Anything else — see the Privacy Policy for full details.