Data handling in ArcheryNow for Android

This supplement explains Android purchases, backups, AI Coach, Club features and the deletion-request route. Read it with the Privacy Policy and Terms of Service. It makes the Privacy Policy’s general platform descriptions specific to the current Android implementation. Where descriptions of Android data handling differ, the specific explanation in this supplement takes precedence. It does not change the scope of iOS features.

Club accounts and explicit sharing

Club features use Supabase authentication, databases and private storage. Depending on the enabled sign-in method shown in the app, we process provider identifiers from Google or another enabled provider, an email address if supplied, and account and session information. If you sign in to a provisioned account with an email address and password, those credentials are sent to Supabase for verification. Your password is not shared with Club members. Available sign-in methods vary by platform and configuration.

Joining a Club does not automatically send your existing personal records from your device. A record you choose to share includes its round label, date and time, score and maximum score, arrow count, 10 and X counts, administrative identifiers and revision information, and your selected audience. Recipients are authorized Club members, Team members or Team coaches.

For a Selection Event submission, we send a structured snapshot of your selected sessions, including competition settings and individual arrow values. Event permissions and visibility settings govern its use. Neither shared records nor Event submissions include your private notes, photos, locations or Arrow Plot impact positions. Separately choosing and uploading a Club icon or Profile image sends that image and its administrative information to private storage.

Purchases and purchase identifiers

Personal Pro purchases and restores on Android use Google Play and RevenueCat to check purchase status. Purchases on iOS use Apple’s App Store. The relevant store and RevenueCat process purchase, subscription and restore status, identifiers used for purchases, and technical information. Personal Pro and Club plans are separate: buying Pro or joining a Club does not by itself start Club billing.

On Android, a RevenueCat anonymous purchase identifier with purchase history may be stored in Google Block Store with Google cloud backup. This helps recover purchase identity after reinstallation or device migration. It is not a backup of score records or a Club sign-in. The app does not store a Club authentication token as this purchase identifier.

Purchases, cancellations and refunds follow the terms of the store where you purchased. Account deletion or uninstallation does not cancel a subscription. Purchase records and purchase-identifier handling must be considered separately from Club account deletion.

Local data and backups

Personal records are local-first. If you connect Google Drive and enable backup, personal records and other included data are sent through the backup features you choose. Automatic backup is not automatic synchronization that downloads and merges changes from other devices.

Depending on Android settings, databases, preferences, some note photos and some Form Tracking information may also be eligible for OS backup or device transfer. Club authentication sessions are stored separately in encrypted storage excluded from backup. “Stored on the device” does not mean that all backup mechanisms are always disabled.

AI Coach on Android

On supported devices, Google ML Kit and Gemini Nano process questions and record summaries on the device. When unavailable, the app may show that a download is needed or use a response built locally. Input content passed to ML Kit, such as text or images, and its outputs are processed on the device. The app does not send your questions or records to ArcheryNow’s servers or a cloud AI service to generate these responses. Separately, the ML Kit SDK sends usage, performance and error diagnostics, device and app information, user/device or other identifiers and per-installation identifiers to Google for diagnostics and usage analytics. This is separate from the input content itself. Model downloads, updates and OS services also follow Google’s terms. In-app advertising, usage analytics and backups are separate processing paths. See ML Kit privacy and SDK data collection.

Private enquiries and deletion requests

See account deletion. You can request deletion through the existing contact form without reinstalling the app. We verify your identity and the scope of the request. Do not send passwords, one-time codes, authentication tokens, secret keys or identity-document images. Do not post personal information or deletion requests in public GitHub Issues.

Provider policies: Google, RevenueCat, Apple, Supabase.