Obada Dallo (عبادة دللو) — Product Engineer
Legal Documentation · Android Application

Mirro Privacy Policy

Product: Mirro · Package: app.mirro.android · Effective Date: September 19, 2026 · Developer: Obada Dallo (Chemnitz, Germany)

Architectural Summary: Mirro is an on-device utility providing an isolated app runtime on Android. Mirro processes application and clone metadata locally on your device, does not operate an external user-data backend, does not display advertisements, does not require an account, and does not sell or share your personal data.

1. Overview

This Privacy Policy applies to the Android mobile application Mirro (package name: app.mirro.android), developed by Obada Dallo. Mirro is designed as a privacy-focused utility providing an isolated app runtime and application cloning capability on Android devices. Mirro operates without mandatory accounts, serves no advertisements, requires no subscriptions, and operates no external cloud backend to store or collect your personal information.

2. Information Mirro Accesses

To perform its core utility—allowing you to create, manage, and run cloned or isolated instances of Android applications—Mirro accesses limited metadata directly through standard Android operating system APIs.

Mirro processes this information locally on your device. Mirro does not harvest, transmit, or monetize your personal data, communications, media, or browsing activity.

3. Installed Apps & Package Information

In order to display an app picker from which you can choose which application to clone or run in an isolated environment, Mirro inspects installed package information on your device (such as package names, application labels, and launcher icons) via standard Android PackageManager APIs.

This query occurs entirely on-device. Mirro does not upload your list of installed apps to any remote server or third party.

4. Local Clone and Sandbox Data

When you create an isolated clone or container using Mirro, the application creates and manages isolated sandbox directories within Mirro’s allocated local application storage on Android. This local data may include clone metadata, target package configuration flags, user clone preferences, and local sandbox caches or databases generated during runtime.

These files remain strictly on your local device storage inside Mirro’s app sandbox. They are never transmitted to the developer or any external server unless you explicitly export or share something.

Architecture boundary: Mirro does not intentionally access another application’s private Android data directory (/data/data/<package_name>).

5. Diagnostic & Runtime Logs

To assist in troubleshooting runtime errors and compatibility issues, Mirro may maintain temporary diagnostic and execution logs on your device. These logs reside solely in local storage. Mirro does not automatically upload, transmit, or synchronize diagnostic logs to any cloud service.

6. On-Device Processing

Mirro is designed with an on-device first architecture. Core containerization logic, package inspection, configuration adjustments, and file sandboxing are executed directly on your device. Mirro currently does not operate an external user-data backend.

7. Data Sharing and Transfer

Mirro does not sell, rent, trade, or transfer any user data, package lists, or device identifiers to third parties. There is no transmission or sale of user information to brokers, advertisers, or external partners.

8. Advertising

Mirro does not contain advertising. The application does not integrate commercial ad networks, ad mediation SDKs, or behavioral profiling technologies.

9. Analytics

Mirro currently does not integrate third-party analytics SDKs, session recording tools, or behavioral telemetry frameworks.

10. Accounts and Authentication

Mirro does not require user registration or account creation. You can use Mirro immediately without providing an email address, phone number, password, or login credential. There is no Mirro user account database.

11. Data Retention

All clone data, preferences, and logs are stored locally on your device. Mirro retains local sandbox files only for as long as the application remains installed or until you delete individual clones.

12. User Deletion and Control

You maintain full control over your data through standard Android controls: deleting an individual clone removes its container files; clearing application storage (via Android Settings > Apps > Mirro > Storage > Clear Storage) erases all local clones and logs; uninstalling Mirro permanently removes all internal sandbox data.

13. Third-Party Applications and Services

When you run a third-party application inside a Mirro clone container, that application executes its own code and may connect to its own servers over the Internet. Any data you enter into a cloned third-party app is governed by that application's privacy policy, not Mirro's.

14. Security Limitations and Technical Boundaries

Mirro operates within the security framework of the Android operating system. Mirro does not attempt to bypass DRM, Google Play Integrity API, SafetyNet, hardware-backed keystores, anti-fraud systems, or application security restrictions. Compatibility varies by app; Mirro does not guarantee compatibility with all applications.

15. Children’s Privacy

Mirro is a general-purpose Android utility tool and is not directed to children under 13 (or the applicable age of digital consent). Mirro does not knowingly collect personal information from children.

16. Changes to this Privacy Policy

We may occasionally update this Privacy Policy. Any revisions will be published on this page with an updated Effective Date.

17. Contact Information

If you have questions regarding this Privacy Policy or Mirro’s on-device practices, contact the developer: