1. Developer and Privacy Contact Information

The data controller or developer responsible for processing data:

• Developer Name: Zentro Studio

• Contact Email: alltasks.tachmet@gmail.com

2. Information We Process

The Application follows the principle of data minimization and processes relevant information only to the extent necessary to provide device security and cleaning and management features and to ensure the proper operation of the Application. The types of data processed by each feature module and the applicable processing methods are described below.

2.1 Device, System, and Network Information

To ensure the proper operation, system security, performance maintenance, and functional optimization of the Application, the Application and its integrated third-party services process necessary device, system, and technical information.

Types of information: Such technical information includes device and operating system environment parameters, Application version, language and regional settings, network connection status, technical diagnostic information, crash and performance data, technical identifiers related to push notifications, advertising identifiers such as the AD_ID, and basic Application interaction events.

Purposes of use: This information is used to maintain the Application’s basic functionality and stability, diagnose and resolve technical issues, deliver necessary notifications, optimize user experience, support data analytics and attribution, identify and prevent fraud or abuse, and manage in-app advertising and remote configuration.

Processing mechanism: Relevant technical data is processed strictly in accordance with the operational requirements of the Application and the specifications of the integrated third-party SDKs, subject to your system permissions and privacy settings.

2.2 File and Storage Information

When you actively use features such as junk cleaning, storage analysis, large-file identification, media cleaning for photos, videos, audio files, or documents, or compression, and grant the corresponding storage or media access permissions, the Application locally processes the necessary file attributes and metadata.

Scope of information processed: This includes basic file attributes, such as file name, file type, file size, and creation or modification time, as well as information concerning storage space usage.

Purposes of use: This information is used solely to identify unnecessary files and large files, calculate storage usage, generate cleaning recommendations, display scanning results, and perform the file processing or photo compression operations selected by you.

Local processing and zero-upload principle:

• Entirely local operation: Storage scanning, file analysis, photo compression, and related calculations are performed entirely on your device. The Application does not transmit or upload the contents of your private files, photos, videos, audio files, or documents to our servers.

• User-initiated decisions: The Application never automatically deletes or modifies any of your files. All file deletion, cleaning, or processing of original images following compression is performed only after you actively initiate and confirm the relevant operation.

2.3 Installed Applications and Application Usage Information

When you actively use features such as application management, storage cleaning, App Lock, or virus scanning and grant the corresponding permissions, such as access to the application list or usage access, the Application locally processes basic information and operating status relating to installed applications.

Scope of information processed: This includes basic identifiers and attributes of installed applications, such as application name, package name, version number, installation time, application size, and installation status.

Purposes of use: This information is used solely to generate an application management list, assist you in selecting, managing, or uninstalling applications, configure App Lock protection, identify unnecessary applications to provide storage-cleaning recommendations, and perform application security risk detection.

Local processing and security comparison standards:

• Entirely local operation: Core features such as displaying and managing the application list, storage analysis, and App Lock protection operate entirely on your device. The Application does not upload your installed application list to our servers.

• Cloud-based security comparison: When you initiate a virus security scan, necessary application security-related technical characteristics, such as package names, file hash values, and signatures, are transmitted in encrypted form to the Trustlook CloudScan service for comparison. For details regarding the applicable mechanisms and privacy standards, please refer to the description of third-party SDKs in Section 6 of this Policy.

• Permission controls: Access to installed application information depends entirely on your authorization. If you do not grant or subsequently revoke the relevant permissions, features related to application management, App Lock, or virus scanning will not function properly.

2.4 Virus and Malware Scanning

When you actively initiate a virus scan or security check, the Application and the Trustlook security component process necessary application security-related technical information to identify potential security risks.

• Data processing and comparison: To determine whether an application is safe, the scanning process extracts basic characteristics of installed applications, such as application package names, file hash values, and signature data, and compares them against the Trustlook CloudScan cloud-based security database.

• Nature and limitations of the data: The data processed consists solely of technical characteristic parameters used for security identification. It does not include your photos, private files, chat records, contacts, or other private personal content and is used solely for security detection purposes.

• Third-party policy: Cloud-based security detection is provided by Trustlook. For specific data processing rules, please refer to the Trustlook Privacy Policy.

2.5 Notification Information

When you enable the notification management feature and grant notification access in your system settings, the Application locally processes necessary notification information and associated metadata.

• Purpose of use: This information is used solely to provide notification organization, notification filtering, message cleaning, notification reminders, and other management features that you choose to enable.

• Local processing and privacy protection:

• Entirely local processing: All notification content and filtering rules are processed entirely on your device. The Application does not upload, store, or transmit your notification content, such as chat messages, SMS previews, or private reminders, to our servers.

• User control: You may revoke notification access at any time through the Android system settings. Revoking this permission affects only notification cleaning and management features and does not affect the Application’s other basic features.

2.6 App Lock Information

When you actively enable the App Lock feature and grant the corresponding system permissions, the Application locally processes necessary application protection configurations and operating-status information.

• Purpose of use: This information is used solely to identify protected applications, verify unlock status, and provide locking protection when a protected application is opened.

• Local storage: Your App Lock password, list of locked applications, and related protection configurations are stored and processed entirely on your device. The Application does not upload your password or App Lock configurations to our servers.

• Service operation and user control: To ensure that locking protection operates in real time, the Application may run necessary local protection services in the background. You may disable App Lock, revoke the relevant system permissions, stop the protection service, or uninstall the Application at any time.

2.7 Battery, Storage, and Device Status

When you use device management or cleaning tools, the Application locally reads necessary device operating-status and storage information.

• Purpose of use: This information is used solely to display system storage usage, provide junk-cleaning recommendations, display battery status, and provide related device tools.

• Local operation: The device-status and storage-analysis data described above is processed and displayed only locally on your device. The Application does not upload such local device operating-status information to our servers.

• Third-party technical data: Third-party SDKs used for advertising, data analytics, or crash diagnostics may process basic device technical parameters in accordance with applicable law. For specific processing rules, please refer to the description of third-party services in Section 6 of this Policy.

2.8 Reminders and Background Processing

When you actively enable certain features, such as real-time security protection or App Lock, and grant the corresponding system permissions, the Application runs necessary system services in the background to ensure the real-time availability and continuity of the relevant security protection and management features.

Purposes and necessity of operation:

• Real-time security protection: When you manually enable security protection, background services are used to monitor newly installed applications or files in real time for security risks and to protect against malware threats.

• Real-time App Lock and notification management: Background services are used to trigger App Lock immediately when you open a protected application or to provide real-time notification organization.

Local processing and zero upload:

Background services process only the local device-status data necessary to implement the security and management features described above. All calculations and determinations are performed entirely on your device. The Application does not upload data involved in background processing to cloud servers.

User control: Background services operate only when actively enabled by you. You may disable real-time protection or App Lock or revoke the relevant system permissions at any time.

2.9 Network Speed Testing

When you actively initiate a network speed test, the Application and its integrated third-party speed-testing services process necessary network connection-related technical information to evaluate the performance of your current network.

• Purpose of use and scope of data: The speed-testing process is used solely to measure network latency, connection quality, and upload and download speeds. Temporary test traffic and data generated during the speed test do not contain and are not used to access your photos, personal files, or private communications.

• To complete network connection and performance testing, technical testing nodes must be provided by third-party network service providers, such as Cloudflare, Measurement Lab, and OVHcloud. Relevant network technical parameters, such as IP addresses and request logs, are independently processed by those third-party service providers in accordance with their respective privacy policies. (https://www.cloudflare.com/privacypolicy/, https://www.measurementlab.net/privacy/, https://www.ovhcloud.com/en/terms-and-conditions/privacy-policy/)

3. How Information Is Obtained

3.1 User-Initiated Operations

When you actively use a feature or interact with the Application, the Application processes relevant information only to the extent necessary to implement the corresponding feature. Such operations include:

• Initiating scanning, checking, cleaning, or network speed-testing features;

• Selecting and confirming the processing of specific files, media, or applications;

• Confirming cleaning, deletion, or other device-management instructions;

• Enabling App Lock, security protection, or notification management features; and

• Adjusting advertising, privacy, or other relevant preference settings within the Application.

3.2 Android Permissions and System Interfaces

To implement specific features, the Application obtains necessary data through standard Android system interfaces after you provide explicit authorization, such as file access, installed application lists, usage access, or notification access. The Application strictly follows the principle of permission minimization, and the actual scope of processing is limited by your specific authorization and the relevant system mechanisms. You may revoke the relevant permissions at any time through the system settings.

3.3 Automatic Processing by Third-Party SDKs

Third-party SDKs integrated into the Application, such as SDKs for advertising, data analytics, crash diagnostics, and security services, automatically process necessary device and technical information while the Application is running. In regions where user consent is required, such as under UMP or GDPR mechanisms, data processing is performed strictly in accordance with your privacy choices. The specific data processing practices of third parties are independently governed by their respective privacy policies, as further described in Section 6.

4. Purposes for Which Information Is Used

The Application processes relevant information solely to provide its core features, optimize the service experience, and protect system security. The specific purposes are as follows.

Core features and services

• Feature provision and display: Display system storage and device status, generate cleaning recommendations, perform network speed tests, and display management results;

• Execution of user instructions: Perform the file cleaning, media compression, application management, or related processing selected and explicitly instructed by you;

• Real-time protection and security: Support real-time security scanning, App Lock protection, and notification organization features actively enabled by you; and

• Local storage of settings: Store your App Lock configurations, reminder settings, and related preferences locally on your device.

System operation and service optimization implemented by third-party SDKs

• Performance and stability: Analyze crash logs and technical errors to correct Application defects and improve compatibility;

• Advertising and promotional services: Display advertisements and evaluate advertisement impressions and conversions; and

• Security and anti-fraud: Identify abnormal access and malicious traffic to protect the technical security of the Application and the advertising ecosystem.

• The specific data processing practices of the relevant third-party SDKs are governed by their respective privacy policies, as further described in Section 6.

Processing and protection of sensitive content

• Your personal files, photos, videos, audio files, communication records, and notification content are used only on your device for the corresponding features actively initiated by you, such as cleaning or locking. Such private personal content is not used for any purpose unrelated to the relevant feature and is not uploaded to any server.

5. Android Permissions and System Access

To provide certain Application features, the Application may use permissions and special access provided by the Android system, depending on the specific feature, Android version, and your choices. Relevant permissions are used only when required by the corresponding feature.

5.1 Network Access

To support network connectivity and assess the network environment, the Application requests network access and network-status permissions for core and auxiliary features that require an internet connection.

• INTERNET (network access permission): Used to support data interactions between the Application and servers, including network speed testing, virus database synchronization, advertisement loading, and basic services required for Application operation.

• ACCESS_NETWORK_STATE and ACCESS_WIFI_STATE (network and Wi-Fi status permissions): Used to help detect the current network connection type and availability.

Network-status checks are used solely to determine network availability and connection quality and are not used to collect your private personal data.

5.2 Notification Permission

To provide you with timely information regarding security status, feature-operation results, and important service updates, the Application requests permission to send notifications (android.permission.POST_NOTIFICATIONS) and integrates Firebase Cloud Messaging (FCM).

Purposes of use:

• Local and service reminders: Used to display virus-scanning results, security alerts, App Lock status notifications, and application management results locally on your device.

• FCM cloud push notifications: Used to send necessary update reminders, important service notifications, and feature-status changes to your device through FCM.

Data security and transmission commitments:

• FCM Token processing: To successfully deliver cloud messages to your device, FCM generates and uses an anonymous device push identifier known as an FCM Token. This Token is used solely for message addressing, is not associated with personally identifiable information (PII), and is not used for unlawful cross-application tracking.

• Transmission security: All cloud push messages are transmitted using encrypted transmission protocols, such as HTTPS/TLS, to protect the security of communications.

Permission controls: This permission must be actively granted by you. You may disable it at any time by navigating to the system settings (“System Settings → Apps → Notifications”). If you disable notification permission, local reminders and FCM cloud push notifications will no longer be displayed, but the Application’s other basic features will remain available.

5.3 File and Media Access

To support core features such as file scanning and storage-space cleaning, the Application requests file-access capabilities appropriate to the applicable Android system version.

Types of permissions used:

• Basic storage permissions (READ_EXTERNAL_STORAGE / WRITE_EXTERNAL_STORAGE): Applicable to earlier versions of Android and used to read and clean unnecessary temporary files.

• All files access permission (MANAGE_EXTERNAL_STORAGE): On Android 11 and later, used solely to provide the core device storage-cleaning feature actively initiated by you. The Application retrieves only necessary file attributes locally on your device and never collects or uploads your private personal files.

Purposes and mechanisms of use:

• When you actively initiate file scanning, storage analysis, or junk cleaning, the Application reads the files and directories necessary to perform the relevant feature.

Data security and privacy commitments:

• Local processing: All scanning, analysis, and cleaning of files and media content is performed entirely on your device. The Application does not upload any of your personal files, photos, or documents to cloud servers or share them with any third party.

• Limited scope: The Application reads and processes only the files necessary to provide the security and cleaning features described above and does not collect personal or private data contained in file contents.

Permission controls and revocation: These permissions must be granted by you through the system settings or a permission prompt. You may revoke them at any time through the system settings. After revocation, cleaning and scanning features that depend on storage access will cease to function, but the Application’s other basic features will remain available.

5.4 Visibility of Installed Applications

To provide device security checks, malicious-application detection, and application management features, the Application requests permission to query all installed applications (android.permission.QUERY_ALL_PACKAGES).

Purposes and use scenarios:

• Virus scanning: Used to read the list of applications installed on the device and determine whether malware, high-risk applications, or abnormal behavior that may threaten device security is present.

• Application management: Used to display the device’s application list and storage usage and assist you in managing and cleaning applications.

Third-party SDK processing and cloud data transmission:

When you actively initiate a security scan, the integrated third-party Trustlook SDK processes technical application-characteristic data, such as application package names and hash values, and compares it against the Trustlook cloud-based security database to return security-scanning results. The Trustlook SDK’s processing and transmission of this technical data, together with the applicable security safeguards, are governed by its own privacy policy. For details, please refer to the Trustlook Privacy Policy.

Permission controls: Application security scanning and management services depend on identifying the installation status of applications on your device. You may disable the relevant services within the Application at any time.

5.5 Usage Access

To provide core features such as App Lock, application usage statistics, and application management, the Application requests the android.permission.PACKAGE_USAGE_STATS permission.

• Purpose of use: This permission is used solely to identify the foreground application for App Lock security protection, calculate the duration and frequency of application usage, and assist you in identifying and managing applications on your device.

• Data processing and privacy: Usage statistics obtained through this permission are analyzed and processed only locally on your device. They are not used for user profiling, cross-application tracking, or advertising, and are not uploaded to any server or sold to any third party.

• Permission controls: This is a special Android system permission that must be actively enabled by you through the system settings. You may revoke it at any time through the system settings. After revocation, App Lock, usage statistics, and related features will not function properly, but the Application’s other basic features will remain available.

5.6 Notification Access

To provide notification management and unwanted-notification blocking services, the Application requests notification access (android.permission.BIND_NOTIFICATION_LISTENER_SERVICE).

• Activation mechanism and user control: The Application does not proactively or automatically intercept notifications from any application. Notification blocking and management apply only to specific applications after you manually enable notification access through the system settings and manually add or select those applications within the Application.

• Purpose of use: This permission is used solely to clean, organize, and provide reminders for notifications from applications actively selected by you, helping to keep the status bar organized.

• Local processing: The Application identifies notification titles and text only locally on your device for filtering purposes. All notification information is processed entirely on your device and is not uploaded to any server.

• Permission revocation: You may revoke this permission at any time through the system settings (“Settings → Special Access → Notification Access”) or remove applications from the blocking list within the Application at any time.

5.7 Display Over Other Apps Permission (System Alert Window Notice)

The Application requests the android.permission.SYSTEM_ALERT_WINDOW special access permission to support the core App Lock security protection service.

• Specific use scenario:

• When the Application detects that a locked application is launching or is in the foreground, it immediately displays the App Lock interface over that application to prevent unauthorized access to your private applications.

• Strict privacy and security compliance commitments:

• Unlock protection only: The overlay is displayed only when App Lock is active and does not contain any third-party advertisements or unrelated notices.

• No interface hijacking or keystroke logging: The Application receives unlock input only through its own unlock interface. It never uses overlay technology to intercept, record, or view input fields, passwords, or private pages in other applications.

• Local verification: Unlock credentials are verified entirely on your device. The Application does not upload your unlock password or operation records to any cloud server.

• User autonomy:

• This permission is entirely under your control. You may revoke it through the system settings or disable the App Lock feature within the Application at any time.

5.8 Foreground Services

To ensure that the real-time security protection and App Lock features actively enabled by you continue to operate reliably in the background and are not inadvertently terminated by the system’s background-management mechanisms, the Application requests and uses foreground service permission (android.permission.FOREGROUND_SERVICE and the corresponding service types permitted by the system).

Purposes and necessity of use:

• Real-time App Lock protection: Maintains the operation of the App Lock background detection service to ensure that the unlock interface can be displayed immediately when you launch a protected application.

• Real-time security detection: Maintains the background security-monitoring service to detect newly installed applications or device security risks in real time and provide timely interception and security warnings.

Local processing and zero upload: Foreground services are used solely to maintain the local operation of the security and management features described above on your device. The services themselves do not collect or upload any of your private personal data.

User controls: Foreground services may operate when you grant notification permission or enable features such as real-time security protection or App Lock, as necessary to support the relevant functionality. You may revoke the applicable permissions through the system settings or disable the relevant features within the Application at any time.

5.9 Boot and System Events

To ensure that security protection and application management features actively enabled by you continue to function properly after the device restarts or its status changes, the Application requests the boot broadcast permission (android.permission.RECEIVE_BOOT_COMPLETED) and listens for necessary system events.

• Purposes and use scenarios: This permission is used to automatically restore App Lock and real-time virus-scanning services after the device restarts, without requiring you to manually reopen the Application. It is also used to monitor application installation and uninstallation events for new-application security scanning and App Lock list updates, as well as screen-unlock events to reactivate App Lock protection.

• Privacy and performance commitments: Relevant system events and status data are processed locally on your device and are not uploaded to any server, shared with any third party, or sold. Processing the system events required for these features does not involve collecting sensitive personal information associated with device events and is not used for advertising or cross-application tracking.

You may disable App Lock and other protection features within the Application at any time to stop the automatic operation of the relevant background services.

5.10 Battery Optimization Exemption

To ensure the continuous and stable operation of security protection features such as App Lock and real-time virus scanning, the Application requests permission to ignore battery optimizations (android.permission.REQUEST_IGNORE_BATTERY_OPTIMIZATIONS).

• Purpose of use: Android’s advanced battery-saving policies may restrict or suspend Application services running in the background. This permission is used to prevent the system from terminating App Lock and virus-scanning services in the background, ensuring that security protection is not interrupted by system background-cleaning operations.

• Local processing: Requesting this permission does not involve collecting or uploading any personal or private data.

• Permission controls: This is a special system permission that must be actively confirmed by you through a system prompt or the system settings. You may re-enable battery optimization restrictions for the Application at any time by navigating to the system settings (“System Settings → Battery → Battery Optimization”). After revocation, App Lock and real-time protection features may be delayed or cease to operate due to the system’s battery-saving policies.

5.11 Request Delete Packages Permission

To support application cleaning and uninstallation through the application management feature, the Application requests the android.permission.REQUEST_DELETE_PACKAGES permission. This permission is used to open the standard Android system uninstallation confirmation interface after you actively select and confirm that you wish to uninstall a specified application.

All uninstallation operations must be manually initiated and selected by you. The Application does not automatically or silently uninstall any application from your device in the background. The Application only initiates the system uninstallation request. The final uninstallation process depends entirely on and complies with the native Android confirmation interaction and security mechanisms and can be completed only after you confirm the operation again in the system prompt. Relevant uninstallation operations and application-list information are processed entirely locally on your device and are not uploaded to any server or used for cross-application tracking or advertising.

5.12 Advertising Identifier

To support advertisement display, data analytics, attribution statistics, and anti-fraud protection, the Application requests permission to use the Google Play services advertising identifier (com.google.android.gms.permission.AD_ID). This identifier is used to measure advertising effectiveness, analyze Application usage, and identify and prevent fraudulent activity.

• The Application strictly complies with Google Play policies governing the use of advertising identifiers. If you disable personalized advertising or reset your advertising ID through the Android system settings, the Application will stop using the identifier or automatically use the newly reset identifier.

• Data processing standards: The identifier is processed and transmitted in accordance with the principle of data minimization. It is not associated with your sensitive personal identity information and is not used for unlawful cross-application tracking outside the scope permitted by applicable policies.

6. Third-Party SDKs and Services

The project includes or is configured to use the following third-party SDKs and services. Their actual use may vary depending on the Application version, remote configuration, region, consent status, and advertising configuration.

6.1 Firebase Services (Google Firebase)

The Application integrates Firebase service components provided by Google to support application analytics, crash diagnostics, and messaging features. All data collected by Firebase SDKs is protected during transmission using standard encrypted protocols, such as HTTPS/TLS.

Components used and data processing:

• Firebase Analytics: Processes application events, interface interactions, device technical parameters, advertising identifiers (AD_ID), and diagnostic information to analyze Application performance and improve user experience.

• Firebase Crashlytics: Processes crash stack traces, device model, operating system version, Application version, and runtime diagnostic data to promptly identify and correct Application crashes.

• Firebase Cloud Messaging (FCM): Processes encrypted device push identifiers (FCM Tokens), technical parameters required for message delivery, and delivery-status information to transmit necessary security reminders and service notifications to your device.

Relevant privacy policy links:

• Firebase Privacy and Security

• Google Privacy Policy

6.2 Google Advertising Services and Privacy Choices (Google Mobile Ads and UMP)

The Application integrates the Google Mobile Ads (AdMob) SDK and Google User Messaging Platform (UMP) SDK to provide in-app advertising and regional privacy-consent management services.

Component functions and data processing:

• Google Mobile Ads (AdMob): Processes advertising identifiers (com.google.android.gms.permission.AD_ID), IP addresses used for approximate location determination and anti-fraud purposes, device technical parameters, and advertisement impression and interaction data. This information is used for advertising delivery, effectiveness measurement, anti-fraud risk control, and the display of non-personalized or personalized advertisements.

• Google UMP (User Messaging Platform): Displays privacy-choice and consent prompts to users in applicable regions, such as the European Economic Area (EEA) and the United Kingdom, and manages user authorization relating to data collection and personalized advertising. If you are located in the EEA, the United Kingdom, or another applicable region, you may access the “Privacy Policy” section of the Application’s “Settings” page at any time to reopen the consent prompt and modify or withdraw your authorization for data collection and personalized advertising.

Data security and transmission standards:

• Encrypted transmission: Data collected and transmitted by the relevant SDKs is protected using standard encrypted transmission protocols, such as HTTPS/TLS.

• User controls: You may change your authorization preferences through the privacy policy entry provided within the Application or reset or delete the advertising identifier through the Android system settings (“Settings → Google → Ads”). The Application respects the privacy choices you make through the UMP prompt or system settings.

Official policy links: Google Privacy Policy; Google Advertising Services Information

6.3 Third-Party Advertising Services

To support data analytics, advertising monetization, crash diagnostics, advertising attribution, messaging, and related service features, the Application integrates the following third-party services and SDK components:

• Google Firebase: https://policies.google.com/privacy

• AdMob (Google Ads): https://policies.google.com/privacy

• AppLovin: https://www.applovin.com/privacy/

• Pangle: https://www.pangleglobal.com/privacy

• Meta (Facebook): https://www.facebook.com/privacy/policy/

• Mintegral: https://www.mintegral.com/en/privacy

• Unity Ads: https://unity.com/legal/privacy-policy

• Liftoff: https://liftoff.io/privacy-policy/

Scope of data collection and processing: Depending on their functional requirements, the SDKs described above may automatically process the following types of information while operating:

• Advertising identifiers: Such as the Google Advertising ID (GAID/AD_ID);

• Device and system information: Such as device model, operating system version, and screen resolution;

• Network and connection data: Such as IP addresses used for approximate location identification and anti-fraud purposes; and

• Application interaction data: Such as Application usage events, crash logs, and advertisement impression and click records.

Purposes of processing: The data described above is primarily used for the following compliant purposes:

• Delivering and optimizing in-app advertisements;

• Advertising attribution and statistical measurement;

• Identifying and preventing fraudulent activity through anti-fraud risk controls;

• Application performance monitoring, crash diagnostics, and aggregated data analytics; and

• Enabling accurate delivery of cloud messages through FCM.

Each third-party service provider independently processes data in accordance with its own published privacy policy. You are encouraged to review the links above for further details regarding their data processing practices.

6.4 Trustlook

To support device virus scanning, the Application integrates the third-party Trustlook security SDK. When a security scan is performed, the Trustlook component processes and transmits necessary application technical information, such as application package names, file hash values, and signature data, to its CloudScan servers for comparison against the cloud-based virus database and for risk identification. The transmitted data primarily consists of technical characteristic parameters used for security identification.

Trustlook’s receipt, use, and retention of relevant data are independently governed by its own privacy policy. The Application does not control the internal data processing practices of third-party servers. You are encouraged to review the Trustlook Privacy Policy for complete information regarding its data protection practices.

6.5 OpenCV

The Application uses an open-source local algorithm library, such as OpenCV, to help calculate photo blurriness or duplicate characteristics locally on your device, allowing you to identify and organize redundant images. This process is performed entirely on your device, and the algorithm library does not collect, store, or transmit any of your images or image metadata.

Processing mechanisms and data security:

• Entirely local algorithmic analysis: OpenCV is used solely as a local image-processing tool. All image feature extraction, blurriness calculations, and similarity comparisons are performed entirely on your device.

• No data upload or collection: The OpenCV library does not contain any network data-transmission components. Neither the Application nor OpenCV collects, stores, or uploads your photos or any image-feature data to cloud servers.

For specific information regarding OpenCV’s data processing mechanisms, please refer to the OpenCV Privacy Policy.

7. Information Sharing and Local Processing

The Application strictly respects and protects your privacy and follows the data processing principles described below:

• No-sale commitment: We do not sell users’ private personal information to any third party.

• Local processing: The Application’s core features, including App Lock, junk and file cleaning, media and image analysis, storage management, and notification cleaning, are calculated and processed locally on your device. Your private files, photo content, and notification information, such as SMS previews or chat messages, are not transmitted or uploaded to our servers.

• Limited scope of use: We strictly limit the purposes for which data is processed. Your private files, photos, notification content, and installed application-list information are never used for purposes unrelated to providing, supporting, or optimizing Application features.

• Necessary sharing with third parties: Only where necessary to support Application operation, advertising monetization, performance diagnostics, security protection, and effectiveness attribution may the third-party SDK components process necessary non-sensitive technical information, such as device identifiers, technical diagnostic data, and advertising interaction events. Such sharing is strictly limited to the third-party services described in Section 6 and does not include your private personal content.

8. Data Storage and Security Protection

The Application attaches great importance to data security and adopts appropriate technical and administrative measures to protect relevant information.

• Local storage and processing on the device: Most data relating to cleaning and storage-management features, such as App Lock configurations, file and junk-cleaning records, media-analysis caches, and notification-filtering rules, is stored and processed entirely on your device. We do not upload such sensitive local operation data to cloud servers.

• Security safeguards: We employ reasonable security safeguards consistent with industry standards to prevent unauthorized access, disclosure, alteration, damage, or loss of data.

• Third-party security responsibilities: Technical information that must be processed by third-party SDKs for advertising monetization, performance analytics, or security protection is protected by the relevant third-party service providers in accordance with their own security standards and privacy policies.

• User control and autonomy: You may revoke granted permissions, such as storage access, notification access, or permission to query all applications, through the Android system settings at any time, reset the system advertising identifier, or uninstall the Application to stop the relevant local data processing and use of the associated features.

9. Your Choices and Controls

• Grant or refuse optional system permissions;

• Revoke granted permissions at any time through the Android system settings;

• Disable notifications through the system settings;

• Disable special permissions, such as notification access or usage access, through the system settings;

• Clear the Application’s local data or cache through the Android system settings;

• Uninstall the Application at any time; and

• Contact us using the contact information provided in this Policy to submit applicable privacy requests.

10. International Data Transfers

If you are located in the EEEA, the United Kingdom, or another region that imposes restrictions on data transfers, certain technical data processed by our third-party providers may be transferred outside your region. Where applicable, these providers are responsible for implementing appropriate safeguards in accordance with local law, such as Standard Contractual Clauses or similar legal mechanisms, to protect the security of the data.

11. Changes to This Policy

We may revise or update this Privacy Policy from time to time. When this Privacy Policy is updated, the “Last Updated” date at the top of this page will be updated accordingly. In the event of a material or substantive change, we may notify you through an in-app notice, an explanation on the application store page, or another appropriate notification channel. You are encouraged to review this Policy periodically to remain informed of the latest privacy practices.

12. Children’s Privacy

The Application is intended primarily for a general adult audience and is not directed toward children under the age of 13, or the applicable age threshold for children under local law. We do not knowingly or intentionally collect personally identifiable information from children. If we verify that a child’s personal information has been collected without the consent of a parent or legal guardian, we will take reasonable measures to delete the relevant data as soon as possible.

13. Contact Information

If you have any questions regarding this Privacy Policy, please contact:

• Developer Name: Zentro Studio

• Contact Email: alltasks.tachmet@gmail.com