Privacy Policy

Effective Date: October, 2026 Last Updated: October, 2026

Contents

Introduction
Data Controller
Data We Collect
Legal Bases
Third-Party SDKs
Permissions
Data Sharing
Data Retention
International Transfers
Your Rights
Children's Privacy
Policy Updates
Contact Us

Introduction

ClearHome (the “App,” “we,” “us,” or “our”) is an Android launcher app that provides home screen management, an app drawer, weather forecasts, storage cleaning, voice search, and a flashlight. We understand the importance of privacy and this Privacy Policy explains how we handle information about you. Please read it carefully before using the App.

This Privacy Policy applies to users worldwide and includes specific disclosures for users in the European Economic Area (EEA), the United Kingdom, and Switzerland under the GDPR/UK GDPR, and for California residents under the CCPA/CPRA.

1. Data Controller

Data Controller: ClearHome Individual Developer
Contact: support@icoddy.com
Data Protection Officer (DPO): Given that the App is operated by an individual developer and processes a limited scope of data, we are not required to appoint a DPO. For data protection matters, please contact us at the email above.
EU/UK Representative: We are currently assessing whether an EU/UK representative is required under GDPR Article 27 / UK GDPR. Until a representative is appointed, you may contact us directly at the email above.

2. Data We Collect and How We Handle It

The App is built on a “local-first” design. Except as expressly described below, the App does not collect, transmit, or store your personal information on external servers.

The App does not contain any advertising, does not integrate advertising SDKs, does not collect advertising identifiers for ad targeting, and does not share your data for advertising purposes.

2.1 Data Processed Locally

Installed apps list: app names, package names, and icons are used to display and search apps in the app drawer.
User preferences: home screen layout, hidden app settings, weather city, flashlight status, and similar settings are stored in a local database on your device.
Magnifier view: the magnifier processes camera frames in real time and does not record, save, or upload any images.
QR code scanning: QR codes are recognized locally on your device. Camera frames and scan results are not saved or uploaded.
Cleaning data: the cleaning feature only analyzes local cache files, temporary files, and metadata of app remnants. File contents are not read, uploaded, or shared.
Voice search: voice search is processed locally or through system voice services. We do not record, save, or upload your voice content.

2.2 Data Transmitted Over the Network

Weather forecasts: anonymized approximate geographic coordinates or a manually entered city name are transmitted to a weather data provider.
Bugly crash monitoring: device information, crash logs, and app runtime status are transmitted to Bugly SDK.
AppsFlyer attribution: device identifiers (GAID), install events, and in-app events are transmitted to AppsFlyer SDK.
Sensors Analytics behavioral analysis: device identifiers, device hardware information, operating system information, network information, app information, and user interaction events are transmitted to Sensors Analytics SDK.

3. Legal Bases for Processing (EEA/UK/Switzerland)

If you are located in the EEA, the UK, or Switzerland, our legal bases for processing your personal data are as follows:

Processing Activity	Data Types	Legal Basis	Notes
Crash monitoring (Bugly)	Device information, crash logs	Legitimate interests (GDPR Art. 6(1)(f))	Ensuring app stability is our legitimate business interest and does not override your data protection rights. Processing is necessary to diagnose and fix crashes.
Attribution analysis (AppsFlyer)	GAID, install events, in-app events	Consent (GDPR Art. 6(1)(a))	We initialize the AppsFlyer SDK only after obtaining your explicit consent. You have the right to withdraw consent at any time.
Behavioral analysis (Sensors Analytics)	Device identifiers, interaction events	Consent (GDPR Art. 6(1)(a))	We initialize the Sensors Analytics SDK only after obtaining your explicit consent. You have the right to withdraw consent at any time.
Weather forecasts	Approximate location or city name	Consent (GDPR Art. 6(1)(a))	Processing occurs only after you enable the weather feature and grant location permission.

Where we rely on legitimate interests, we have carried out a Legitimate Interests Assessment (LIA) and confirmed that our interests do not override your data protection rights. You may request a summary of the LIA by contacting us.

4. Third-Party SDKs

To comply with Google Play’s Data Safety requirements and applicable laws, we disclose the third-party SDKs integrated into the App, the data they collect, and how that data is used.

4.1 Bugly SDK

Provider: Shenzhen Tencent Computer Systems Company Limited
Purpose: Monitor crashes and app stability, collect and analyze app quality and performance data, and help improve stability.
Data Collected: Phone model, brand, Android version, Android API level, manufacturer system version, CPU architecture, root status, disk space, SD card space, memory space, network type, current process name and PID, crash logs, device identifier (Android ID).
Privacy Policy: https://privacy.qq.com/document/preview/fc748b3d96224fdb825ea79e132c1a56

4.2 AppsFlyer SDK

Provider: AppsFlyer Ltd.
Purpose: Analyze install sources and marketing channel performance (attribution), and measure in-app event conversions.
Data Collected: Google Advertising ID (GAID), AppsFlyer ID, device type and model, operating system version, install events, in-app events.
Privacy Controls: Supports the anonymizeUser method to delete the device identifier (GAID) and hash the IP address. You may exercise this right by contacting us.
Privacy Policy: https://www.appsflyer.com/legal/services-privacy-policy/

4.3 Sensors Analytics SDK

Provider: Sensors Data Network Technology (Beijing) Co., Ltd.
Purpose: Collect and analyze user interaction data within the App to optimize product experience and feature design.
Data Collected: Device identifiers (Android ID, OAID, UUID, ODID, etc.), device hardware information, operating system information, network information, app information, location information (GPS location; not applicable on HarmonyOS), user interaction events.
Compliant Initialization: The Sensors Analytics SDK is initialized and begins data collection only after you consent to this Privacy Policy. Android SDK v6.0.0 and above supports delayed initialization.
Privacy Policy: https://manual.sensorsdata.cn/sa/docs/tech_sdk_client_privacy_policy

5. Permissions

The App may request the following Android permissions. All permissions are requested only when you actively enable the corresponding feature, and you can revoke them at any time in system settings. In line with Google Play’s 2026 policy updates, we request only permissions necessary for core functionality and follow the principle of incremental authorization. If you deny any non-core permission, you can still use the core launcher features of the App.

Permission (System Name)	What It Is	What We Use It For	When We Request It	What Happens If You Deny It
`QUERY_ALL_PACKAGES`	Allows the app to see which apps are installed on the phone.	The App is a launcher and needs to read the app list to display each installed app on the home screen and in the app drawer.	No prompt; takes effect automatically after installation.	App icons cannot be displayed; basic launcher functionality is unavailable.
`INTERNET`	Allows the app to connect to the network.	Loads news, weather, online icons, and other online content; reports errors to the developer to help improve the product.	No prompt; takes effect automatically after installation.	All online content fails to load.
`ACCESS_NETWORK_STATE`	Checks whether the phone is currently online and whether it is using Wi-Fi or mobile data.	Loads online content only when connected, saving data; also records network type for product optimization.	No prompt; takes effect automatically after installation.	Core features are largely unaffected; some statistical information may be incomplete.
`ACCESS_COARSE_LOCATION`	Gets your approximate location (city-level only; not for precise positioning).	The weather page automatically shows the weather for your area.	Prompted when you first use the weather feature.	Weather still works, but you need to manually select a city.
`RECORD_AUDIO`	Uses the phone microphone for recording.	Voice search in the search bar: speak to search.	Prompted when you tap the voice search button.	Voice search is unavailable; keyboard input still works.
`READ_MEDIA_IMAGES`	Reads photos from the phone gallery.	The storage cleaning feature scans photos to find duplicates and blurry large images and free up space.	Prompted when you enter the storage cleaning feature.	Cleaning cannot scan photos; other features are unaffected.
`READ_MEDIA_VIDEO`	Reads videos from the phone gallery.	The storage cleaning feature scans video files to find large videos taking up space.	Prompted when you enter the storage cleaning feature.	Cleaning cannot scan videos; other features are unaffected.
`READ_MEDIA_VISUAL_USER_SELECTED`	Android 14+ allows granting access to only “selected” photos and videos; this permission identifies what you selected.	Works with the photo/video permissions: if you grant access to only selected photos, the app can still clean the selected items.	Takes effect automatically when you choose “Select photos” in the system prompt.	No impact on other features.
`READ_EXTERNAL_STORAGE`	Legacy “read storage” permission for Android 12 and earlier; same effect as the photo/video permissions above.	On older phones, the storage cleaning feature scans photos and videos.	Prompted when entering the cleaning feature on older phones.	On older phones, cleaning cannot scan photos or videos.
`WRITE_EXTERNAL_STORAGE`	Legacy “write storage” permission for Android 9 and earlier.	On older phones, deleting photos or videos requires this permission.	Prompted when performing cleaning deletion on older phones.	On older phones, deletion cannot be completed.
`SYSTEM_ALERT_WINDOW`	Allows app windows to display above other interfaces (floating window).	When setting the default launcher, shows a small guide overlay telling you where to complete the setup.	No direct prompt; we guide you to system settings to enable it manually when needed.	No guide overlay during setup; you can still complete setup manually.
`FOREGROUND_SERVICE`	Allows the app to run a background service with a notification.	Keeps the default launcher setup guide uninterrupted.	Not a user-facing permission; no authorization required.	No impact on daily use.
`FOREGROUND_SERVICE_SPECIAL_USE`	Declares the specific purpose of the foreground service to the system; system registration only, no authorization required.	Same as above; ensures stable operation of the guide process.	No authorization required.	No impact on daily use.
`SET_ALARM`	Allows the app to open the phone’s alarm page.	Opens the system alarm directly when you tap the clock entry on the home screen.	No prompt; takes effect automatically after installation.	On some brands (e.g., Xiaomi), tapping the clock entry may not respond.
`PACKAGE_USAGE_STATS`	Provides access to app usage frequency.	The app drawer automatically organizes apps based on your frequently used apps.	No prompt; we guide you to the system “Usage Access” settings page to enable it manually when needed.	The app drawer uses your in-app tap history instead, with slightly lower accuracy.

5.2 Permissions Automatically Added by Third-Party SDKs

The following permissions are automatically added by third-party SDKs or Android development tools. These permissions generally do not require user authorization and do not show prompts. They do not affect the App’s actual functionality. Under Google Play’s Data Safety policy, developers are responsible for SDK data collection and must declare it even if the specific SDK feature is not used.

Permission	Source	Impact on You
`READ_PHONE_STATE`	Automatically added by the third-party analytics SDK (Sensors Analytics)	The App itself does not use this permission: no prompt, no reading of related information, no impact on any feature. We plan to remove it in the release version.
`com.samsung.android.mapsagent.permission.READ_APP_INFO`	Automatically added by the third-party analytics SDK (AppsFlyer)	Used to identify whether the app was preinstalled through Samsung channels. No prompt; no user awareness.
`com.google.android.gms.permission.AD_ID`	Automatically added by the third-party analytics SDK	Allows the developer to understand install results from ad campaigns. No prompt; invalidated when ad tracking is disabled in system settings.
`WAKE_LOCK`	Automatically added by Google analytics components	Ensures analytics data completes normally after network recovery; technical safeguard, no user awareness.
`ACCESS_ADSERVICES_AD_ID` / `ACCESS_ADSERVICES_ATTRIBUTION`	Automatically added by Google analytics components	Works with Android’s Privacy Sandbox to identify ad effectiveness. No prompt; no user awareness.
`BIND_GET_INSTALL_REFERRER_SERVICE`	Automatically added by install-referrer components	Identifies which channel the app was installed from (e.g., after clicking an ad). No prompt; no user awareness.
`DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION`	Automatically generated by Android development tools	Internal system security mechanism unrelated to app functionality; no user awareness.

About Camera Permission: If the App includes magnifier, QR scanning, or flashlight features, it will request the CAMERA permission. This permission is requested only when you actively enable the corresponding feature. Camera frames are processed locally in real time and we do not record, save, or upload any camera frames.

6. Data Sharing and Disclosure

We do not sell, rent, or trade your personal information. Information may be disclosed only in the following limited circumstances:

Service providers (processors): Anonymized approximate location or city name may be transmitted to weather data providers. Device information, crash logs, and attribution data may be transmitted to Bugly and AppsFlyer. Device identifiers, device hardware information, operating system information, network information, app information, and user interaction events may be transmitted to Sensors Analytics. We enter into data processing agreements (DPAs) with all service providers, require them to maintain equivalent privacy protections, and limit them to using the data only for the agreed purposes of providing services to us.
Legal requirements: We may disclose information as required by applicable law, regulation, or legal process.
Business transfers: In the event of a merger, acquisition, or asset sale, user information may be transferred as an asset. We will notify you and ensure the recipient remains bound by this Policy.

7. Data Retention

We retain your personal data only for as long as necessary to fulfill the purposes described in this Policy. Retention periods are as follows:

Local data: retained on your device until you clear app data or uninstall the App.
Bugly crash logs: retained by Bugly according to its privacy policy. By default, crash logs are automatically deleted or anonymized within 7 to 30 days.
AppsFlyer attribution data: retained by AppsFlyer according to its privacy policy. Attribution data is generally retained for up to 24 months, depending on the purpose.
Sensors Analytics behavioral data: retained by Sensors Analytics according to its privacy policy and our configuration. The default retention period is 12 months, after which data is automatically deleted or anonymized.
Weather data: weather cache data is retained locally on your device for a short period, typically updated or cleared within a few hours to 1 day.

When the retention period expires or the processing purpose is fulfilled, we will delete or anonymize your personal data. If deletion is not possible (for example, data stored in backup systems), we will securely store your personal data and isolate it from any further processing until deletion is possible.

8. International Data Transfers

Our service providers may be located outside your country or region. When we transfer your personal data to countries outside the EEA/UK/Switzerland, we ensure appropriate safeguards, including:

Standard Contractual Clauses (SCCs): Our contracts with service providers include the SCCs approved by the European Commission to ensure a level of protection equivalent to the GDPR.
Adequacy decisions: Where the destination country has received an adequacy decision from the European Commission, we rely on that decision.
UK International Data Transfer Addendum: For transfers subject to UK GDPR, we rely on the UK IDTA where applicable.
Swiss Addendum: For transfers subject to the Swiss FADP, we rely on the Swiss Addendum to the SCCs where applicable.
Other lawful mechanisms: Where applicable, we may rely on exceptions under GDPR Article 49 (such as your explicit consent).

For more information about the specific safeguards we use, please contact us at the email below.

9. Your Rights

9.1 EEA/UK/Swiss Users (GDPR/UK GDPR)

If you are located in the EEA, the UK, or Switzerland, you have the following data subject rights:

Right of access: You have the right to obtain a copy of the personal data we hold about you.
Right to rectification: You have the right to request correction of inaccurate or incomplete personal data.
Right to erasure (right to be forgotten): You have the right to request deletion of your personal data.
Right to restriction of processing: You have the right to request restriction of processing of your personal data.
Right to data portability: You have the right to receive your personal data in a structured, commonly used, and machine-readable format and to transmit it to another controller.
Right to object: You have the right to object to processing based on legitimate interests.
Right to withdraw consent: Where processing is based on your consent, you have the right to withdraw consent at any time. Withdrawal does not affect the lawfulness of processing based on consent before withdrawal.
Right to lodge a complaint: You have the right to lodge a complaint with the supervisory authority in your member state.

You may exercise these rights by contacting support@icoddy.com. We will respond within 30 days of receiving your request. If necessary, this period may be extended by 60 days, and we will inform you of the reason for the extension.

9.2 California Residents (CCPA/CPRA)

If you are a California resident, you have the following rights:

Right to know: You have the right to request that we disclose the categories and specific pieces of personal information we have collected, used, shared, or sold about you over the past 12 months.
Right to delete: You have the right to request deletion of personal information we have collected about you (subject to certain exceptions).
Right to correct: You have the right to request correction of inaccurate personal information.
Right to opt out: You have the right to opt out of the “sale” or “sharing” of personal information. We do not sell or share your personal information.
Right to limit use of sensitive personal information: You have the right to limit the use and disclosure of sensitive personal information. We collect sensitive personal information (such as precise location) only to provide the weather feature and do not use it for other purposes.
Right to non-discrimination: We will not discriminate against you for exercising your privacy rights.

You may submit CCPA/CPRA requests by contacting support@icoddy.com. We will respond within 45 days of receiving your request. If necessary, this period may be extended by 45 days, and we will inform you of the reason for the extension.

In accordance with CCPA regulations effective January 1, 2026, we ensure that:

The opt-out process is no more complex than the opt-in process, with symmetrical steps.
Closing a pop-up, clicking outside, or navigating away is not treated as consent.
Consent options are presented symmetrically, with “Yes” and “No” buttons of equal size, color, and prominence.

We also honor Global Privacy Control (GPC) signals. If your browser or extension sends a GPC signal, we will treat it as a valid opt-out request.

9.3 All Other Users

Regardless of your location, you may:

Request anonymization of data collected by AppsFlyer (via the anonymizeUser method);
Withdraw consent for optional data processing by revoking permissions or disabling the corresponding feature;
File a complaint with us about our data processing practices.

10. Children's Privacy

The App is not directed to children under 16 in the EEA/UK/Switzerland, or under 13 in other regions. We do not knowingly collect personal information from children. If you believe we have inadvertently collected information from a child, please contact us at the email below and we will delete it promptly.

If we learn that we have collected personal information from a child under the applicable age, we will take reasonable steps to delete that information as soon as possible. If you are a parent or guardian and believe your child has provided personal information to us, please contact support@icoddy.com.

11. Updates to This Policy

We may update this Policy from time to time. Material changes will be communicated via in-app notice or an updated policy page. We encourage you to review this Policy periodically. If changes affect how we use your personal data or your rights, we will notify you prominently before the changes take effect.

For EEA/UK users, if changes involve consent-based processing, we will seek your consent again. For California residents, if changes involve the categories of personal information or purposes of use, we will update this Policy and notify you.

12. Contact Us

For any privacy-related questions, data subject requests, or complaints, please contact:

Email: support@icoddy.com

We will respond as soon as possible. For GDPR requests, we respond within 30 days; for CCPA/CPRA requests, we respond within 45 days.