Puzzle Hub is a local-first puzzle game. This policy explains the data handled by the current Android version and the third-party services integrated into it.
Puzzle Hub stores gameplay and preference data on the device so the game continues to work offline. This can include coin balance, Arrow Escape progress/stars/best moves, hints and wrong-move counters, Daily Challenge completion/streak/reward state, achievement state, owned/selected themes and board backgrounds, and device preferences such as sound, vibration and reminders.
Local app data remains on the device until the user clears the app's data or uninstalls the app, subject to Android backup/restore behavior configured by the device and platform.
Puzzle Hub uses Firebase Anonymous Authentication and Cloud Firestore for cloud backup and synchronization. The app does not ask for a name, email address, phone number or password for this cloud identity. Firebase assigns an anonymous user ID (UID), and Firestore data is scoped under that UID.
Cloud data can include coins, Arrow Escape progress/stars/best moves, hints/wrong-move counters, rewarded-progress guards, cosmetic ownership/selection, Daily Challenge completion/streak/reward summaries, achievement state and synchronization metadata/timestamps. The Daily Challenge puzzle itself remains generated by the app.
Production release builds use Firebase Crashlytics to diagnose crashes, ANRs and unexpected non-fatal errors. Reports can contain stack traces, relevant app state, device/app metadata and Firebase installation identifiers. Puzzle Hub can also attach limited diagnostic context such as the current screen/game, Arrow Escape level ID, Daily Challenge identifier and selected app theme. Puzzle Hub does not intentionally attach a player's name or email address to Crashlytics reports.
Puzzle Hub uses Firebase App Check. Production release builds are prepared to use the Google Play Integrity provider so Firebase can receive app-integrity/security signals and an integrity token to help distinguish authentic Puzzle Hub requests from abusive or modified clients. Debug and release-candidate builds use Firebase's debug App Check provider for private testing. App Check enforcement is enabled only after legitimate app traffic has been validated.
Puzzle Hub uses Google Mobile Ads for rewarded ads and existing limited interstitial placements. The advertising SDK may process IP address (which may estimate approximate location), app/ad interactions, diagnostics/performance information, and device/app-set/advertising identifiers where available for advertising, analytics and fraud prevention/security.
Puzzle Hub integrates Google's User Messaging Platform (UMP). Where Google determines that consent/privacy messaging is required, the app presents that flow before ads are requested. Where required, users can revisit advertising choices from Settings → Privacy → Privacy Choices.
The current app has no Google Play Billing or paid-subscription flow.
Puzzle Hub directly declares Internet and network-state access. The Google Mobile Ads SDK can contribute Android advertising-ID permission through manifest merging. Puzzle Hub does not enable cleartext HTTP traffic.
Puzzle Hub uses Firebase Authentication, Cloud Firestore, Firebase Crashlytics (including applicable transitive Firebase Installations/Sessions), Firebase App Check with Google Play Integrity for production attestation, Google Mobile Ads and Google User Messaging Platform. Firebase is used as a service provider for app functionality and diagnostics. Google Mobile Ads processes/shares advertising-related data according to Google's advertising services and user choices.
Puzzle Hub provides an in-app deletion path at Settings → Privacy → Delete Player Data. The flow requires internet access, deletes the current player's known Firestore cloud documents and anonymous Firebase Auth identity first, and only then clears Puzzle Hub's local gameplay/profile/settings data. If cloud deletion cannot complete, local progress is not silently erased.
An external deletion/request resource is available at https://rkfreelantask.com/puzzlehub/delete-data.html.
Crash/advertising data retention is subject to the applicable Google service terms and settings and is not controlled by the Puzzle Hub Firestore deletion action.
Puzzle Hub uses authenticated, user-scoped Firestore rules and does not intentionally send gameplay traffic over cleartext HTTP. Third-party SDK traffic uses the security mechanisms provided by those services.
The final Google Play target-audience declaration must match the audience selected by the developer. This policy does not claim Puzzle Hub is directed to children. If the app is later targeted to children, advertising configuration and this policy must be reviewed against Google Play Families requirements.
This policy describes Puzzle Hub version 1.0.0 as prepared on 30 August 2026. It may be updated when features, SDKs, data practices or legal/policy requirements change.
Privacy questions and deletion assistance can be requested at rksattanathan@gmail.com. Player data can also be deleted directly in-app, and deletion requests can be initiated through the external deletion resource linked above.