SWINGDOMS Privacy Policy

Android

Game data uses webview storage, with selected keys mirrored to native Preferences for recovery. The local advertising-age choice is stored separately: Under 16, 16 or older, or Prefer not to say. SWINGDOMS does not request a date of birth for that choice. Change it in Options → Privacy choices. Device backup services may separately retain app data.

Google Play builds may request Google Play Age Signals before allowing gameplay or new purchases. Google may show its own age-sharing or age-verification screens. SWINGDOMS does not request a date of birth or identity documents. Only two local access restriction flags persist: one records that the player is known to be under 13 and one records that Google verification is required. These flags are excluded from device backup.

Returned age ranges, source information, dates, and installation identifiers are not retained or sent to AdMob, UMP, RevenueCat, the reviewer service, or gameplay analytics. Declining Google's sharing does not clear a known-under-13 restriction, and errors preserve existing holds. A qualifying fresh result can clear the flags. Support, legal information, and subscription management remain accessible while gameplay and new purchases are held.

Authorized Google Play reviewers may voluntarily submit a private review credential to a SWINGDOMS service on Cloudflare. The service verifies it and issues a signed session token valid for up to eight hours. It does not persist submitted credentials, request bodies, or tokens, and application logging and tracing are disabled. The app uses session storage only for the one-use handoff, removes the token during review startup, and then keeps review state in memory.

Private review mode does not start RevenueCat, AdMob, native save backup, or gameplay analytics. Cloudflare may separately process network and security metadata under its own retention practices.

iOS

The reviewed iOS wrapper uses webview storage and mirrors selected game keys to native Preferences (UserDefaults) for local recovery. This is not a SWINGDOMS cloud account. Device or iCloud backups may retain app data depending on your settings. The Android age-range dialog is not implemented on iOS.

Web

Standalone builds use browser storage. Clearing site data or using private browsing can remove saves. The optional PWA build also caches game files for offline use.

CrazyGames builds use its Data Module when available. Game save keys include settings, the random installation identifier, and the diagnostic/event buffer, so these are not guaranteed to remain only on your device. CrazyGames can synchronize this data with a platform account; guest storage and sign-in migration follow its rules. If initialization fails, the game can fall back to local browser storage.

Android

The Android advertising integration uses Google AdMob. The SDK automatically collects and shares IP-derived general location, app interactions and advertising events, diagnostic information, and device or account identifiers for advertising, analytics, fraud prevention, and security. This information is encrypted in transit.

The reviewed bridge requests non-personalized ads and a maximum G content rating. Those settings do not prevent AdMob from collecting or sharing the information above and do not establish child-privacy or consent compliance.

The advertising-age choice and Google's User Messaging Platform (UMP) check are independent of the Google Play Age Signals access check. No new ads are requested when the advertising-age choice is Under 16, Prefer not to say, or has not been selected. For 16 or older, UMP is checked at each launch and presents a form when required. Ads are enabled only when UMP reports that ads may be requested. Errors keep new ads off; gameplay and available purchases do not depend on ad consent.

Open Options → Privacy choices to change the age range or retry. Google privacy options are available when Google requires that entry point. A restrictive change blocks new requests but cannot undo prior processing, unload an initialized SDK, or dismiss an ad already on screen.

iOS

The reviewed iOS wrapper keeps ads disabled. It does not start the Android UMP flow or request advertising tracking permission. The AdMob dependency is still included; disabled ad requests are not evidence that every native dependency is inactive.

Before enabling iOS ads, we must review the actual SDK behavior, update these disclosures, and implement any required consent and Apple App Tracking Transparency flow. Apple's tracking permission is separate from advertising consent. This policy does not claim an iOS consent flow has been implemented or verified.

Web

Standalone development builds can contain simulated ads; these are not an advertising network. The itch.io wrapper does not request network ads. CrazyGames Basic disables in-game ad requests, while its Full integration can request rewarded and interstitial ads through the CrazyGames SDK.

CrazyGames or another host may separately process identifiers, device/browser information, IP addresses, usage and advertising events, and cookies or similar storage under its own policy. Use that host's privacy controls. Android's UMP dialog does not govern browser-platform services, and a game-level opt-out does not necessarily stop host analytics.

Android

In-app purchases and subscriptions use Google Play Billing and RevenueCat. During normal startup, after the app-access check permits access and outside private review mode, RevenueCat retrieves products and entitlements and supports purchases and restoration. Because normal play has no SWINGDOMS account identifier, RevenueCat creates an anonymous App User ID.

RevenueCat processes required, non-ephemeral purchase history for app functionality and analytics. SWINGDOMS does not supply name, email address, or telephone attributes and does not enable RevenueCat device-identifier collection. No downstream RevenueCat integrations are currently enabled. Google Play handles payment details; we do not receive your full payment-card details.

iOS

Apple App Store purchases use Apple's in-app purchase system and RevenueCat when configured for release. Apple processes payment and store-account information. We do not receive your full payment-card details from Apple. Purchase restoration checks eligible store purchases; it does not restore all local gameplay progress.

When configured for an iOS release, RevenueCat validates purchases and restores and maintains entitlement state. It processes required, non-ephemeral purchase history for app functionality and analytics and may use an app-user identifier to associate records. Final SDK behavior and integrations must be reviewed before release.

Web

The reviewed standalone browser build has simulated test purchases, not real payment processing. The CrazyGames and itch.io game adapters do not complete real in-game purchases. A separate purchase or account transaction on a hosting site is governed by that site's payment and privacy practices.