Updated: 27 October 2026
App: CloneX: Dual App & Cloner · Android package: com.clonex.app
Developer: Save Forge (CloneX)

This policy explains how CloneX handles information when you create and manage separate instances of supported Android apps and games, use backup and restore, or choose to send diagnostic reports. Loot&Learn hosts our reporting service and this policy.

1. Information used on your device

• App information: CloneX uses app names, package names, icons, versions and installation details to show apps you can clone, create clones and manage compatibility. It may cache this information locally. Automatic reporting does not upload your complete installed-app list.
• Cloned app data: Working files can include preferences, databases, cache, saved games, account sessions, messages and other content created or used by a cloned app. These files are stored in CloneX-managed storage on your device; they are not included in automatic diagnostic reports.
• Settings: Clone configuration, theme, reporting choices and other preferences are saved locally. CloneX does not require you to create a CloneX account. Accounts used inside cloned apps belong to those services.

2. Permissions and cloned apps

CloneX requests Android access for supported features. Depending on the Android version and feature, this can include camera, microphone, contacts, approximate or precise location, audio or selected media, storage, notifications, network and Wi-Fi state, biometric checks and system settings. Android controls runtime permissions and special access. You can review or revoke them in Android Settings.

Permissions used inside CloneX are granted to the CloneX host app, rather than being independent Android grants for each clone. A cloned app may use the capabilities available in its host environment. Revoking access can prevent a feature from working. Automatic reporting itself does not require contacts, camera, microphone or location access.

Cloned apps and support services can connect to their own servers, process account information, collect activity or content, and use identifiers under their own policies. CloneX may adapt app identity and storage within the virtual environment for compatibility; this does not make a cloned app anonymous. Review the policies of the apps you run.

3. Optional automatic error reports

Automatic reporting is off by default. CloneX explains the feature before you choose to enable it, and you can use cloning features without enabling reporting. When enabled, reports may be collected and sent in the background to the developer through lootandlearn.com, including after the affected app has closed, to diagnose crashes, startup failures and compatibility problems.

Reports can contain:

• Phone manufacturer and model, Android version and processor architecture.
• CloneX version, report identifier, timestamp and limited session information.
• The affected app’s package name, when known, identifying which cloned app had a problem.
• Technical error codes, exception types, code locations, recognized missing-method signatures and available bounded native crash details.

Automatic reports do not include raw logcat, arbitrary error-message text or file paths, messages, account contents or passwords, browsing history or URLs, Android ID, advertising ID, game saves, app databases, app preferences, arbitrary files or your full installed-app list. Reports do not detect every crash, freeze or blank screen.

The reporting service issues a random client identifier and access credential for this installation. These are used to authorize uploads, apply limits and associate deletion requests with its reports. They are not a CloneX user account. A separate random identifier identifies each report. Your internet address reaches our hosting service; hosting access logs may retain it, and the reporting service uses a keyed hash of the address for abuse prevention and request checks.

4. Sending, security and storage

Reporting registration, uploads and deletion requests use HTTPS with Android’s certificate validation. Reports can use Wi-Fi or mobile data by default. You can enable Wi-Fi only in Privacy & diagnostics; your saved network choice is retained. Android or connectivity conditions may delay sending.

Up to five reports can wait on the device. Unsent reports become ineligible after seven days and are removed when CloneX next checks the queue. The server is configured to expire diagnostic reports after 30 days, with removal performed during server cleanup. Reporting credentials are also time-limited. No internet transmission or storage system can be guaranteed completely secure.

We use restricted administrator access for report review. Hosting connection logs, security records, reporting authorization records and website backups are separate from report storage; some may remain longer than the reports. Their cleanup depends on server maintenance and hosting or backup schedules. Deleting an active report does not immediately erase every historical backup or connection log.

5. Turn reporting off or delete sent reports

Open CloneX → Settings → Privacy & diagnostics. Turn automatic reporting off and save to stop new collection, cancel sending and clear waiting reports. A request already transmitted may still finish. Turning reporting off alone does not delete reports already received by the server.

Choose Delete sent reports → Delete reports to turn reporting off, clear waiting reports and request server deletion of reports associated with this installation’s saved reporting credential. On success, those active reports are removed and the credential is revoked. If offline, the request waits for a connection. Keep CloneX installed until it confirms deletion.

Clearing app storage or uninstalling removes the saved credential. Reports from earlier installations or other devices may not be identifiable by the current installation. Contact us for help; we may need information to locate a report, and phone model alone may not identify it uniquely. See Delete your CloneX diagnostic reports for instructions and a contact option without the app.

6. Reports you share yourself and support

Share diagnostics report is separate from automatic reporting. It gathers the latest 32 available retained app sessions, or fewer when fewer exist, and opens Android’s sharing interface. It can include device details, app and component names, configuration, error messages and accessible runtime logs. These larger reports may contain sensitive information produced by apps you run. Review them before sharing.

The automatic reporting service does not upload these manual ZIP reports. Your chosen email, messaging, cloud storage or other destination handles them under its own policy. If you send us a report or a support request, we receive its contents and any email address, message or attachment you provide.

We use reports and support information to investigate problems and improve CloneX. Relevant diagnostic information may be provided to technical assistance or AI tools, including ChatGPT, for troubleshooting. Share only what is needed and avoid including private content. Those providers process supplied information under their applicable terms and privacy policies. We do not use diagnostic reports for advertising or sell them.

7. Backup and restore

Backups can include the categories you select: Internal, External, APK, Expansion (OBB) and Media. Internal and External are selected by default. CloneX writes the backup to the location you choose through Android’s file interface. Restoring reads your selected archive and restores supported contents to the selected clone, including an explicitly chosen target app when migration is offered.

Backups may contain personal data, account sessions and sensitive app files. CloneX does not automatically send them to the diagnostic server. If you select a cloud storage provider, that provider handles the file under its own policy. Keep backup files private; a ZIP file or a known/shared archive password is not a guarantee of confidentiality. Delete exported copies separately when no longer needed.

8. Retention and other deletion choices

Cloned app working data stays on the device until you remove or clear it using CloneX or Android controls, subject to Android storage behavior. Clearing only a cache does not erase all app data. Backups, shared reports and files exported outside CloneX can remain after uninstalling; remove them from their storage locations and any services where you shared them.

Our retention target for diagnostic files directly received through support is 30 days from receipt. Support correspondence is retained for up to 90 days after the issue is closed. You can request earlier deletion; we aim to complete identifiable requests within 30 days. Server automatic-report expiry is described above. Copies held by services you choose, hosting logs and backup copies follow their separate retention arrangements.

9. Website and policy updates

This policy covers the CloneX Android app and its developer reporting service. The Loot&Learn website may separately use cookies, analytics, hosting logs or plugins. See the website privacy policy for the website’s practices. A website visit is separate from enabling reporting in CloneX.

We update this page when our practices change and revise the date above. Material changes to optional reporting will be explained in the app, with renewed consent when required.