1. Who we are and what this covers
Firefly Exit is a puzzle game developed by Masood Ur Rehman. Contact: masoodbarkiwork@gmail.com. Its Android package is com.nomorepaid.fireflyexit.
The game is currently in development. This policy describes the implemented game and Android advertising integration reviewed on the date above, as well as the developer and privacy websites. A public store release has not been announced on these pages.
The game has no player account or developer-operated cloud-save service. Local game storage and third-party advertising processing are described separately below.
2. Game progress and settings on your device
The game stores a local save in its app's web storage. It contains:
- Campaign and daily-puzzle completion and best star scores.
- Your selected lantern and preferences for sounds, music, touch feedback and calmer motion.
- An unfinished puzzle, including remaining trails, hearts, mistakes, hints, undo history and earned extra-hint credits.
This storage lets you resume play and keep your preferences. The daily puzzle is generated on your device using its local date. The inspected game code does not send the save to a developer server or add a separate analytics or crash-reporting service.
You can remove the local save by clearing Firefly Exit's app storage in Android settings. In a browser build, clear that game's site data; cached game files may also be stored locally for offline play. Clearing data removes progress and settings. Android backup is enabled, so platform or device backups may preserve or restore copies; manage those backups through your device or platform settings.
3. Google advertising and information it handles
Android builds integrate Google AdMob / Google Mobile Ads for optional rewarded ads that give extra hints and occasional interstitial ads between completed campaign levels. The current configuration defaults to non-personalized ad requests.
Google's official Mobile Ads disclosure describes automatic collection and sharing of the following information by its SDK:
- IP address, which may be used to estimate a device's general location.
- Product interactions, such as app launches, taps and video views.
- Diagnostic information, such as launch time, hangs and energy usage.
- Device and account identifiers, such as the Android advertising ID, app-set ID and, where applicable, identifiers related to signed-in accounts.
Google documents purposes including advertising, analytics and fraud prevention. Its SDK disclosure states that collected data is encrypted in transit using TLS. Non-personalized ads use contextual information and can still use mobile identifiers for purposes such as frequency capping and aggregated ad reporting. They do not mean that no information is collected or shared.
The inspected Android integration pins Mobile Ads 25.4.0 and Google's User Messaging Platform (UMP) 4.0.0. Google's current Mobile Ads disclosure refers to a newer SDK release; the categories above are Google's current published guidance, rather than a claim that every network request from this particular build has been independently measured.
Read Google's SDK data disclosure, its personalized and non-personalized ads explanation, Privacy Policy and information for people using apps with Google services.
4. Consent and your advertising choices
The app asks Google's UMP for updated consent information before initializing or loading ads. UMP may present a privacy or consent form when required and available. The game checks UMP's canRequestAds result before allowing ad requests. The consent-information update itself communicates with Google; this flow does not imply that no information is processed before a form appears.
UMP manages consent state and privacy choices. Relevant consent signals are stored locally by the SDK and used in privacy and advertising requests; these are separate from the game-progress save. Google describes GDPR consent signals and US state privacy signals in its regional guidance.
When UMP reports that a privacy-options entry point is required, the game's Settings screen offers Ad privacy choices. Use it to revisit the available choices. Its availability and the options displayed depend on Google's messages, your region and the SDK's consent state. The app rechecks consent and refreshes ad readiness after this form is closed. If consent, configuration or network checks fail, ads may be unavailable while the puzzle game remains playable.
You can also manage, reset or delete your Android advertising ID using the controls available on your device; paths vary by Android version. Google's advertising ID guidance describes these controls. Google's My Ad Center provides additional Google ad settings. These controls have different scopes and do not erase all information that a service may already hold.
For details on the consent service, see Google's UMP guidance. For privacy questions or requests concerning information handled by the developer, use the contact below. Requests concerning Google's processing may also need to be made to Google.
5. Intended audience and age
Firefly Exit is intended for people aged 13 and older and is not designed for children under 13. An audience label of 13+ does not establish the legal age for privacy consent in every country. The inspected game does not verify each player's age, and privacy rights and any parental or guardian consent requirements vary by location.
If you believe information has been provided inappropriately by a child, contact the developer so the situation can be reviewed. Google's consent and advertising controls are described above; this policy does not assert that an age label or an SDK alone guarantees compliance with every law.
6. Retention, deletion and security
The game keeps local progress and settings until they are changed, replaced or removed from app or browser storage. It has no timed save-deletion rule. Device backups may have their own retention and restoration behavior.
Google controls the retention and deletion of information processed by its services under its policies and available account or device controls. See Google's retention explanation. The developer cannot directly delete every identifier or record held by Google or your device's backup provider.
These websites use HTTPS, and Google documents TLS for Mobile Ads data in transit. Local saves use the device's app or browser storage. No storage or transmission method can be guaranteed completely secure.
7. These websites and support email
The developer and privacy pages are hosted on GitHub Pages. We do not add analytics, advertising scripts or tracking cookies to them. GitHub states that it logs and stores visitors' IP addresses for security, regardless of whether a visitor is signed in. See GitHub Pages data collection and the GitHub Privacy Statement.
If you email support, the developer receives your email address and whatever message, attachments or other information you choose to send, and uses them to respond to your request. Email providers also process messages under their own policies. Avoid including unnecessary sensitive information. To ask about or request deletion of your support correspondence, email the address below.
Links to Google or other external services open resources governed by those providers' policies.
8. Contact and policy updates
For questions, privacy requests or concerns, contact Masood Ur Rehman at masoodbarkiwork@gmail.com. Depending on your location and the processing involved, you may have rights to access, correct or delete information, object to certain processing, or withdraw consent. Tell us what your request concerns so it can be directed appropriately.
This policy may change as the game or its services change. Updates will be posted here with a revised date. Material changes to the actual app configuration should be reflected in the policy before the affected release.