2048 Twisted

Last updated: November 8, 2026

Provider: Rice Awn LLC
Contact: contact@riceawn.com

This policy explains how 2048 Twisted and its integrated services handle information. Practices depend on the app version, platform, privacy choices, and services available to you.

1. Earlier Offline Versions

Versions 1.0.3 and earlier were standalone, offline puzzle games without advertising or analytics SDKs. Game progress and settings were stored on the device.

2. Advertising

Ad-supported releases, starting with version 1.0.4, integrate the Google Mobile Ads SDK (AdMob). AdMob may process:

Device identifiers, including app- or developer-scoped identifiers and, on iOS when authorized through App Tracking Transparency (ATT), the advertising identifier (IDFA).
IP addresses and approximate location derived from network information. The game does not request GPS or precise-location permission.
Advertising data, such as advertisements shown, and interactions such as impressions, taps, and video views.
Crash logs, performance information, and other diagnostics used to operate, analyze, and improve advertising services.

Some advertising and interaction data may be associated with a device. When applicable permissions and consent allow it, identifiers may be used for advertising measurement or personalized advertising, including linking information with data from other companies' apps or websites. Refusing ATT prevents access to IDFA; eligible ads may still be served without it.

The separate Remove Ads purchase disables advertisements when its entitlement is recognized. Ownership of an earlier paid version alone does not grant ad-free access. Removing ads does not remove Firebase Analytics or automatically opt you out of otherwise permitted analytics.

3. Firebase Analytics

The iOS 1.0.5 release includes Google Analytics for Firebase to understand app use and improve the game. Android releases that include Firebase Analytics use the corresponding platform integration.

When measurement is enabled, Firebase may process an app-instance identifier, device and app information (such as operating system, app version and language), approximate location derived from network information, and automatic lifecycle and engagement events such as app opens, sessions, and time spent in the app. These records may be associated with an app instance or device even though the game has no account or login.

The app does not set a Firebase user ID, send the saved game board or undo history to Firebase, or include Firebase Crashlytics. The current integration disables Firebase Analytics collection of advertising identifiers; AdMob's separate advertising practices are described above.

On iOS, basic analytics is enabled automatically when the configured consent process determines that prior consent is not required, while preserving an explicit previous refusal. Where consent is required, analytics follows the Analytics consent choice obtained through Google's User Messaging Platform (UMP). Unknown or unconfigured required Analytics consent does not create a new opt-in. A refusal of advertising personalization or ATT permission is not itself a refusal of first-party analytics. Withdrawing Analytics consent disables further analytics collection; it does not automatically erase previously collected records.

Android's integration uses Google's consent mode, which can permit restricted measurement requests when analytics storage is denied. A denied storage setting should not be understood as a promise that the SDK makes no network requests.

4. Your Privacy Choices

The app uses UMP to request applicable regional consent and provides a Privacy Choices entry in Settings when UMP requires it. You can use that entry to review or change the choices offered for your region. Analytics consent and advertising consent are separate purposes. On iOS, ATT is a separate system permission that can be managed in the device's Settings.

Google's processing is described in its Privacy Policy and Firebase privacy information.

5. Purchases

The optional Remove Ads purchase is processed by Apple StoreKit on iOS and Google Play Billing on Android. We do not receive payment card numbers or bank details. The app uses store-provided purchase and transaction information to verify access and restore purchases. On Android, purchase tokens are also used to acknowledge purchases.

6. Local Game Data

Scores, board state, undo history, settings, language preference, and tile-guide discoveries are stored locally on the device. The game does not upload these saved records as cloud saves. Automatic SDK usage events described above are separate from these saved game records. Local data can be removed by clearing app data or uninstalling the app, subject to the device's backup and restore behavior.

7. Retention and Requests

Local game records remain until removed or replaced. Google processes and retains SDK information according to the relevant service settings and policies. Changing consent affects subsequent processing and is not a guarantee that earlier records are deleted. You may contact contact@riceawn.com with questions or applicable access, deletion, or objection requests. We will explain what information we can access and how to direct requests concerning the relevant provider.

8. Children's Privacy

We do not knowingly collect personal information from children under 13. If you believe a child has provided personal information through the app, contact us so we can investigate and address the request.

9. Contact

Rice Awn LLC

Email: contact@riceawn.com

Need a hand?

contact@riceawn.com