Quick Clean: Storage Manager Privacy Policy

Effective date: October 12, 2026

1. Scope and Contact

This Policy applies to the Quick Clean: Storage Manager Android app, package com.quickclean.storagemanager. Privacy contact email: ladenappdeveloper@gmail.com.

It describes processing for file management, photo compression, recovery, battery information, app management, notification management, reminders, advertising and analytics. It does not replace feature-specific notices, system permissions or separate consent required by law. Third-party advertising pages and external websites you choose to open have their own policies.

2. Important Information

On-device file management, photo compression and notification collection involve access to device information; they do not mean that the App never reads personal data. Local content processing is different from data transmitted for advertising, push messaging and analytics.

Notification management may receive notification text containing personal information. Choose the apps you manage carefully. Access to other apps’ notifications is separate from permission for Quick Clean: Storage Manager to send its own notifications.

3. Information Used by Features

3.1 File Scanning, Cleaning and Recovery

To identify junk, large or duplicate files and similar photos, and to find or recover photos, videos, audio and documents, we access authorized file content and information such as names, locations or content identifiers, types, sizes, timestamps, image dimensions and data needed for similarity checks. Scanning and comparison run on the device. Operations you confirm may delete, copy or save files.

These features do not operate by uploading your personal file content to our servers, and do not provide your photo, video, audio or document content to advertising services. Content you deliberately share or submit through another app or support channel is handled through that separate process.

WhatsApp and TikTok cleaning processes only related local files accessible through the operating system. It does not read account passwords or imply access to private chat databases or cloud accounts. Installation status of supported apps is also used to decide whether to show relevant entries.

3.2 Photo Compression

We read the selected image and necessary size, format, dimensions and orientation information to generate a JPEG copy on the device. The original is retained and the copy is saved in device picture storage. Necessary local output records help exclude copies generated by this App from subsequent selection lists.

Compression does not require sending photos to a remote compression service. Unfinished temporary files are removed under task-cleanup rules. You can delete saved copies using your gallery or file manager. Output format, quality or metadata may differ from the original.

3.3 Battery and Device Information

We read available device data to show battery level, temperature, voltage, health, technology, design capacity and available time estimates. Storage and device-information features also use available storage totals, device model, operating system version and hardware information.

Data needed for these displays is distinct from device data processed by advertising and analytics SDKs, described in Section 4. Unavailable readings are not replaced with fabricated fixed results.

3.4 App Management and Installation Checks

We query app names, package identifiers, icons, installation times, installation-file sizes and installation status available through the operating system. These support app lists and sorting, system uninstall requests you select, notification-management settings and relevant cleaning entries or reminders.

These features do not require passwords or account content from other apps. Installation inventories needed for the features are processed on-device and are not used to build advertising profiles from sensitive app-installation information.

3.5 Notification Management

After you explicitly grant notification access in system settings and enable management, the service may receive eligible notifications from other apps in the background. Accessible fields include the source app, notification identifier, time, and system-provided titles, message text, expanded text or messaging content. They may contain sender details, message previews or other sensitive information.

Our collection logic uses time and text fields to generate an on-device content digest to recognize duplicate posts or changed content. Local records contain notification identifiers, source package and app names, collection times and content digests, not the original notification titles or text. Generating a digest does not mean that a record is treated as fully anonymous.

Original notification text is not used for advertising, uploaded to our analytics services or written to business analytics logs. We save management records before attempting to remove eligible system notifications; this does not delete messages in source apps. Protected or unreliably classified notifications should not be automatically collected or removed.

You can disable the main switch, disable individual apps or revoke notification access. Revocation stops further collection but does not automatically erase earlier records; use the feature’s clearing action to remove them. New or updated records arriving during clearing may remain. Uninstalling a source app does not automatically delete existing records.

3.6 Our Reminders, Push Messages and Toolbars

With necessary notification permission and system conditions, we may show cleanup reminders, feature prompts, charging or battery prompts, and toolbars. Trigger checks may involve foreground/background state, charging state, battery level, supported app installation or removal, new screenshots, cleaning-task status and earlier notification displays or interactions.

We retain necessary local configuration, timestamps and counts to schedule reminders, prevent duplicates and apply frequency limits. Device restart or app updates may reactivate configured background capabilities, subject to system permissions and restrictions.

Firebase Cloud Messaging (FCM) processes installation identifiers and push tokens to deliver messages. We also send push tokens to our event service and Adjust for push association, installation or uninstall measurement, and troubleshooting. A token is not notification text, but can be associated with an app installation. Turning visible notifications off does not necessarily delete tokens or stop all analytics; see Section 8 for data requests.

3.7 Settings, Feedback and Support

We locally store language choices, feature switches, permission-state records, flow progress and necessary display records to maintain your choices. If you contact support, we process the email address, description and attachments you provide to respond and investigate. Do not send passwords, verification codes or unrelated sensitive information.

4. Advertising, Analytics and Other Services

The App includes advertising and event analytics. Relevant services process device or app identifiers, advertising identifiers and their availability settings, IP addresses and approximate regions inferred from them, operating system and app versions, language, network information, installation sources, feature and ad interactions, and installation identifiers and tokens used for push messaging. Categories vary by service and your privacy choices. Recipient categories and purposes are described below.

Purposes include serving and measuring ads, attributing installations, understanding feature use, maintaining reliability, preventing advertising fraud and delivering push messages. Personalized and non-personalized advertising involve different processing; non-personalized advertising does not mean no device or network data is processed.

The App’s own features do not require direct permission for precise location, contacts, SMS databases, microphone or camera. This does not mean messages or contact information cannot appear in system-provided notification content, or replace disclosures about SDK processing.

Services and recipient categories:

(1) Google Firebase Cloud Messaging: push delivery using installation identifiers and push tokens. Policy: https://firebase.google.com/support/privacy

(2) Google Analytics for Firebase: usage and effectiveness analysis using app-instance identifiers, device/app information, and feature and advertising interaction events. Google Policy: https://policies.google.com/privacy

(3) Adjust: installation attribution, advertising-effectiveness and uninstall measurement using push tokens and applicable device/advertising identifiers, installation sources and interaction events. Policy: https://www.adjust.com/terms/privacy-policy/

(4) Our event service: configured business events, installation/session identifiers and push tokens for feature usage, campaign and push measurement and troubleshooting. Send related personal-data requests to ladenappdeveloper@gmail.com.

(5) Advertising mediation and ad networks: TopOn/HyperBid-related mediation components connect advertising services. Participating networks may receive advertising identifiers, IP addresses, device/app information and ad request, impression and click data to deliver and measure ads and prevent fraud. Ads may link to advertisers’ sites or apps, which have their own policies. Contact us for information about applicable advertising providers and processing activities.

(6) Google Play Install Referrer and advertising-identifier components: provide installation sources and available advertising identifiers to the applicable attribution and advertising services described above. Google Policy: https://policies.google.com/privacy

Providers may process data on our instructions or, where permitted by law, under their own privacy policies. We remain responsible for our App’s practices as required by law. Provider policies do not replace this Policy.

We do not sell personal files or original notification text as commodities or provide that content to advertisers for targeted advertising. Disclosing device/advertising identifiers and interaction data to advertising partners may constitute a “sale,” “sharing” or targeted advertising under some US state laws. You may submit applicable opt-out requests under Section 8. Receiving no payment for data does not by itself mean there is no legal sale or sharing.

5. Conditions for Processing and Disclosure

We process information for the purposes described in this Policy. Where EEA or UK data-protection rules apply, processing necessary to provide the service you request is based on performance of a contract; necessary security, abuse prevention, troubleshooting and service improvements rely on legitimate interests where those interests are not overridden by your rights; advertising, tracking and analytics that require consent rely on consent; and legally required retention or valid legal demands rely on legal obligations. Using the App, granting notification permission or contractual necessity is not blanket consent for all advertising and analytics.

In addition to disclosed providers, we may provide relevant information where necessary to meet legal obligations, respond to valid legal process or protect security and lawful rights. In a merger, acquisition or business transfer, we will provide legally required notice and protections, not use the transaction to arbitrarily change processing purposes.

If we propose an incompatible new use, we will provide notice and obtain any required consent.

6. Retention and Deletion

Local notification records remain until you clear them, clear App data or uninstall the App. Revoking access or uninstalling the source app does not automatically remove them. Settings, flow states and output indexes remain until overwritten, reset or cleared with App data. Original images, compressed copies and recovered files in shared storage may remain after uninstalling and must be deleted separately.

Server records are retained using these criteria: event and analytics records until the relevant measurement, troubleshooting or security purpose is complete; advertising and attribution records for the period necessary for measurement, reconciliation and fraud prevention; push identifiers until no longer needed for delivery and association or an effective deletion request is executed; and support correspondence until the issue and necessary follow-up are resolved. Retention also considers sensitivity, purpose, unresolved disputes and legal requirements. Data no longer needed is deleted or de-identified. Backup data is removed according to applicable backup cycles, and legally retained data is used only for the relevant purpose. Third-party services also apply their respective retention rules.

Uninstalling the App does not automatically delete information already sent to providers. Request deletion through Section 8. We will verify information needed to locate the data, act under applicable law, and explain legal retention or identification limits. We will not require identity evidence unrelated to verifying the request.

7. Security and International Processing

We use technical and organizational measures proportionate to processing risks to protect information and require providers to protect information as required by law. No system guarantees absolute security. If a security incident occurs, we will take appropriate action and provide legally required notices.

Advertising, push and analytics services may process data outside your country, where protection rules may differ. Where transfer safeguards are required, we will use applicable mechanisms, such as valid adequacy decisions or standard contractual clauses with any necessary supplementary measures. Contact us for information about applicable processing locations and safeguards. A provider’s certification does not mean we hold the same certification.

8. Choices and Rights

Use system settings to manage file permissions, permission to send notifications and notification access. Use notification-management switches to control collection. Clearing App data or uninstalling can remove private local App data and reset settings, but does not delete shared-storage files or already-transmitted records.

Use available device advertising-privacy settings to manage advertising identifiers and personalization options; options vary by system version. To withdraw consent, stop applicable analytics, or opt out of targeted advertising or sale/sharing, email ladenappdeveloper@gmail.com. We will verify and address requests under applicable law. Device settings do not replace every provider’s opt-out mechanism, and disabling notifications does not stop all analytics.

Depending on applicable law, you may have rights to access, obtain a copy, correct, delete, restrict or object to processing, obtain portability, withdraw consent or appeal decisions. Withdrawal does not affect earlier lawful processing. Where applicable, you may complain to a data-protection authority. We will not discriminate against you for lawfully exercising privacy rights.

Request email: ladenappdeveloper@gmail.com. Identify the App, your request and necessary information that helps locate relevant records. Do not send passwords or verification codes. We may require reasonable identity verification or proof of agent authorization and will respond within applicable legal deadlines. If a lawful extension is necessary, we will explain why. If we cannot fulfil a request in full, we will explain the reasons and applicable appeal options. You may appeal to the same email address with the subject “Privacy Appeal.”

Where US state privacy laws apply, you may request access, correction, deletion or a copy of relevant data, and opt out of applicable sales, sharing or targeted advertising. You may authorize an agent as permitted by law. Where EEA or UK law applies, you may also restrict or object to processing, withdraw consent and complain to a competent data-protection authority. These rights are subject to applicable legal conditions and exceptions.

9. Children

The App is intended for a general audience, not children under 13. We do not knowingly collect children’s personal information without a required lawful basis or parental consent. Where local law imposes a higher age threshold or additional child protections, those requirements apply.

If you believe we processed a child’s information without the necessary basis, contact our privacy email. We will investigate and delete the information or take other action required by law.

10. Changes and Contact

Updates will state an effective date. We will notify you appropriately of material changes and obtain renewed consent where required. Continued use, dismissal of a prompt or a countdown does not replace affirmative consent required by law.

This is the English version provided to users. Any Chinese working translation is for internal reference. Interpretation of this document does not limit non-waivable legal rights. Contact: ladenappdeveloper@gmail.com.