DOWNRANGE SCORE LAB — PRIVACY NOTICE Version 2026-11-02.1 • 2 November 2026 1. Who is responsible Downrange Score Lab LTD (company number 17512168) is responsible for personal information handled for its service. Registered office: Unit 6 Nuffield Trade Centre, Poole, BH17 0UF. Email info@downrangescorelab.com for support, privacy, access, correction and account deletion requests. The launch service is for UK residents aged 18 or over. This notice covers the website and released iOS and Android apps. Acknowledging it means it was provided to you; it is not blanket consent to other uses. 2. Website, accounts and access The public marketing site serves its fonts, images and film without advertising trackers or third-party analytics scripts. Its interactive product preview uses fictional sample records. Hosting systems receive connection information such as IP address and requested page to deliver and protect the website; this is separate from your local scoring records. When account services are available, they hold username, email, display name, salted password hash, account identifier, session/device-binding information, terms/privacy version receipts, eligibility declaration, and subscription verification references. Passwords are not stored as readable text. An essential browser cookie maintains a web session. Paired native apps keep their session credential in device-protected Keychain on iOS or Keystore-backed storage on Android; the server uses account identity and short-lived access checks. Signing in is not consent to research or public sharing. Downrange does not ask for your Apple or Google password. 3. Scoring and training records You choose to enter shooter names or codes, courses, stages, sessions, target impacts, scores, times and splits, notes, drafts and training progress. Optional cognitive tasks and workload ratings can be linked to those local records. Managers are responsible for having authority and a lawful basis to enter other shooters' information. The web scoring workspace keeps these records in account-scoped browser storage on that device. Signing out does not erase it, and clearing browser storage can remove it. Android keeps scoring records in private app storage; the current Android app disables its own operating-system backup. iOS keeps app-private records and can place recovery snapshots, including linked training/cognitive records, in your Apple account's private CloudKit database. Apple operates iCloud. A private recovery snapshot is not guaranteed complete backup or website/Android score synchronisation. Shared subscription access does not automatically upload or synchronise scores across these platforms. In the current iOS release, automatic collection is on by default for newly saved score data and newly completed cognitive records. Uploads are associated with a pseudonymous device identifier. Score uploads contain numeric scores, timing and target observations, a run reference and any shoot, stage or team-session references; the score producer excludes names, photographs and free-text notes. Cognitive uploads contain the completed task's JSON result and any associated group, session or shoot references retained with that result. Coded records are not necessarily anonymous. This collection is separate from a public leaderboard and from synchronising scoring history between platforms. You can stop automatic score and cognitive sending in Settings by selecting ‘Do not automatically send score and cognitive data’. The choice applies to both paths and holds queued automatic originals. It does not delete data already received or erase local results. Turning automatic collection on again applies to future completions; earlier held records are not automatically restarted. Assigned Study submissions remain a separate intentional action, described below. 4. Optional device features On iOS, target-image scoring requests camera or photo-library access when chosen and processes target images on the device. Images and annotations can remain with app records. The phone timer uses microphone access to detect events and record timing values; the inspected implementation has no audio-recording upload route. Compatible external timers use Bluetooth timing values and splits. Android target photos are processed locally; temporary captures can remain in app cache and saved target photos remain in private app storage until cleared. Its microphone timing detects live events without a file-audio upload path. Bluetooth scanning on Android 11 and earlier may request location permission, but the app does not collect location coordinates. Available permissions and tools vary by platform. You can deny or change permissions in device settings, although this can disable that tool. A device permission is not permission for research or public sharing. 5. Payments and providers Apple processes App Store purchases and provides signed transaction information for native subscription verification. Google Play manages Google Play purchases; the current release must not claim verified new Google purchase access until that integration is operational. Relevant transaction information includes product, transaction/subscription identifiers, account-binding token where used, environment, expiry and cancellation/revocation status. Store and provider privacy notices apply to their own services: apple.com/legal/privacy and policies.google.com/privacy. Apple also operates optional private iCloud storage and any Apple diagnostic reports made available under your device/provider settings. Your email provider or a service you choose for an export processes what you send to it. These providers can process information outside the UK under their own notices. This notice does not claim a particular hosting country, automatic backup purge or unverified international-transfer arrangement. Downrange's collection service receives the automatic uploads and assigned Study submissions described in this notice. Access to server account records is restricted to authorised operators for service, security, support and legal purposes. We do not sell scoring records. 6. Purposes and lawful bases Account registration, authentication, subscription verification and requested service functions are used to provide the service contract. Payment and compliance records are used to meet applicable legal obligations where required. Security and responding to support requests serve legitimate interests in protecting accounts and providing reliable assistance, subject to your rights. Optional device processing follows your chosen action and operating-system controls; privacy acknowledgement is not a substitute for any consent required by law. Automatic score and cognitive uploads follow the collection setting described in section 3. Cognitive/workload records are descriptive practice records, not a diagnosis. Completing an ordinary cognitive task does not itself submit an assigned Study. Any future processing that reveals health or other special-category information needs an appropriate additional condition and safeguards before it is enabled. 7. Sharing, research and automated decisions User-selected exports create independent files. We cannot recall copies you send to others. The app does not automatically publish results to a public leaderboard or enrol you into an assigned Study. Automatic collection is described in section 3. For an assigned Study, the app displays versioned participant, withdrawal and retention information. Completing its form and choosing Submit records your decision to participate in that Study and sends the response. General app acceptance, a manager action or a purchase does not itself submit an assigned Study. Scoring calculations and progress suggestions assist you; they are not decisions determining employment, medical status or fitness for duty. 8. Retention and deletion Local records remain until you remove them using available deletion controls or clear app/browser storage. Private iCloud snapshots and exported copies can remain separately. Provider purchase and diagnostic records follow the relevant provider's retention rules. Downrange account, subscription-binding and acceptance records are needed while providing and protecting the account; on an erasure request, an authorised operator reviews what can be removed and what remains necessary for accounting, a legal obligation or a specific dispute/security matter. Support correspondence is needed to respond, follow up and resolve a related dispute or legal obligation. These are retention criteria, not a promise of a fixed automatic deletion period. Hosting connection logs and backup schedules must be confirmed by the actual operator; this notice does not promise they disappear immediately. Request deletion or other rights at info@downrangescorelab.com. Where available, the authenticated account screen can create an erasure request receipt and separately close access by revoking sessions and device bindings. Closure alone does not erase retained records or cancel subscriptions. A pending request is not completed erasure. We may take reasonable steps to verify your identity and explain any records retained and why. Deleting one local copy does not delete an export, another person's file, iCloud copy or provider's record. We cannot directly retrieve your private local/iCloud records merely from your Downrange account. 9. Rights and changes Depending on the information, lawful basis and circumstances, you may request access, correction, erasure, restriction, portability, or object to processing, and withdraw a specific consent without affecting earlier lawful processing. Contact the monitored email above. You may complain to the UK Information Commissioner's Office at ico.org.uk/make-a-complaint. We update the dated notice when data handling materially changes and seek a new choice where required. Automatic collection follows the Settings choice described above. Participation in an assigned Study is recorded when you complete and submit its form; public sharing is not inferred from ordinary use.