MicSentry privacy policy

About MicSentry

MicSentry helps users understand when the Android device microphone is active. It processes microphone activity information supplied by Android system APIs and does not record, listen to, save, upload or transmit microphone audio.

Microphone audio

MicSentry does not request Android's RECORD_AUDIO permission. It does not record conversations, save audio or send microphone audio to Emiliza Labs or anyone else.

Microphone activity history

Detected activity events may be stored in the app’s local database. A record may contain:

• Activity start and end time and duration
• Android audio source information
• Audio input device type
• Name or package identifier of an app likely associated with the activity

This monitoring history is not transmitted to Emiliza Labs, advertisers, analytics providers, data brokers or other third parties. Individual events, selected periods or all stored history may be deletable using the app’s available controls.

Application identification and Usage Access

Android ordinarily does not provide third-party applications with a confirmed identity of the app recording audio. Optional Usage Access, enabled explicitly in Android settings, may help identify the foreground app likely linked to an event.

Unrelated usage information is not stored in microphone activity history. Any associated app name is an estimate, not guaranteed attribution.

Phone state

Optional phone-state access may be used to detect whether an ordinary phone call is active so that the microphone event is represented appropriately.

MicSentry does not read, collect, store or transmit phone numbers, contacts, call logs, call history, call audio or call content.

Background monitoring and notifications

Background monitoring starts after an in-app disclosure and explicit user action. It may run an Android foreground service with an ongoing notification. Users can stop monitoring inside the app or using the Android notification.

If enabled, MicSentry may also notify the user when microphone activity begins.

Local data, backups and deletion

Monitoring history is stored locally on the device. Application backup is disabled for monitoring history, excluding the local monitoring database from normal Android application backups.

History can be deleted within the app. Clearing app data in Android settings or uninstalling MicSentry removes locally stored history. There is no Emiliza Labs server-side monitoring database to delete.

Internet access and data sharing

Microphone monitoring information and activity history are not sent to Emiliza Labs servers and are not sold, rented or shared with advertisers, analytics companies or data brokers.

Monitoring information is not used for advertising, profiling or tracking. Google Play purchase processing and verification may require communication with Google Play services.

Accounts

No Emiliza Labs account or sign-in is required. Google Play may separately require the user to sign into a Google account to buy or restore purchases.

Four-day trial

MicSentry may offer a four-day full-feature trial starting at first use. Trial eligibility and timing are managed locally, with no Emiliza Labs account or server-side trial record.

Clearing application data or reinstalling the application may reset locally stored trial information. Continued use after the trial may require a one-time purchase.

Purchases and Google Play Billing

MicSentry may offer a single non-subscription purchase to unlock ongoing use. Purchases are processed by Google Play Billing rather than directly by Emiliza Labs.

MicSentry may communicate with Google Play to initiate and verify a purchase, check ownership and restore purchases after device changes or reinstallation. Entitlement information may be received to unlock paid features; it is not used for advertising, profiling or tracking.

Third-party platform services

Google Play and Android may independently process information needed for installation, distribution, licensing, purchases, purchase history, fraud prevention, application security and device security. Their processing is governed by the applicable Google and Android policies.

Emiliza Labs does not directly receive payment card numbers, banking credentials or Google account passwords through Google Play Billing.

Security

Local application information is stored in the Android application storage environment, subject to Android application security mechanisms. No security method offers absolute protection; Emiliza Labs aims to avoid unnecessary data collection and transmission.

Children's privacy

The application is not specifically directed toward children under 13. Emiliza Labs does not knowingly collect personal information from children through the app and does not maintain profiles of child users.

Changes to this policy

This policy may change when application features, data practices, applicable laws, Google Play requirements or third-party services change. The revision date shown on this page identifies the referenced version.

Contact

Developer: Emiliza Labs

Privacy and support enquiries: support@emilizalabs.com