Privacy policy
Block Master — Privacy Policy
Updated: 28 October 2026
Developer: Forintx Games
Package: com.forintxgames.blockmaster
Support/privacy: nmburak25@gmail.com
1. Offline play
Classic, Pure, Daily Puzzle and Quick Mode can be played offline. Once an update is detected for your Google Play account, it must be installed before playing. The required version code is stored on this phone; offline play remains available when no update has been detected. Pure is ad-free. Initial Classic tool uses are free; players may optionally watch one rewarded ad per tool per run, with an internet connection, to unlock one extra use. Boards, scores, best scores, themes, settings, player name, friend list and the last 20 race results are stored on the phone. Friend lists remain on the phone. Players aged 13+ may opt in to publishing their name and records as described below. This version has no purchases or paid subscriptions. Classic optionally offers one rewarded continue, one remaining-piece swap, one theme trial and one block-style or effect trial per round. Trials last one round; mission unlocks are permanent. Run IDs, spent allowances and appearance selections are stored on the phone; resuming the same round does not reset them.
2. Online races and Firebase
Friend cards and races use Google Firebase Authentication to create an anonymous player ID (UID). No email, phone or Google account sign-in is requested. Firebase stores this anonymous account separately from the phone and temporary rooms.
Firebase Realtime Database processes participant UIDs, invite target, piece seed, timestamps, latest scores, connection/leave states and the shared result in a temporary room. Connection loss or backgrounding has a 15-second return window. Rematch-enabled rooms temporarily store each player’s ready status and a link to the next round. The same players can race again within 10 minutes after a result. An online client attempts cleanup of a linked previous round after 60 seconds; an unused result room is cleaned when both players leave or after 10 minutes. Older versions clean after both result acknowledgements, or after 60 seconds when an acknowledgement is missing. Waiting invitations expire after 10 minutes. If both devices close, cleanup may wait until a later online session. Boards, full move histories, permanent match archives and phone contacts are not uploaded.
The friend leaderboard stores the highest race score and update time per UID. The world leaderboard is opt-in for ages 13+ and requires accepting its usage rules; an existing local name is never published automatically. The server stores a unique guest fallback, chosen public name, canonical name reservations, last name change time and accepted rules version. Only the highest score and update time for each of Classic, Pure and Race are stored. Existing records are imported on joining. Signed-in players can view these public names and records in pages of 50. Names and pages are cached for five minutes. Boards, move histories and friend lists are not uploaded. Do not include personal information in a public name. Blocking hides a player from lists on this phone and prevents direct invitations. Name reports contain target and reporter UIDs, the reported name key, reason and time, and are private to the developer. Reports and moderation records may remain until abuse review is complete; deletion requests also cover their review. Social-data deletion removes the public profile, all three mode records and name reservations.
Firebase may also process IP addresses and security/service logs under Google's applicable retention policies. An anonymous account can remain until identity deletion is requested.
Friend requests and direct race invitations temporarily store sender/recipient UIDs, the sender’s display name, message type and timestamp; race invitations also include the room code. Accepting a friend request sends a reciprocal acknowledgement so both phones can save the friendship. These are targeted in-game messages, not public lists or push notifications. Only the latest 50 messages per inbox are read while the app is in the foreground. Race invitations expire after 10 minutes and friend requests after seven days. Expired messages are removed when the receiving client reads them; if the recipient never returns, records may remain until social-data deletion. Accepting or declining removes the processed message; deletion removes received messages and known outgoing messages. Complete friend lists remain on the phones.
First-to-two series use protocol 4 rooms with a temporary series ID, predecessor/next-room links, match number, win counters, readiness, transition acknowledgements and an immutable series outcome. Draws do not add a win. Active matches keep the 15-second reconnection window; between matches the pairing waits up to 10 minutes. Clients attempt linked-room cleanup after both transition acknowledgements and 60 seconds, or after 10 minutes if acknowledgements are missing. Cleanup may wait until a later online session. No additional permanent series profile or paid service is used. A small SQLite ledger of received match IDs, participant UIDs, scores, outcome and time remains on this phone to calculate head-to-head totals and prevent duplicate counting; it is not uploaded. Old history without an opponent UID is not attributed to a friend. Social-data deletion removes this ledger. Result cards are generated locally as PNG images in a private cache and shared only through the Android share sheet at the player’s request. Cards contain display names and scores, not player UIDs or room codes. Images older than one day are removed when another card is generated; social-data deletion also clears cached cards. Copies already shared with other apps cannot be withdrawn. The interactive tutorial uses a separate local practice board and a completion preference; it does not submit records, statistics or rewards.
In Play Together, two friends take turns on one board and share one score. Firebase temporarily stores participant UIDs, invite target, the latest board and pieces, last move, turn and sequence, shared score, ready/connection/approval state, and timestamps in a cooperative room; it does not store the full move history. Play pauses on disconnection and the same player can return within 10 minutes. The best valid shared score and friend's name stay on each device and are not added to world rankings. A targeted in-app invitation temporarily includes the room code. Deleting social data also removes the local cooperative record. The room is cleaned after both result acknowledgments, or on a later online launch if acknowledgment is missing. If both devices close, immediate cleanup cannot be guaranteed.
3. Advertising
Google AdMob and User Messaging Platform (UMP) provide ads and privacy choices. One rewarded ad unlocks 5 friend-race entries, including rematches. Remaining entries are saved on the phone. If loading, display or ad preparation fails, users can continue without an ad. The main menu and Classic/race result screens may contain banners in separate space; active gameplay has no banners. A cached interstitial may appear when leaving every third completed Classic round. Interstitials are suppressed for three minutes after earning a rewarded ad. Pure gameplay and Pure results are ad-free. Missing ads never delay navigation. Race result exits do not show an additional interstitial. The reward is explained before opting in.
The ads SDK may collect/share IP addresses (including derived approximate location), ad/app interactions, device and advertising identifiers, performance and diagnostic information for advertising, measurement and fraud prevention. Processing depends on age flags, device settings and regional consent. Ad service data is separate from Firebase room data. Age choices and ad history are not written to the race database. Race passes and the latest ad error details are stored locally. Users may copy error details for support; these records are not automatically uploaded.
Settings → Ads and privacy provides age and available consent choices. Android ad ID controls also apply. We do not request location permission; the provider may infer approximate location from IP.
4. Mixed ages and children
Before ad requests, users select under 13, 13–17 or 18+. We do not request a birth date or upload age bands to Firebase. Child-directed and under-age-of-consent flags apply; requests for under-18s are non-personalized. Maximum ad content rating is G. Extra result interstitials are disabled for under-13s. Store and ad-account audience settings must also match this behavior.
5. QR and permissions
Camera permission is requested only for QR scanning. Frames and selected QR images are decoded on-device and not uploaded. Users may paste codes or select images instead. Microphone and address-book permissions are not requested. Internet/network access is for races, ads and Google Play update checks; vibration is for feedback.
6. Deletion and controls
Settings → Ads and privacy → Manage my data deletes the anonymous online identity, public world profile, name reservations, all three world mode records, online race record, on-device friend list, player name, race history and unused race pass. Leave any active room/race first. Identity deletion needs internet; failures preserve local social records so users can retry. Using online features again creates a new identity. Old cards stored on other people's phones cannot be removed remotely.
Offline boards, best scores and themes are kept by this social-data deletion. To erase all local records, use Android → Apps → Block Master → Storage → Clear data. Uninstalling alone does not automatically delete the Firebase anonymous account.
If you cannot access the app, request deletion using the page below or our support email. Include the UID from an old friend card if available. A UID alone is not ownership proof; requests are verified to avoid deleting another person's data. Do not send passwords, verification codes or access keys. Because accounts are anonymous, a name alone may not identify an account. Google ad records and security/service logs follow provider retention and legal obligations.
https://block-master-1d807.web.app/delete-data/
In-app updates are managed by Google Play. A quiet availability check may run on the main menu; downloads and installation require player consent. This feature does not upload boards, moves, friend lists or a new player profile. Availability depends on the Play account and release track.
Authored daily puzzles and their calendar are downloaded as small static files from Firebase Hosting and cached on the phone. Puzzle boards are shared game content; player moves, attempts, daily streaks and stars stay on the device. Players aged 13+ who separately opt into the puzzle league publish their UID-linked best completed daily score, normalized daily contribution, monthly total and update time through Firebase, associated with their existing public username. Daily records and monthly contributions are validated together; comprehensive server-side move verification is not provided. Only the current and previous UTC months of rankings are retained; older records are removed during the next content publication. Social/online data deletion includes these public puzzle rankings. Local puzzle progress can be removed by clearing Android app data. Previously downloaded puzzles remain playable offline when content or rankings cannot be downloaded.
The Report a problem form prepares lag and freeze details only on this device. Technical details (app version, device model, Android version, selected appearance, and Canvas draw times from the last 60 seconds) are added only if the player selects that option. The game does not automatically upload reports. The player can review and send an email draft or copy the text. If sent, the email is handled by the email providers involved.
7. Security and providers
Production traffic uses HTTPS/TLS. Firebase rules restrict access to rooms and scores. Absolute security is not guaranteed. World scores are reported by the phone; there is no comprehensive server-side move verification or real-money reward.
Google: https://policies.google.com/privacy
Firebase: https://firebase.google.com/support/privacy
Ads: https://developers.google.com/admob/android/privacy/play-data-disclosure
8. Contact
Forintx Games — nmburak25@gmail.com
Changes will be reflected on this website and in the bundled policy.