OpsArmours Privacy Policy

Version 1 · Effective date: 2026-07-27

This Privacy Policy explains how the OpsArmours platform ("OpsArmours," "we," "us") and your employing organization (the "Organization") collect, use, share, and protect information when you use the OpsArmours workforce management application (the "App").

OpsArmours is a workplace tool for security and operations teams. Accounts are created by your Organization's manager — there is no public sign-up — and the App is intended only for authorized employees and contractors. It is not a consumer social product.

1. Who this policy covers

Authorized guards, supervisors, and managers who use OpsArmours for Organization work.
Your Organization controls your employment records and decides who has access. OpsArmours processes data on the Organization's behalf to run the service.
Contact for privacy questions: support@opsarmours.com or your Organization administrator.

2. Information we collect

What we process depends on your role (guard, supervisor, or manager) and how you use the App.

Account and employment data

Name, work email, employee ID, role, and employment status (active, suspended, or terminated).
Position title, region, manager assignment, and employment start/end dates.
Phone number and emergency contact details (name, relationship, phone) that you or your Organization provide.
An optional profile photo you upload from your camera or photo library.
Sign-in credentials are handled by our authentication provider; we never see or store your password in plain text.

Scheduling and attendance data

Weekly availability you submit, shift assignments, schedules, site roster assignments, and replacement (coverage) shifts you create or claim.
Clock-in and clock-out times, along with any notes you or your supervisor add (for example, a reason for a forced clock-out).
Location at clock events: when your assigned site uses geofencing, the App captures your device's GPS position at the moment you clock in or out to verify you are on site. The coordinates and a verified/not-verified flag are stored with the clock record. See Section 4 for details.

Employment letters

Letter requests and their workflow history, including the letter type, purpose, notes, and the generated letter body.
Employment details included in a letter, such as position, hourly rate, and your mailing address.
Signed letter PDFs stored securely, with a cryptographic fingerprint (SHA-256) and revision history kept for document integrity.

Communications

Announcements you author or receive, and read receipts confirming when you read them.
A device push token (issued by Apple or Google) when you enable notifications, along with a record of notifications queued for delivery.
The App has no user-to-user chat or direct messaging.

Settings and preferences

Notification preferences, biometric unlock and auto-lock choices, profile visibility, appearance, and time format.
Biometric data (Face ID / fingerprint) never leaves your device — it is used only by your device's operating system to unlock the App locally.

Security and audit data

Audit logs of operational actions (for example changes to profiles, sites, schedules, shifts, clock entries, letters, and password reset requests), including who made the change and what changed. Audit logs are visible only to your Organization's managers.
Records of data exports and account deletions you perform.
In-app password reset requests and their resolution status.

What we do NOT collect

No product analytics, usage tracking, or behavioral profiling.
No advertising identifiers, and no ads.
No background or continuous location tracking (see Section 4).
We never sell personal information.

3. How we use information

We use this information to:

Operate scheduling, timekeeping, availability, replacement shifts, employment letters, and announcements.
Verify on-site presence for clock events at geofenced sites.
Deliver push notifications you have enabled (announcements, schedule decisions, letter updates, replacement shifts, and report summaries).
Provision and secure accounts, including manager-initiated enrollment and password resets.
Maintain security, prevent abuse (including rejecting mocked or spoofed GPS locations), and keep audit records required for compliance.
Meet payroll, employment-records, and legal obligations of your Organization.
Provide support and honor your data-export and account-deletion requests.

4. Location: exactly when and how it is used

Location is captured only in the foreground and only at specific moments: when you tap clock in or clock out at a geofenced site, and when a manager pins a site's coordinates during site setup.
The App requests "while in use" location permission only. It does not request background location, and it does not track your movements between clock events.
At clock-in on a geofenced site, your position must fall within the site's geofence radius; otherwise the clock-in is rejected. At clock-out, your position is recorded and flagged if outside the geofence, but the clock-out still succeeds.
Captured coordinates are stored with the clock record and are visible to your supervisor and Organization managers under role-based access rules.
If you deny location permission, you will not be able to clock in at geofenced sites.

5. Device permissions

The App requests the following permissions, each tied to a specific feature:

Location (while in use): verify on-site clock in and clock out.
Camera and photo library: take or choose a profile picture.
Notifications: deliver work alerts you enable.
Biometrics (Face ID / Touch ID / fingerprint): unlock the App on your device when you enable biometric login. Processed entirely on-device.

You can change these permissions at any time in your device settings.

6. Data stored on your device

The App keeps a local, offline cache of your work data (schedules, shifts, clock records, announcements, letters, and settings) so you can keep working with limited connectivity. Actions taken offline are queued and synced when you reconnect.
You can clear the local cache from Settings. Clearing the cache does not delete records already stored on Organization servers.
Optional biometric unlock and auto-lock help protect the cached data on your device.

7. Who can see your information

Access inside your Organization follows role-based rules enforced at the database level:

You can always see your own records.
Your supervisors can see the profiles and clock, availability, and letter records of guards they supervise or schedule.
Your Organization's managers can see workforce records across the Organization, including audit logs.
Profile visibility setting: you can hide non-essential contact details (phone, emergency contacts, photo) from the directory. Your name, employee ID, role, position, and employment status remain visible because they are needed for operations.

Data from one organization is never visible to another organization.

8. Sharing with service providers

We share information only as needed to run the service:

Supabase hosts authentication, the database, file storage, and realtime infrastructure.
Apple Push Notification service and Firebase Cloud Messaging (Google) deliver push notifications. Analytics and advertising features of these services are disabled.
Authentication emails (password setup, password recovery, email change confirmations) are delivered through our authentication provider.
We may disclose information when required by law, or to protect rights, safety, and security.

We do not sell personal information and do not share it for cross-context behavioral advertising.

9. Retention

Operational records — clock entries, schedules, letters, and audit logs — are retained for payroll, compliance, and employment-records purposes for as long as your Organization requires and applicable law permits.
Released employment letter PDFs are treated as immutable records and are retained even if your employment ends.
When you delete your account (Section 10), your personal data is deleted or anonymized as described there.

10. Your choices and rights

In the App (Account → Data & Privacy) you can:

Adjust profile visibility and notification preferences at any time.
Download My Data: export a machine-readable copy of your account data, including your profile, settings, clock history, schedules, availability, letters, and announcement read receipts. Each export is recorded in the audit log.
Delete Account: permanently remove your access.

When you delete your account:

Your login is disabled and your device push tokens, settings, password reset requests, and announcement read receipts are deleted.
Your profile is anonymized — your name, email, phone, emergency contacts, and photo are removed.
Operational records required for payroll and compliance (clock entries, schedules, letters) are retained in anonymized form.
Organizational constraints may apply: a supervisor must have their sites reassigned first, and the last active manager of an organization cannot self-delete.

You may also contact support@opsarmours.com or your Organization administrator to request access, correction, or deletion where applicable under Canadian privacy law (including PIPEDA) and other laws that apply to you. Some employment records are controlled by your Organization, and requests about them may be referred to your employer.

11. Security

We use industry-standard safeguards, including:

Encrypted transport (HTTPS/TLS) for all communication.
Role-based access control and row-level security on all organizational data.
Private, access-controlled storage for photos, signatures, and letter PDFs.
Tamper-evident audit logging of operational changes.
Optional biometric app lock and auto-lock on your device.

No method of transmission or storage is 100% secure, but we work to protect your information appropriate to its sensitivity.

12. Children

OpsArmours is a workplace application for working-age employees and contractors. It is not directed to children under 13 (or the equivalent minimum age in your jurisdiction), and we do not knowingly collect information from them.

13. International processing

Data may be processed in Canada and in other regions where our infrastructure providers operate. Wherever data is processed, we apply safeguards appropriate to its sensitivity and applicable law.

14. Changes to this policy

We may update this Policy from time to time. The version and effective date at the top identify the current Policy. Material changes will be reflected in the App and at the published Policy URL below.

15. Contact

OpsArmours

Email: support@opsarmours.com