AmaSnakes - Privacy Policy

A local multiplayer snake game for 1–4 players with phone controllers and a global leaderboard.

Thank you for using AmaSnakes ("App"), an application created by Michal Bukáček for Android devices. This Privacy Policy explains how information is handled when you use the App.

Last updated: 24 October 2026

Who Is Responsible for Your Data?

AmaSnakes is provided by Michal Bukáček. For privacy questions or requests about your information, contact michal@bukacek.cz.

Local Multiplayer and Phone Controllers

AmaSnakes is a snake game for 1–4 players. Players connect their phones to the same local network as the device running the game and open a browser-based controller using the on-screen QR code. Player nicknames, control inputs and game state are exchanged to provide the multiplayer session. Network addresses are used to establish these connections. Use a nickname rather than your real name, and do not enter contact details or other sensitive information as your player name.

Global Statistics and Leaderboard

When results are submitted to the global leaderboard, the server processes the following information:

• The player nickname.
• The score achieved.
• A device-related identifier submitted as a 64-character hash, associated with the app’s Android ID-based identification.
• The time when the result is accepted or replaced by a higher score.
• Basic information about the device running the game: its category (phone, tablet, TV or automotive), device name derived from manufacturer and model, manufacturer and model, and flags identifying the device category.

The leaderboard endpoint stores this hash, rather than a raw Android ID, in the score records. The identifier and nickname are used together to distinguish results and update a player’s higher score. A hash is a pseudonymous identifier; it is not a guarantee of anonymity. These records support global game statistics and ranking.

Player nicknames and scores are displayed to other users in the global leaderboard. The leaderboard response does not disclose the stored hash or timestamp. A device hash and the basic device information listed above may also be sent when reading the leaderboard. The hash lets the service mark that device’s own results; this read request does not renew their timestamps. Do not use a nickname that reveals information you do not want other players to see.

24-Hour Validity and Automatic Removal

Each accepted leaderboard record, including its device-related hash, has a validity period of 24 hours from its stored timestamp. Once that period expires, the record is excluded from subsequent leaderboard processing and is automatically removed from the stored score file on the next successful leaderboard read or score submission. If nobody reads the leaderboard or submits a score, an expired record can remain in the underlying file until the next cleanup; physical deletion is not scheduled for the exact expiry time.

If a higher score replaces an existing result, a new timestamp is stored and a new 24-hour period begins for that result. Submitting an equal or lower score does not extend the existing record’s validity. Records may disappear sooner if displaced from the leaderboard, which retains up to 50 results. The same device hash can occur in several player records and can be submitted again in later games.

This 24-hour rule applies to the game’s leaderboard records. It does not describe the retention of data independently processed by Google Analytics, AdMob, website analytics, hosting logs or privacy-related email correspondence.

Analytics and Advertising

AmaSnakes uses Google Analytics for Firebase to understand app usage and Google AdMob to display advertising. Depending on SDK configuration, privacy choices and device settings, these services may process app interactions, app-instance or device identifiers, advertising identifiers, technical device information, diagnostic data and IP addresses. IP addresses may be used to estimate a general location. These services have their own processing and retention arrangements; their data is not automatically deleted by the leaderboard’s 24-hour cleanup.

The website displaying this policy also uses Google Analytics to measure visits and page usage. Website analytics may use cookies or similar identifiers and technical browser information. Website analytics is separate from the game’s leaderboard.

• Google Privacy Policy
• Privacy and Security in Firebase
• Google Mobile Ads SDK data disclosures

Service Providers and Technical Records

The hosting provider processes network requests needed to operate the leaderboard and website. Technical server logs may include IP addresses, request times, requested URLs and error information. Such logs are separate from the leaderboard score records. The app sends basic device information with score submissions and leaderboard read requests; the storage and retention of that additional information depend on the leaderboard service configuration. Google and hosting services may process information outside your country under their applicable data-protection arrangements.

The leaderboard interface returns player names and scores without exposing stored device hashes. No internet service can guarantee absolute security.

Your Choices and Privacy Requests

You can stop further gameplay submissions by stopping use of the app. Uninstalling the app does not itself delete records already sent to the server; the leaderboard expiry rules continue to apply. Advertising controls available in Android or your Google account do not necessarily disable all analytics or technical processing.

Contact michal@bukacek.cz to request information about your data, correction or deletion, or to raise an objection or request a restriction on processing. Depending on applicable law, you may also have rights of access and data portability, and the right to complain to a data-protection authority. If processing is based on consent, you may withdraw that consent without affecting processing that took place before withdrawal.

To help locate a leaderboard entry, provide your player nickname, approximate submission time and score. Please do not email a raw Android ID or identity document. Additional proportionate verification may be needed to avoid modifying another player’s record. Email requests and replies are handled separately from the leaderboard and are not covered by its 24-hour validity period.

Children and Player Names

Player names may be visible to other players. Parents and guardians should help children choose nicknames that do not disclose their real name, age, school, address or contact details. If you believe a child has submitted personal information through a nickname, contact the developer so the record can be investigated and removed as appropriate.

Changes to this Privacy Policy

This Privacy Policy may be updated from time to time. Any changes will be published on this page. You are encouraged to review this page periodically to stay informed about how privacy is handled.

Contact

If you have any questions about this Privacy Policy or the App, please contact the author by email:
michal@bukacek.cz