Back to Privacy Hub
CountCue Multi Timer Wear OS Privacy Policy
Last Updated: July 8, 2026
Quick Summary
A standalone Wear OS multi-timer that stores timer names, durations, active timer state, history, notification state, tile/complication state, and optional Pro entitlement state locally.
App-Specific Details
Specific data handling practices for CountCue Multi Timer Wear OS.
- Stores locally: timer names and durations, active timer state, completion history, notification and alarm state, tile and complication state, app preferences, optional Pro entitlement state.
- Uses only the app permissions needed for current functionality: POST_NOTIFICATIONS for timer alerts on supported versions, SCHEDULE_EXACT_ALARM or alarm APIs where needed for user-created timers, VIBRATE for haptic cues, RECEIVE_BOOT_COMPLETED where needed to restore user-created timer/reminder state, foreground service capability where needed for active user-started timers.
- Uses platform services where required: Google Play Billing for optional one-time Pro unlock, Google Play app distribution and updates, Wear OS tiles and complications.
- Not described by the current app code: account system, developer backend, custom cloud sync, ads, analytics SDK, location, microphone, camera, contacts, calendar, files/photos, health/body sensors, advertising ID.
- Local app data is removed when you clear app storage or uninstall the app.
Detailed Official Policy
Full technical and legal disclosure for CountCue Multi Timer Wear OS.
# CountCue Multi Timer Wear OS Privacy Policy
Last updated: July 5, 2026
CountCue Multi Timer Wear OS is published by Quazmoz / Quinn Favo.
## Summary
A standalone Wear OS multi-timer that stores timer names, durations, active timer state, history, notification state, tile/complication state, and optional Pro entitlement state locally.
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:
- timer names and durations
- active timer state
- completion history
- notification and alarm state
- tile and complication state
- app preferences
- optional Pro entitlement state
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:
- POST_NOTIFICATIONS for timer alerts on supported versions
- SCHEDULE_EXACT_ALARM or alarm APIs where needed for user-created timers
- VIBRATE for haptic cues
- RECEIVE_BOOT_COMPLETED where needed to restore user-created timer/reminder state
- foreground service capability where needed for active user-started timers
## Platform services
The app may rely on these platform or user-selected services:
- Google Play Billing for optional one-time Pro unlock
- Google Play app distribution and updates
- Wear OS tiles and complications
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
- custom cloud sync
- ads
- analytics SDK
- location
- microphone
- 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.
## 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