Privacy Policy
1. Scope
This Privacy Policy explains how the developer identified above handles information in the Bus Hop Party mobile application (the “App”). It applies to the App and any related services that the developer operates. It does not replace the privacy notices of Google Play, the device manufacturer, or any third-party service provider.
2. Information stored on your device
The App can store gameplay progress and preferences locally on your device. Depending on the features you use, this may include the selected level group, level progress, sound and vibration preferences, in-game inventory and currency, and locally maintained reward or cooldown state. The current implementation uses Android application storage through Unity PlayerPrefs for these values.
This locally stored information is used to provide and preserve game features. It is not an online account, and the current App does not require you to register or provide your name, postal address, phone number, or email address to play. Local data is generally removed when the App is uninstalled or its application data is cleared, subject to Android, device-backup, and operating-system behavior.
3. Network access and third-party components
The core game is designed to be playable without an online account. However, the Android package requests network-related permissions, including Internet and network-state access, and the inspected release package contains Google/Firebase-related component files and requests the Google advertising ID permission. The presence of a permission or component in the package does not, by itself, establish that information is collected or transmitted during use.
Before publication, the developer must verify whether any included Unity, Google, Firebase, Google Play, device-manufacturer, advertising, analytics, crash-reporting, messaging, attribution, or other SDK is initialized or makes network requests in the shipped build. If any such service accesses, collects, receives, or shares information, this Policy and the App Store data declarations must identify the relevant information, purposes, recipients, retention, and user choices accurately. Add each active provider and its privacy notice below:
- [PROVIDER NAME — DATA/SDK FUNCTION — PRIVACY NOTICE URL]
If no such service is active in the published build, remove the provider entry above and state that only after verifying the exact release artifact.
4. Advertising, analytics, and purchases
The current game code includes rewarded-ad interface points, but its ad service is an unimplemented stub. The current project documentation also describes advertising, analytics, remote configuration, and in-app purchase integrations as not implemented. This describes the project state reviewed for this draft; it is not a guarantee about a later build, a store-provided service, or another component included in a release.
If advertising, analytics, attribution, crash reporting, remote configuration, or purchases are enabled in a future version, this Policy must be updated before release to explain what data those services process and why. The Google Play Data safety form must also be reviewed against the behavior of the App and all SDKs in the shipped version.
5. Permissions
Android permissions are requested to support functions included in the App or its packaged components. The inspected release manifest includes network and network-state access, vibration, notifications, wake lock, advertising ID, and other platform or library permissions. Some permissions may be declared by a bundled library and may not correspond to a user-visible feature currently active in the App. Permission declarations alone do not prove that the related data is accessed or transmitted.
Review the final merged manifest and each active SDK before publication. Explain any runtime permission prompt at the point it is shown, and remove permissions that are not needed where practicable.
6. How information is used and shared
Locally stored gameplay information is used to operate the game and remember your progress and settings. The developer does not sell locally stored gameplay information. The developer does not intentionally share that local information with third parties through the game code reviewed for this draft.
If a third-party SDK or service is active, it may process information under its own role and privacy notice. The developer must disclose such processing here and in the applicable store disclosures before enabling that service.
7. Retention and deletion
Gameplay and preference data stored only on your device remains there until it is deleted by the App, the operating system, or you clear the App's storage or uninstall it. The current App does not provide an online account, so it does not currently offer account deletion. If a future version creates accounts or stores information on a server, this section must be revised to explain how to request deletion and what information is retained or deleted.
Any information handled by an active third-party provider is retained according to the verified configuration and the provider's applicable terms and privacy notice. [CONFIRM WHETHER ANY PROVIDER RETAINS DATA AND INSERT APPLICABLE RETENTION DETAILS.]
8. Children's privacy
[BEFORE PUBLICATION, STATE WHETHER THE APP IS DIRECTED TO CHILDREN, INTENDED FOR A GENERAL AUDIENCE, OR AGE-RESTRICTED. Describe any age screening, parental consent, child-specific data handling, and advertising restrictions that apply. Do not leave this section unresolved.]
The developer must not enable an SDK or feature that collects personal information from children unless the required notice, consent, and other safeguards have been implemented for the relevant markets.
9. Security
The developer uses reasonable measures appropriate to the information and the App's design. No method of storage or transmission is completely secure. Because the current gameplay data described above is stored locally, users should protect access to their device and use its available security controls.
10. Your choices and regional rights
You can clear the App's local data or uninstall the App using Android settings. You may also control relevant Android permissions and advertising settings through your device settings, where available. These controls may affect functionality and may not apply to all information handled by a third-party provider.
Depending on where you live, you may have additional rights regarding personal information. To make a privacy request or ask a question, contact the developer using the address in the heading. [INSERT ANY REQUIRED REGION-SPECIFIC RIGHTS, REPRESENTATIVE, OR COMPLAINT-ROUTE DETAILS AFTER LEGAL REVIEW.]
11. Changes to this Policy
The developer may update this Policy when the App's features, providers, or legal requirements change. The current version and effective date will be published at [INSERT THE PUBLIC, STABLE PRIVACY POLICY URL]. For material changes, the developer will provide additional notice where required.
12. Contact
For questions or requests about this Policy, contact:
[DEVELOPER'S LEGAL NAME]Email: [MONITORED PRIVACY CONTACT EMAIL]
[POSTAL ADDRESS, IF REQUIRED]
Publisher completion checklist — remove before publication
- Replace every bracketed placeholder and decide the children's audience statement.
- Confirm whether Firebase-related files, advertising ID permission, notification/FCM components, and any manufacturer services in the exact release APK are operational. Inspect SDK initialization and network behavior rather than relying only on filenames or permissions.
- Reconcile this Policy with Google Play's Data safety form and the Play listing. Include an accessible policy link in the app and Play Console.
- Verify the final version with qualified counsel for every intended distribution region.