Privacy Policy

Pahadi Bus Simulator · Last updated: 16 October 2026

1. Information we collect

We do not collect any personal information ourselves. The game has no account system, no sign-in, and no server of our own. We never ask for your name, email address, phone number or any other personal detail, and nothing you do in the game is sent to us.

Two Google SDKs inside the app do collect data, and under Google Play’s rules that counts as the app collecting it. They are listed in full in section 4.

• Game progress — your in-game money, unlocked buses, settings and completed routes are saved on your own device. We never receive it and cannot see it. Android’s own backup service may copy it to your Google account so that it can be restored if you reinstall; that is Android’s backup rather than ours, and you can switch it off in your phone’s backup settings.
• No location, contacts, photos, SMS, microphone or camera access is requested or used by the game. It does ask to read audio files already on your phone, and only for the reason in section 2.

2. Your music files

The game can play your own music while you drive. To do that it has to read audio files that are already on your phone, so Android asks you for permission the first time you start a drive.

• It looks for audio files in your Music and Download folders and in its own folder, including sub-folders, because music is usually kept in album folders. If you point it at another folder yourself, with the FOLDER button in the music panel, that folder and its sub-folders are searched first as well. It stops after the first 300 tracks it finds.
• It reads them in order to play them. It does not copy them, move them, change them, or send them anywhere. Nothing leaves your phone.
• If you refuse the permission the rest of the game works exactly as before — only the music player will find no tracks.
• You can withdraw it at any time in Settings → Apps → Pahadi Bus Simulator → Permissions.

3. Permissions the app requests

Five permissions are asked for by the game itself:

• READ_MEDIA_AUDIO (Android 13 and newer) — only to find and play your own music, as described in section 2. Android asks you for it when you start a drive, and never before that — the menu, the route list and the settings all work without it.
• READ_EXTERNAL_STORAGE (Android 12 and older) — declared for the same purpose, but this build never actually asks for it. On Android 12 and older no permission dialog appears and the music player finds only the tracks in the game’s own folder.
• INTERNET and ACCESS_NETWORK_STATE — used by the two Google SDKs in section 4, and by nothing else. The game itself has no server to talk to, so every route, every bus and all of your progress works with the connection switched off; you simply see no ads.
• com.google.android.gms.permission.AD_ID — the advertising identifier, used to serve and cap the ads. Android lets you reset or delete it at any time; see section 4.

Eight further permissions are declared by the Google and Android libraries built into the app. None of them ever asks you for anything — Android grants them at install, and they are listed here only so that the list you see on Google Play is fully explained. WAKE_LOCK and com.google.android.finsky.permission.BIND_GET_INSTALL_REFERRER_SERVICE come from Google Analytics for Firebase. ACCESS_ADSERVICES_AD_ID, ACCESS_ADSERVICES_ATTRIBUTION and ACCESS_ADSERVICES_TOPICS come from Google Mobile Ads and Google Analytics for Firebase; they are the Android Privacy Sandbox equivalents of the advertising ID. FOREGROUND_SERVICE and FOREGROUND_SERVICE_DATA_SYNC come from Google Play Asset Delivery, which installs the game’s own data pack on first run. DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION is a signature-level permission AndroidX defines for the app’s own internal messages, and no other app can hold it.

Beyond those thirteen, the app requests no other permission — no location, no contacts, no photos, no SMS, no microphone and no camera. There is no crash reporting.

4. Advertising and analytics

The game is free and is paid for by advertising. Two Google SDKs are built into it, and both of them send data to Google. Neither of them sends anything to us.

Google AdMob — the ads

• Where you see them: a banner on the menu screens, and an optional video you can choose to watch on the results card for an in-game reward. No advertising is shown while you are driving — the banner is removed before a route starts and does not come back until you return to the menu.
• What AdMob handles: your advertising ID, the approximate location Google derives from your IP address, and the fact that an ad was shown, tapped or watched to the end. This is used to choose and cap the ads and to detect fraud.
• Watching the rewarded video is always your choice. Refusing it costs you only the in-game reward.

Google Analytics for Firebase — the player count

• Why it is there: so we can see how many people installed the game and how many are still playing it. That is the whole purpose.
• What it handles: an app instance ID (a random number for this installation — a different identifier from your advertising ID, and not linked to you by name), your advertising ID, the fact that the app was opened and for how long, and the device model, Android version, language and country that Google collects automatically. The advertising ID is the same one AdMob uses, and the controls under “Your choices” below apply to it here too.
• What it does not handle: nothing you do inside the game is reported. The app sends no events of its own — not the routes you drive, not your money, not your settings, not your music.

Your choices

• In the EEA and the UK, the first time you open the game it asks for your consent before any ad is requested, using Google’s own consent form. If you refuse, the game requests no ads at all for the rest of that session — you simply see no banner and no reward video.
• Anywhere, you can reset or delete your advertising ID, and switch off ad personalisation entirely, in Settings → Google → Ads (the exact path varies by phone). The game respects that setting; it cannot override it.
• Both SDKs need a connection to reach Google. With the connection off no ad is served and nothing leaves your phone at the time — but the analytics SDK still records that the app was opened and for how long, keeps that on the phone, and uploads it the next time you are online. The game itself is identical either way.

5. How long anything is kept

We keep nothing, because we receive nothing — there is no server of ours for your data to sit on. What the two Google SDKs in section 4 send goes to Google and is kept under Google’s retention rules, not ours. Your saved game stays on your phone for as long as the app is installed, and uninstalling it removes the files the game created on your device. We keep no backup of it. Android’s own backup service may hold a copy in your Google account and put your progress back when you reinstall; you can turn that off in your phone’s backup settings.

6. Sharing

We do not sell your personal information, and we receive none of it to sell. The sharing that does happen is with Google, through the two SDKs in section 4, under Google’s own privacy policy. There is no other third party, and no data broker.

7. Children

The game is intended for a general audience and is not directed at children under 13. We do not knowingly collect personal information from children under 13. If you believe a child has provided information through the app, contact us and we will act on it.

8. Deleting your data

There is no account to delete, because none is ever created. To remove the game’s data from your device, uninstall the app — that erases the files it created. If Android’s backup service is switched on for your phone it may also hold a copy of your saved game in your Google account; clear that from your phone’s backup settings if you want it gone. Music in your own Music and Download folders is never copied or altered by the game and is left exactly as it was.

9. Purchases

The game contains no in-app purchases. In-game money has no real-world cash value and cannot be bought, sold or withdrawn. If purchases are ever added, this policy will be updated first and payments would be handled by Google Play — we would never receive or store your card details.

10. Security

Because no personal data is transmitted to or stored by us, there is no personal data of yours for us to lose. Data on your device is protected by Android’s own app sandbox.

11. Changes to this policy

If the app changes in a way that affects this policy — for example if an online feature is added — we will update this page and change the date at the top.

12. Contact

Questions about this policy: support@seeproyale.com