Wrist Trainer Privacy Policy
This policy applies to Wrist Trainer (com.ugk.wristrehab). Core training, local history and local deletion do not require an account. The App uses device motion sensors for repetition counting.
1. Training and settings on your device
Raw accelerometer and gyroscope samples are processed in device memory, not persisted or uploaded. Training summaries, including start/end times, counting settings, repetition counts and the largest estimated change in device orientation, and preferences such as theme, language and orientation stay on the device. The current limit is 100 summaries. Account and subscription services do not receive training data or provide training cloud sync.
2. Optional accounts and sign-in
Android uses Google sign-in and processes its stable user identifier, email, display name and profile image URL. iOS uses Sign in with Apple and processes the stable Apple user identifier and an authorized name, email or private relay address. Apple and Google identities are separate; matching emails do not automatically link accounts or share membership.
Login credentials are sent over an encrypted connection to the separate Wrist account service for validation. Original identity tokens and Apple's one-use authorization codes are not persisted or written to App logs. The Cloudflare Worker/D1 service stores accounts, identity mappings, HMAC fingerprints of sessions, expiry times and verified membership snapshots. The original Wrist session stays in system secure storage (iOS Keychain); server sessions expire after 30 days by default.
The first Apple authorization name may temporarily be kept in Keychain, isolated by Apple identity, for retry after a network failure. It is removed after the server confirms saving the name and contains no identity token, authorization code or nonce. The Apple refresh token required for authorization revocation is encrypted with a separate server key, stored only in Wrist D1 and removed on account deletion.
3. Membership, payment and subscription analytics
Signing in does not activate membership. Google Play handles Android checkout and Apple App Store handles iOS checkout. RevenueCat provides products, purchase/restore processing, receipt validation and subscription status. Android membership uses the Wrist account ID to associate purchase history and entitlements and is verified by the Wrist service. On iOS, purchasing, restoring and using membership do not require an App account. The subscription SDK retains a customer identifier on the device; new installations use an anonymous identifier by default. Verified App Store entitlements provide membership independently of optional Apple sign-in, which does not switch the subscription customer identifier. Purchase records associated by earlier versions remain subject to the relevant service retention policies. Signing out of or deleting an App account does not cancel a store subscription.
Payment cards and other payment instruments are handled by the store; Wrist does not receive these payment details. The App does not actively set names, emails, phone numbers, training data or marketing attribution as RevenueCat custom customer attributes, or enable advertising attribution or cross-app advertising tracking.
The subscription SDK still processes technical metadata such as the vendor device identifier (IDFV), OS/App versions, locales, store environment, request times and privacy permission status (ATT). Reading that status does not mean the App requests tracking permission or performs advertising tracking. RevenueCat handles subscription and technical records under its service rules; see its privacy policy. Disabling SDK debugging diagnostics does not disable all technical service data.
RevenueCat also retains first and most recent service connection times and infers a country from the IP address of the last connection for subscription analytics. According to its service documentation, it retains the country and discards the original IP used to infer it. This is not GPS location. Subscription webhooks received by Wrist may contain this country information alongside transaction events for membership verification, subscription analytics and event troubleshooting.
4. Service providers, network and support
Apple or Google verify sign-in and handle payments, RevenueCat processes subscriptions, and Cloudflare hosts the account API and static website. Requests contain network information needed to provide these services. Hosting providers may process IP addresses, browser/client versions, request paths, times and security logs for delivery, security and troubleshooting, retaining records under their policies and legal obligations.
The account service enables necessary request and diagnostic logs, including request outcomes, errors, CPU execution time and elapsed response time, to check service operation and troubleshoot failures. These logs do not contain training samples; Wrist does not actively log original login credentials or session tokens.
This page has no advertising, analytics scripts or cookies. The App has no separate training-behavior analytics SDK, does not sell or rent training data, and does not request location, contacts, camera, microphone, photo, HealthKit or Health Connect access. If you voluntarily contact support, your email, message and reply records are used to handle support and privacy requests.
5. Retention, deletion and cancellation
You can delete all local summaries on the History page or clear App data through the OS; system backup settings may affect local retention. Deleting training history does not erase purchase history.
In the App, open Account, tap Settings at the top right, then choose Delete account. This deletes Wrist-controlled accounts, identity mappings, sessions, membership snapshots and linked webhook records, and clears the device's secure session. On iOS it also revokes this App's Apple authorization; failures are reported and can be retried. Local training records are deleted separately. If the App is inaccessible, use the account-deletion instructions.
To safely recognize repeated deletion requests and prevent misuse, Wrist retains a separate deletion-completion record: a random operation identifier, a session HMAC fingerprint and the completion time. These records do not cascade-delete with the account, contain no name, email or original login credentials, and currently have no automatic cleanup period.
Deleting an account does not cancel a store subscription.On iPhone, cancel renewal in Settings → Apple Account → Subscriptions or the App's Manage subscription entry. On Android, use Google Play → Payments and subscriptions → Subscriptions. You can delete your Wrist account without waiting for the subscription to expire. Transaction/security records retained by Apple, Google or RevenueCat under their service rules or legal obligations are not automatically erased by deleting a Wrist account.
6. Security, children and updates
Encrypted transport, device secure storage, session fingerprints and encrypted Apple revocation credentials protect data, but no technology guarantees absolute security. The App is intended for adults, is not directed at children and does not knowingly collect children's personal information. We update this policy and check store disclosures when features or processing change.
7. Contact
For privacy, feedback or account-deletion requests, use the website's support contact. Never send passwords, verification codes, identity tokens, authorization codes, session tokens or payment-card details.