CloneX Privacy Policy

CloneX Privacy Policy

Updated: 18 November 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.

At a glance

Your cloned app files and CloneX settings are stored on your device. Automatic error reporting is optional and off by default. When you enable it, small technical reports go to our server to help us investigate problems. You can separately choose to send a manual support report, including selected technical logs, to Loot&Learn. Newer CloneX builds use Google AdMob directly for home-screen advertising; previously released versions may use Unity LevelPlay or direct Unity Ads. The provider and choices depend on your installed app version. Apps running inside CloneX have their own services and privacy practices.

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.

Advertising and ad privacy choices

Advertising on the CloneX home screen is separate from advertising and services inside cloned apps. The provider depends on your installed version. Newer builds use Google AdMob directly, without Unity LevelPlay mediation. Previously released versions may continue using Unity LevelPlay, direct Unity Ads or an earlier AdMob integration.

New direct Google AdMob builds

The free version shows a home-screen banner and occasional full-screen interstitial ads at a return from a cloned app. Interstitials are not displayed on a fresh CloneX launch. CloneX keeps a local record of confirmed full-screen ad displays to enforce a five-minute cooldown and a maximum of three displayed ads in a rolling six-hour period. These counters contain no cloned-app names or account information and are not uploaded by CloneX. Loading an ad does not consume the display quota.

A separate advertising notice explains Google’s role. Continuing acknowledges that notice and is not consent to tracking. Google’s User Messaging Platform checks applicable regional requirements and presents configured privacy messages when required. Advertising requests are gated by that platform’s request eligibility. CloneX requests non-personalized ads; these may still require consent for device storage. Non-personalized advertising does not mean no data processing.

Google may process IP address and approximate location, device or advertising identifiers where permitted, ad views and interactions, and diagnostic or performance information for ad delivery, measurement, fraud prevention and related functionality. CloneX does not intentionally supply its cloned-app list, cloned-app files, account contents or diagnostic-report credentials for advertising. CloneX disables Google’s publisher first-party ID before loading ads. Google may process other permitted identifiers under its policies and the applicable choices.

Review available regional choices through CloneX → Settings → Privacy & diagnostics → Ad privacy choices. Where Google requires a privacy-options form, that entry reopens it to review or change choices. Android also provides advertising-ID controls. There is no free ad-removal switch and no paid ad-removal purchase is currently available; this does not remove applicable rights to decline or withdraw consent. See Google’s Privacy Policy and Google’s advertising information.

Updating from Unity to AdMob does not automatically erase information previously held by Unity or its partners. Existing diagnostic-reporting choices remain separate and are not reset or treated as advertising consent.

Previously released Unity LevelPlay and Unity Ads builds

The free version of CloneX is supported by a banner on the home screen. Newer builds can also show occasional full-screen interstitial ads when you return to CloneX home after using a clone. These ads are served by CloneX, separately from advertisements inside cloned apps. Newer ad-supported builds do not offer a free switch to disable all ads. Before the first Unity ad request, an advertising notice explains the processing involved. Continuing acknowledges this notice; it does not give consent to tracking or personalized advertising. No paid ad-removal purchase is currently available.

CloneX keeps local visit counters and timing values to limit how often interstitials can appear. These frequency counters contain no cloned-app names, account information or persistent user/device identifiers and are not uploaded by CloneX.

Unity LevelPlay and Unity-enabled builds currently request limited, non-personalized ads. CloneX does not send a personalized-ad opt-in or ask for your age through this advertising choice. Non-personalized ads do not mean no data processing. When advertising is requested, Unity LevelPlay and its configured Unity Ads and ironSource Ads networks, service providers or advertising partners may process your internet address and approximate location, device or advertising identifiers when available, information about ad views and taps, and technical diagnostic or performance information. Unity’s SDK disclosures also describe purchase-history information and app-use timing when its Acquire Optimization feature is enabled. Processing depends on SDK features, device availability, settings and privacy choices.

This information is used to deliver and measure advertising, provide related functionality, and address fraud, security and compliance. CloneX does not intentionally supply Unity with your cloned-app inventory, cloned-app files, account contents or diagnostic-report credentials. Information that cloned apps or their own services collect remains subject to their separate policies.

Review advertising information in CloneX → Settings → Privacy & diagnostics → Ad privacy choices. Personalized advertising remains disabled and CloneX applies privacy opt-out/non-behavioral signals. Available Unity data-access, deletion and other privacy controls can be opened through the privacy icon on an ad; Android also provides advertising-ID controls. These privacy rights are separate from removing advertisements. See Unity’s Privacy Policy and its Unity Ads data disclosures for its practices and privacy-request options.

Some earlier Unity test builds included Allow ads / Keep ads off. When updating from those builds, CloneX presents the revised advertising notice before making new ad requests; the previous setting is not treated as consent to tracking or personalized advertising.

Earlier AdMob builds

Earlier builds may use Google AdMob and Google’s User Messaging Platform for available regional advertising choices. Google and its partners may process internet addresses, approximate location, device or advertising identifiers, ad interactions and diagnostics to deliver and measure ads, prevent fraud and, where permitted by the applicable choices, personalize ads. Reopen available options through Ad privacy choices. See Google’s Privacy Policy and Google’s advertising information. Updating to a Unity build does not automatically delete information previously held by Google.

Advertising choices are separate from automatic and manual diagnostic reports. Turning reporting off or deleting reports does not change an advertising choice or delete advertising-provider data. The server’s diagnostic-report retention period below does not apply to advertising-provider records, which follow those providers’ policies and applicable requirements.

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 and version, when known, identifying which cloned app had a problem.
  • Technical error codes, exception types, code locations, recognized missing-method signatures, bounded thread code locations, states and wait-owner links for Android-reported hangs when available, and available bounded native crash details such as signal numbers, library names, relative offsets and build identifiers. Newer versions can also include recognized missing-library or unresolved-symbol names, null-object code targets, fixed permission-denial references, the type of native-library search path without the paths themselves, process bitness, memory page size and the number of APK files for the affected app.

CloneX can examine recognized error messages or available diagnostic traces on the device to extract these technical fields. Automatic reporting sends the extracted fields, not the original messages or traces.

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. It keeps a rolling store of up to 2,000 non-deleted automatic and manual reports. Older reports can be removed sooner when report-count or storage limits are reached. 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 automatic reports (called Delete sent reports in some earlier versions) → 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. Manual problem reports, exported diagnostics and support

Report a problem is separate from automatic reporting and works when automatic reporting is off. You can select one to five cloned apps, optionally describe the problem, and choose Send report to upload a manual support report to the developer through Loot&Learn. The report can include your optional message, selected app names and versions, phone and CloneX details, and up to five available retained launch or resume sessions per selected app. Missing or truncated coverage is identified; these limits do not guarantee complete logs.

Manual support reports can contain raw technical logs, error messages and code locations. Logs produced by apps and shared services can include private text, account-related details, URLs or other information entered in apps. Process filtering limits collection but does not automatically remove every sensitive value. Avoid entering private details in your description, and consider these contents before sending. CloneX does not automatically include your game saves, app databases, APK files or arbitrary app files in these reports.

Manual reports use a separate encrypted queue on your device and separate reporting credentials. They can be sent over Wi-Fi or mobile data after you choose Send report, including later in the background when connected. Up to three reports can wait locally; pending reports expire after seven days when the queue is next checked. The server is configured to retain received manual reports for up to 30 days, subject to its cleanup schedule and the shared rolling storage limits described above. Website backups and connection logs may remain longer. Review status or choose Delete manual reports in Report a problem to clear pending manual reports and request deletion of sent manual reports linked to this copy of CloneX. Automatic-report controls do not delete manual reports, and manual-report controls do not delete automatic reports. Losing the saved credentials can limit which earlier reports can be identified for deletion.

Export diagnostic file remains a secondary, user-shared option. It exports the latest 32 available retained sessions, or fewer when fewer exist, and lets you choose a destination through Android’s sharing interface. It can contain device details, app and component names, configuration, error messages and accessible runtime logs. These larger exports may contain sensitive app information. Review them before sharing. The automatic-report endpoint does not silently upload these exported ZIP files; your chosen email, messaging or storage provider handles the file under its own policy.

If you send us a report or 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 supplied to technical assistance or AI tools, including ChatGPT, for troubleshooting under their applicable terms and privacy policies. Share only what is needed and avoid private content. 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.

10. Contact

Developer: Save Forge (CloneX)
Privacy and support: saveforgeapp@gmail.com

Use the subject “CloneX privacy” or “CloneX data deletion.” Do not send passwords, upload credentials or unnecessary private files.