PRIVACY POLICY - POCKET FILE CLEANUP
Last updated: November 7, 2026
Contact: vtbtsoft@gmail.com
This policy describes the data handling implemented in Pocket File Cleanup. The app includes local storage-management features, Google Mobile Ads, the Google User Messaging Platform (UMP), and Firebase Remote Config. Advertising behavior depends on the distributed version and its configuration.
1. Files and local storage tools
With your permission, the app reads files in shared device storage, including names, paths, sizes, modification dates and image information. It uses this information to scan for unnecessary or duplicate files, compare photos, display previews, and carry out file actions you select. File hashes and photo comparisons are computed on the device. The app's own storage and photo-analysis code does not upload the contents of your files or photos to a server.
Opening or sharing a file with another app gives the chosen app access to that selected file through Android. That app's handling is governed by its own policy. Rename, deletion, trash and restore actions change files on your device. Permanent deletion and emptying the trash cannot be undone.
2. Installed apps, usage and device information
The app can read the installed-app inventory, package information, requested permissions and APK hashes for local app management and risk checks. If you grant usage access, it also reads app-usage information and available app/cache sizes to display usage-based tools. Battery status, charging information, storage totals and device specifications are read from Android.
Risk checks use locally available indicators. A configured service may supply a signed malware-hash list by HTTPS. The app does not upload your app inventory or APK hashes through that list-download code. The current build has no malware-list download address configured.
3. Notifications and reminders
Notification access is optional. When you grant it, Android allows the notification-listener service to receive notification content. The app uses the app name, title, time and notification identifiers needed to clear or hide notifications you choose. Hidden-notification history stores the app name, masked title and time; it does not store message bodies. Sequences of four to eight digits in stored titles are masked. Hidden history is retained for up to seven days and cleaned during maintenance.
Notification permission allows reminders and alerts you enable, including cleanup and charging reminders. You can turn these features off and revoke notification access in Android Settings.
4. Permissions
All-files access, or applicable older Android storage permissions, supports scanning and file management. Usage access supports app-size and usage tools. Package visibility supports installed-app review. Notification access supports notification management, and notification permission supports alerts. Uninstall requests open Android's confirmation flow. Internet access supports Remote Config, configured list downloads and advertising SDK services. The app does not request camera or microphone permissions.
5. Google Mobile Ads and UMP
The app includes Google's advertising and consent SDKs. When advertising is enabled and the SDKs operate, Google may process IP addresses, advertising/app-set or other applicable identifiers, ad and app interactions, and diagnostic information. IP addresses may be used to estimate general location. These services support advertising, measurement and fraud prevention; behavior also depends on consent, account settings and SDK configuration.
The app checks UMP before initializing ad requests. An ad privacy choices entry appears in Settings when UMP requires it. You can also manage the Android advertising ID through system settings. The absence of a displayed ad is not a promise that the app or every included SDK processes no data.
Google SDK disclosure:
https://developers.google.com/admob/android/privacy/play-data-disclosure
Google Privacy Policy:
https://policies.google.com/privacy
6. Firebase Remote Config
Firebase Remote Config retrieves app configuration, including advertising settings. Firebase uses installation identifiers to return configuration to app instances. Requests also involve network communication with Google. Remote configuration values may be cached locally. This app does not explicitly integrate Firebase Analytics or Crashlytics, and its own code does not send custom analytics events. Included SDKs may still perform their documented diagnostic or measurement processing.
Firebase privacy information:
https://firebase.google.com/support/privacy
7. Local retention and deletion
Preferences, cleanup history, ignored-app records, risk-check reports and notification-management settings are stored locally. Cleanup records are kept for up to 90 days; the storage-freed summary uses a 30-day window. Hidden-notification records and optional trash use seven-day retention. Scheduled maintenance is best effort and may run later because of Android background-work restrictions. Risk reports and preferences may remain until replaced or local app storage is cleared.
Settings includes a Delete Pocket File Cleanup data action for cleanup history, ignore-list data, notification-management lists/history and trash. That action preserves preferences and does not necessarily remove every risk report or SDK cache. Android's clear-storage or uninstall controls remove private app storage, subject to Android behavior. Files kept in shared storage are separate and are not automatically removed merely by uninstalling the app.
Deleting local app data does not guarantee immediate deletion of data already processed by Google. Google controls the retention described in its policies; contact us about requests concerning data under the publisher's control. The app currently has no dedicated in-app request to delete a Firebase installation identifier.
8. Security
The app uses Android's private app storage for its internal records and disables Android backup for app data in its manifest. File sharing grants access to the selected file. Google documents encrypted transport for its services. No security or storage method can guarantee complete protection.
9. Children
The publisher must confirm the intended age groups and any child-directed treatment before release. Advertising and consent settings must match the published audience. Questions or concerns about a child's data can be sent to vtbtsoft@gmail.com.
10. Changes and contact
The policy may be updated when functionality or SDK data handling changes. The date above identifies this version. For privacy questions or requests, contact vtbtsoft@gmail.com.