Last Updated: July 6th, 2026
This Privacy Policy describes how [Company Name] ("we," "us," or "our") collects, uses, and discloses information in connection with the CleanerMaster – Storage Clean mobile application (the "App"), available on Google Play for Android devices. By downloading, installing, or using the App, you agree to the collection and use of information in accordance with this policy.
The App is a device storage-cleaning utility. It has no login system, no user accounts, and no cloud storage — all scanning and file-cleaning operations are performed locally on your device. We do not upload, copy, or transmit the contents of your files, photos, videos, or documents to any server.
We collect information in the following categories. We do not collect the categories of information listed separately in Section 1.4 below.
The App uses Google Firebase Analytics and Google Firebase Crashlytics to understand how the App is used and to diagnose technical problems.
App interaction data. We collect data about how you interact with the App's screens and features, such as which screen you viewed, which button you tapped, whether a scan started/completed/failed, and summarized results of cleaning actions (for example, the total number of bytes and number of files affected by a scan or delete operation). This data is transmitted as named events with a fixed set of parameters (for example: screen name, feature/category type, byte counts, file counts, operation duration in milliseconds, ad placement identifiers, ad format, error codes).
What is explicitly excluded from this data by design: the App's analytics layer includes a parameter-level filter (PrivacyParameterFilter) that is applied to every outgoing analytics event and drops any parameter whose key name matches: file name, file path, image URI, video URI, phone number, contact name, message content, email address, IMEI, MAC address, or raw Android ID. We verified this filter is applied uniformly before any event is sent.
Diagnostic and crash data. If the App crashes or encounters an unhandled error, Firebase Crashlytics automatically collects a crash report containing the device state at the time of the crash (such as device model, OS version, memory state, and the stack trace of the error), along with a short breadcrumb log of the names of recent in-app events (event names only — not file names, file paths, or file contents). We do not intentionally log file names, file paths, or media URIs to crash or debug logs in Release builds.
Standard technical parameters automatically collected by the Firebase SDK. As part of its normal operation, the Firebase Analytics SDK automatically collects certain standard technical parameters common to virtually all apps using the SDK, such as app version, operating system version, device model/manufacturer, and a coarse (city/region-level, not precise) geographic region inferred from IP address, consistent with Google's own documentation for the Firebase SDK. This collection is performed by Google's SDK itself, not by app-specific code we wrote.
The App is funded entirely by advertising and does not charge for downloads or offer in-app purchases or subscriptions. We use Google AdMob to display advertisements (app open ads, interstitial ads, rewarded video ads, native ads, and banner ads).
Google AdMob may collect and use device and advertising identifiers (such as the Google Advertising ID, where available), IP address, and general device information in order to serve and measure advertising, in accordance with Google's own privacy practices. We also send AdMob-related events (ad requested, ad loaded, ad failed to load, ad shown, ad clicked, ad closed, reward earned) and revenue/impression-value events to our analytics pipeline; these events are tied to an ad placement identifier and ad format, not to any personal profile we maintain, because we do not maintain user profiles or accounts.
Consent for advertising in regions requiring prior consent. See the important note at the top of this document (visible only in the internal draft): as of this version, the App does not yet include a dedicated consent-management flow. If you are located in a region where prior consent is legally required before ads are shown or before advertising identifiers are used, please refer to your device's advertising settings (see Section 5) to opt out of personalized advertising until such a flow is available.
The App requests only the permissions below. We describe what each one is actually used for, based on how the App's code uses it — not a generic description.