Your play.
Your privacy.

Your solo play stays on this device

Mingle stores your profile name, puzzle progress, scores, daily streak, preferences, unfinished rounds, coins, gems, inventory, collected items and reward records locally on your device. Hourly challenge attempts, deadlines, timed puzzle checkpoints, retry-access state and one-time coin-claim records are also kept locally so timers and rewards persist when the app reopens. A local backup of the saved profile helps recover an unreadable save; it stays in the same installation. Mingle does not upload this solo profile to a developer server. The optional soundtrack is synthesized locally and uses no microphone or audio recording.

Optional Game Center play

Apple provides optional Game Center sign-in, matchmaking and leaderboards. If you are already signed in to Game Center, Mingle can restore that connection automatically on launch or return to the app. A login screen is presented when you choose Connect or an online action. While connected, eligible unassisted solo scores are submitted automatically to Apple’s leaderboards. A match shares your Game Center display name, the puzzle setup and live/final scores with the other player through Apple’s connection. Other players can see the information Apple makes available for these features. You can play solo without signing in.

Optional coin and gem purchases

Apple handles payment authentication and financial information. Mingle receives the product and transaction identifiers and verification/refund status needed to deliver fixed coin or gem packs, prevent duplicate delivery and process refunds in the matching currency. These records and your currency balances are stored on this device; Mingle does not receive card details or send the purchase ledger to a developer server. Apple packs credit Main wallet. Starting with app build 21, one Main wallet is usable in all five game shops; balances from earlier game wallets are combined once on update. Verified refunds can reduce the matching remaining local currency, up to the refunded pack amount. A verified reversal of a previously recorded refund restores only the amount actually deducted on this device. Starting with app build 24, Mingle requires iOS or iPadOS 18 or later and uses Apple’s finished-consumable history to reconcile these locally recorded refunds and reversals. That history does not restore a deleted wallet, spent consumables or another device’s balance.

Rewarded and replay advertising

Where enabled in the iPhone/iPad app, you can choose a Google AdMob rewarded ad to continue an eligible puzzle, claim the optional 40-coin boost or unlock retry access after a failed hourly challenge. A separate standard advertisement may appear when you choose Play again after a lost solo round, where that format is enabled. It grants no coins, gems or continuation. Ads never run during online matches or in the middle of an active puzzle. The browser edition has no ad SDK. Google can process network and device information, approximate location inferred from an IP address, ad views and interactions, and diagnostics to provide, measure and protect its ads. These practices are separate from Mingle’s local solo saves.

Mingle applies the same restricted child/under-age ad treatment to everyone and does not determine or verify your age. It requests non-personalized, general-audience ads, disables the publisher first-party identifier and does not ask for tracking permission. Starting with app build 20, Mingle also requests Google’s Limited Ads treatment before privacy preparation and ad loading. This limits personalization and advertising features that use local identifiers. Network delivery still uses IP addresses, and programmatic limited ads may use invalid-traffic-only cookies and local storage to prevent fraud and abuse. Limited Ads does not mean Google processes no device information. Google’s privacy status is checked before an ad request. Under the current under-age setting, Google does not request consent through its consent-request form. The rewarded flow starts after your explicit Watch choice. The replay placement may silently refresh the privacy status and prepare an ad on a lost-round screen, but skips the advertisement if a new privacy choice is required. Neither placement loads an ad at initial launch. Open Advertising privacy in Settings to review privacy options when Google makes them available; otherwise the app explains the current restricted treatment. Rewarded rescues, hourly retry videos and the coin boost are optional. Each game includes a first hourly attempt every hour. Rewarded retry access applies after a failed hourly challenge.

A continuation ad earns one video credit only when Google confirms its reward. The first, second and third rescue in a round require one, two and three completed video credits respectively. Partial credit progress is saved on this device. Local reward-delivery identifiers link the reward to the unfinished round and prevent duplicate delivery. One optional ad can award 40 coins, followed by a 30-minute cooldown saved on this device. The timer does not start an ad automatically. A completed hourly retry video unlocks one fresh attempt at the same current-hour puzzle; it awards no coins or gems and does not start play automatically. The new attempt receives its full timer only when you choose to start. Winning an hourly challenge pays the displayed double-coin gameplay reward once into your local coin balance. Ads never award gems. An unavailable ad, or an ad interrupted before earning its reward, gives no credit, coins or retry access. Google manages its advertising records under its own privacy policy and controls.

Standard replay advertisements use a separate unit and Google's close controls when available. A fresh round starts after the ad is dismissed. Unavailable, offline or failed ads are skipped. Local replay records retain the last full-screen-ad time and recent round/failure identifiers to limit frequency and duplicate presentation; rewarded advertisements also count toward the shared replay cooldown. These records are not uploaded to a developer server. Google test ads produce no advertising income. Live ads and any income depend on Google’s verification and review, eligible ad delivery and the applicable service settings. Full ad serving requires Google’s approval; an unavailable replay ad is skipped as described above.

Permissions and accounts

Mingle has no public chat or custom account system. It does not request your contacts, camera, microphone, precise location or photo library. Your solo profile is not sent to Google as an advertising profile.

Your choices and local data

Settings lets you change your local name, sounds, music, guide language, color symbols, contrast and motion. Reset local progress clears puzzle progress while keeping stored currency balances, purchase/refund records, collected styles, Star Seals, claimed Passport stamps and hourly attempt/deadline/retry/coin-claim records. Deleting the app can remove its local saves, wallet and collected items. There is no cloud wallet or cross-device/reinstall recovery in this version. Apple’s own Game Center and purchase records are managed through your Apple Account and Apple’s controls.

Retention, support and changes

Local records remain in the installation until you change or remove them. The developer does not keep a separate copy of your solo profile or payment details. For support or privacy questions, email builtbysmit@gmail.com. If you email support, we receive your address and message so we can reply. Support correspondence is kept as needed for the request and any required records; you can ask about its removal. Please do not send passwords or full payment-card details. This policy describes the current version; it should be updated if the app’s data practices change.