Privacy Policy

Effective date: July 29, 2026

1. Who We Are

This Privacy Policy applies to the Android app Game2048, package name play.game2048.blocks.number.puzzle.games. Game2048 is provided by Quovad Studio. In this policy, "we", "us", and "our" refer to Quovad Studio.

For privacy questions, contact us at support@quovadstudio.cc.

2. Scope and Accounts

This policy describes the current data practices of Game2048. The app does not require you to create an account, and we do not operate a Game2048 account database.

3. Data Stored Locally on Your Device

Game2048 uses Android Room and MMKV to store information needed to provide the game. Local data may include:

• Current and completed game boards, scores, move counts, game history, and statistics.
• Undo snapshots and local achievement or highest-tile progress.
• Selected board mode, haptic-feedback preference, reduced-motion preference, and other app settings.

This gameplay data is not automatically uploaded to us. You can remove it using the in-app clear-history option where available, by clearing the app's storage in Android settings, or by uninstalling the app.

Android Backup

Android backup is enabled for the app. Depending on your device, Android version, Google account, and backup settings, eligible local app data—including game data, preferences, and diagnostic files—may be backed up or transferred by the Android operating system. These backups are controlled by you, Android, and your backup provider rather than by Game2048. You can manage device backup in Android settings and review the provider's privacy policy.

4. Local Diagnostic Logs

Game2048 writes diagnostic logs to the app's private storage to help identify bugs. These logs may record app screens, game operations, feature results, errors, app and build version, device manufacturer and model, Android version, language, time zone, and similar technical information.

Logs are rotated through four files of approximately 1 MB each, so the app normally keeps no more than approximately 4 MB of local logs. Older log segments are overwritten. Local log contents are not automatically uploaded to us or attached to Firebase Crashlytics reports. They remain in the app's private storage unless included in an Android system backup, and are deleted when you clear app storage or uninstall the app.

5. Firebase Crashlytics

Eligible release versions distributed as an Android App Bundle use Firebase Crashlytics to diagnose crashes, Android application-not-responding events (ANRs), and selected non-fatal errors. Debug builds and local release APK builds keep local logs but are configured not to upload Crashlytics reports.

Crashlytics and its supporting Firebase libraries may process:

• Stack traces and relevant application state at the time of an error.
• App package, app version, build information, and relevant Remote Config rollout metadata.
• Device manufacturer and model, operating-system information, language, network connection type, session information, and similar technical metadata.
• A Crashlytics installation UUID and a Firebase installation ID used to distinguish app installations and measure how many installations are affected.
• Low-cardinality diagnostic classifications and custom keys for selected non-fatal errors.

We do not set a Crashlytics user ID and do not intentionally attach gameplay history, local diagnostic log text, email addresses, advertising identifiers, or other direct identity information to Crashlytics reports.

6. Firebase Analytics

Eligible release versions distributed as an Android App Bundle use Firebase Analytics to understand whether core screens and game features work as expected and to improve the app. Debug builds and local APK builds are configured not to upload analytics events.

Analytics events use bounded categories, booleans, and numeric ranges. They may describe:

• App opens, broad installation-age and retention checkpoints, and app-screen navigation.
• Visible interface modules and selected actions, such as starting, resuming, undoing, or restarting a game.
• Board-size mode, first-move and first-merge milestones, highest-tile ranges, and bucketed score and move-count ranges for a completed game.
• Settings actions and coarse feedback-flow results, including a bucketed attachment count and whether diagnostic logs were requested.
• App, device, operating-system, language, country or region, session, and Firebase installation information supplied by Firebase and Android.

We do not intentionally send raw board contents, exact scores, feedback text, contact details, attachment names or contents, file paths, diagnostic request identifiers, or user-selected timestamps to Firebase Analytics. We do not use Analytics for advertising or personalized advertising.

7. Firebase Remote Config and Installation Data

Game2048 uses Firebase Remote Config to retrieve technical configuration, such as compatibility or feature-control values, without requiring an app update. The app may fetch configuration when the relevant feature is initialized and uses caching to limit repeated requests.

Remote Config and Firebase Installations may process a per-installation Firebase installation ID, country code, language code, time zone, platform and operating-system version, Firebase Android App ID, app package name, app version, and Firebase SDK version. A Firebase installation ID identifies a particular installation of the app; Firebase states that it does not uniquely identify a person or a physical device.

Game2048 does not use Remote Config personalization or analytics-based audience targeting.

8. Optional Feedback You Send

The app includes a feedback form. If you choose to use it, you may enter a problem description, select issue categories, provide optional contact information, and attach up to five screenshots, photos, or videos using Android's system file picker. You may also choose to attach an encrypted diagnostic package containing rotated app logs and app and device technical details. Diagnostic logs may include board states and app actions.

Game2048 prepares this information in an email draft addressed to support@quovadstudio.cc. The information is shared only if you review and send the email through your chosen email app. Feedback text, contact information, and selected media are not stored in the game database or sent to Firebase Analytics. Temporary attachment copies created for the email flow are kept in the app's private cache and may be removed by Android or when app storage is cleared.

9. Google Play Games

The current release does not enable Google Play Games sign-in, online leaderboards, or online achievements because its Play Games project and resource identifiers are not configured. Local achievements remain on your device.

If a future release enables Google Play Games, we will update this policy before enabling the feature. Google Play Games may then process your Google Play Games player identity, authentication status, leaderboard scores, achievement progress, and related service diagnostics according to your Google account settings and Google's privacy policy.

10. Permissions and Device Identifiers

• Internet: Used for Firebase Crashlytics, Firebase Remote Config, and opening pages you choose, such as this Privacy Policy.
• Network State: Used to check network availability for these online services.

Game2048 does not request broad access to contacts, photos or media, camera, microphone, precise or approximate device location, SMS, call logs, phone state, nearby devices, or notification permission. If you add a feedback attachment, Android's system picker grants access only to the files you select.

Game2048 does not contain an advertising SDK, does not display ads, and does not read the Android Advertising ID, IMEI, IMSI, SIM serial number, hardware serial number, or MAC address. Firebase creates the service-specific installation identifiers described above.

11. How We Use Data

• Provide gameplay, restore progress and undo state, calculate statistics and achievements, and remember preferences.
• Diagnose crashes, ANRs, non-fatal errors, compatibility problems, and reliability issues.
• Deliver technical configuration and maintain compatibility across app and Android versions.
• Measure aggregate feature usage and broad retention patterns to improve the game.
• Protect app and service security and respond to legal obligations.
• Respond to support or privacy requests that you choose to send to us.

12. Third-Party Services and International Processing

Game2048 uses Google Firebase Analytics, Crashlytics, Remote Config, Installations, and supporting Firebase components. This Privacy Policy is published using Firebase Hosting. Google may process service data on servers outside your country or region under its applicable data-transfer safeguards.

More information is available from Google and Firebase:

• Google Privacy Policy
• Privacy and Security in Firebase
• Firebase Android Data Disclosure
• Google Play Terms and Policies

13. Sharing and Sale of Data

We do not sell personal information, use personal information for behavioral advertising, or share data with advertising companies. Limited information may be disclosed only:

• To Google as our service provider for Analytics, Crashlytics, Remote Config, Firebase Installations, supporting Firebase services, and Hosting.
• When required by applicable law, legal process, or a valid government request.
• When reasonably necessary to protect users, app security, our rights, or public safety.
• At your direction, such as information you choose to send in a support email.

14. Retention and Deletion

Local gameplay data and preferences remain on your device until you clear them, clear app storage, or uninstall the app, subject to any Android backup retained by your backup provider. Local diagnostic logs are automatically rotated as described above.

Firebase retains Analytics, Crashlytics, installation, session, and Remote Config service data according to our Firebase settings and Google's applicable retention practices. Firebase identifiers may be recreated if the app continues to use a Firebase service after an identifier is deleted. Feedback correspondence that you send may be retained as needed to answer and document your request, and can be deleted on request unless retention is required by law or for security.

Because Game2048 has no user accounts, there is no Game2048 account to delete. To request deletion of support correspondence or to ask about Firebase data associated with your installation, contact support@quovadstudio.cc. We may need technical information from you to identify a relevant record, and some service data may not be reasonably linkable to you.

15. Security and Your Choices

Local data is stored in the app's Android private storage. Data sent to Firebase is transmitted using encrypted network connections. We apply reasonable technical and organizational safeguards, but no storage or transmission method can guarantee absolute security.

You can clear game history in the app where available, clear all local app storage, uninstall the app, and manage Android backup in device settings. Depending on where you live, you may have rights to access, correct, delete, object to, or restrict certain personal data. Contact us to exercise an applicable right.

16. Children's Privacy

Game2048 is a general-audience puzzle game and is not specifically directed to children under 13. We do not knowingly ask children to provide names, email addresses, or other direct identifiers through the app. If you believe a child has sent personal information to us, contact us and we will take appropriate action.

17. Changes to This Policy

We may update this Privacy Policy as the app changes. The latest version will be posted on this page with a revised effective date.

18. Contact Us

For questions or requests about this Privacy Policy, contact support@quovadstudio.cc.

This page is provided for Google Play and in-app privacy policy access for Game2048.