HamamDoku privacy policy

Accounts and local game data

You can play without linking an account. Firebase Authentication creates an anonymous identifier when online. You may optionally link Google or Apple to retain your player name. Firebase processes your account ID and the name, email and provider details supplied during sign-in. Firestore stores your chosen public player name, its reservation, your account ID and timestamps in the EU (eur3). Signed-in players can look up player names. This data provides account access and prevents duplicate names; it is not used to personalize ads. Settings, scores, earned hints and saved runs stay on this device and may be included in OS backups. Signing in does not sync game progress. There are no in-app purchases.

Ads and technical data

Google AdMob provides interstitial ads only. An ad can appear when you choose to play again after a run ends, at most once per three finished runs and once per two minutes; there are no rewarded ads and no banners. Where the law requires it, a consent form (Google User Messaging Platform) is shown before any ad is requested, and a privacy options entry in the game's settings lets you change your choice later. The game requests no ads until that check allows it. It does not mark its ad requests as child-directed and does not itself restrict them to non-personalized ads: where consent is required, your consent choice decides; elsewhere Google's default settings apply. The iOS build does not ask for App Tracking Transparency permission. Ad services may process IP addresses, approximate location inferred from IP, device and app identifiers including the platform's advertising identifier, ad interactions and diagnostics for ad delivery, measurement and fraud prevention. No GPS location is requested. See https://policies.google.com/technologies/ads.

Analytics and crash reports

Firebase Analytics records only its automatic events — first open, sessions and screen views — together with an app-instance identifier, device and app information, and approximate location derived from masked IP addresses. The game sends no events of its own: nothing about individual boards, moves or scores. Crashlytics runs only in release builds and processes crash and error traces, installation identifiers, device, OS and app versions and diagnostic information so we can fix faults. These technical identifiers are not your name but can distinguish installations. Transfers use HTTPS/TLS; retention follows Firebase service settings. See https://firebase.google.com/support/privacy.

Contact and deletion requests

For privacy questions or deletion requests, including requests from parents, email teameksgames@gmail.com. We process the contact details and message you provide to respond. Do not send passwords. Uninstalling the game or clearing its data deletes everything it kept on your device but does not automatically delete previously transmitted service records. We will explain what can be located and deleted without claiming we can identify every installation from an email address. Material changes to this policy will be posted here.

Delete your HamamDoku account

In the game, open Settings → Delete account and confirm. You may be asked to sign in again. This deletes your Firebase account, player profile and name reservation, and clears scores, saved runs and earned hints on this device. To request deletion without the app, email teameksgames@gmail.com with the subject “HamamDoku account deletion”, your player name and the email used with Google or Apple (including an Apple relay email if used). Do not send passwords or login codes. We may verify ownership before deleting; we do not require you to reinstall the app. Anonymous accounts may require an account identifier because an email alone cannot identify them. Previously transmitted advertising, analytics and crash records follow the providers’ retention settings and are not automatically erased by the in-app button. Contact us about those records. Accounts and name reservations are retained until deletion is requested.