30 Sec Chaos Privacy Policy

Contact Us

If you have questions, concerns, or requests regarding this Privacy Policy or the privacy practices of 30 Sec Chaos, please contact us at:

Email: prashant.vapt@gmail.com

1. About this policy

This policy explains how the current Android version of 30 Sec Chaos handles information. For privacy questions or requests, use the contact details above.

30 Sec Chaos is an offline-first game with no user account and no custom game backend. Offline-first does not mean that no personal data is collected: the Google services described below can process information about your use of the app and your device.

2. Game data stored on your device

The game uses AsyncStorage to save progress and preferences on your device; saved progress is not synchronized to a game server.

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 local identifier, score, coins, maximum combo, normal/daily mode, new-best status and rewarded-bonus claim status.

These records save progress, apply preferences, manage daily challenges, calculate rewards, control gameplay access and prevent duplicate reward claims. Cooldown records remain local. 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. Ad privacy choices collected through UMP do not automatically control all Firebase Analytics processing. 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.

• app_open: opening the app; no custom parameters.
• session_start: starting a game session, with mode (normal or daily). Firebase may also collect its own session_start event.
• daily_challenge_started and daily_challenge_completed: no custom parameters.
• game_abandoned: leaving an unfinished game, with mode.
• challenge_started, challenge_completed and challenge_failed: challenge_type and difficulty.
• session_complete: mode, score, max_combo, coins_earned and difficulty_reached.
• replay_tapped and share_tapped: no custom parameters.
• sound_toggled and haptics_toggled: enabled (true or false).

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.

5. Advertising and rewarded ads

The game integrates AdMob rewarded video ads on Android. Explicitly configured production builds use the publisher's Double Coins rewarded-ad unit. Development/debug builds, development clients and preview builds use Google's test rewarded-ad unit. Missing or inconsistent release ad configuration disables ad requests rather than substituting a test unit. Test ads still communicate with Google's SDKs and do not guarantee 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.

The Android app requests updated privacy information through Google's User Messaging Platform (UMP) at startup and asks the SDK to show a consent form when required. Ad requests wait for this handling and are allowed only when the SDK reports canRequestAds. On errors, ads remain unavailable unless the SDK permits requests using previously stored choices. Gameplay is not blocked by a consent error. A form being dismissed is not treated as acceptance.

Forms, required choices and available ad serving modes depend on the publisher's AdMob Privacy & messaging configuration, region and SDK state.

Advertising information supports ad delivery, measurement, analytics, fraud prevention and potentially personalization depending on configuration and applicable choices. The app does not force a non-personalized-ad request flag or set child-directed/under-age ad flags. Do not assume ads are always non-personalized or that canRequestAds means every processing purpose was accepted.

6. Other network activity and sharing you choose

On Android, the app checks the public Google Play listing for this application's package ID to compare the installed native version with the available store version. Checks can run at launch, after reconnection or when returning to the app following an update prompt or interrupted check. Requests include the package ID, an English-language setting and a timestamp to avoid cached results, plus ordinary network metadata such as IP address. They do not attach your scores, coins, local cooldown records or an account identifier. The update decision is session-only, not a permanently saved lock.

When a valid check finds a newer version, an update prompt blocks access until you update or the check no longer requires it. If you select UPDATE NOW, the app opens Google Play or its website, which has its own privacy practices. Checks are skipped or allow continued use when connectivity or valid version information is unavailable.

Opening Privacy Policy in Settings loads the hosted policy at https://30-sec-chaos-privacy.pages.dev inside the app. This sends an ordinary webpage request to the hosting service, including network metadata such as IP address; the app does not attach your saved game data to that request.

The game-over Share action opens the system share sheet with a message containing your score and a challenge hashtag, but no Play Store URL. It also requests a share_tapped Analytics event when tapped, even if you later cancel sharing.

Settings > INVITE FRIENDS opens the system share sheet with a general invitation to play. The current invitation includes no score or Play Store URL, and this action does not request a share_tapped event. For either sharing action, you choose the destination; any service you share through handles the message under its own privacy policy.

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. Installed but unused location and image-picker modules declare sensitive permissions; the Android Expo configuration blocks coarse/fine/background location, camera, microphone recording, legacy external storage and media-image/video permissions because the game does not use them. Source configuration is not proof of the final packaged permissions or runtime data collection.

8. Who receives information

Google / Firebase / AdMob receive the Analytics and advertising information described in Sections 3–5, and their affiliates and service providers may handle it under their terms. The publisher may view Analytics reports. Other requests and user-selected sharing destinations are described in Section 6. 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.

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 GAME DATA, after confirmation, clears the best score, total games, total score, coins and daily results. It preserves sound/haptic preferences, completed-game count, cooldown state and the most recent game/reward-claim record, including its local identifier. Resetting is not a fresh installation and does not restart the free-game allowance or erase an existing cooldown. It does not delete information already sent to Firebase or advertising providers.

The publisher reports the following Google Analytics property retention settings: event data retention is 2 months; user data retention is 14 months; reset on new user activity is enabled. These are the corresponding Analytics settings, not universal deletion deadlines for all Google services or all information. Aggregated reports, backups and provider logs can follow different 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 or automatic provider-data deletion button.

When UMP requires it, Settings shows Ad Privacy Options to open Google's advertising privacy form directly. After an error, a retry is shown only if ad permission remains unavailable or privacy options are required. If no privacy-options entry is required, use Advertising privacy / Retry consent update; if options are required, a separate Retry update action is available. A failed update that still permits ads and requires no privacy-options entry does not show a retry. Actions are disabled while an update is in progress.

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 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 is not a permanent Analytics opt-out; see Section 3 for offline event queuing.

11. Children's privacy

The publisher's stated intent is a general audience aged 13+, with children not being the target audience. This is a statement of intent, not a finalized age-specific legal declaration. Ages 13–15 may be treated as children in some jurisdictions.

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.

A parent or guardian with concerns should contact the publisher using the privacy contact above. This policy 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. This policy does not guarantee absolute security.

13. Contact and policy changes

For privacy questions or requests, contact Nayan Om using the email above. No company incorporation or legal-entity status is asserted here.

The publisher may update this policy when the app or its services change. The Last updated date above identifies the policy's latest revision.