Gedi Run privacy policy

Updated 4 October 2026. This policy explains how Gedi Run handles local game progress, optional online scores, result sharing and support requests.

Contact and scope

Gedi Run / गेड़ी दउड़ support and privacy contact: support@technicaldost.com. This policy covers local game progress, the optional public leaderboard and these help pages.

Local progress

The game saves progress and local scores on your device. If you join the public leaderboard, it also saves a random private credential and your generated Mitaan nickname on that device.

Optional public leaderboard

Before joining, the game asks you to confirm that your nickname and score will be public. The public board shows your generated nickname, best score and distance. It does not ask for a player email, real name or advertising identifier.

Joining creates a profile with a random identifier, credential hash, nickname and creation time. Completed online runs send a run ticket, score, distance, coins, clean hops, coin points, hop points and elapsed seconds for score validation. The service stores your best score, distance, coin count and achievement time, as well as temporary run-ticket records.

Sharing a run result

The results-screen share action sends only the game title, score and whole-metre distance to your device's sharing interface when you choose it. On desktop it copies that text to the clipboard. It does not include your leaderboard credential, nickname or save file. If you choose another app to send or post the text, that app processes it under its own rules. Opening or returning from a share chooser does not prove that a post was made.

Hosting and security

Cloudflare Workers and D1 process requests and store leaderboard records. The hosting service receives ordinary network request information, including your IP address. Registration uses a hash of that address for rate limiting. Viewing the public board or these pages also sends network requests, even without joining. Configuration enables sampled service logs and traces. Cloudflare documents three-day retention for Workers Free logs, seven-day retention for traces in its current trace documentation, and a seven-day D1 Time Travel restoration window on Free. D1 Time Travel is always enabled. Profile deletion changes the active database; historical backup data can remain within that restoration window. A fixed retention period for support correspondence has not been established. You can contact us about deletion of your support messages.

The leaderboard uses HTTPS, private credentials, short-lived run tickets and score-validation checks to provide the board and help prevent abuse. These measures do not guarantee anonymity or cheat-proof scores. These help pages add no cookies or analytics scripts. The deletion form sends a deletion-only code and your explicit confirmation to this service.

Retention and deletion

Profile and best-score records have no automatic expiry. You can delete them through the in-game public leaderboard or with a deletion-only code in the external deletion form. Codes expire after 15 minutes, are single use, and issuing a new one invalidates the previous one. The game copies a requested deletion-only code to your device clipboard; keep it private. Only a hash is stored on the server; expired codes are cleaned on a subsequent issuance or redemption request. Deletion removes your profile, scores, run tickets and deletion codes from the active leaderboard database. In-game deletion clears the online credential locally; external deletion revokes it on the server, and the game clears it when a later authenticated request reports that the profile no longer exists. Local progress remains.

Run tickets expire after 30 minutes. Rate-limit records have an expiry at the end of the following hourly window. Expired entries are removed on a later run-start request, so expiry is not a guaranteed deletion deadline. Profile deletion does not itself erase rate-limit records or provider logs/backups. See Cloudflare log retention, trace retention and D1 Time Travel for the documented Free-plan windows. We will update this policy when the described processing changes.

For deletion instructions or a request outside the app, see profile deletion help. If you email support, your message and reply address are used to handle your request. Do not email private credentials. Contact us about access, correction or deletion questions; ownership must be verified before a profile is removed.