Effective Date: March 4, 2026 • Version 1.0.0
This privacy policy transparently details how MacMirror for Android handles data, requests system permissions, and guarantees zero remote data collection. Designed with a local-first, privacy-by-design architecture, MacMirror mirrors notifications exclusively over your local Wi-Fi network without relying on external cloud servers.
Operates strictly on your local Wi-Fi (LAN). No remote servers, cloud databases, or third-party proxies.
Ephemeral ECDH (P-256) key agreement with 6-digit PIN and authenticated AES-256-GCM notification encryption.
No analytics SDKs, no behavioral trackers, no advertising libraries, and no external crash reporting tools.
100% open-source under the MIT License. Anyone can inspect and verify the complete codebase on GitHub.
MacMirror for Android is an independent, open-source software project developed and maintained by Angel Velasquez ("Developer"). The companion desktop application is MacMirror for macOS.
MacMirror operates under an absolute Zero Cloud model. The application does not deploy, connect to, or interface with any remote servers, cloud databases, relay brokers, or hosted backend services.
All network communication occurs strictly over your private local area network (LAN / Wi-Fi) between your Android smartphone and your macOS computer. Notification data never leaves your personal local network under any circumstances.
To deliver its core utility—mirroring notifications from Android to macOS—MacMirror requests specific Android system permissions. Below is the full disclosure of each permission, the exact technical purpose, and data boundaries:
Purpose: Captures incoming notifications posted to the Android status bar (notification title, text body, emitting application package, and notification icon).
Data Handling: Notification data is held strictly in volatile device memory (RAM) for the duration required to encrypt it. It is immediately dispatched via local WebSocket to your paired Mac. The application never logs notifications to permanent disk storage, never saves message history, and never uploads notification content to any remote server.
Purpose: Under Android 14+ (API 34+), foreground services require a designated functional type. MacMirror declares connectedDevice because it communicates directly with a physically paired desktop companion (your Mac). This grants process execution priority and prevents aggressive OEM task killers (such as Xiaomi MIUI/HyperOS, Samsung One UI, or OnePlus ColorOS) from prematurely severing the local socket.
Data Handling: Governs OS process lifecycle and connection resilience only. Collects zero personal metrics, usage statistics, or user data.
Purpose: Prompts the user to exempt MacMirror from Android's aggressive battery saving mechanisms (Doze Mode). When an Android device enters sleep mode with the screen off, Doze cuts active network sockets and restricts background task execution, which would delay or prevent notification mirroring.
Data Handling: This is an OS power management exemption. It does not record, harvest, or transmit any user information. It strictly ensures uninterrupted local Wi-Fi transmission while the device screen is turned off.
Purpose: Required on Android 13+ to post a persistent, low-priority (silent) status notification (IMPORTANCE_LOW) informing the user of the live connection state ("Connected to Mac" / "Standby"). Also used when triggering in-app local test notifications.
Data Handling: Generates transparent local visual cues on the device. Transmits zero notification logs off-device.
Purpose: Reads the list of installed applications on your device solely to display them within the in-app "Apps Filter" settings screen.
Data Handling: This allows you to selectively include or exclude specific apps from having their notifications mirrored. The list of installed applications is processed exclusively on-device, is never transmitted over the network, and is not shared with any entity.
Purpose: Enables Network Service Discovery (mDNS / Bonjour under the _macmirror._tcp service) and local WebSocket communication with your Mac companion on port 50002.
Data Handling: Despite requiring Android's general INTERNET permission, MacMirror initiates zero outbound connections to the public internet. All network packets circulate exclusively inside your local LAN subnet.
Even across your local Wi-Fi, MacMirror enforces authenticated End-to-End Encryption (E2EE) to safeguard notification payloads against local network eavesdropping or packet inspection:
POST /pair/initiate and POST /pair/confirm).EncryptedSharedPreferences, backed by hardware security modules (TEE/StrongBox) where supported.| Category | Status | Description |
|---|---|---|
| Personal Data Collection | NONE | No accounts, emails, names, phone numbers, or device IDs collected. |
| Analytics & Telemetry | NONE | No Google Analytics, Firebase, Mixpanel, or custom telemetry SDKs. |
| Advertising Frameworks | NONE | Completely ad-free. No advertising libraries or tracking cookies. |
| Remote Crash Logging | NONE | No external crash monitoring tools (e.g. Sentry, Crashlytics). |
| Data Sale or Sharing | ZERO | Data is never monetized, sold, rented, or transferred to third parties. |
Because MacMirror collects zero data on remote servers, there is no remote user profile or database record to purge.
You retain absolute sovereignty over your local device configuration:
EncryptedSharedPreferences, and terminates the WebSocket channel.MacMirror does not knowingly collect, request, or process personal identifiable information from anyone, including children under the age of 13 (or under 16 in applicable jurisdictions).
Because the application is published under the MIT License, our privacy and security claims are directly verifiable. Developers, security researchers, and users can independently inspect the source code, verify dependencies, and build the APK directly from source:
For privacy questions, security disclosures, or technical audits regarding MacMirror for Android, contact the developer directly: