Updated: 3 November 2026

Publisher: Aktiengesellschaft-

Support and privacy contact: gardnerdghjrz456@gmail.com

This policy describes version 1.2.0, package app.clearspace.cleaner.

Local file handling

Clutterleaf analyzes file names, sizes, metadata and contents on your device to show files, find exact duplicates and offer supported previews and visual-photo suggestions. You choose a folder or explicitly start a shared-storage scan with optional All files access on Android 11 or later. Other apps’ private data, Android/data, Android/obb and inaccessible locations are excluded. Suggestions are review candidates, not automatic deletion instructions. Access errors may prevent complete results. Visual-photo suggestions inspect up to 500 supported images; exact-duplicate discovery has no fixed file-count or folder-depth cap.

Preferences, protection rules, scan comparisons and cleanup history stay in private local storage. Local trash holds recovery copies and still uses storage until permanently purged. Uninstalling or clearing app data deletes those copies. Restore needed files first. Android app backup is disabled. Optional Usage Access reads available app usage/storage statistics locally. Android-controlled cache cleanup requires system confirmation, bypasses local trash and does not guarantee a measured saving. External document providers and apps you explicitly open have their own practices.

Installation and usage data

With data sending enabled, Clutterleaf sends an installation ID and credential, app version, locale, first-open time, installation referrer and timestamps, FCM token, a legacy push flag (always false) and Android notification permission status to the publisher over HTTPS. The credential is stored as a hash on the server. It also sends basic events for app opens, scans started/completed and confirmed permanent cleanup, including item counts and byte totals. File names, file contents, paths and detailed scan results are not uploaded. These records support acquisition measurement, basic usage analysis and FCM token registration.

Data sending starts enabled and can be disabled in Settings. This stops new app transmissions and clears pending events; an in-flight request may finish. Disabling also requests deletion of the FCM registration token. This does not automatically delete existing publisher-server records. No Google Analytics or advertising SDK is included.

Advertising attribution and the website

The website records a random visit token, an advertising click ID when supplied, traffic label (such as adv1), campaign, placement, creative, format, landing variant and visit/store-click times. It uses no cookies or third-party browser scripts. A visit token is passed through Google Play Install Referrer to link a first launch to an earlier visit within seven days. When enabled by the publisher, a conversion postback sends the advertising click ID and conversion stage to PropellerAds. FCM tokens and user files are not included in that postback.

Firebase Cloud Messaging

Firebase Cloud Messaging, provided by Google, processes installation identifiers and technical data needed to register and deliver messages. Firebase SDKs can process their own technical metadata as described at https://firebase.google.com/support/privacy and https://firebase.google.com/docs/android/play-data-disclosure. FCM is currently used only for token registration. Received data messages do not trigger actions or display notifications. The local cleaner does not depend on messaging. Local low-space reminders remain a separate optional feature and do not scan or delete files automatically.

Retention, deletion and choices

The default server retention is 90 days for events, visits and imported spending records, and 90 days since the last update for installation records. The publisher must run scheduled maintenance and apply equivalent retention to backups. Identifiers and events are not purely ephemeral. Hosting and network services necessarily receive IP addresses; the application database does not store them. Infrastructure log retention must be limited by the operator.

To request deletion of publisher-server data, disable data sending and contact support with the installation reference shown in Settings. The publisher can delete the installation and related events, attribution and queued postbacks. Uninstalling does not itself notify the publisher to delete server records. There are no user accounts. Local source files cannot be retrieved or restored by the publisher.

Security and contact

Connections to the publisher and Firebase use HTTPS. Server data and credentials are restricted to the operator. No absolute security guarantee or independent certification is claimed. Contact gardnerdghjrz456@gmail.com for privacy questions and requests. Changes to data practices will be reflected in this policy before the corresponding release.

Clutterleaf · app.clearspace.cleaner