Privacy Policy
Last updated 8 November 2026
Bengaluru Bolt is designed to collect as little as possible. Here is everything it stores and why.
On your device
Your progress (kaapi, Metro Tokens, runners, upgrades, music, missions, best scores and settings) is saved in your browser's local storage. It never leaves your device unless you sign in. Clearing your browser's site data deletes it.
Leaderboard
To show the city leaderboard, the game signs you in anonymously in the background. If you choose a leaderboard name, we store that name, your best score, distance and runner, linked to a random anonymous ID. Anyone can see leaderboard entries.
Google sign-in and cloud save (optional)
If you sign in with Google, we receive your Google account's name, email address and profile picture, and we store a copy of your game progress so you can continue on another device. Only you can read your saved progress. We never post anything to your Google account.
Analytics
We use Google Analytics for Firebase to understand how the game is played (for example, runs started, scores reached, items bought) and to fix problems. It may use device identifiers and collect information such as your device type, browser and approximate region. We don't use this for advertising.
What we don't do
- No ads and no in-app purchases.
- We don't sell or rent your data.
- Microphone, camera, location and contacts are never accessed.
Service providers
Online features run on Google Firebase (Authentication, Cloud Firestore, Analytics, Hosting), so Google processes this data for us under its own terms and privacy policy.
Your choices
- Play without signing in, and without setting a leaderboard name.
- Sign out at any time in Settings; your progress stays on your device.
- To have your leaderboard entry or cloud save deleted, contact us via the GitHub Issues page.
Children
The game is suitable for all ages. Children under 13 should only sign in with Google with a parent's permission.
Changes
If this policy changes, we'll update the date above. Contact: GitHub Issues page.