CloneX Privacy Policy

1. Information used on your device

• Installed app information: Package names, app names, icons, version information, and installation paths are used to discover apps, create clones, and refresh the app list. CloneX may retain local catalog information and icon files for faster loading. The reviewed app-discovery implementation does not upload this catalog as an analytics dataset.
• Cloned app data: CloneX stores the installation copies and working data needed by supported clones. Depending on the cloned app, this can include files, preferences, databases, cache, account sessions, messages, or other information entered or generated inside that app.
• CloneX preferences: Theme choices, clone configuration, permission-related settings, and diagnostic preferences are stored locally.

CloneX itself does not require a CloneX account. Signing in to an app running inside CloneX is separate and governed by that app’s provider.

2. Permissions and device access

CloneX uses Android permissions to provide supported features for itself and apps running inside it. Depending on your Android version and the feature used, access may include notifications, camera, microphone, audio files, network and Wi-Fi state, and permission to modify system settings. Backup and restore use the file location you choose through Android’s file interface.

Permissions are granted to CloneX at the Android host-app level; they are not independent Android permission grants for each clone. A cloned app may use the capabilities available to its host environment. You can review or revoke permissions in Android Settings. Revoking access may prevent a feature from working.

3. Diagnostic reports and support

CloneX can create a diagnostic report on your device to help investigate compatibility problems. Reports may include device and Android version information, CloneX version, timestamps, package and component names, clone configuration, technical test results, exception messages, and accessible runtime logs.

Logs may contain personal information or information produced by apps you run. Do not assume reports are anonymous or contain only device specifications. Review a report before sharing it and avoid sending passwords, authentication codes, or other sensitive information.

When you use Share diagnostic report, Android lets you choose the destination or app. That destination handles the file under its own terms and privacy policy. If you send a report or contact support, we receive the information you provide, such as your message, email address, and attachments, and use it to respond and troubleshoot.

The supplied implementation reviewed for this policy contains local report collection and manual sharing. An automatic crash-report uploader was not identified in that implementation. This policy must be updated before automatic uploads or a new collection service are introduced.

4. Backup and restore

When you create a backup, CloneX exports the selected cloned app data to a ZIP file at the location you choose. When you restore a backup, CloneX reads the selected file and restores supported data to the clone. The backup can contain personal information, account sessions, or other sensitive app data.

CloneX does not automatically upload these backups to a developer cloud service in the reviewed implementation. If you choose a cloud-storage provider or share a backup, that provider’s policies apply. Protect your backups and do not rely on the ZIP format alone to make them confidential.

5. Apps and third-party services

Apps running inside CloneX, and installed compatibility or support services they use, may send information to their own servers. This may include account details, app activity, device information, or content you provide, depending on the service and permissions available.

CloneX does not make those apps anonymous or guarantee that they do not collect data. Review each app’s privacy policy before using it. Information you choose to send through email, messaging, cloud storage, or other sharing services is also subject to those services’ policies.

6. Retention and deletion

Local cloned data is retained until removed through CloneX, Android’s app-data controls, or uninstalling CloneX, subject to Android’s storage behavior. Clearing a clone’s cache removes disposable cache; it does not delete all clone data. Use the clone’s clear-data or removal option to remove its managed working data.

Backup files and exported reports saved outside CloneX may remain after a clone is removed or CloneX is uninstalled. Delete those copies from the chosen storage location and any services to which you sent them.

Support correspondence and diagnostic reports received by the developer are retained according to this schedule: Diagnostic reports received by us are deleted within 30 days of receipt. Support correspondence is deleted within 90 days after the issue is closed. You can request earlier deletion by contacting our support email. We aim to complete deletion requests within 30 days. These periods apply to copies under our control; copies held by services you use to share information are governed by those services’ policies..

To request deletion of information you sent to us, contact the email below and provide enough information to identify your correspondence or report. Do not send additional sensitive information merely to make the request. Turning off diagnostic preferences does not delete files already exported or received.

7. Changes and website scope

We will update this page when CloneX’s information-handling practices change and revise the effective date. Where required, new collection or uses will be explained in the app before they begin.

This policy describes the CloneX Android app. The WordPress website hosting this page may use its own hosting logs, cookies, analytics, or plugins; those practices should be described separately in the website’s privacy policy.