Privacy Policy
Developer: Ginger Ninja Developments
Effective date: 27 September 2026
Ginger Ninja Developments provides Echo Dodge and its friends leaderboard. This policy explains how we handle information when you use the game and this privacy policy website.
1. Information saved on your device
Echo Dodge saves your best scores, sound and accessibility preferences, tutorial progress, earned coins, and cosmetic selections on your device. It also saves your leaderboard nickname, board code, a randomly generated player identifier, and any pending score submission. A score checkpoint is saved before a revive offer so an interrupted run can be submitted later. These local files let the game remember your progress and retry an unconfirmed leaderboard submission.
Local progress, preferences, and cosmetic purchases are not uploaded by the game. A leaderboard score and the associated information described below are sent when you use online leaderboard features.
2. Information used by the online leaderboard
When you join or refresh a board, start a ranked run, or submit a score, the game sends the information needed for that action:
- Your chosen nickname and board code: to register your player and select your friends leaderboard. Use a nickname rather than your real name or contact details.
- A random player identifier: generated by the game to associate your submissions with your leaderboard entry. It is not your advertising ID, hardware serial number, or Google account identifier. The server hashes this identifier before using it in leaderboard storage.
- Ranked-run information: scores, game ruleset, and a server-issued run identifier. The server records run start time and submission results to check scores and prevent duplicate submissions.
- Network information: the server receives your IP address when you connect. The leaderboard application uses a hashed version for short-lived request limits to help prevent abuse. Our hosting provider also processes network and request information to deliver and protect the service.
Leaderboard data is used to provide rankings, remember best scores, validate ranked runs, retry submissions safely, and protect the service. The game does not require an email address, password, or Google account sign-in.
3. Visibility and service providers
Your leaderboard nickname and score may appear in the top entries shown to anyone using the same board code. A board code is not a private account or a guarantee of confidentiality: another person can share or guess it. Your player identifier and IP address are not included in the leaderboard entries returned to other players.
We use Vercel to host the leaderboard API and this website, and Upstash to store leaderboard data. These providers process information needed to operate, store, secure, and deliver the service. Their infrastructure may process information outside your country.
We do not sell leaderboard records. In ad-enabled builds, Google processes advertising data as described below; personalized ads depend on applicable consent choices and settings. We may disclose information when required by applicable law or to address abuse and protect the service. If you contact us by email, we use your address and message to respond and handle your request.
Optional rewarded ads and consent
In ad-enabled builds, friends games can offer one optional rewarded ad to revive after a collision. Watching an ad is not required to play or submit your score. The run remains frozen while the ad is open. A revive is granted only when Google's SDK reports that the reward was earned. Offline games do not offer ad revives.
The game uses the Google Mobile Ads SDK and Google's User Messaging Platform (UMP). When you open the friends leaderboard, the game requests a consent-status update and displays a consent form where required and configured. Ad initialization and requests are gated by UMP's permission to request ads. Merely choosing not to watch an ad does not undo data processing from an ad request made to prepare the optional offer.
Google's SDK can collect and share IP addresses (including approximate location inferred from them), device and account identifiers such as the advertising ID and app set ID, interactions such as taps and video views, and diagnostic information. Google uses this information for advertising, measurement, analytics, and fraud prevention. Google states that this SDK data is encrypted in transit. Collection depends on consent, device settings, and the ad service's configuration. The game does not pass your leaderboard nickname, board code, or run token to the ad SDK.
Where UMP requires a privacy-options entry point, an Ad privacy options button is available in the game menu after consent status is checked. Use it to review or change your choices. Android's privacy settings also let you reset or delete your advertising ID. Some ad requests may use limited or non-personalized ads; these can still involve data processing.
Google applies its own retention and deletion practices to SDK data. See Google's Privacy Policy, How Google uses information from apps that use its services, and Google Mobile Ads SDK data disclosures.
4. Retention and deletion
- Local saves: remain until you clear the game's app data or remove it from your device, subject to any device backup or restore features you use.
- Leaderboard nicknames and best scores: have no automatic expiration. They remain until removed by the developer, including in response to a verified deletion request.
- Active ranked-run records: expire after 24 hours if not consumed earlier. Submission receipt records expire after 24 hours.
- Application rate-limit counters: expire after 60 seconds. This includes the counters associated with hashed IP addresses and player identifiers.
- Provider operational records: hosting logs and any provider backups have separate retention rules under the providers' services; the short application expiration periods above do not describe those records.
- Privacy correspondence: is kept as needed to respond, carry out and document your request, and meet applicable legal obligations.
To request access, correction, or deletion of your leaderboard information, email gingerninjadevelopments@gmail.com with the subject Echo Dodge privacy request. Include your board code and nickname, and describe your request. We may need additional information to locate your entry and verify that it belongs to you. Do not send passwords or unrelated sensitive information.
There is no automated in-game deletion control. Clearing app data or uninstalling the game does not delete records already held by the online leaderboard. Contact us before clearing your local data if you need help identifying an entry. We handle requests in accordance with applicable law and explain any information that must be retained for a legal obligation.
5. Security and your choices
The game connects to its production leaderboard over HTTPS, and the backend connects to storage over HTTPS. Storage credentials are kept on the server rather than in the game. The backend validates requests, hashes player and run identifiers for storage, and applies request limits. No online service can guarantee absolute security.
You can play without using the friends leaderboard. Avoid joining a board or starting ranked runs if you do not want new leaderboard data sent. Previously pending submissions may be retried when you use leaderboard features.
Echo Dodge does not request access to your contacts, camera, microphone, or precise location. This policy page does not include analytics scripts, advertising, or application-set tracking cookies. Its host still processes normal web requests.
6. Children and personal information
Players should not put real names, contact details, or other sensitive information in leaderboard nicknames or board codes. A parent or guardian who believes a child has submitted personal information can contact us at the address below to request its removal.
7. Changes to this policy
We may update this policy when the game or its data practices change. The current policy will remain available at this URL with an updated effective date. Where required, we will provide additional notice or request consent before a new use of personal information.