DOCTYPE html> Privacy Policy — Clean Game Turbo

Privacy Policy

Clean Game Turbo
Last updated: October 7, 2026

1. Scope and overview

This Privacy Policy describes information that the Clean Game Turbo Android app (the “App”) accesses, processes, or stores and the third-party services it uses. The App does not provide an in-app account or sign-in and the current app source does not operate a developer-managed server or database. The App stores certain preferences and gaming-session history on your device. It also connects to Google Play Billing and Google Mobile Ads/Google User Messaging Platform (UMP); Google handles information sent through those services under its own terms and privacy notices.

This Policy describes the App’s current implementation. It does not replace Google’s own privacy information for Google Play, Google Mobile Ads, or UMP.

2. Information accessed and processed by the App

2.1 Media library and file information

If you grant the relevant Android access, the Cleaner can query photos, videos, and audio items made available through Android’s media library. It uses information such as the item name, media identifier/URI, size, and modification date to list and sort items. It can render a local preview and, for duplicate detection, read candidate media locally to calculate a comparison hash. This processing is performed on the device. The App’s current code does not upload the media items or their comparison hashes to a developer-operated server.

When you choose media for deletion, the App asks Android to show its system confirmation flow. The App does not silently delete selected media. Any recovery option after deletion depends on Android and the media app or device you use; the App does not provide a recovery service.

2.2 App list and app-owned files

The App queries apps that have a launcher entry so you can add and open games or view launchable apps in its app-management tools. It may use the app label, package name, and installed APK/split-APK file sizes for those screens. The manifest uses a launcher-intent query rather than the broad QUERY_ALL_PACKAGES permission.

The Cleaner can inspect and remove cache files and selected temporary-file types in Clean Game Turbo’s own app storage. It does not clear another app’s private cache or RAM. A separate session preparation action may clear Clean Game Turbo’s own internal and external cache only.

2.3 Usage Access and game-session history

If you enable Auto Game Mode and grant Android Usage Access, the App checks foreground-usage events to determine whether a game you registered in the App has entered or left the foreground. It processes app package identifiers and event timing locally for that detection and for session tracking. It does not inspect another app’s screen, messages, or in-app content.

Gaming-session history may include the selected game’s display name and package identifier, session start/end times and duration, launch count, battery readings, battery-temperature readings, and system-wide RAM-use samples. These are device/session readings, not measurements of the game’s own RAM use or performance. The App stores the history locally. The storage code keeps up to 500 session records; free users see the latest five, while the full history is available to VIP users. You can delete a session or clear the history from the Gaming History screens.

2.4 Device information

Device and information screens read values supplied by Android, such as device model and operating-system information, battery, storage, network status, CPU information, and temperature. These values are displayed by the App and are not transmitted by the App to a developer-operated server. They describe the device; the App does not measure in-game FPS or the selected game’s internal CPU/GPU performance.

2.5 Notification access

If you grant Notification Access and enable notification filtering for a game, while a gaming session is active the Notification Listener checks the sending app’s package identifier and Android notification key, then may dismiss notifications from other apps. The current code does not inspect or store notification titles or message text. This feature is optional and can be disabled by turning off the per-game setting or revoking Notification Access in Android Settings.

2.6 Settings changed during a gaming session

If you enable the relevant controls and grant Android’s system-setting permissions, the App can change screen brightness, media/ringtone volume, and the Do Not Disturb interruption filter. Per-game preferences and temporary brightness/volume values used by the App are stored locally. When a session ends, the current implementation attempts to restore saved brightness and volume values; it sets the interruption filter to “All” rather than restoring a previous custom Do Not Disturb filter. Please review your device’s Do Not Disturb setting after a session if you had a custom filter enabled. The optional screen-awake control applies while the Game Mode overlay is active.

2.7 Notifications from the App

If permitted by Android, the App may post its own notifications, including notifications associated with an active foreground service. These are generated by the App and are separate from notifications received from other apps.

3. Google services: advertising, consent, and billing

3.1 Google Mobile Ads and UMP

The App integrates Google Mobile Ads and may request or display ads in the App. Google may process information associated with ad requests and delivery under Google’s own policies. See Google’s Partner Policy and Google’s Privacy Policy.

The App also integrates Google’s User Messaging Platform (UMP). A “Privacy Options” / “Manage Consent” control is available in Settings to open Google’s consent-options form. Whether a form or particular choices are shown is determined by Google UMP and the applicable settings.

Current implementation note: the Home screen’s post-scan interstitial ad path in this app version does not check the App’s VIP flag or UMP consent state before requesting/showing the ad. Therefore, this version cannot promise that every ad request is held until consent is resolved or that every ad placement is suppressed for VIP. This behavior should be corrected in the app before making a broader consent-gating or ad-free claim.

3.2 Google Play Billing

Subscription products and payments are handled through Google Play Billing. The App queries product and subscription entitlement status and stores a local VIP status flag so it can enable or disable app features. Payment-card and billing credentials are handled by Google Play, not collected through the App’s own forms. See Google’s privacy information for data processed by Google Play.

4. Local storage and retention

Game selections, per-game settings, Auto Game Mode preference, VIP status cache, and session history are stored in app-private storage on your device. The App does not provide cloud synchronization for this information. You can delete individual session records or clear all session history in the App. You can also clear the App’s data or uninstall it through Android Settings; Android controls the removal of app-private data. Uninstalling does not delete media files that you previously chose to keep, and it does not cancel a Google Play subscription.

Google’s retention of data processed by Google Play, Google Mobile Ads, or UMP is governed by Google’s policies and your Google account settings.

5. Sharing

The App’s current source does not send its locally stored game list, session history, notification information, or scanned media to a developer-operated server. Information is exchanged directly with Google services when the App uses Google Mobile Ads/UMP or Google Play Billing. Android also handles permission requests, media deletion confirmation, app-uninstall confirmation, and system settings through its own interfaces.

6. Your choices

Contacting support

If you email the support address below, the App developer receives the email address and message contents you choose to send and uses them to respond to your inquiry. Your email provider may also process that message. Please do not include information you do not want to share by email.

7. Children

The App does not provide an in-app account or a mechanism for submitting personal information to a developer-operated server. The App’s audience and age rating are determined through its Google Play listing. Google’s services may process information under their own policies.

8. Changes to this Policy

This Policy may be updated when the App or its data practices change. The “Last updated” date above identifies the current version. Please review the latest version published at the App’s Privacy Policy link.

9. Contact

Questions about this Privacy Policy or the App’s privacy practices: support.cleangameturbo@gmail.com.

Read the Terms of Service.