CGuardPro data security and privacy
what we do, stated plainly
CGuardPro checks every request against the company the user belongs to, so one security company cannot read another's data. Inside your company, access follows editable roles with per-person grants and denials, each person has one active session per app, officers' location is recorded only while on shift, and the selfie check detects a face without facial recognition. Third-party credentials are stored encrypted (AES-256-GCM), and all traffic is served over HTTPS behind Cloudflare.
How does CGuardPro protect your data?
Company isolation
Every request is checked against the company (tenant) the signed-in user belongs to. One company cannot read another company's officers, sites, reports or clients.
Role-based permissions
Built-in roles for administrators, managers, supervisors, officers and clients, all editable. On top of the role, individual permissions can be granted or denied to a specific person.
One session per person per app
Each person has one active session per app. Signing in on another device ends the old session, so a lost or shared phone does not stay signed in.
Encrypted service credentials
Credentials for third-party services connected to your account are stored encrypted with AES-256-GCM, not in plain text.
Rate limiting
The API limits how many requests can be made in a period, to slow down automated abuse.
Location only on shift
An officer's location is recorded only while they are on shift. Off duty, the app does not track where they are.
Face present, not face recognized
The selfie check at clock-in detects whether a face is present in the photo. It does not perform facial recognition and does not store biometric templates.
Retention you set
Each company sets its own retention periods for GPS trails, communication logs and audit logs.
Change log
A change log records who changed what in the company's records, so an edited schedule or report can be traced to a person.
Encrypted in transit
Traffic to the web command center and the apps is served over HTTPS, behind Cloudflare.
What do security buyers usually ask?
| Question | CGuardPro |
|---|---|
| Can another company see our data? | No. Every request is checked against the company the user belongs to. |
| Who inside our company sees what? | Editable roles, plus per-person grants and denials. |
| Are officers tracked off duty? | No. Location is recorded only while on shift. |
| Is the selfie facial recognition? | No. It only detects whether a face is present; no biometric templates are stored. |
| How long is GPS and log data kept? | Each company sets its own periods for GPS trails, communication logs and audit logs. |
| Can we see who changed a record? | Yes. A change log records who changed what. |
Why does officer privacy matter to a guard company?
A guard app sits on the officer's own phone in many companies. Officers accept location tracking and a selfie at clock-in more readily when the limits are clear: location is recorded only while on shift, and the selfie is checked for the presence of a face, not matched against anyone's identity. Those limits are part of the product, not a setting someone has to remember to turn on. The selfie check itself can be set to off, flag for review, or require a retake; see selfie clock-in verification.
Who decides how long data is kept?
You do. Each company sets its own retention periods for GPS trails, communication logs and audit logs, so you can match them to your contracts and your own policies. Separately, the change log records who changed what in your company's records, which is what you need when a schedule, a report or a permission is questioned later. Access inside the company is covered on roles and permissions.
Where are the legal terms?
This page explains the controls in plain language. The binding documents are our privacy policy and our terms of service.
Frequently asked questions
How does CGuardPro keep one security company's data away from another?+
Every request to CGuardPro is checked against the company (tenant) the signed-in user belongs to. A user can only read and change records of their own company, so one company cannot see another company's officers, sites, reports or clients.
Does CGuardPro use facial recognition on officers?+
No. The selfie check at clock-in only detects whether a face is present in the photo, so a picture of a wall or a finger is caught. It does not identify who the person is and does not store biometric templates. Each company decides whether the check is off, flags a missing face for review, or asks for a retake.
Does the guard app track officers when they are off duty?+
No. An officer's location is recorded only while they are on shift. Each company also sets how long GPS trails are kept.
What happens if an officer signs in on a second phone?+
Each person has one active session per app. Signing in on another device ends the session on the old one, so the same account is not left open on two phones.
Is CGuardPro SOC 2 or ISO 27001 certified?+
This page lists only the controls we can state today, and those certifications are not among them. If your procurement process requires a specific certification or questionnaire, write to [email protected] and we will answer exactly what we can.
Who do I contact about privacy or a data request?+
Write to [email protected] for privacy questions and data requests, and to [email protected] for anything else about your account. Our privacy policy and terms of service describe how data is handled in full.
Questions about privacy or a data request: [email protected]. Anything else about your account: [email protected].
Bring your security questionnaire
Book a demo and we will walk through company isolation, roles and the officer's view on a 7-day trial.