CountCue Wear OS Timer Privacy Policy

# CountCue Wear OS Timer Privacy Policy Last updated: August 17, 2026 CountCue is a standalone Wear OS timer and stopwatch app published by Quazmoz / Quinn Favo. ## Summary CountCue keeps its timer, stopwatch, history, settings, and entitlement data locally on the watch. It does not require a phone companion, app account, developer backend, advertising service, or analytics service. Google Play Billing is used for the optional permanent Pro purchase. Google Play independently handles payment and Google Account purchase information. ## Data stored locally Depending on the installed CountCue version and the features the user configures, the app may store: - Timer names, durations, and haptic choices. - Active timer state and scheduled alert information. - Completed timer history. - Stopwatch state and related local settings. - Saved timer, preset, bundle, or sequence definitions where available. - App and notification preferences. - Tile and watch-face complication state. - A local cache of optional Pro entitlement state. This information is used only to provide CountCue features on the watch. ## Timer scheduling and notifications The current CountCue manifest declares capabilities used for user-created timer alerts and recovery: - SCHEDULE_EXACT_ALARM for exact user-created timer alarms where Android permits it. - POST_NOTIFICATIONS for timer alerts on Android versions that require notification permission. - VIBRATE for haptic cues. - RECEIVE_BOOT_COMPLETED so eligible scheduled timer state can be restored after reboot. - WAKE_LOCK so time-sensitive alarm handling can complete reliably when required. CountCue does not declare a foreground-service permission in the current manifest. It does not use these capabilities for unrelated background tracking. ## Wear OS Tile and complications CountCue provides Wear OS Tile and watch-face complication surfaces for quick access, timer status, and stopwatch shortcuts where supported. These surfaces use app-local state and do not send timer content to a developer backend. ## Google Play Billing and Pro CountCue offers an optional one-time Pro purchase through Google Play Billing. Google Play handles payment processing, transaction history, and Google Account association. CountCue receives only the product and purchase state needed to display the offer, unlock eligible features, acknowledge a completed purchase, restore ownership, and reconcile entitlement state. The developer does not receive payment-card details. CountCue does not offer a subscription for the current Pro unlock. ## Network, accounts, advertising, and analytics CountCue does not use a developer-operated account system, application backend, custom cloud sync, advertising SDK, analytics SDK, location, microphone, camera, contacts, calendar, health/body sensors, or advertising ID for its current functionality. Google Play and packaged Google components may process app distribution, purchase, security, and technical service information under Google's policies. ## Backup and deletion The current app manifest disables Android application backup. CountCue app data remains local to the watch unless a platform service independently handles installation or purchase information. Users can remove local CountCue data by clearing app storage in Wear OS settings or uninstalling the app. Google Play purchase history is managed separately by Google Play and may be restored after reinstall. ## Safety CountCue is a general timing utility. Timer alerts can be affected by device state, Android alarm permissions, battery conditions, operating-system behavior, or hardware limitations. Do not rely on CountCue as the only timing mechanism for medical, emergency, safety-critical, legal, or other high-consequence situations. ## Changes This policy will be updated when CountCue materially changes its permissions, storage, SDKs, billing behavior, or data handling. ## Contact For privacy questions or support, contact Quazmoz@vivaldi.net.