01. Who is responsible
Batz develops GalaxyBreaker and operates the leaderboard API. You can contact us about privacy at Batzlabstudio@gmail.com.
The game is a paid download, does not show ads and does not require an account or sign-in.
02. What data we process and why
- Leaderboard name: your chosen alias is saved on your device. It is sent when you view the leaderboard and when you submit a result to identify your participation.
- Results and gameplay statistics: when you submit a result, the API receives your score, level, duration, counts of collected items, game version and the relevant game mode. These are used to record, rank and validate results.
- Run validation: when a run starts, the game requests a run identifier and token from the API. It sends them with the result to validate the run and prevent invalid submissions. This does not create a user account.
- Technical connection data: when you visit this website or connect to the API, the infrastructure may process IP addresses, timestamps, request information and technical logs needed to provide, maintain and secure the service.
- Email inquiries: if you contact us, we receive your email address and message to respond and handle your request.
This page does not embed forms, analytics tools or advertising scripts.
03. What other players can see
The leaderboard is public. Its information includes your alias, position, score, level, run duration and date. Do not use your real name or personal information as an alias.
Submitting a result is optional: you can skip it on the name entry screen. Skipping submission does not prevent the technical connections the game makes when starting a run or viewing the leaderboard.
You do not need an account to play. An alias identifies a leaderboard entry and should not be treated as a unique or verified identity.
04. Cloudflare and Google Play
Cloudflare: we use its infrastructure to host this website and our leaderboard API. Cloudflare is involved in processing data sent to the service and technical connection data. See Cloudflare's privacy policy for more information.
Google Play: the game is purchased and downloaded through Google Play. The game does not request or store payment card numbers. Google handles purchase information under its privacy policy.
Published names and results are shared with people viewing the leaderboard. The providers above participate in delivering their respective services.
05. How long we keep data
Leaderboard data: We keep entries while the leaderboard service remains operational or until you request deletion of your entry. You can request deletion by email as described in the contact section.
Technical logs and inquiries: Technical logs and validation data are kept for as long as necessary to operate the service, validate runs and investigate incidents or abuse, according to the API and service provider configuration. Emails are kept for as long as necessary to address the inquiry and follow up on related incidents or obligations.
The locally saved alias remains until you change it or clear the game's local data. Clearing local data or uninstalling the game does not automatically delete results already sent to the server.
06. How we protect data
The production API address uses HTTPS to protect data in transit. The game uses run identifiers and tokens as part of result validation.
No system can guarantee absolute security.
07. Inquiries and deletion
If you want your leaderboard entry deleted, you can request it using the contact email below. Once we locate the entry and verify the request, we will delete the relevant data from the leaderboard. You can also ask about your data or request a correction. To help locate a leaderboard entry, include its alias, score and approximate run date. Do not send passwords, run tokens or banking details.
Because there are no accounts and aliases may be shared by different people, we may need additional information about the run to avoid modifying someone else's data.
08. Changes to this policy
We will update this page when game features or data handling practices change. The revision date is shown at the beginning of this policy.