hi-client.com has partial failures. We are looking into it. View status
Security information
How we protect your information and how you can look after your account and computer.
Revised November 11, 2026 · edition 18.
1. Local processing and service separation
Recognition takes place on your computer. Licensing and updates do not send video, records, biometric data or alerts to hiClient. People's records are stored encrypted. This protection does not replace computer security or prevent access from an authorized session.
2. Device access and recovery
The application includes operator PINs and role permissions. Protect Windows accounts, physical access, disks, recovery phrases and backups as well. Keep the recovery phrase secure and verify recovery before depending on the system. Exports and source photos need their own safeguards; database encryption does not automatically extend to them.
3. Communications
The website, licensing and update services use encrypted connections. The application checks that it is communicating with the authorized service. Cameras and external services you configure have their own security conditions.
4. Portal accounts
We protect account access with attempt limits and temporary lockouts. You can reset your password and end sessions. Google sign-in is optional when enabled. Do not share passwords or codes; use a trusted computer to activate installations.
5. Licences and continuity
Your license is linked to the devices in your plan. You can work offline until it expires. If it cannot be renewed, passage monitoring is restricted, but you can still view, export and delete people's records. Plan an alternative for outages or unavailability.
6. Distribution and updates
The app checks the origin and integrity of updates before installing them. The Windows app is distributed only through Microsoft Store, which downloads and installs its updates. Use official channels and follow update notices. These checks do not guarantee the absence of errors.
7. Cameras, networks and vendors
Administrators configure network cameras and bridges. Their transport and security also depend on hardware, firmware, protocols and vendor services; some bridges use a vendor cloud. Use private credentials, maintained firmware and restricted networks. The application does not record the video stream, but cameras or other software may have recording enabled.
8. Payments and administration
Card details are entered with the payment provider; hiClient does not store them. We restrict administrative access to the service and record sensitive actions.
9. Scope and responsibilities
Security requires maintaining devices, credentials, permissions and backups and reviewing authorised people and retention. No ISO 27001 or SOC 2 certification, percentage uptime or universal recovery time is offered here. Additional commitments must be in the relevant agreement. Matches and alerts require context-appropriate review and do not themselves establish a threat.
10. Reporting vulnerabilities or incidents
Use the published contact or a Technical or Privacy ticket with “Security” in the subject, affected version, description, reproduction steps and observed scope. Do not send people databases, third-party images, keys, card details or unnecessary data. Ask for a suitable channel before supplying sensitive evidence.
Test only your own or expressly authorised devices and accounts. Do not access others’ data, disrupt the service or conduct mass production testing. Receiving a report does not authorise those activities or promise a reward. Reports will be assessed and appropriate mitigation and communications coordinated.
11. Incident management and legal duties
Notification duties depend on the data, risk and each party’s role. Where hiClient is the controller, legal periods apply: under the GDPR, a notifiable breach is reported to the authority without undue delay and, where feasible, within 72 hours of awareness; high-risk breaches also require notifying affected people without undue delay. This is not a general support response time. Local installation controllers must handle incidents involving their data.