Privacy Policy

Tdevs LTD built the Duplyn app, which lets you run more than one copy of an Android app on the same device. This Service is provided by Tdevs LTD and is intended for use as is.

This page explains what information Duplyn handles, where it is kept, and the one case in which anything leaves your device. If you choose to use the Service, you agree to the handling of information described in this policy. We will not use or share your information with anyone except as described here.

The terms used in this Privacy Policy have the same meanings as in our Terms and Conditions, unless otherwise defined in this Privacy Policy.

Summary

• Duplyn has no accounts, no advertising and no analytics or tracking SDKs.
• Your cloned apps, their data and your Duplyn settings are stored only on your device.
• The only information sent to us is an automatic crash report when the app or a cloned app crashes, stops responding, or hits a serious error, described in full below. You can turn crash reports off in Settings.
• We do not sell, rent or share your information with third parties. Crash reports are stored for us by our hosting providers, which do not use them for anything else.

Information Stored on Your Device

The following stays on your device. We never receive it:

• Cloned apps and their data. Each clone runs inside an isolated space within Duplyn. Everything the cloned app stores, including its logins, messages and files, stays in that space.
• Settings and organisation. Spaces, profiles, custom names and icons, home screen shortcuts, temporary spaces, Focus Mode and daily usage limits, theme and language.
• App Lock. Your PIN is stored only as a one-way hash, never in readable form. Fingerprint and face unlock are handled by Android's own biometric system; Duplyn only receives a yes or no answer and never has access to your biometric data.
• Local diagnostic logs. Duplyn keeps a short technical log on the device to help troubleshoot problems. It stays on the device unless you choose to export and send it yourself.

Permissions and Why They Are Used

• List of installed apps. Used to show which apps you can clone. The list is read on the device and never sent to us.
• Focus Mode and daily limits. Duplyn counts the time you spend in your clones itself, on the device. It does not read Android's usage history of your other apps, and the time it counts is never sent to us.
• Camera and photos. Used only when you choose to take or pick a picture for a custom clone icon. The picture stays on your device.
• Biometrics. Used only for App Lock, as described above.
• Notifications. Used to show notifications from your cloned apps and from Duplyn. If you choose, Duplyn hides the content or sender of notifications from the clones in a Space, and silences clones during Focus Mode. Notifications are handled on the device and never sent to us.
• Internet. Used by your cloned apps, to display this policy and the Terms inside the app, and to send crash reports.

Permissions requested on behalf of cloned apps. Duplyn declares a wide set of Android permissions (for example SMS, call log, contacts, location, microphone, calendar and storage) so that the apps you clone keep working as they do outside Duplyn. These permissions are requested only when a cloned app needs them, and Android asks you before granting them. Any data obtained this way is used by that cloned app alone, under that app's own privacy policy. Duplyn itself does not read, collect or upload it.

Crash Reports

When Duplyn or an app running inside it crashes, stops responding, or hits a serious error, Duplyn automatically sends a crash report to a server operated by Tdevs LTD, so that we can find and fix the problem. No third-party crash service is involved. A report contains:

• A random installation ID generated by Duplyn, and a random ID for each report. Neither is tied to your name, email, phone number, Google account or any hardware identifier.
• Device information: manufacturer, brand, model, device codename, Android version and SDK level, security patch level, build fingerprint, processor architecture and, on Samsung devices, the One UI version.
• App information: Duplyn's version, version code and build type.
• Technical details of the crash: the time it happened, the error type, message and severity, the stack trace, the name of the thread that failed, the internal process name and process number, the reason and exit status Android records for closing the app, whether it was in the foreground or background at the time, and how much memory it was using.
• When an app stops responding or crashes in native code, the diagnostic trace Android keeps for it: for an app that stops responding, the stack of every thread in that app at that moment; for a native crash, a summary Duplyn takes from it: the signal and its cause, the abort message, and the stack frames, library paths and processor register values of the thread that crashed. The rest of Android's native crash record, such as the app's recent log messages, memory contents and open files, is not read.
• The package name of the cloned app that was running when the crash happened (for example com.example.app), together with an internal number for the space it ran in, so we can tell which app is affected.
• A short list of the technical events that came just before the crash.

Before a report is saved or sent, Duplyn removes clone identifiers, the names of apps other than the cloned app named above, and anything in the error text and traces that looks like personal or secret information. It also replaces storage locations on your device with placeholders. Crash reports are not designed to collect the content of your cloned apps, your messages, contacts, photos, files, location or keystrokes. An error message written by a cloned app can in rare cases still contain a short fragment of what it was handling when it failed; we do not use such fragments for anything other than fixing the crash.

Reports are sent over an encrypted connection (HTTPS). As with any internet connection, our server can see the IP address the report came from; we do not use it to identify you. Crash reports are kept for up to 90 days to investigate and fix problems, and are then permanently deleted.

Turning crash reports off. Crash reports are on by default. You can turn them off at any time in Settings → Crash reports. While they are off, Duplyn does not save or send any new report, and reports still waiting on your device are deleted; only a report that was already being sent at that moment may still arrive. Reports already sent are kept for up to 90 days, as described above.

Backups

If you create a backup, Duplyn encrypts it with a password you choose and saves or shares it wherever you decide. We never receive your backup or its password. If you forget the password, we cannot recover the backup for you.

Purchases

Duplyn does not currently process payments. If paid features are introduced, payments will be handled by Google Play under Google's privacy policy, and this policy will be updated before that happens.

Sharing of Information

We do not sell, rent or trade any information. Crash reports are used only by Tdevs LTD to keep the Service working. We may disclose information if required by law.

Hosting providers. Crash reports are handled by two cloud providers that act only on our behalf and under our instructions, and do not use the reports for any purpose of their own:

• Render runs our crash report server, in the United States.
• Turso stores the reports in its database, hosted on Amazon Web Services in India.

This means crash reports are transferred outside the United Kingdom. Transfers to Render are covered by the Standard Contractual Clauses and the UK International Data Transfer Addendum in Render's data processing terms. Access to the stored reports is limited to Tdevs LTD and protected by a password.

Security

Duplyn protects your data with sandbox isolation between clones, an optional App Lock with a hashed PIN or biometrics, encrypted backups and encrypted transmission of crash reports. No method of transmission over the internet or of electronic storage is 100% secure, and we cannot guarantee absolute security.

Links to Other Sites

The Service may contain links to other sites, such as Google Play when you choose to rate the app, or Telegram and WhatsApp when you choose to contact us. These sites are not operated by us, and we advise you to review their privacy policies. We have no control over and assume no responsibility for the content, privacy policies or practices of any third-party sites or services.

Children’s Privacy

The Service is not directed at anyone under the age of 13, and we do not knowingly collect personal information from children under 13. If you are a parent or guardian and believe your child has provided us with personal information, please contact us and we will delete it.

Your Rights and Data Deletion

You have the right to access, correct, object to or erase the data we hold about you.

• Data on your device: you can delete all of it at any time by removing a clone, clearing Duplyn's storage in Android settings or uninstalling the app.
• Crash reports on our server: uninstalling the app does not delete reports that were already sent. Because they contain no name, email or account, we usually cannot link a report to a particular person, but if you write to us with your device model and the approximate date, we will delete any reports we can identify.

Email: support@tdevs.co

If you believe our processing of your personal data infringes data protection laws, you have the right to lodge a complaint with a supervisory authority.

Changes to This Privacy Policy

We may update this Privacy Policy from time to time. Changes are posted on this page with a new "Last Updated" date, so please review it periodically.

This policy is effective as of 2026-10-07.

Contact Us

If you have any questions or suggestions about this Privacy Policy, contact us at:

• Email: support@tdevs.co
• Website: https://tdevs.co
• UK Office: A, 82 James Carter Road, Mildenhall, Bury St. Edmunds, United Kingdom, IP28 7DE