Privacy Policy for Clean Keeper

Last Updated: July 1, 2026
Effective Date: July 1, 2026

1. Introduction

Clean Keeper is developed and operated by MANGOMOBI TECHNOLOGY (HONGKONG) CO., LIMITED ("we," "our," or "the Company"). We are committed to protecting your privacy. This Privacy Policy explains how we collect, use, and safeguard your information when you use our mobile application.

By using Clean Keeper, you agree to the collection and use of information in accordance with this policy.

2. Information We Collect

This section describes the information handled by the app. Sections 2.1–2.2 describe data that is processed on your device for core cleaning features. Sections 2.3–2.6 describe data that is transmitted to third-party services (Google Firebase, Google AdMob) as part of app functionality. Section 2.7 lists categories we explicitly do NOT collect. Third-party SDKs integrated in this app may also collect device information according to their own privacy policies — see Section 5 for details.

2.1 Device Storage Information

• What we access: File names, file sizes, file types, file locations, and timestamps
• Purpose: To identify and display junk files, cache files, and large files for cleaning
• Storage: Processed on your device by Clean Keeper for cleaning features
• Data Retention: Local data is immediately deleted when you clear the app's data or uninstall the app

2.2 Device Information

• What we access and use: Device model, OS version, screen resolution, storage space, memory (RAM) usage, battery level percentage
• Purpose: To optimize app performance, display device status (including real-time memory and storage usage in the status bar notification and home screen widget, and battery level on the home screen), and include in crash reports and analytics
• Status Bar Notification: The app displays a persistent notification showing real-time memory and storage usage percentages, allowing you to monitor your device status at a glance. This notification is refreshed periodically while the app is active.
• Home Screen Widget: An optional home screen widget displays real-time storage and memory usage. Widget data is refreshed periodically and processed entirely on your device.
• Storage: Screen resolution, storage space, and memory usage are processed locally only. Device model and OS version are also included in crash reports (Section 2.3) and usage analytics (Section 2.4) transmitted to Firebase, and may be collected by AdMob as described in Section 5.
• Data Retention: Local data is immediately deleted when you clear the app's data or uninstall the app. Server-side retention follows the policies of each service provider (see Section 4.1).

2.3 Crash Reports and Diagnostics (Firebase Crashlytics)

• What we collect:
  • Crash stack traces (technical information about errors)
  • Device manufacturer and model
  • Android OS version
  • App version information
  • Crash timestamp
  • Anonymous crash session ID
• Purpose: To identify and fix crashes, improve app stability
• Service Provider: Google Firebase Crashlytics
• Data Transmission: Crash reports are transmitted to Firebase servers for analysis
• Data Retention: Firebase retains crash data for 90 days

2.4 App Usage Analytics (Firebase Analytics)

• What we collect:
  • App open events and screen views
  • Feature usage patterns
  • Session duration and frequency
  • Device information (manufacturer, model, OS version)
  • General geographic region (country/region level only)
• Purpose: Understand app usage to improve user experience
• Service Provider: Google Firebase Analytics
• Data Anonymization: Analytics data is not associated by our app with any personal identity. Firebase uses an anonymous app instance identifier (not linked to your name, email, or account).
• Data Retention: Firebase Analytics retains event-level data for 2 months
• Conversion Events: We log conversion events including privacy consent, first scan completion, first clean completion, and retention milestones (day 1/3/7) to measure app engagement.
• User Properties: We collect anonymized user properties such as device RAM tier, app language, and storage availability level to better understand our user base.
• Ad Funnel Events: We track anonymized ad lifecycle events (request, load, display, click, dismiss) per ad position to optimize ad experience.
• Ad Revenue Reporting: We report anonymized ad impression revenue data (amount in USD, ad format, precision type) to Firebase Analytics for optimization purposes. This data does not include any personal information.
• Ad Consent Status: We log an anonymized consent status event to Firebase Analytics recording whether GDPR applies in your region, the ad personalization type (personalized or non-personalized), and the consent flow completion reason and duration. This helps us monitor the consent system's health and does not include any personal identifiers.

2.5 Advertising Identifiers and Attribution Data

• What we collect (after user consent only):
  • Android Advertising ID (GAID) — collected by Google AdMob
  • Ad revenue data (impression-level revenue amount, currency, ad format)
  • Conversion events (app install, first scan, first clean, retention milestones)
• Purpose: Ad attribution, conversion measurement, and ad performance optimization
• Service Providers: Google AdMob, Firebase Analytics
• Data Transmission: Transmitted to Google servers after user consent
• User Control: You can reset or disable your Advertising ID in device Settings → Google → Ads. We gate collection of advertising identifiers and attribution data behind privacy policy consent.

2.6 Push Notification Registration Token (Firebase Cloud Messaging)

• What: An anonymous device registration token generated by the Firebase Cloud Messaging SDK to enable delivery of cleanup reminder notifications.
• Purpose: To let us send occasional invitational cleanup reminders (for example, suggesting you scan for junk files, duplicate photos, large files, or empty folders). See Section 5.6.
• How It Is Handled: The token is sent to and stored by Google Firebase to route notifications to your device. Clean Keeper operates no servers of its own and does not retrieve, store, or upload this token to any server we control, nor link it to your identity.
• Consent & Control: The token is registered only after you accept this Privacy Policy. You can stop these notifications at any time in your device's notification settings, without affecting the app's cleaning features.
• Service Provider: Google Firebase Cloud Messaging (see Section 5.6)

2.7 Information We Do NOT Collect

3. How We Use Your Information

We use the information described above for the following purposes:

• Device Status Monitoring: Display real-time memory usage, storage usage, and battery level on the home screen, status bar notification, and home screen widget
• File Cleaning: Identify junk files, cache files, temporary files, and unused APK files for cleaning
• Storage Analysis: Analyze storage usage by files and folders on your device storage
• System Optimization: Provide optimization recommendations
• Crash Analysis: Fix bugs and improve app stability
• Usage Analytics: Understand feature usage to improve user experience
• Advertising: Display advertisements via Google AdMob (personalized or non-personalized depending on your region and consent status) to support the free app
• Ad Attribution: Measure advertising campaign effectiveness and optimize ad spending (via Firebase Analytics)

4. Data Storage and Security

4.1 Data Processing Location

*Note: "NO" means Clean Keeper does not transmit this data. However, third-party SDKs (AdMob, Firebase) may collect device information like model and OS version per their own policies. See Section 5 for details.*

4.2 Security Measures

• ✓ HTTPS Encryption: All data transmitted to third-party services (Firebase, AdMob) uses HTTPS encryption
• ✓ Android Sandbox: Local data protected by Android OS security
• ✓ Local Processing: File scan results and device status readings are processed on your device by Clean Keeper for cleaning features. Third-party SDKs may collect device information per their own privacy policies (see Section 5).
• ✓ Secure Coding: Regular security reviews and updates

4.3 International Data Transfers

Data transmitted to our third-party service providers (Firebase, Google AdMob) may be processed on servers located in the United States or other countries where Google LLC operates. These providers maintain appropriate safeguards for international data transfers in compliance with applicable data protection laws. By using Clean Keeper and consenting to this Privacy Policy, you acknowledge that your data may be transferred to and processed in these locations.

4.4 Legal Basis for Processing (EEA/UK Users)

If you are located in the European Economic Area (EEA) or the United Kingdom, our legal basis for collecting and using the information described in this Privacy Policy depends on the data type:

• Consent: We process your data based on your explicit consent given when you agree to this Privacy Policy. For personalized advertising in GDPR regions, we obtain additional consent via the Google UMP consent dialog. This includes analytics data, ad attribution data, personalized ad data, and Advertising ID collection. You may withdraw consent at any time by clearing app data, uninstalling the app, or changing your ad preferences via the UMP consent dialog in Settings (GDPR regions).
• Legitimate Interest: We process crash reports to maintain and improve app stability, which is in both our and your legitimate interest.
• Contract Performance: We process local device data (files on storage, device status readings) to provide the core cleaning and optimization services you requested.

4.5 Your Rights Under GDPR and CCPA

For EEA/UK residents (GDPR): You have the right to access, rectify, erase, restrict processing, data portability, and object to processing of your personal data. You also have the right to withdraw consent at any time and to lodge a complaint with a supervisory authority.

For California residents (CCPA): You have the right to know what personal information is collected, to request deletion, and to opt out of the sale of personal information. We do not sell your personal information.

To exercise any of these rights, contact us at wd@mangolm.com. We will respond within 30 days.

5. Third-Party Services

5.1 Firebase Crashlytics (Google LLC)

• Purpose: Crash reporting and app stability monitoring
• Data Shared: Only crash-related technical data
• Privacy Policy: firebase.google.com/support/privacy

5.2 Firebase Analytics (Google LLC)

• Purpose: App usage analytics, conversion tracking, and ad performance measurement
• Data Shared: Usage events, conversion events, user properties (device tier, language, storage level), ad funnel events, and ad revenue data as described in Section 2.4. No personal identifiers are included.
• Privacy Policy: firebase.google.com/support/privacy

5.3 Google AdMob (Advertising)

• Purpose: Display advertisements to support the free app
• Ad Type: The type of ads shown depends on your region and consent status:
  • Non-GDPR regions (e.g., South Korea, Southeast Asia): Personalized ads may be shown based on your interests and activity, as managed by Google AdMob
  • GDPR/EEA regions (e.g., European countries): A consent dialog (powered by Google UMP) is shown on first launch. If you consent, personalized ads are shown; if you decline, only non-personalized ads are shown
  • If consent is unavailable (e.g., network timeout): Non-personalized ads are shown by default, equivalent to previous app versions
• Google UMP (User Messaging Platform):
  • We use Google UMP SDK to manage ad consent in compliance with GDPR and other privacy regulations
  • In GDPR regions, a consent dialog is displayed before any personalized ads are shown
  • Your consent choice is stored locally on your device following the IAB TCF v2.0 standard
  • You can change your ad preferences at any time via the app's Settings page (available in GDPR regions)
• Android Privacy Sandbox APIs: This app declares support for the following Android Privacy Sandbox APIs, which are processed by the Android operating system on your device:
  • Attribution Reporting API: Measures ad effectiveness without exposing individual user data
  • Custom Audiences API: Enables interest-based ad targeting without sharing your browsing history across apps
  • Topics API: Classifies user interests into broad categories on-device (Android 13+) for contextual ad selection
  These APIs are designed by Google to protect user privacy. Data is processed on your device by the Android system; our app does not directly access or upload this data to our servers.
• Data Collected by AdMob:
  • Android Advertising ID (GAID) — used for ad serving, personalization (when consented), and fraud prevention
  • IP address (for geographic ad targeting, country-level only)
  • General device information (model, OS version)
  • Ad revenue data per impression (reported back to Firebase Analytics for attribution)
  • User interests and interaction data (for personalized ads only, when consent is given)
• NOT Collected by our app:
  • Personal profiles or identity information
  • Browsing history outside of ad interactions
• Privacy Policy: policies.google.com/privacy

5.4 Firebase Remote Config (Google LLC)

• Purpose: Manage app operational parameters remotely, including advertisement display settings (ad placement availability, display frequency limits, ad unit identifiers) and service parameters (such as notification refresh intervals and feature availability flags). This enables us to adjust operational parameters without requiring an app update.
• Data Sent to Firebase:
  • Firebase Installation ID (anonymous app instance identifier)
  • App version and version code
  • Device model and Android OS version
  • Country/region (derived from IP address by Firebase; IP address is not stored)
• Data Received from Firebase: Operational parameters only (ad positions, display rules, frequency caps, notification refresh intervals, and feature availability flags). No personal user data is included in the configuration.
• NOT Collected: No user behavior data, no file content, and no personal information is uploaded through Remote Config.
• Fetch Frequency: Configuration is cached locally and refreshed approximately every 1 hour.
• Privacy Policy: firebase.google.com/support/privacy

5.5 Google Install Referrer (Google LLC)

• Purpose: Determine how the app was installed (e.g., which ad campaign or referral link led to the installation) for ad attribution purposes
• Data Collected: Install referrer string (contains campaign source information provided by Google Play), install timestamp, and app version
• NOT Collected: No personal information, no device identifiers, and no user behavior data
• Data Transmission: The referrer data is retrieved locally from Google Play by Firebase Analytics for attribution measurement
• Privacy Policy: policies.google.com/privacy

5.6 Firebase Cloud Messaging (Google LLC)

• Purpose: To send occasional cleanup reminder notifications (for example, suggesting you scan for junk files, duplicate photos, large files, or empty folders). These notifications are invitational only; they never promise results or include fabricated numbers.
• Registration Token: The Firebase Cloud Messaging SDK generates an anonymous device registration token that is sent to and stored by Google Firebase to enable message delivery to your device. This token is an app-instance identifier and is not linked to your name, email, or account.
• We Do NOT Upload or Store the Token: Clean Keeper operates no servers of its own. We do not retrieve, collect, store, or transmit your registration token to any server we control. We send notifications through the Firebase Console to broad audience segments (such as device language) or topics — never by collecting individual device tokens.
• Notification Only: We only send display notifications. We do not send silent/background data messages, do not use messaging to keep the app running in the background, and do not read any content from your device through this service.
• Consent Gate: Cloud Messaging is initialized only after you accept this Privacy Policy. No token is registered before your consent.
• How to Turn Off: You can disable these notifications at any time in your device's notification settings (notification channel "Cleanup tips"), without affecting the app's cleaning features.
• Privacy Policy: firebase.google.com/support/privacy

5.7 Services We Do NOT Use

• ✗ Data broker services
• ✗ Third-party user profiling services
• ✗ Sale of personal data to any third party

6. Permissions Explanation

7. Your Rights and Choices

7.1 User Consent

7.2 Your Control Options

• Access Data: View all data described above within the app interface
• Delete Local Data: Clear app data via Settings → Apps → Clean Keeper → Clear Data
• Request Server Data Deletion: Contact us at wd@mangolm.com to request deletion of any data stored on Firebase servers. We will process your request within 30 days.
• Revoke Permissions: Manage permissions via device Settings
• Opt-Out of Analytics: Clear app data or uninstall and reinstall
• Change Ad Preferences: In GDPR/EEA regions, change your personalized ad preferences via the app's Settings page (Google UMP consent dialog)
• Opt-Out of Ad Tracking: Reset or disable your Advertising ID via device Settings → Google → Ads
• Stop All Processing: Uninstall the app

7.3 Data Deletion

You have the right to request deletion of your data. Here is how each data type is handled:

After deletion, the following data may be retained in anonymized, aggregated form that cannot be linked back to you: aggregated analytics statistics (e.g., total number of app opens) and aggregated crash statistics. This aggregated data contains no personal identifiers.

8. Children's Privacy

Clean Keeper is not intended for children under 13 (or the minimum age required in your jurisdiction). We do not knowingly collect information from children. If you believe a child has provided information to us, please contact us at wd@mangolm.com for immediate deletion.

9. Changes to This Policy

We may update this Privacy Policy periodically. We will notify you of changes by updating the "Last Updated" date at the top of this page. We encourage you to review this Privacy Policy periodically for any changes. Changes to this Privacy Policy are effective when they are posted on this page. Your continued use of Clean Keeper after the updated Privacy Policy has been posted constitutes your acceptance of the changes. If you do not agree with the updated policy, you may stop using the app and uninstall it at any time.

10. Data Security Commitment

11. Contact Us

If you have questions or concerns about this Privacy Policy, please contact us:

• Email: wd@mangolm.com
• Website: https://www.mangolm.com/chanpin
• Response Time: Within 30 days