BingoDoku - Privacy Policy
Last updated: 2026-10-01
BingoDoku is operated by Digterious. This policy explains what data the game collects and how it is used.
Data we collect
- Registered player and account identifiers when you choose to create or sign in to an account
- Display name, email address, password verifier, and authentication token for registered accounts
- Google or Apple account identifier and verified email when a player chooses provider sign-in; the game never receives the provider password
- Match results, ranking points, wins, losses, streaks, and leaderboard records
- Optional Classic cloud backups of saved puzzles, entered numbers, notes, play time, personal statistics, Daily progress, and practice progress when you choose to upload them
- Basic server request logs needed for security, debugging, and abuse prevention
- Advertising identifiers and ad interaction data that Google Mobile Ads may process for ad delivery, measurement, frequency capping, fraud prevention, and SDK operation
How we use data
We use this data to provide online matchmaking, account login, rankings, leaderboards, account deletion, security checks, service diagnostics, and ads.
Guest play does not require an account and is limited to Classic Sudoku. Guest progress and personal statistics stay on the device and are not uploaded to competitive leaderboards or cloud backups. Guest play still includes ads; the advertising SDK may process device and ad interaction information without a game account.
Optional rewarded ads can grant five Classic rounds without interstitial ads. Remaining credits and recent reward/round identifiers are stored locally on this device for granting and duplicate prevention, not in online rankings. Declining an ad does not block ordinary Classic play.
Classic cloud backup is optional and manual. Choosing an upload stores the selected backup under your signed-in account; simply signing in does not upload local progress. These private backups are used to restore progress across devices, not to award public ranking points.
Sharing
We do not sell personal data. The app includes Google Mobile Ads, which may process platform-permitted device identifiers and ad interaction data for ad delivery, measurement, fraud prevention, and SDK operation. Google and Apple process provider sign-in when a player chooses those options. This build does not connect Firebase, Google Play Games, or separate analytics SDKs.
On iOS, advertising requests are gated by the consent status returned by Google's consent SDK. Where required, you can revisit advertising privacy choices in the app's settings. The app does not request permission to access the Apple advertising identifier.
Security and retention
Registered passwords are not stored as plaintext. The server stores salted PBKDF2-HMAC-SHA256 password verifiers and uses constant-time checks for authentication tokens and secret verifiers. Authentication tokens expire by default after 30 days. iOS session tokens are stored in the device Keychain, not synchronized through iCloud. Apple authorization refresh tokens, when required for provider account deletion, are stored encrypted on the server with encryption keys kept separately from the database. Account and ranking data is retained while the account exists. Optional Classic cloud backups remain until replaced or the account is deleted; there is no daily reset of these backups. Finished match snapshots are retained briefly for result synchronization; the current server default is 30 minutes. Limited server logs may be retained for up to 90 days for security, debugging, and abuse prevention. Operator-managed SQLite backup snapshots, when enabled, may be retained for up to 30 days before rotation or deletion. Longer retention is used only when required for security, fraud prevention, dispute handling, or legal obligations.
Account deletion
Players can delete an account in the app from the online account panel. A web deletion request option is also available on the account deletion page. Account deletion removes the account credentials, authentication tokens, display name, email address, provider account link, ranking records, and Classic cloud backups associated with the account. The app clears the saved account session and returns to the login/sign-up screen.
For Apple accounts with stored authorization tokens, deletion revokes those tokens with Apple before removing the account. If revocation cannot be completed, the request reports an error so you can retry. For a legacy Apple account without stored tokens, you may also need to remove BingoDoku from Sign in with Apple in your Apple account settings.
Contact
Email: admin@easylinkai.online