PRIVACY POLICY · RICE AWN LLC

Jelly Mingle: Merge Puzzle

Last updated: November 1, 2026

Rice Awn LLC (“we,” “us,” or “our”) operates Jelly Mingle (the “Game”). This Privacy Policy explains how information is handled when you use the Game on Android or iOS or visit this policy page. Features and privacy controls can differ by platform and version.

For privacy questions or requests, contact contact@riceawn.com.

1. Game information stored on your device

The Game stores level progress, stars, best move counts, daily challenge results, tutorial progress, and preferences such as music, sound effects, and Color Assist on your device.

We do not operate a game-account or cloud-save service. We do not upload your complete game-save file, saved boards, or solution routes to a developer-operated server. Limited gameplay events may be sent to Firebase as explained below. Device or operating-system backups are managed by the relevant platform and your settings.

You do not need to provide your name, email address, or payment details to play. Gameplay does not request access to your contacts, photos, camera, microphone, or precise GPS location.

2. Advertising and privacy choices

The Game uses Google AdMob / Google Mobile Ads to display banner and interstitial advertisements. We use Google's User Messaging Platform (UMP) to present and manage privacy choices where applicable.

These services may collect or generate:

• IP addresses and approximate location inferred from them.
• Device, operating-system, app-version, and network information.
• Advertising IDs, app-scoped identifiers, and other platform-permitted device or account identifiers, where available.
• Interaction information, such as app launches, ad requests, impressions, taps, and video views.
• Diagnostics, including errors and app or advertising-SDK performance information.
• Consent records and privacy-preference signals.

This information is used for ad delivery, measurement, permitted personalization, service operation, and fraud prevention. Google and providers involved in serving advertisements may process it according to your choices, their roles, and applicable requirements. Advertising eligibility does not by itself authorize our gameplay analytics.

For more information, see Google's Privacy Policy (https://policies.google.com/privacy) and How Google uses information from apps that use its services (https://policies.google.com/technologies/partner-sites).

3. Gameplay analytics

Android and iOS versions that include Firebase use Google Analytics for Firebase to help us understand gameplay and improve the Game. When enabled, Analytics may process app-instance identifiers, app and device details, approximate location, session and interaction information, and events such as starting a level, completing a level, the move count at completion, and completing a tutorial.

On supported iOS versions, Analytics may also record in-app purchase information, such as the product identifier, price, and currency. We do not receive your payment-card details or store-account password through Analytics.

Our gameplay integration does not send your complete game save, saved boards, solution routes, name, or email address to Analytics. It does not enable Firebase advertising-ID collection or use Firebase gameplay measurement for advertising personalization. The separate advertising SDK's practices are described above.

Analytics follows the applicable Analytics consent signals managed through UMP. An unknown Analytics permission or unsuccessful initial consent refresh does not enable our gameplay analytics. On iOS, you can additionally switch Usage Statistics off in Settings. Switching it on does not override a refusal in an applicable consent form. Android currently has no separate Usage Statistics switch.

See Privacy and Security in Firebase (https://firebase.google.com/support/privacy) for information about Google's handling of Firebase data.

4. Crash reports and diagnostics

We use Firebase Crashlytics to diagnose technical failures. Reports may include crash traces, app version, operating-system and device information, installation identifiers, and SDK diagnostic information. Native crash reports may contain technical memory-dump data used to investigate a failure. When Analytics is enabled, reports may also include recent Analytics events as diagnostic breadcrumbs.

Android: Automatic crash reporting is enabled by default. It is separate from gameplay Analytics and advertising personalization. No additional crash-reporting dialog is shown, and the current Android version has no separate in-game crash-reporting switch.

iOS: Share Crash Reports in Settings is initially off. If you enable it, Crashlytics can upload diagnostic reports. Switching it off stops subsequent automatic uploads and requests deletion of reports that have not yet been sent. It does not automatically erase reports already received by Google. This setting is separate from Usage Statistics and Apple's tracking permission.

We do not deliberately add saved boards, solution routes, your name, or your email address to crash reports. Google's Firebase privacy information (https://firebase.google.com/support/privacy) describes the diagnostic data processed by its services.

5. Purchases

Where an optional in-app purchase is offered, such as removing advertisements on supported iOS versions, the relevant app store processes the payment. The Game receives transaction and entitlement information needed to verify, provide, and restore the purchase. We do not receive your payment-card details or store-account password.

Removing advertisements does not automatically change Analytics or crash-reporting preferences. The app store handles its own account, payment, and transaction records under its privacy policy.

6. Your controls

Where required and available for your region, you can revisit advertising and related consent choices through Settings → Privacy Options. Withdrawing consent does not affect processing that was lawful before withdrawal.

Your device may offer additional controls. Android settings can let you reset or delete an advertising ID. On iOS, system Tracking settings and any applicable App Tracking Transparency prompt control permission for tracking. Refusing tracking permission does not prevent normal gameplay.

Depending on your choices, region, and ad availability, advertisements may be contextual or limited, or some advertising features may be unavailable. Turning off personalization does not necessarily stop permitted processing needed for ad delivery, measurement, security, or fraud prevention.

You can also review Google's advertising controls (https://myadcenter.google.com/).

7. Support and this website

If you contact contact@riceawn.com, we receive your email address and the information you choose to send, such as a problem description, device details, or screenshots. We and our email provider process this correspondence to answer you, investigate issues, and maintain necessary support or legal records. Please do not send passwords, payment-card details, or unrelated sensitive information.

This policy page is hosted using GitHub Pages. When you visit it, GitHub may process network, browser, and usage information under the GitHub Privacy Statement (https://docs.github.com/en/site-policy/privacy-policies/github-general-privacy-statement). Viewing this page does not give us access to your locally stored game save.

8. Recipients of information

Information may be processed by Google and the advertising, analytics, diagnostics, app-store, hosting, and email providers described in this policy. We may also disclose information we hold when reasonably necessary to comply with applicable law or legal process, prevent fraud or abuse, or protect rights and safety.

Google Play, the App Store, and third-party destinations opened from advertisements operate under their own privacy policies.

9. Retention and deletion

Local records: Your progress and preferences remain on your device until removed. Clearing the Game's app storage on Android or deleting the app on iOS removes its local records; iOS offloading may retain them. Deleting local records may permanently remove progress. Separately retained platform backups must be managed through the platform's controls.

Support correspondence: We retain it for as long as reasonably needed to handle the request, resolve related issues, and meet applicable legal obligations.

Provider records: Advertising, consent, Analytics, diagnostics, and store records are subject to the providers' retention practices and applicable service settings. Google states that Crashlytics retains crash traces, extracted diagnostic data, and associated identifiers for 90 days before beginning removal from live and backup systems. See Firebase's retention information (https://firebase.google.com/support/privacy).

Disabling collection, clearing local storage, or uninstalling the Game does not automatically erase information already received by a provider. Contact contact@riceawn.com to ask about information we control or request deletion. We cannot remotely retrieve or erase a save that exists only on your device.

10. Legal grounds and your rights

Where applicable, processing relies on consent for activities requiring it, providing requested services, legitimate interests such as maintaining a reliable and secure Game and responding to support requests, or compliance with legal obligations.

Depending on your location, you may have rights to access, correct, delete, or receive a copy of personal information; restrict or object to processing; withdraw consent; or complain to a relevant data-protection authority. Some U.S. privacy laws may treat certain targeted-advertising disclosures as a “sale” or “sharing” of personal information. Where applicable, use the available privacy choices to opt out or contact us about information we hold.

We may request information reasonably needed to verify and respond to a request and will handle it as required by applicable law.

11. International processing and security

Providers may process information in countries other than yours, including countries with different privacy laws. Their privacy information describes applicable transfer safeguards.

We use device-storage protections and the security mechanisms of the services we integrate. Google states that its advertising SDK encrypts transmitted user data using TLS; see its SDK data disclosure (https://developers.google.com/admob/android/next-gen/privacy/play-data-disclosure). No method of storage or transmission can be guaranteed completely secure.

12. Children

Jelly Mingle is intended for a general audience and is not specifically directed to children under 13. We do not knowingly seek personal information from children under 13. Additional protections may apply to minors under local law.

If you believe a child has provided personal information in connection with the Game, contact contact@riceawn.com. We will review the concern, take appropriate action concerning information we control, and direct you to the relevant provider when appropriate.

13. Updates and contact

We may update this policy as the Game or our information practices change. The date above identifies the latest revision. Where required, we will provide additional notice or request a new choice before a relevant change takes effect.

Developer / Operator: Rice Awn LLC
Game: Jelly Mingle
Privacy contact: contact@riceawn.com