This Privacy Policy explains how Vokey – Voice Control & Phone Finder ("Vokey", "we", "our" or "us") handles information when you use the Android application. Vokey is designed to process finder audio on your device and does not require an account.
1. Information processed by Vokey
Microphone audio: Android microphone permission (RECORD_AUDIO) is requested when you choose to use a microphone feature. Audio samples are analysed locally in memory for supported sound events. The application does not intentionally store or transmit raw audio recordings.
Detection measurements: The app calculates temporary measurements such as audio level, peak amplitude, noise estimate and frequency. These measurements are used locally by the detection algorithms and are not uploaded to a Vokey server.
Local app preferences and history: Settings such as alert preferences, voice-command choices and onboarding state are stored on your device. The event history stores event type, time and limited numeric metadata (for example, a detected frequency or count). The history is limited to the most recent 250 events. You can clear it in Settings. This data is not sent to a Vokey backend.
Offline voice model: If you choose to enable offline voice commands, the app downloads the English (US) Vosk model once over HTTPS and stores it in the app's private storage. The download request is sent to the model host and may expose normal network metadata such as IP address and request headers to that host. Once installed, recognition and supported command matching happen on the device without a speech-to-cloud service. Vokey does not store transcripts or upload audio.
Device and battery information: The Battery Centre reads charge level, charging state, reported battery health, temperature, voltage, Android power-saver state and app memory information. These readings are displayed locally and are not uploaded by Vokey.
Flashlight: If you enable flashlight alerts, Android Camera permission is required on supported versions. Vokey uses the Android torch API only. It does not open a camera preview, capture photos or record video. The torch may be unavailable when another app is using the camera or the device has no supported flash.
Optional screen lock: If you enable the optional Voice Screen Lock, Android asks you to activate a Device Admin permission that allows the app to lock the device. The feature only requests the lock action; it cannot unlock the device or bypass your PIN, pattern, password or biometrics.
Information we do not ask for: Vokey does not require your name, email address, phone number, contacts, SMS, call history, precise location or account credentials for its core finder features.
2. When the microphone is active
- Microphone capture starts only after an intentional action in the app and the required Android permission.
- Active finder monitoring runs as an Android microphone foreground service and displays an ongoing notification with a Stop action.
- Audio is processed on the device and is not intended to be retained as a recording.
- You can stop an active test or finder mode in the app. You can also revoke microphone permission in Android settings.
Detection performance depends on your device microphone, microphone placement, Android version, surroundings and noise. Vokey does not guarantee that every clap, whistle or voice command will be detected.
3. Advertising and third-party services
Vokey includes the Google Mobile Ads Flutter SDK and Google's User Messaging Platform (UMP). At app launch, UMP requests updated consent information and displays any required consent form. Vokey checks UMP's canRequestAds() status before it creates an ad request. If the consent refresh or required form cannot complete, advertising remains disabled for that session. Where UMP requires a privacy-options entry point, the app shows a Settings item that opens Google's privacy choices.
The current ad placement is a standard banner on the Home screen only when finder monitoring is off. Ads are not shown while microphone monitoring is active or on the finder, alert, permission and other feature screens. Development builds use Google's test banner unit. A production banner request is made only when a real AdMob banner unit ID is supplied to the release build; without that ID, no banner is requested. The Google Mobile Ads SDK remains included in the application package.
When the Google Mobile Ads SDK is initialized or an ad request is made, Google may automatically collect and share information for advertising, analytics, measurement and fraud prevention, including:
- IP address, which may be used to estimate a device's general location;
- Product interactions, such as app launches, taps and ad views;
- Diagnostic information about app and SDK performance, such as launch time, hangs and energy use;
- Device and account identifiers, including Android Advertising ID and app-set identifiers where available and permitted. Android Advertising ID collection is optional and may be limited by device settings or SDK configuration.
Google states that information collected by the Google Mobile Ads SDK is encrypted in transit using TLS. The exact data processed depends on the SDK version, app configuration, device settings, user choices and applicable law. Google describes its SDK data practices in its Google Mobile Ads SDK data disclosure, Google Privacy Policy and advertising technologies information.
Vokey also uses the Vosk model host for the optional one-time English speech-model download. The model download request is sent over HTTPS and the host can receive normal connection metadata such as IP address and request headers. After installation, speech recognition runs locally and no speech audio is sent to a cloud recognition service.
We do not control the independent privacy practices of Google or other third-party providers. The Google Play Data safety form must be completed against the exact SDK versions and release configuration. The inclusion of an advertising SDK must be disclosed even in builds where the production banner unit ID is not configured.
4. How information is used
Vokey uses locally processed audio to detect supported sound events and commands, local preferences to remember your chosen settings, and local event metadata to show your detection history. Google Mobile Ads and UMP are included for the optional Home banner placement and privacy-choice flow. Vokey does not sell microphone recordings or use microphone audio to build advertising profiles.
5. Sharing and disclosure
Vokey does not send microphone audio, voice transcripts or local finder preferences to a Vokey-operated server. When the Google Mobile Ads SDK is initialized or an ad request is made, advertising-related information described above may be sent to Google and its service providers under Google's service and privacy terms. The optional speech-model installer sends a download request to the model host over HTTPS; that host can receive normal connection metadata. We may also disclose information where required by law or to protect the security and rights of users and the service.
6. Storage and retention
App preferences, the optional offline speech model and event history are stored in Vokey's app-private storage. Event history is capped at 250 records and can be cleared in Settings. Android removes the app-private data when you uninstall the app. The speech model can be removed by clearing Vokey's app storage. Advertising data retention is governed by Google and its partners' applicable privacy terms and controls.
7. Security
We design Vokey to minimise the information it handles. Microphone processing is local, and the app does not maintain a Vokey account database or cloud audio store. No method of electronic storage or transmission is completely risk-free. Third-party advertising traffic is handled under the provider's own security controls.
8. Children's privacy
Vokey is a general utility and is not designed or marketed specifically for children. We do not knowingly collect children's personal information through a Vokey account or backend. The app's target-audience and advertising settings must be configured consistently with the actual release and Google Play Families requirements if children are included in the intended audience.
9. Your choices
- Grant or revoke microphone permission using Android system settings.
- Stop microphone testing or monitoring using the in-app Stop control or the monitoring notification when available.
- Change local preferences in Vokey or clear Vokey's app storage/uninstall the app to remove locally stored settings.
- Use Android and Google advertising privacy controls to manage advertising identifiers and ad personalization where available.
10. Changes to this policy
We may update this Privacy Policy when app features, permissions, advertising SDKs or legal requirements change. The updated date at the top of this page will show when the policy was last revised. Material changes will be communicated in the app or through the app's store listing where appropriate.
11. Contact
For privacy questions or requests, use the developer contact details shown on the Vokey Google Play Store listing. Those contact details must be published and monitored before the app is released.