Applies to SuperClean – Phone Storage version 1.1.x for Android (com.superclean.phone.storage), the version that shows ads.

The short version. Your files stay on your device: SuperClean does not upload your photos, videos, audio, documents or notification content, and it does not send your file or folder names, apart from the rare crash-report case in section 3(d). Unlike version 1.0.x, this version connects to the internet. It shows ads and uses advertising, consent, analytics, crash-reporting, configuration and push-message services from Google, and an operational log service run for our advertising integration partner. It also shows a storage overview in the notification bar, which you can turn off in Settings. Ad requests start only after the consent step has a result. Analytics and crash reports start only after that too, and where the law requires consent they stay off unless you agree. A few things happen earlier: the consent form itself, the operational logs, and Google services that deliver settings and push messages (section 4).

1. Who we are

This Privacy Policy explains how the SuperClean – Phone Storage mobile application for Android (the "App") handles information. In this policy, "we", "us" and "our" refer to the developer of the App. It covers what the App reads on your device, what it sends off your device and why, and the choices you have.

2. What the App accesses on your device, and why

To do its job, the App reads certain information on your device. This is processed on your device and is not uploaded, and none of the services in section 3 receives it. Every permission below is optional: if you decline one, only the related feature is limited.

• Photos, videos and audio (media access; on Android 14+ you may allow selected photos only; on older Android versions, storage read/write access) — to find similar photos, large files and audio files, show thumbnails, and compress photos you select.
• All files access (optional) — to find junk files such as caches, temporary files, logs, leftover folders from uninstalled apps, empty folders, installer packages (APKs) and large non-media files. Without it, the App scans only what it is allowed to see and tells you the scan is limited.
• Notification access (optional) — to show your current notifications grouped by type and let you clear them, and, if you turn it on, to clear notifications from apps you choose. Notification content is read in memory only to display and group it; it is not saved or sent anywhere. Notifications that look like messages, calls, email, alarms, reminders or calendar events, verification codes, notifications from your default SMS app, and notifications an app marks as sensitive are kept.
• Usage access (optional) — to show data usage per app (Network Traffic), app sizes and last-used times (App Manager), and recently used apps (Process Manager).
• List of installed apps — to list apps that have a launcher icon in App Manager and Process Manager. The list is not stored or shared.
• Storage measurements — free and used space, and the size and number of junk files, large files, similar photos, compressible photos and audio files found by the App's own scans. Some of these checks also run in the background, mainly while your phone is charging. The results are kept on your device and used to show numbers in the App, in suggestion notifications and in the storage overview bar (section 6). They are not sent off your device.
• Device, battery and sound information — such as device model, Android version, storage and memory usage, battery level and temperature, and media volume, to display them in the App. Volume is changed only when you adjust it.

3. What this version sends off your device

This version has the Android internet permission. The services below are built into the App. Like any internet request, each of them receives your IP address. None of them receives your files, notification content, your storage measurements or the list of your installed apps. The App does not send file or folder names; the one place a name could appear is the text of a crash report, which is described in 3(d).

• (a) Advertising. The App shows ads through Google AdMob, loaded by an advertising component from our integration partner. It can show an ad when the App opens or returns to the screen (including when you open it from a notification), a full-screen ad at certain points (for example after a clean-up finishes), and ads inside some screens (the home screen and result screens; an ad for a result screen may be requested in advance, for example when a scan starts or the photo list loads, but it is shown only on the result screen). To serve and measure ads, Google processes your device's advertising ID, your IP address (from which it can infer an approximate location), ad interaction data such as impressions and clicks, and diagnostic information about the ad request. Ad requests start only after the consent step has a result (section 4). You can reset or delete your advertising ID, and opt out of ad personalization, in Android settings.
• (b) Consent form. Where the law requires it, the App shows a consent form from Google (User Messaging Platform) when it starts, and records your choice on your device. See section 4.
• (c) Analytics. The App uses Firebase Analytics (Google) to count usage events: events from the advertising and messaging component (for example that an ad was requested, shown or clicked, or that a suggestion notification was shown or tapped; each time an ad is shown and earns revenue, an ad impression event also records the amount of revenue that impression earned, its currency, the ad network, the ad format, the ad unit and the ad placement, which we use to measure how our ads perform; if a click on an ad looks accidental or automatic, for example because there was no touch on the ad, the event also carries the ad placement and format, the identifier that Google assigns to the ad creative (not to you), and how long ago the screen was last touched, which we use to find and block abusive ads), automatic events such as the App being opened, and counts of how the App's tools are used (for example which tool was used, how many items a scan found and their total size, and whether a permission was granted). Events never contain file names, paths, notification content or app names. Firebase Analytics also creates an app instance identifier for this installation. Analytics collection is switched off when the App starts and is switched on only after the consent step allows it (section 4).
• (d) Crash reports. The App uses Firebase Crashlytics (Google) to receive crash reports. A report can include the type and message of the error, the stack trace, the state of the device at the time of the crash, the device model, Android version and App version, and an installation identifier created by Crashlytics. Before a crash report is sent, the App removes file paths and file addresses (such as file:// and content:// links) from the error message. This cannot catch every possible piece of text, so in rare cases a crash report may still contain a file name or text added by other software. Crash reporting is switched off when the App starts and is switched on only after the consent step allows it.
• (e) Remote configuration. The App uses Firebase Remote Config (Google) to fetch settings, for example which ads and notifications are switched on, how often suggestions may be shown and how the storage overview bar behaves. This can happen as soon as the App starts, before the consent step has a result. The request includes technical information such as your country, language, Android version and App version.