Back to Privacy Hub
dbGuard Noise Meter Privacy Policy
Last Updated: July 6, 2026
Quick Summary
A standalone Wear OS noise meter that uses microphone input only for local decibel estimation and does not record, store, or transmit raw audio.
App-Specific Details
Specific data handling practices for dbGuard Noise Meter.
- Stores locally: decibel readings or recent exposure history where enabled, threshold settings, haptic/visual alert preferences, app preferences, complication or quick-launch state where available.
- Uses only the app permissions needed for current functionality: RECORD_AUDIO or microphone access for local decibel estimation, POST_NOTIFICATIONS where noise alerts are enabled on supported versions, VIBRATE for haptic cues.
- Uses platform services where required: Google Play app distribution and updates, Wear OS complication support where available.
- Not described by the current app code: account system, developer backend, cloud sync, ads, analytics SDK, location, camera, contacts, calendar, files/photos, health/body sensors, advertising ID.
- Local app data is removed when you clear app storage or uninstall the app.
- Audio is processed temporarily in memory for local dB estimation and is not recorded, stored, or transmitted to the developer.
Detailed Official Policy
Full technical and legal disclosure for dbGuard Noise Meter.
# dbGuard Noise Meter Privacy Policy
Last updated: July 5, 2026
dbGuard Noise Meter is published by Quazmoz / Quinn Favo.
## Summary
A standalone Wear OS noise meter that uses microphone input only for local decibel estimation and does not record, store, or transmit raw audio.
The app is designed to minimize data collection. Unless a feature explicitly uses a platform service listed below, app content is stored locally on your device and is not sent to a developer-operated backend.
## Data stored locally
The app may store the following data locally on your device:
- decibel readings or recent exposure history where enabled
- threshold settings
- haptic/visual alert preferences
- app preferences
- complication or quick-launch state where available
This data is used only to operate the app features you choose to use.
## Permissions
The current app code may use the following permissions or permission-backed capabilities:
- RECORD_AUDIO or microphone access for local decibel estimation
- POST_NOTIFICATIONS where noise alerts are enabled on supported versions
- VIBRATE for haptic cues
## Platform services
The app may rely on these platform or user-selected services:
- Google Play app distribution and updates
- Wear OS complication support where available
These providers may process limited technical or transaction data according to their own policies.
## Data collection and sharing
The developer does not sell personal information and does not share personal information with advertisers. The current app code does not include a developer-operated account system, advertising SDK, or analytics SDK unless specifically stated in this policy.
## What the app does not use
The following are not described by the current app code:
- account system
- developer backend
- cloud sync
- ads
- analytics SDK
- location
- camera
- contacts
- calendar
- files/photos
- health/body sensors
- advertising ID
## Data deletion
You can delete local app data by clearing app storage in Android or Wear OS settings or by uninstalling the app. If the app includes an in-app reset, clear-history, delete-data, or export feature, that feature applies only to local app data unless explicitly stated otherwise.
## Safety note
dbGuard is informational only. It is not a certified hearing protection device, medical device, or workplace safety instrument.
## Contact
For privacy questions or support, contact Quazmoz@vivaldi.net.
General Privacy Terms
These terms apply across all our applications.
Questions or privacy requests? Contact us at Quazmoz@vivaldi.net