Encryption in transit
All traffic to GuardWatch is encrypted over SSL/TLS.
Trust Center
Plain-language security practices we follow today, and an honest list of what is still in progress.
In place today
All traffic to GuardWatch is encrypted over SSL/TLS.
Stored data is encrypted at rest with our cloud hosting providers.
Access is protected by authentication and access controls scoped to each role.
Residents, guards, community admins, and security companies see only what their role needs.
Regular backups and recovery procedures guard against data loss.
Internal access to personal information is limited on a need-to-know basis.
In progress
We would rather tell you what is not published yet than let you assume it exists.
A SOC 2 report will be linked here once an audit is completed and available to share.
Not started
ISO 27001 certification will be published here only after it is obtained.
Not started
A summary from an independent penetration test will appear after the engagement is completed.
Not yet commissioned
A public uptime and incident status page will be linked here when published.
Planned
Questions
Yes. Data is encrypted in transit over SSL/TLS and encrypted at rest with our cloud hosting providers.
Access is restricted to team members who need it to provide support or operate the platform, on a need-to-know basis.
Not yet a formal program. If you believe you have found a security issue, email us at pilots@guardwatch.pro and we will respond directly.
Not yet. This is on our roadmap — see the "in progress" list above and our Roadmap page for status.