Jelly Merge: ASMR · iOS

Privacy policy

Effective September 23, 2026 · Jelly Merge: ASMR

This policy covers Jelly Merge: ASMR and its support website. Contact the game operator at samuel@matsonshouse.com with privacy questions or requests.

Information stored on your device

The game saves scores, discovered jelly stages, selected maps, settings, tutorial progress, power-up quantities, gems, and local purchase or reward records on your device to keep the game working between sessions. Local information is not sent to us merely because it is saved. Removing the app normally removes its local app data, but device backups and system-managed credentials may be retained separately. Do not rely on the current build for cloud recovery after deleting the app.

Cloud accounts and progress

Cloud-enabled test versions use Google Firebase to create an anonymous guest account. “Anonymous” means that a player need not supply a name or email; the account still has a persistent user identifier. Cloud records can include that identifier, high score, evolution progress, map selections and unlocks, preferences, tutorial progress, rounds played, and synchronization timestamps. These records support progress recovery, authentication, and fraud prevention. Normal cloud account creation and syncing are disabled in this release, but records created during earlier cloud tests may remain.

Firebase App Check with Apple App Attest, when enabled, processes app attestation and assertion data to check that requests come from a genuine app. Service infrastructure may process IP addresses, request timestamps, and security logs. We do not use those records for advertising or to infer your location.

Private friend-challenge testing

Private test builds can use a Firebase anonymous guest identifier to connect two players through a one-time invite link. The service stores the two guest identifiers, their friend connection, the match start and end times, and scores reported by their games. Each participant can see the other participant’s challenge score. Invite links expire after ten minutes; a match lasts three minutes. Match records are replaced when a new challenge begins or removed with an account-deletion request. Challenge scores are client-reported casual competition and are not a verified global leaderboard. The currently released App Store build does not offer this feature.

Technical information

The included Firebase libraries can send technical information such as device model information, operating-system version, app bundle identifier, developer platform, and SDK version for service operation and SDK diagnostics. Firebase describes its SDK user-agent diagnostics as not linked to a user or device identifier. This build does not integrate Firebase Analytics or Crashlytics.

Support requests

If you email us, we receive your email address, message, and any attachments you choose to send. We use them to respond, investigate problems, and handle privacy requests. Do not send passwords, payment-card information, government identification, or other sensitive information. Email is handled through Gmail.

Advertising and privacy choices

The iOS release includes Google Mobile Ads (AdMob) and Google User Messaging Platform (UMP). The release uses the game's production ad units for optional ads to continue a lost round or earn one power-up and occasional automatic Break ads. Development builds and simulators use Google's demonstration units instead. Ad delivery may be unavailable, including while Google reviews the app. Break ads require at least three minutes of active gameplay, exclude menus, pauses, background time and ad time, and wait for a safe pause in gameplay. A displayed rewarded ad restarts that interval. Unavailable ads do not block play or grant a reward.

Google's SDKs can process IP addresses (which can imply approximate location), app- or device-related identifiers, app and ad interactions, ads shown, crash information, performance information, other diagnostics, and consent choices to deliver and measure ads, prevent fraud, and operate their services. These SDKs can collect information even when the creative is a test ad. We do not send your score, gem balance, power-up inventory, support emails, or Firebase account identifier to AdMob. The app does not request precise location.

This build requests non-personalized treatment and restricted data processing for every ad request, disables Google's publisher first-party identifier and publisher personalization, and does not request Apple's tracking permission or access to the advertising identifier (IDFA). Under restricted data processing, Google limits its use of the data to providing services to us and does not use it for ad personalization. Non-personalized ads still involve data processing; they are not a promise of zero collection. We do not use this release to track you across other companies' apps and websites or to sell or share information for cross-context behavioral advertising. No third-party mediation SDKs are included in this release.

UMP checks the applicable consent requirements at launch before the ad SDK is initialized. Where required, Google presents privacy choices. Open Settings → Privacy → Ad Privacy Choices to revisit available choices. If Google reports that no privacy-choice form is required, the button checks consent status again. If consent cannot be resolved, ads remain unavailable and the game remains playable. You can also contact us using the email below for privacy requests. See Google's description of Mobile Ads SDK data processing and Google's privacy policy.

Purchases

No in-app purchases are offered in this release, including gem packs or No Ads. The game does not collect payment-card details or initiate store transactions. If purchases are added in a later update, the product terms, data practices, restoration behavior, and applicable choices will be disclosed before they become available.

Service providers and disclosure

Google Firebase hosts cloud test data and this website; Apple provides platform, distribution, and app-integrity services. Google AdMob and UMP provide advertising and consent choices. Gmail handles support correspondence. These providers process information for their services under their applicable terms. We may disclose information when required by law, to protect security and legal rights, or as needed to respond to a request you authorize. We do not provide saved gameplay progress or support correspondence to advertisers; the ad SDK processes the technical and interaction information described above.

See Firebase privacy and security, Google’s privacy policy, and Apple’s privacy policy.

This website

This is a static Firebase-hosted website with no analytics, advertising, tracking pixels, or cookies set by our pages. The friend-invite page uses a small local script solely to open the game or display an invite code. Hosting infrastructure processes network information needed to deliver and secure the site. Email links open your chosen mail application; no support form transmits information automatically.

Retention and security

Local progress remains on the device until removed or replaced. Existing cloud account and progress records remain until deleted; they do not currently expire automatically. Support correspondence is retained as needed to resolve requests and maintain necessary business or legal records. Service providers may retain operational logs and backups according to their own retention practices. Information needed for legal obligations, fraud prevention, or security may be retained when necessary.

Cloud connections use encryption in transit, and access controls are intended to restrict each player’s private records to that account and authorized backend services. No service can guarantee absolute security. We do not promise that a local guest save can be recovered if its credentials or device are lost.

Your choices and requests

You can change available settings in the game and choose not to email support. Contact samuel@matsonshouse.com to request access to, correction of, or deletion of information associated with you, or to ask about other rights available under applicable law. We may need limited information to verify the request and locate the correct account; an anonymous account may be difficult to identify without its account identifier or access to the original device. We will not require a password or charge for making a privacy request.

See privacy and deletion requests. Deleting an app does not automatically delete an existing server account. This release does not create cloud accounts. Earlier test-account records can be addressed through the privacy request process; any future account-creation feature will include in-app deletion.

Audience and location

The game is intended for a general audience ages 13 and older and is not specifically directed toward children. We do not knowingly collect personal information from children under 13. If you believe a child has provided information, contact us so we can investigate and delete it where appropriate. Initial App Store availability is limited to the United States. Service providers may process information in the United States or other countries where they operate.

Changes

We will update this page and its effective date when practices change. Material new data uses will be explained before they begin, and consent will be requested where required.