Privacy Policy

30 Sec Chaos

DRAFT — complete publisher details and release checks before publishing.

App
30 Sec Chaos
Publisher
[PUBLISHER / LEGAL OPERATOR NAME]
Privacy contact
[PRIVACY CONTACT EMAIL]
Postal address
[POSTAL CONTACT ADDRESS, if applicable]
Effective date
[EFFECTIVE DATE — publisher to complete]
Last reviewed
15 October 2026

1. About this policy

This policy explains how the current Android version of 30 Sec Chaos handles information. The publisher and privacy contact are identified above. An iOS release may be added later; its SDKs, permissions and disclosures must be reviewed before release.

30 Sec Chaos is an offline-first game with no user account and no custom game backend. This does not mean that no personal data is collected. Google Firebase Analytics and Google AdMob / Google Mobile Ads can process identifiers, usage information and other device-related data.

2. Game data stored on your device

The game uses AsyncStorage to save progress and preferences on your device. It is not a dedicated encrypted storage vault. There is no custom game server that synchronizes your saved progress.

Saved information includes best score, total games, total score, coins, daily challenge results by date (score and completion), sound and haptic settings, completed-game count, cooldown end time, and the most recent completed game's score, coins, maximum combo, normal/daily mode, new-best status and rewarded-bonus claim status.

The cooldown and reward-claim records are used locally to control gameplay access and avoid claiming the same reward twice. The current code does not send these local cooldown records to a custom server. Some gameplay statistics are separately included in Analytics events as explained below. Coins are in-game progress, not a payment account.

3. Firebase Analytics

The Android app uses Google Analytics for Firebase to understand app use, gameplay engagement and preferences. Analytics collection is not explicitly disabled or gated by a consent choice in the current implementation. Events may be queued by the SDK while offline and transmitted when a connection is available.

The app requests the following events. Actual reporting also depends on Firebase SDK rules and project configuration. In particular, Firebase has automatically collected and reserved event names; a call in the app is not proof that a separate custom event was accepted.

4. Information collected by Google's SDKs

In addition to the app's event parameters, Firebase Analytics may automatically process app-instance identifiers, device or advertising identifiers where available, app and operating-system information, device characteristics, language, session and engagement information, and approximate geographic information derived from network information such as IP addresses. The app does not set a custom account User ID or submit names, email addresses or phone numbers in its gameplay event parameters.

Google Mobile Ads documents collection and sharing of IP addresses (which may estimate general location), app/ad interactions such as launches, taps and video views, diagnostic/performance information, and device or account-related identifiers such as Android advertising ID and app set ID, where available. Collection depends on SDK version, device settings, provider configuration and any applicable consent requirements.

Identifiers can make data relate to a device or app installation even though the game has no sign-in. This policy does not describe SDK data as completely anonymous. See the provider links below for their current collection and processing descriptions.

5. Advertising and rewarded ads

The game integrates AdMob rewarded video ads on Android. The current implementation uses Google's test rewarded-ad unit, including release-mode builds of this implementation; a live advertising unit has not been selected in this code. Test ads still initialize and communicate with Google's advertising SDK and must not be treated as a guarantee of zero data collection.

Where the rewarded option is offered, you can choose to watch an ad to earn an additional coin bonus and clear that completed game's cooldown. The reward is granted only when the SDK reports that it was earned. Closing an ad early or an ad failure does not earn the bonus. You may instead wait for the local cooldown. Choosing not to watch is not an Analytics opt-out.

No app-controlled ad-personalization setting, non-personalized-ad request flag, consent form, or child-directed/under-age ad configuration is implemented in the reviewed app code. Do not assume ads are always non-personalized. The publisher must verify and configure the required advertising/consent choices for its audience and release regions before launch. Replacing test ads with live ads requires a fresh disclosure review.

6. Other network activity and sharing you choose

On Android, the app may check the public Google Play listing for this application's package ID to compare the installed native version with the available store version. This communicates with Google and involves ordinary network metadata, such as IP address. The current check does not attach your scores, coins, local cooldown records or an account identifier. Its update decision is session-only, not a permanently saved lock.

If you select UPDATE NOW, the app opens Google Play or its website, which has its own privacy practices. The check is skipped or fails open when connectivity or valid version information is unavailable.

If you choose the game's Share action, the system share sheet offers a message containing your score to the app or recipient you select. Your chosen sharing service handles the message under its own policy. The game also requests a share_tapped Analytics event.

7. Permissions and device features

The reviewed source uses internet/network connectivity for SDKs, ads and the Play Store check, local storage for saved progress, audio playback for effects, and vibration/haptics for feedback. Android libraries declare network/Wi-Fi state, wake-lock, audio-settings and vibration permissions. Google's SDKs may also declare advertising-ID-related permissions in the final merged app manifest.

Gameplay code does not request camera, microphone, contacts, photo-library or precise-location access. However, installed but unused location and image-picker modules include manifest declarations for coarse/fine location, camera and legacy storage access. The final native build's merged permissions have not been audited as part of this draft. A declared permission is not proof that access was granted or that data was collected; the publisher must verify the final release and update this section as needed.

8. Why information is used and shared

Local information is used to save progress, apply settings, manage daily challenges, calculate rewards and enforce the local cooldown. Analytics information is used to understand game use and performance. Advertising information is used by the advertising service for delivery, measurement, analytics and fraud prevention, and potentially personalization depending on configuration and applicable choices.

SDK information is transmitted directly to Google / Firebase / AdMob and may be handled by their affiliates and service providers under their terms. The publisher may view Analytics reports. The absence of a custom backend does not prevent this sharing. Information may be processed outside your country under the providers' arrangements.

No additional publisher-operated data broker or sale mechanism is present in the reviewed game code. This statement is not a legal conclusion that advertising-related processing can never count as a 'sale' or 'sharing' under a particular privacy law. Provider roles, linked services and release configuration must be confirmed before publication.

9. Retention

Local progress and preferences remain until they are overwritten, cleared or removed. The app does not set a general expiry for saved statistics or daily history. A cooldown can expire without deleting its historical state. Device backup/restore settings can also affect whether local data is retained or restored.

Settings > RESET ALL DATA currently clears scores, total games, total score, coins and daily results. Despite its label, it preserves sound/haptic preferences, completed-game count, cooldown state and the most recent game/reward-claim record. It does not delete information already sent to Firebase or advertising providers.

Analytics user/event retention depends on the publisher's Google Analytics property settings; this period is not set in the app code. [ANALYTICS RETENTION PERIOD — publisher must verify and fill in.] Aggregated reports and provider logs can follow different retention rules. Advertising retention is governed by Google's applicable policies and configuration; no fixed AdMob deletion period is implemented by the app.

10. Your choices

Sound and haptic switches change game preferences; they do not turn off Analytics or advertising collection. The current app has no dedicated Analytics opt-out, advertising-consent control or automatic provider-data deletion button.

You can choose not to request a rewarded ad and wait for the cooldown. You can use Android's available advertising/privacy controls, including resetting or deleting the advertising ID where supported. These controls do not necessarily stop all SDK processing.

Android app settings can clear this app's local storage; doing so removes progress and preferences. Uninstalling normally removes local app data, subject to device backups/restores. Clearing or uninstalling the app does not itself send a deletion request for information already held by Google.

Depending on your location and applicable law, you may have rights to request access, correction, deletion or restrictions on processing, or raise concerns with a competent authority. Contact the publisher using the completed contact details above. What can be identified and acted on depends on the data and provider systems; there is no game account to look up.

Playing offline limits immediate network activity but is not a permanent opt-out, since SDKs may queue data for later transmission.

11. Children's privacy

[TARGET AUDIENCE / MINIMUM AGE / CHILD-USE POLICY — publisher must confirm before release.] The intended age groups cannot be established from the game code alone.

The current app does not implement an age gate, parental-consent flow, or child-directed/under-age advertising configuration. The lack of an account or a form asking for a child's name does not prevent identifiers from being processed by SDKs. The publisher must assess children's access and applicable Google Play Families, advertising and legal requirements before distribution.

A parent or guardian with concerns should contact the publisher using the completed privacy contact. This draft does not claim COPPA, GDPR or other legal compliance.

12. Security

Local data relies on the app's storage and operating-system protections; AsyncStorage is not a dedicated encrypted vault. Google documents encryption in transit for the SDK data described in its disclosures. The game uses HTTPS for its Play Store webpage request.

No storage or transmission method is completely secure. Avoid sharing sensitive information in game-related messages. The publisher must assess release-build security and service-provider access controls; this policy does not guarantee absolute security.

13. Contact and policy changes

For privacy questions or requests, contact the publisher using the name, email and any applicable postal address above. These placeholders must be replaced with real details before this policy is published.

The publisher may update this policy when the app or its services change. A completed effective date and the updated policy should be made available at the final Privacy Policy URL. Changes such as live ads, consent controls, additional platforms, SDKs, accounts or cloud storage require a new review.

Provider links