MOONROOT · SEEDLIGHT PRIVACY POLICY

A clear guide to your game data

Privacy
Policy

This page explains what Moonroot: Seedlight stores on your device and what its advertising and store services may process.

Effective date

THE SHORT VERSION

Your progress stays on your device.

The game stores progress, settings, and the age range you choose in local app storage. If advertising is available, Google’s Mobile Ads and consent services may process device and ad-use information. The game does not ask for an exact birth date or require an account.

01 · ABOUT THIS POLICY

Who publishes the game

Moonroot: Seedlight (the “Game”) is published by [PUBLISHER LEGAL NAME — replace before publishing] (“we,” “us,” or “our”). This policy applies to the Game’s Android app and its in-game services.

This policy explains how the Game handles information when you play and when you use its advertising or store services.

02 · INFORMATION

Data the Game uses

Saved game data

Progress and preferences such as Dew, level completion, checkpoints, collected items, music and sound levels, vibration, and screen-shake settings. This information is saved in the app’s local storage to keep your game state between sessions.

Age range choice

The Game asks you to select an age range: 12 or younger, 13–20, 21 or older, or “Prefer not to say.” The selected group and a rule-version value are saved locally. The current screen does not ask for or save your exact date of birth.

Advertising and device data

When Google Mobile Ads is used, its SDK may automatically collect and share an IP address, app and ad interactions, diagnostics and performance information, and device or account identifiers. An IP address may be used to estimate general location. Google describes these data practices in its Google Mobile Ads data disclosure.

Consent choices

Google’s User Messaging Platform (UMP) may process consent status and privacy choices so the Game can determine whether an ad request is allowed and show a required privacy message. See Google’s UMP information.

03 · ADVERTISING

Advertising and consent

The current implementation can request a banner ad on the main menu after an age group is selected, consent checks are complete, and the Game determines the player is eligible. The “Prefer not to say” choice does not enable ads. Child and teen age treatments and a general-audience content rating are sent in ad request configuration.

Whether an ad is personalized depends on the consent choices, applicable settings, and Google’s services. Google may process information for advertising, measurement, analytics, and fraud prevention. Google’s processing is also governed by its own Privacy Policy.

The Game checks consent through UMP and requests ads only when the SDK reports that ads can be requested. If consent or SDK setup fails, the Game suppresses the ad request. The available privacy-options control appears in the Game’s Settings when the consent service says it is required.

04 · PURCHASES

Store purchases

If an in-app purchase is offered, Google Play handles payment and provides the Game with purchase and product information needed to process the transaction. The Game does not receive your full payment-card number. Google Play and Unity IAP may process transaction, receipt, product, and purchase-status information under their own terms and privacy policies.

The current code includes a store-purchase integration, but product availability and purchase flows depend on the active store configuration. See Google’s Privacy Policy for Google services.

05 · SERVICE PROVIDERS

Who receives data

  • Google Mobile Ads and UMP: may receive the ad, device, diagnostic, interaction, and consent information described above to provide advertising and privacy-message services.
  • Google Play: processes app distribution and any in-app purchase transactions made through Google Play.
  • Android backup: if enabled in your device or Google account settings, Android may back up app data and restore it to a device. Android’s default app-backup behavior is described in its Auto Backup documentation.

We do not operate an account system or a game server for player progress in the current version. We do not receive the local save data through the Game’s own code.

06 · STORAGE

Storage and deletion

Game progress, settings, and the selected age group remain in app storage until they are overwritten or removed. You can remove local data through Android’s app-storage settings or uninstall the Game. If Android backup is enabled, backed-up app data may be restored according to your device settings.

Google’s ad and consent services control retention for data they collect. Refer to Google’s privacy information and account controls for details about those records. The publisher does not have a server-side player account from which to delete a profile.

07 · AGE GROUPS

Children and age groups

The Game offers age-group choices and does not request a precise birth date in the current screen. If “12 or younger” or “13–20” is selected, the ad SDK receives the corresponding child or teen treatment. Ad requests use a general-audience content rating. A missing or declined age choice does not enable ads.

These age bands are the Game’s current technical settings; they are not a statement that one age threshold satisfies every country’s law or store policy. The publisher must review the target-audience and family-policy settings for each intended market and keep the Play Console declarations consistent with this policy.

08 · YOUR CHOICES

Your privacy choices

  • Choose an age range on the Game’s first screen, or choose “Prefer not to say” to keep ads off.
  • When the Game shows a Privacy Options control in Settings, use it to reopen Google’s consent choices.
  • Use Android settings to reset or remove the Game’s local data and to manage device advertising or backup settings.
  • For questions about data handled by Google, use the privacy and account controls linked in Google’s policies.

09 · SAFEGUARDS

Security and policy changes

Local game data is stored in Android app storage. The Game does not add its own encryption layer to that save data. Google states that Google Mobile Ads SDK data is encrypted in transit using TLS; third-party services apply their own security controls.

We may update this policy when the Game or its services change. The effective date at the top of this page identifies the latest version. If a change materially affects the Game’s data practices, we will update this page and provide any notice required by applicable law.

10 · GET IN TOUCH

Contact

For privacy questions or requests, contact the publisher:

[PUBLISHER LEGAL NAME — replace before publishing]
Email: [PRIVACY CONTACT EMAIL — replace before publishing]
Postal address: [Add a postal address if required for your markets]