WristCapture: Phone Screenshot Privacy Policy

# WristCapture Privacy Policy Last updated: September 4, 2026 WristCapture is an Android and Wear OS utility that lets you deliberately request the paired Android phone's normal system screenshot action from a Wear OS watch. This policy describes the current WristCapture app behavior. If the app's permissions, SDKs, data handling, or features change, this policy will be reviewed before the changed behavior is released. ## What WristCapture does A deliberate WristCapture action on the watch sends an operational request to the paired phone. The phone validates the request and required conditions, then asks Android to run its built-in screenshot global action. Android creates and stores the screenshot. WristCapture does not receive the screenshot image. ## Screenshot and screen-content privacy WristCapture does not access, collect, upload, analyze, edit, or retain: - Screenshot images or thumbnails. - Screenshot filenames or file paths. - Gallery contents. - Visible screen text. - Accessibility node contents. - Accessibility event contents. - Typed text or form values. - Foreground-app contents. WristCapture does not provide a screenshot gallery. Screenshots created by Android must be viewed, managed, or deleted using Android's normal screenshot, gallery, or file-management tools. Android and individual apps can block or blank screenshots of protected or secure content. WristCapture does not bypass those protections. ## AccessibilityService WristCapture uses Android AccessibilityService for one core purpose: requesting Android's built-in Take screenshot global action after a deliberate WristCapture capture request or the phone compatibility test. The service is configured not to retrieve window content and WristCapture does not inspect accessibility events or accessibility node trees. Before WristCapture sends you to Android Accessibility settings, the app presents a prominent disclosure and asks for affirmative consent. You can decline. You can disable WristCapture's AccessibilityService at any time in Android settings. WristCapture does not use the service to read visible text, inspect other apps, dispatch arbitrary gestures, type content, unlock the device, or run hidden or scheduled screenshots. ## Help, feedback, and diagnostics WristCapture provides a Help & feedback flow for reporting bugs, requesting features, and contacting the developer. The canonical support page is https://consultant.quinnfavo.com/support/wristcapture. Opening the support page is a user action. WristCapture does not silently submit a support request or automatically upload diagnostics. If you choose Copy diagnostics, WristCapture generates a sanitized summary locally and places it on the system clipboard. You decide whether to paste or submit that summary. The allowlisted summary can include app versions, device/API information, support context, AccessibilityService enabled/connected state, protocol/capability categories, connected-node category, safe result classifications, screen/lock eligibility, timeout category, and entitlement category. Support diagnostics do not include: - Screenshot pixels, image data, screenshot files, filenames, or paths. - Gallery information. - Accessibility node content, accessibility event text, or raw accessibility hierarchy. - Foreground-app or private screen content. - Purchase tokens, order IDs, payment details, or Google account information. - Reviewer plaintext codes or reviewer-code hashes. - Secret material. - Sensitive raw Data Layer payloads. - Arbitrary logcat output. The support URL itself is limited to a support type, source (android or wear), safe context, and app version. Request IDs and diagnostic bundles are not placed in support URLs. When Help & feedback is initiated from Wear OS, the watch can send a small versioned support-navigation message to the paired phone so the phone can open the support surface. This support path is separate from the screenshot-request path and does not authorize or replay a capture. Information voluntarily entered into the external support webpage is handled as a separate, explicit web interaction. ## Information stored locally WristCapture stores limited operational state on your phone or watch so the app can work reliably. Depending on the features you use, this can include: - Setup and disclosure acknowledgement. - Compatibility-test state. - Reduced purchase-entitlement and verification state. - The number of included watch captures already used. - Temporary local Play-review access state when applicable. - Watch auto-close and haptic preferences. - A paired-device node identifier used for deterministic phone selection. - Recent random capture request identifiers used to prevent replay or duplicate execution. - Short-lived prompt/throttle state, including support-navigation deduplication/throttling. - A random per-install Wear quick-action marker used to distinguish WristCapture-created Tile and complication launches. This operational state is not sent to a WristCapture developer backend because WristCapture does not operate one. Clearing app storage or uninstalling the relevant phone/watch app removes that app's local WristCapture state, subject to normal Android and Google Play behavior for purchases and app installation. ## Phone and watch communication WristCapture uses the Wear OS Data Layer provided through Google Play services to communicate between the paired phone and watch. Operational messages can include values such as: - Protocol and app version information. - Random request identifiers. - Request timestamps. - Capture trigger source. - Safe support context for Help & feedback navigation. - Capture status or failure reason. - Compatibility state. - Reduced entitlement state. - Remaining included-capture count. - Watch behavior settings. These messages do not contain screenshot images, visible screen content, gallery data, payment details, reviewer secrets, copied diagnostic bundles, or the local Wear quick-action marker. WristCapture does not operate a server that receives these paired-device messages. Google Play services may process device/service data as part of providing its platform functionality under Google's own terms and privacy policies. ## Purchases Lifetime Pro purchases are processed by Google Play Billing on the Android phone. WristCapture uses Google Play-provided product and ownership information to display localized pricing, start the purchase flow, acknowledge completed purchases, restore ownership, and reconcile entitlement state. WristCapture does not store payment-card details. It does not send purchase tokens, order identifiers, payment details, or Play account information to the Wear OS app or support diagnostics. Google processes purchase and account information under Google's own terms and privacy policies. ## Accounts, advertising, analytics, and developer backend WristCapture currently has: - No WristCapture user account system. - No developer-operated app backend. - No advertising SDK. - No developer analytics SDK. - No developer crash-upload SDK. The external support webpage is a separate web surface and does not change the app's no-account/no-telemetry posture. Because WristCapture does not create a WristCapture account, there is no separate WristCapture account-deletion process. Local WristCapture app data can be removed by clearing app storage or uninstalling the app. ## Permissions The phone app uses AccessibilityService only for the screenshot-request function described above. The current core feature and Help & feedback flow do not require WristCapture to request photo, broad storage, camera, microphone, contacts, or location permission. The Wear OS app does not need those permissions for the core capture-request or support-navigation flow. Third-party platform libraries can contribute their own manifest declarations. Release builds are reviewed against the merged manifests before publication. ## Data Safety and third-party services Google Play Data Safety declarations must be completed against the exact submitted bundles and current Google Play definitions. The main platform services used by WristCapture are: - Google Play services / Wear OS Data Layer for paired-device communication. - Google Play Billing for purchases. - The user's browser for the user-initiated support webpage. Device-local processing, paired-device Data Layer traffic, user-initiated browser navigation, and data voluntarily submitted through the external support website are separate data flows and should not be treated as interchangeable. ## Security and reliability controls WristCapture limits capture requests using controls such as: - Versioned and bounded capture-protocol messages. - A separate bounded support-navigation protocol and path. - Request freshness checks. - Duplicate/replay protection. - Deterministic paired-phone selection. - Phone lock/screen and AccessibilityService checks. - Capture cooldown and transaction coordination. - Final phone-side purchase/reviewer/included-use checks. - Timeout handling without automatic resend. - Local validation of WristCapture-created Tile and complication quick actions. - A typed diagnostic allowlist with no screenshot/accessibility-content or billing/reviewer-secret input. These controls are designed to keep capture user-driven and to avoid duplicate or ambiguous execution. No software can guarantee that every screenshot request will succeed on every phone, firmware version, app, or protected screen. ## Children's privacy WristCapture is a general utility and is not specifically designed or marketed for children. It does not provide social features, advertising, or a developer-operated account service. ## Changes If WristCapture adds a new SDK, permission, backend, data-processing purpose, account system, advertising, analytics, support-data behavior, or screenshot-content access, this policy and related disclosures will be updated before that behavior is released. ## Contact For privacy or support questions, use the Help & feedback flow in WristCapture, the canonical WristCapture support page, or the developer contact information shown on the Google Play listing.