Mirror Pocket
Your privacy is as clear as a reflection. At Mirror Pocket, we believe that a utility tool should remain a private sanctuary. This document details our commitment to data integrity and the technological framework that ensures your personal life stays personal.
01. Camera & Sensory Privacy
As a makeup mirror utility, Mirror Pocket requires access to your device's camera hardware. This access is utilized strictly for real-time video rendering on your screen. At no point is the feed recorded, captured as a static image, or uploaded to any remote server. The "Mirror" is a live, local-only bridge between the hardware and your display.
02. Zero-Data Retention Model
Our application architecture is built on a stateless foundation. We do not maintain any user databases. This means:
- No account registration or personal profiling.
- No storage of facial geometry or biometric markers.
- No collection of names, emails, or contact information.
03. Third-Party Infrastructure
To ensure high performance and application stability, we integrate industry-leading SDKs. These partners handle technical telemetry under their respective privacy mandates:
Google & Firebase Telemetry
We use Firebase to monitor crash reports and app performance. This data is technical (e.g., device type, OS version) and contains no personal identifiers. It is used solely to optimize the mirror's frame rate and stability.
Meta (Facebook) Attribution
The Facebook SDK is utilized to measure the effectiveness of our advertising campaigns. It may process device-level advertising identifiers (IDFA) to attribute app installs, governed by Meta's data usage policies.
04. Advertising Disclosures
Mirror Pocket is supported by advertisements. These are managed by third-party ad networks that may use anonymized device tokens to serve relevant content. We do not provide your camera data or any local files to these advertisers. You can manage your ad-tracking preferences in your device's system settings.
05. Local Permissions
Any local permissions requested (such as brightness control or storage) are handled via the OS-level permission gates. These are required for the tool's functional core and are never exploited for data exfiltration.