Effective: 25 October 2026 (crash log section added in 2.0.1; system-app visibility note added in 2.0.2) · App: Dohr ("Clone Apps. Your Way.") · Publisher: PostCora.com
Dohr is a free app that runs extra copies ("clones") of apps already installed on your phone. This policy describes what the app actually does, based on its source code.
1. What Dohr collects
Nothing is collected by us. Dohr has:
- no advertising and no advertising ID (the
AD_IDpermission is explicitly removed from the app manifest); - no analytics, crash-reporting, tracking or telemetry SDKs (no Firebase, no Google Analytics, no Crashlytics, no Facebook SDK);
- no account, sign-up or login;
- no servers. Dohr's own code makes no network requests.
We removed a feature in the open-source engine Dohr is built on that would have uploaded logs and device details to a third-party web service when apps crashed. That code is not in Dohr.
Crash logs (since Dohr 2.0.1) stay on your device unless you share them. When a clone (or Dohr itself) crashes, Dohr writes a short text report (time, app package and process name, clone number, error and stack trace, Android version, phone model, Dohr version) to its private storage on your phone. It keeps at most the 20 newest reports. Nothing is uploaded or sent automatically. Only if you tap Settings > Share crash log does Dohr build one text file (the saved reports, Android's list of recent Dohr process exits, and the system log lines written by Dohr and its clones) and open the Android share sheet; the file goes only to the app and person you choose. That file can contain text the cloned apps wrote to the system log, so check it before you send it. You can delete the saved reports with Delete saved crash reports on the same screen, or by clearing Dohr's storage.
2. What stays on your phone
Dohr stores these only in its private app storage on your device:
| Data | Why | Where |
|---|---|---|
| Your list of clones: app package, clone name, clone number, status, dates | to show and manage your clones | local database (Room/SQLite) |
| Settings: theme, default naming format, sort order | your preferences | local DataStore file |
| Each clone's own app data (logins, messages cache, settings, files) | so each clone works independently | a separate folder per clone inside Dohr's private storage |
| Crash reports (up to 20, since 2.0.1) and the last exported crash log file | so you can send a crash log yourself if you want help | Dohr's private storage and cache; shared only via Settings > Share crash log |
Dohr reads the list of apps installed on your phone (QUERY_ALL_PACKAGES) so you can pick one to clone. That list is shown on screen only. It is never stored remotely, shared or uploaded.
App backups (Android Auto Backup) are disabled for Dohr. Your clones are not copied to Google Drive by Dohr.
3. The cloned apps and the internet
Clones run inside Dohr's process. Android therefore requires Dohr to declare every capability the clones may need, including Internet access. When you use a clone of, say, Facebook, that clone talks to Facebook's servers just like the normal app would. That traffic:
- is created by the cloned app, not by Dohr;
- is not read, logged, modified, proxied or stored by Dohr;
- is governed by that app's own privacy policy and terms.
Whatever a cloned app collects about you is between you and that app's publisher.
4. Permissions
Dohr's own screens use no sensitive permission. The manifest lists permissions that cloned apps may ask for (camera, microphone, location, contacts, calendar, phone state, photos/media, Bluetooth, notifications). None of them is granted when you install Dohr. Android asks you the first time a clone needs one, and you can revoke it at any time in system settings. A permission you grant to Dohr is then available to clones running inside Dohr, so grant only what you need.
Since 2.0.2 Dohr also declares REORDER_TASKS, a normal permission granted automatically at install, so the engine can bring a clone's existing window to the front. It gives no access to your data.
Not requested at all: SMS, call log, outgoing calls, background location, body sensors, usage stats, all-files access, installing other apps, drawing over other apps.
5. Isolation between clones
Each clone runs as its own virtual user with its own data folder, separate from the original app and from other clones. Deleting a clone deletes only that clone's folder. It never touches the original app or its data. Isolation is provided by the virtualization engine and depends on Android and on the app. Since Dohr 2.0.2 a clone can see which system apps are installed on the phone (for example Google Play services, the Play Store and WebView), much like the original app can, so Google's own libraries inside the clone work. Your other (non-system) apps stay hidden from clones. Nothing about this leaves your phone. See COMPATIBILITY.md for limits.
6. Backups
Dohr 2.0 has no clone backup feature (it was removed). Dohr creates no backup files.
7. Children
Dohr is not directed at children and collects no personal data from anyone.
8. Changes and contact
If this policy changes, the new version will ship with the app update that changes the behaviour. Contact: PostCora.com.