Rather than sort this policy by legal topic, it walks through a session of BusColorDash from beginning to end and says, at each moment, what the app is doing with information. If you want to know what happens when you tap something, find the moment and read that section.

Before You Open the App

Downloading BusColorDash is a transaction between you and the app marketplace. The marketplace knows which account downloaded the app, on what device, and in which country; we do not receive that account. What reaches us afterwards is anonymous install and update counts, which tell us how many copies exist and nothing about who holds them.

First Launch

The first thing BusColorDash does not do is ask who you are. There is no sign-up card, no email field, no linked social profile, and no way to log in. Instead the app generates a random installation reference and writes it into its own storage area. That reference is how a save file knows it belongs to this copy of the game. It is not derived from your phone number, your marketplace account, or your hardware serial, and generating a fresh one is as simple as reinstalling.

At the same launch the app reads the shape of the machine it landed on — model, chipset tier, system release, available memory, screen width, height and density, the language and region you have configured, and whether you are on cellular or wireless. Buses have to fit the lane width on a phone and on a tablet, so the layout is calculated from these readings before the first frame is drawn.

During a Round

While you are moving passengers onto buses, the app counts. It records which route you are on, how many colour groups you have cleared, how many bus slots you have opened, how long the round has been running, whether a booster was spent and which one, and whether the round ended in a win or a jam. These counters are what feed the score at the end and what feed the progress bar on the route map.

Nothing about this reaches out to your phone's other applications. BusColorDash does not read your location, your contacts, your photo library, your microphone, your camera, your calendar, or any file outside its own folder, and it never asks for the permissions that would let it.

Between Rounds, When an Advertisement Appears

If you are playing a build that shows advertisements, the space between rounds is where they appear, and a separate advertising company fills that space rather than us. To choose something to show and to count that it was shown, that company may read the advertising identifier your operating system hands out. Your system settings decide what it gets: resetting the identifier breaks the link to anything shown before, and switching off personalised advertising limits it to contextual selection. BusColorDash passes along whichever choice is recorded there and has no way to override it.

When You Finish a Route

The result is written into the save file: route cleared, best time, stars, the coins and boosters you now hold, and the settings you have toggled. That file sits in the private area the operating system reserves for BusColorDash, walled off from other apps. If you have switched on the platform's cloud save, a copy also travels to the save service run by Apple or Google, under whatever rules their settings screen describes.

When Something Breaks

A freeze or a sudden close produces a report before the app dies: the line the program stopped on, the chain of calls that got there, how much memory was in use, the hardware readings from launch, and the clock time. An engineer opens that report to reproduce the jam and fix it. Nothing in it names you, and once the bug behind it is closed the report goes with it.

When You Buy Something

Coin bundles and booster packs are optional, and the moment you tap buy, the transaction leaves BusColorDash entirely and happens inside the marketplace. Your card, your wallet, your billing address, your marketplace password — all of that is typed into their sheet, not ours, and none of it comes back to us. What comes back is a signed receipt saying that a particular product went through, which is what lets the coins land in your account and what we look at if you later ask for a refund.

When You Write to Us

Support is something you start, never something we start. Whatever you put in the message is what we get: the address it came from, your account of what went wrong, screenshots or clips if you attach them, and a receipt number if the problem is about a purchase. We read it, answer it, and clear the thread when the problem is settled.

When You Put the Phone Down

Closing BusColorDash or switching to another app ends the session. The app stops counting, writes what it has, and does nothing in the background — no silent wake-ups, no background location, no listening. Reopening it picks up the save file where it stopped.

When You Uninstall

Deleting BusColorDash removes the app's private folder, and the save file inside it goes too: routes, coins, boosters, settings, and the installation reference. That is not recoverable by us, and reinstalling produces a fresh reference and an empty save unless you had cloud save on, in which case the platform's copy is what restores. Two things do outlive the uninstall: the marketplace's own record that your account once bought something, and any support message you already sent us, until we clear it.

Who Else Handles Any of This

Four kinds of outside company touch parts of the above — an analytics service that receives round counters and launch readings, a crash service that receives failure reports, an advertising network that receives the advertising identifier and impression counts, and the marketplace that distributes the app and validates receipts. Each gets the fields its job needs, works to our instruction, and publishes privacy terms of its own. None of them buys anything from us, because we sell nothing: no player records go to data brokers, advertisers, or anyone else for their own use.

How Long Each Thing Lasts

The save file lasts as long as the install. Crash reports last until their bug is fixed. Round counters are rolled into totals — how many players clear route 40, how long the average jam lasts — from which no single install can be pulled back out. Receipts last as long as tax rules say they must. Support threads last until the question is answered.

How It Is Kept Safe

Anything that travels to us travels over an encrypted connection, and what sits on our side sits behind access controls that only the people running the game can pass. We also keep the pile small on purpose, because the shortest route to protecting something is not to hold it. That said, anything reachable over a network carries risk, and we would rather say so than promise otherwise.

Younger Players

BusColorDash is built for a general audience rather than for children under thirteen, and we do not knowingly take personal information from a child that age. If you are a parent or guardian and think your child has sent us something, write to support and it will be tracked down and removed.

Asking Us to Change or Remove Something

Where the law where you live allows it, you can ask to see the record attached to your install, ask for it to be corrected, ask for it to be deleted, or object to a particular use of it. Send the request through official support with the installation reference from the settings screen — the game knows no name for you, so that reference is the only handle we have. Anything we are legally required to keep, or that we need to stop fraud, stays behind after the rest is removed.

When This Page Changes

Adding a feature, swapping a supplier, or a change in the law can all make this page out of date, and when that happens we publish a corrected one through our official channels. The published version is the one that applies.

Reaching Us

Anything you want to ask about the moments described above goes to the BusColorDash support team through the official support channels.