Data we may process
When authorized by a customer administrator, SecOps may process account membership, officer profile labels, checkpoint scan records, route assignment context, foreground location evidence when available, device identifiers, app version, push-notification registration state, time punch records, schedule responses, audit records, and support metadata.
On personal phones, the app is intended to capture work-related patrol proof and operational status only while the user is signed in and using the SecOps Guard workflow.
Location and checkpoint evidence
Checkpoint scans may include method labels such as NFC, QR, or manual fallback. Location may be captured as foreground evidence when device permissions allow it.
Location evidence is used for patrol verification, safety review, sync troubleshooting, and supervisor reporting. It is not intended for unrelated personal tracking.
Push, device, and retention
Push registration records help deliver operational notifications. Device trust records help customers manage approved or revoked devices.
Retention periods, legal holds, and export requirements may vary by customer agreement, applicable law, and administrator settings. Customers remain responsible for their own employee notices and workplace policies.
Your choices
Users can manage device permissions through their operating system. Some features, such as location evidence or push alerts, may be limited if permissions are denied.
For privacy questions, email support@thesecops.app and include only safe account-identifying context.