Data safety

A plain-language summary of what BECK collects, why, and how it's protected.

Last updated: 1 August 2026. This page mirrors BECK's privacy policy and the Data Safety section of our Google Play listing.

Data BECK collects

App activity — anonymized in-game events (cases started/solved, clues collected, hints used, rank changes), to balance and improve the game.
App info and performance — crash logs and diagnostics, to find and fix bugs.
Device or other identifiers — an app-instance identifier collected by analytics, plus an installation identifier used by crash reporting. BECK does not collect your device's advertising identifier by any route: ad requests are child-directed, so no advertising ID is transmitted to AdMob, and analytics collection of it is switched off. You can stop the remaining identifiers being collected by turning analytics and crash reporting off in the game's Settings → Privacy.
Game progress and achievements — only if you sign in to Google Play Games, stored with Google as your cloud save so it syncs across your devices.

Is data shared with third parties?

Data is processed by Google services acting on our behalf: Google Firebase (Crashlytics, Analytics, Firestore), Google Play Games Services, and Google AdMob (rewarded ads). We do not sell your personal data.

How data is handled

Encryption in transit: yes — all service traffic is TLS-encrypted by default.
You can request deletion: yes — see the data deletion request page.
Account required to play: no — Google Play Games sign-in is optional.
Independent security review: no.

Data deletion

You may request deletion of any data BECK holds about you via the data deletion request page. Uninstalling the game removes all data stored locally on your device.