Privacy
Product-practice summary · 25 October 2026
This page records verified product practices. Approved operator-specific policy text and genuine contact details are still required. It is not a complete privacy policy.
1. Accounts and access
The application uses personal username and password accounts. Browser authentication uses a secure, HttpOnly session cookie. An account is separate from an enabled organization membership, role, geographic scope and unit assignment.
2. Protected records
Reports can contain source photographs, counts, location and time claims, author identity, review decisions and correction history. Protected evidence and exports require current authorization. Evidence is stored privately; this website does not expose operational records.
3. Local device storage
Offline preparation stores encrypted assigned work and retained drafts on the device. Unlocking requires the device’s passphrase. Clearing browser storage or uninstalling a field client may destroy unsent work. Local unlocking does not establish a server session.
4. Processing information that must be supplied
The operator must publish its verified identity and contact, applicable legal basis, retention schedule, rights-request process, recipients and international-transfer information before this page can serve as its privacy notice. Those organization-specific facts have not been provided.
For product guidance, visit Support.