Privacy Policy
Effective: 11 October 2026
1. About this policy
This Privacy Policy explains how the Jag Stories Android application and compatible Wear OS 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, training and performance results | Provide ballistics, training, match, analytics and performance 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, Shared Hunt photos, VTT camera images, Match Stage Video and QR scan input | Provide hunting records, Shared Hunt albums, VTT, Stage Video and QR joining |
| Shared Hunt information | Hunt name, dates, location/farm, Host/participants, planned animals, submitted animal results, outcome, weapon used, photo links and synchronization metadata | Provide Shared Hunt group, results, photo linking, synchronization and printable Hunt Results |
| 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 and Shared Hunt metadata exported by the user | Backup, restore and user-directed transfer |
| Technical app data | App configuration, permissions state, calibration timestamps and phone/watch or Shared Hunt synchronization status | Operate the app and maintain feature state |
| Tester application information | Full name, Google Play email, contact email, country, shooter/hunter type, Android phone model, optional watch model and feedback agreement | Administer the Jag Stories closed testing programme, approve testers and send testing instructions |
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. Local device-to-device communication
Shared Hunt starts on each phone. When the host and participating hunters can reach one another on the same Wi-Fi network or the host phone’s hotspot, supported hunt information and photos can be exchanged directly between devices. Scanning a hunt QR code shares joining information; it does not itself create a Wi-Fi connection. Local network access and authorization are required.
4A. Optional Shared Hunt cloud synchronization
When Shared Hunt cloud features are used, Jag Stories may transmit a hunt identifier, hunt name, dates, location, host and authorized member identifiers, membership information, supported planned targets, harvest details and synchronization metadata to the Jag Stories Cloud API. These records allow authorized members to access basic hunt updates when direct local connectivity is unavailable. Shared Hunt photos are not part of this cloud synchronization design and remain on participating devices for direct local transfer. Cloud access requires authentication and server-side membership authorization; a hunt identifier or QR code alone is not proof of membership. The app may use a device push-notification token to deliver hunt-related alerts. Push notifications require internet connectivity and may use a third-party notification delivery provider. Full weapon profiles, DOPE, training, match records and Stage Videos are not uploaded as part of Shared Hunt cloud synchronization.
Cloud synchronization and push notifications are being introduced in stages. Their availability depends on the installed app version and server configuration; publication of a hunt does not mean every feature described here is already active.
Users should join only matches and hunts they trust and only over networks they are comfortable using. Shared Hunt membership is scoped to the individual hunt and controlled by that hunt's Host.
5. Shared Hunt photos
Shared Hunt is designed so that participating devices can keep a local copy of the hunt's shared photo album. Photo metadata may include an internal photo ID, filename, file size, hash, originating device information, hunt association and animal-result link. Shared Hunt backup stores supported hunt metadata and photo references rather than intentionally duplicating Gallery image bytes when those images already exist in the device's Shared Hunt album.
6. 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.
7. 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 and Shared Hunt participation, create exports and backups, provide support, and maintain app security and reliability.
9. 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, Shared Hunt or other transfer feature. Shared Hunt participants receive hunt information and photos according to the hunt workflow and Host-controlled membership.
10. 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. Shared Hunt photos stored in the device Gallery remain subject to the user's device and Gallery controls. Deletion markers may be retained in Shared Hunt metadata as needed to prevent deleted synchronized items from reappearing during later sync.
For cloud-hosted Shared Hunts, the current API is designed to expire a hunt seven days after its configured end date. Copies already synchronized to participating devices, device backups and independently exported records are not automatically deleted by that server expiry. Notification tokens may be held while needed to deliver alerts and should be removed or invalidated when no longer required.
11. 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. Shared Hunt includes role-based controls for hunt records and shared photos. Users can also follow the steps on the Delete Data page.
Deleting the app or its local data does not by itself remove cloud records or copies on other members’ devices. For a request about cloud-held Shared Hunt information, email support@jagstories.com with the hunt reference and sufficient details to verify your authority. Do not email private join codes or authentication tokens.
12. Security
We use reasonable technical and organizational safeguards appropriate to the app's design. These include platform permission controls, local device storage protections and authenticated encrypted Match Director payload communication. No storage or transmission method can be guaranteed to be completely secure.
13. 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.
14. 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.
15. 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.
16. 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.