AT A GLANCE
MicDrop requires no account, embeds no advertising, analytics, crash-reporting, or tracking SDKs, and never sends your audio, camera images, or pairing keys to Maskarauder. Live audio and session controls travel directly between your own explicitly paired phone and computer over encrypted TLS and WebRTC DTLS-SRTP connections.
Scope and summary
This privacy policy applies to the MicDrop mobile applications for Android and iPhone (bundle and package identifier com.maskarauder.micdrop, as well as com.maskarauder.micdrop.dev development builds) and the companion MicDrop desktop and command-line hosts for Windows, macOS, and Linux published by Maskarauder (maskarauder.com).
Maskarauder does not collect, store, rent, or sell personal data from MicDrop users. MicDrop operates without user registration, cloud accounts, or developer-operated telemetry servers. Its first-party source code is open source under the Mozilla Public License 2.0 and publicly inspectable on GitHub.
Device permissions and how they are used
MicDrop requests operating-system permissions only for features you actively choose to use. Denying optional permissions leaves the rest of the app functional.
| Permission | When used | How data is handled |
|---|---|---|
| Microphone ( RECORD_AUDIO, FOREGROUND_SERVICE_MICROPHONE on Android; Microphone & background audio on iPhone) | Only when you enable Send microphone and tap Connect. Not required for desktop audio playback alone. | Streams live audio solely to your paired computer over encrypted WebRTC DTLS-SRTP while the OS microphone indicator and active session notification are visible. Audio is never recorded to storage, transcribed, or sent to Maskarauder. |
| Camera ( CAMERA on Android; Camera on iPhone) | Optional—only when you tap Scan pairing QR to scan an invitation shown on your desktop host. | Camera frames are decoded locally in memory on your phone (via bundled offline ZXing on Android and system AVCaptureSession on iOS) to read the pairing link. Images and video are never saved or transmitted off your device. You can paste a pairing link manually without camera access. |
| Local network & foreground playback ( INTERNET, ACCESS_NETWORK_STATE, FOREGROUND_SERVICE_MEDIA_PLAYBACK, WAKE_LOCK on Android; Local Network / Bonjour _micdrop._tcp on iPhone) | When discovering your computer on LAN or running an active playback or microphone session, including with the screen off. | Locates candidate hosts on your network and maintains the encrypted TLS control channel and WebRTC audio stream with your approved computer. |
| Bluetooth & audio routing ( BLUETOOTH_CONNECT, BLUETOOTH_SCAN with neverForLocation, MODIFY_AUDIO_SETTINGS on Android; audio session routing on iPhone) | When listing or switching connected headphones, speakers, or headset microphones. | Observes and selects audio routes on your phone. On Android, BLUETOOTH_SCAN is declared with usesPermissionFlags="neverForLocation"; MicDrop never scans for nearby beacons or infers your physical location. |
| Notifications ( POST_NOTIFICATIONS on Android) | Optional—during active playback or microphone sessions. | Displays ongoing session status and quick local Pause and Stop controls. No marketing or remote push notifications are sent. |
How audio and pairing data move
First-time pairing uses a short-lived invitation containing your desktop host’s cryptographic key fingerprint and a single-use secret, followed by explicit approval on your computer. Each phone generates a non-exportable hardware-backed or keychain-protected signing key (Android Keystore on Android; Secure Enclave or Keychain on iPhone). Subsequent connections verify both endpoints with mutual TLS 1.3 and bind live WebRTC DTLS-SRTP audio streams to those paired identities.
Your computer cannot silently activate your phone’s microphone: microphone capture begins only after you enable Send microphone and tap Connect on the phone. Tapping Stop immediately ends capture and closes the session.
Local storage, diagnostics, and data deletion
- On-device keys and settings: Paired device identities, saved connection addresses, and audio/route preferences are stored on your own devices. Android disables app backup. On iPhone, pairing credentials use non-synchronizable Keychain items, and the private diagnostic-report directory is excluded from backups. Other preferences and desktop configuration files may be included in operating-system or user-configured backups.
- Bounded local diagnostics: To assist with troubleshooting without automatic crash uploads, the mobile app keeps at most one recent stream summary and one bounded crash trace in private local storage. Host addresses, pairing invitations, and audio content are excluded from stream snapshots. Diagnostic text leaves your device only if you explicitly tap a Copy button in Diagnostics and choose to share it.
- Remove a pairing: Use Forget saved connection in the mobile app to delete its saved pairing and phone identity. A new identity is created when you pair again. Also choose Phones → Remove selected phone on your computer to revoke that phone's host-side approval.
- Android deletion: Clearing MicDrop's app storage or uninstalling it removes the app's local settings, credentials, and diagnostic reports.
- iPhone deletion: Use Forget saved connection before deleting the app if you want to remove its pairing credentials immediately, and check that the operation succeeds. Deleting the app removes its app-container data, but Keychain credentials can survive deletion. MicDrop attempts to clear those surviving credentials on the first launch after a fresh reinstall. Offloading the app preserves its app data.
- Desktop deletion: Uninstalling MicDrop on Windows intentionally preserves settings, pairings, remote configuration, and logs for a later reinstall. Removing the macOS app or Linux executable also does not erase separately stored configuration. To remove this data, turn off MicDrop's sign-in startup option, quit the host, and remove its data directory. Default locations are
%LOCALAPPDATA%\MicDropon Windows,~/Library/Application Support/MicDropon macOS, and$XDG_CONFIG_HOME/MicDrop(usually~/.config/MicDrop) on Linux. If you configured a different data location, remove that location instead. Copies in your own backups must be managed separately.
Maskarauder maintains no MicDrop user accounts or server-side app databases to delete. Removing a pairing on one device does not erase the other device's stored copy; use the corresponding controls on both devices.
Optional self-hosted remote access
Remote connectivity outside your local network is disabled by default. If you opt in and configure a self-hosted or operator-run rendezvous and TURN relay server, your paired TLS 1.3 control channel and DTLS-SRTP audio packets remain end-to-end encrypted and authenticated between your phone and your computer; the relay forwards opaque encrypted bytes and cannot decrypt your audio or impersonate a paired device.
Like any internet relay, the operator of the rendezvous or TURN server you configure can observe standard network transport metadata—such as connecting IP addresses, timestamps, and packet byte counts—necessary to route traffic. Maskarauder does not operate a mandatory central relay for MicDrop.
Website visits on maskarauder.com
The MicDrop mobile and desktop apps make no network requests to maskarauder.com.
If you visit https://maskarauder.com in a browser to read documentation, audio guides, or use the browser audio tools, the website uses no cookies, user accounts, or third-party ad or analytics networks. Microphone input, live stream tab audio, local OBS recordings, short playback clips, and selected WAV files stay in local browser memory on your device and are never uploaded. Public web pages send cookieless first-party pageview, outbound-link, and allowlisted tool-start counts to a self-hosted GoatCounter instance on maskarauder.com/stats/count without audio, measurements, tab titles, filenames, device names, or persistent browser identifiers.
Children’s privacy, updates, and contact
MicDrop is a general-audience audio utility not directed to children under 13, and Maskarauder does not knowingly collect personal information from children or any other users.
Material changes to this policy will be published at https://maskarauder.com/micdrop/privacy/ with an updated effective date at the top of this page. For licensing, app-store distribution, and usage terms, see the MicDrop Terms of Service.
For privacy questions or inquiries about MicDrop, contact Maskarauder using the developer support email listed on the official MicDrop Google Play Store or Apple App Store page, or open an inquiry on GitHub Issues. Please do not post private diagnostic logs, pairing invitations, or security vulnerabilities in public issues; for suspected security issues, follow the private security reporting instructions.
Technical references
MicDrop’s permission declarations, cryptographic boundaries, and Apple Privacy Manifest are verifiable directly in the source repository: