WristRevive: Battery Toolkit Privacy Policy

# WristRevive: Battery Toolkit Privacy Policy Last updated: July 15, 2026 ## Overview WristRevive is a planned Wear OS battery diagnostic and optimisation utility. It measures battery behaviour, creates local diagnostic timelines, supports controlled before-and-after tests, and guides reversible endurance-profile changes. WristRevive does not repair battery chemistry, silently control protected system settings, or provide guaranteed exact per-app electrical attribution. This policy describes the planned watch-first MVP. It will be checked against the final application code, manifest, dependencies, permissions, billing configuration, and release bundle before public launch. ## Data Stored Locally WristRevive may store the following information in app-private storage on the watch: - Battery percentage, charging state, timestamps, and elapsed-time references. - Battery temperature, voltage, current, average current, charge-counter, or energy-counter values when the watch exposes them. - Estimated drain rates, estimated remaining runtime, anomaly classifications, confidence values, and data-quality indicators. - Screen, ambient, interactive, charging, connectivity, or other diagnostic context when available through supported Android APIs. - Device manufacturer, model, Android and Wear OS version, security patch, software-build identifiers, boot markers, and software-update epochs used for diagnostic comparisons. - Revive Scan configuration, progress, results, and history. - Controlled-test phases, comparison results, user annotations, and restoration state. - Active endurance-profile state, explicitly confirmed actions, and restoration checklists. - App settings, onboarding state, retention preferences, and Tile or complication preferences. This information is used to provide WristRevive's battery timelines, estimates, classifications, controlled comparisons, endurance profiles, Tile, and complication. It is not planned to be stored on a developer-operated server in the watch-first MVP. ## Optional Usage Access WristRevive may offer optional Usage Access to improve diagnostic context. When the user explicitly enables this access, WristRevive may read supported foreground-application or interaction context to determine whether a high-drain period coincided with particular watch activity. Usage context is used for correlation, not guaranteed electrical attribution. WristRevive must not state that an application consumed an exact amount of power unless Android provides a supported and reliable source for that claim. In the planned watch-first MVP, usage context is processed and retained locally and is not uploaded to the developer. Users can decline or revoke optional Usage Access. Core percentage-based battery monitoring and supported diagnostics should continue with reduced context where practical. ## Permissions And System Access WristRevive may use Android and Wear OS capabilities required to: - Read battery state and supported battery properties. - Schedule low-overhead, inexact background work. - restore scheduled collection after a device restart or application update where supported. - Provide a Wear OS Tile and watch-face complication. - Open public Android settings screens after a user chooses to review a recommended setting. - Read optional Usage Access context only after the user grants that access. WristRevive does not require root, ADB, Shizuku, accessibility automation, device-owner privileges, or silent control of protected Wi-Fi, Bluetooth, LTE, airplane-mode, global Battery Saver, or third-party application state. The planned watch-first MVP does not use location, microphone, camera, contacts, calendar, photos, files, or health-data permissions for its battery diagnostic workflow. ## Background Behaviour WristRevive uses bounded, low-overhead background collection so that the diagnostic tool does not become a significant battery problem itself. The planned design avoids continuous high-frequency polling, continuous sensor streams, persistent wake locks, indefinite foreground services, and high-frequency network traffic. Controlled tests may temporarily use a defined collection schedule for the duration of the test. ## Network And Third-Party Services The planned watch-first MVP does not include a developer-operated cloud backend, account system, cloud sync, advertising SDK, analytics SDK, remote-configuration service, or developer-controlled tracking service. Google Play may process standard app distribution, installation, update, purchase, refund, licensing, and store-related information under Google's own policies. WristRevive does not receive payment-card details. A future phone companion, export feature, benchmark service, crash-reporting service, or other network feature would require a review and update of this policy before release. ## Data Collection And Sharing The developer does not plan to collect or receive personal data, battery history, application-usage context, device diagnostic history, or profile activity through the watch-first MVP. WristRevive does not sell personal information and does not share personal information with advertisers. The final Google Play Data safety declaration will be verified against the production release build before launch. ## Data Retention Battery samples, scans, tests, and diagnostic history are retained locally according to the application's bounded-retention rules and user-facing history limits. Older local records may be automatically removed to limit storage and monitoring overhead. Clearing WristRevive's app storage or uninstalling the app removes its local app-private data, subject to normal operating-system backup and deletion behaviour. ## Data Deletion Users can remove local WristRevive data by clearing the app's storage in Wear OS settings or uninstalling WristRevive from the watch. Because the planned watch-first MVP has no WristRevive account system or developer backend, there is no server-side WristRevive account data to delete. ## Security WristRevive relies on Android app-private storage and the device's operating-system security controls to protect locally stored information. Users should keep their watch, operating system, and Google Play services updated and use an appropriate device lock where available. No method of storage is completely risk-free, but WristRevive is designed to minimise exposure by keeping diagnostic data local and avoiding unnecessary third-party services. ## Children WristRevive is not directed specifically to children and is not designed to collect personal information from children. ## Changes To This Policy This policy may be updated if WristRevive's functionality, permissions, dependencies, billing model, phone-companion plans, export capabilities, or data practices change. The effective date at the top will be updated when material changes are made. ## Contact For privacy questions or support, contact Quazmoz@vivaldi.net.