Privacy Policy
Effective: 22 September 2026
1. About this policy
This Privacy Policy explains how the Jag Stories Android application and compatible Watch companion access, use, store and exchange information when you use the app. “Jag Stories”, “we”, “us” and “our” refer to the developer or entity named as Jag Stories in the applicable app-store listing.
Privacy enquiries and support requests may be sent to support@jagstories.com.
2. Information used by Jag Stories
| Category | Examples | Purpose |
|---|---|---|
| Weapon and shooting data | Weapon profiles, calibre, loads, DOPE, match stages, hit/miss information, timing and training results | Provide ballistics, training, match and analytics features |
| Training sensor data | Watch movement/stability measurements and trigger-related audio classifications during active sessions | Run TDFS, VTT, Reaction Drill, shot detection and calibration |
| Photos and camera input | Hunter's Room images, VTT camera images and QR scan camera input | Provide trophy records, VTT and Match Director QR joining |
| Participant profile information | Full name, date of birth/age, email address, location and Platform Unique ID | Allow participation in Match Director events and external-system identification where configured |
| Backup data | Supported Jag Stories records exported by the user | Backup, restore and user-directed transfer |
| Technical app data | App configuration, permissions state, calibration timestamps and device/watch synchronization status | Operate the app and maintain feature state |
3. On-device processing
Jag Stories is designed so that substantial app data and feature processing occur locally on the user’s devices. Data that remains only on the device is used to provide the requested app functionality and is not treated as remotely collected merely because the app accesses it locally.
4. Match Director local-network communication
When a user joins a public Match Director event, participating devices communicate over the local network. Current Jag Stories Match Director payloads use authenticated AES-256-GCM encryption at the application protocol layer. The QR join flow supplies the information required to establish the local match session.
Match Director participant information and result data are exchanged only as required for the event workflow. Users should join only matches they trust and only over networks they are comfortable using.
5. Permissions
Jag Stories may request camera, microphone, notification, media/photo, local-network and companion-device related permissions depending on the feature being used. Permission details and feature-specific explanations are available on the Permissions Explained page.
6. How information is used
Information is used to provide requested app functions, maintain saved records, calculate or display shooting information, run Watch-based training and match features, support Match Director event participation, create exports and backups, provide support, and maintain app security and reliability.
7. Sharing
Jag Stories does not require general public sharing of user records. Information may be shared when the user explicitly uses a sharing, export, backup, Match Director or other transfer feature. Match Director participants exchange only the information needed for that workflow. If third-party billing, crash-reporting, cloud or other services are added in a future production release, this policy and the Play Console Data safety declaration must be updated before those services are used.
8. Retention
Locally stored records remain on the user’s device until they are deleted, replaced through restore, removed by app/data deletion, or otherwise managed by the user. Jag Stories backup behavior may retain supported training history within the configured backup window. Match Director event information is retained only as needed for the event and saved records selected by the user.
9. Deletion and correction
Users can remove supported records through Jag Stories features where deletion is available, remove application data through Android, or uninstall the app. Privacy, access, correction or deletion enquiries may also be sent to support@jagstories.com. Users can also follow the steps on the Delete Data page. If account-based services are introduced later, Jag Stories will provide the deletion mechanisms required for those account services.
10. Security
We use reasonable technical and organizational safeguards appropriate to the app’s design. These include platform permission controls, local device storage protections and encrypted Match Director payload communication. No storage or transmission method can be guaranteed to be completely secure.
11. Children
Jag Stories is designed for responsible shooting, training, competition and hunting use. The app is not intended to encourage unsupervised firearm use by children. Where a minor is permitted to use the app under applicable law, appropriate adult supervision and lawful firearm-safety practices remain essential.
12. South African privacy rights
Where the Protection of Personal Information Act 4 of 2013 (POPIA) applies, personal information should be processed lawfully, for defined purposes, and in a manner that is adequate, relevant and not excessive. Users may request access to, correction of, or deletion of personal information where applicable and may raise privacy concerns through the contact details above.
13. International users
Users outside South Africa may have additional rights under their local privacy laws. We will respond to valid privacy requests as required by applicable law.
14. Changes to this policy
This policy may be updated when Jag Stories functionality, data handling or legal requirements change. The effective date at the top of this page will be updated when material changes are published.