What Stays Local When You Use Facenox Cloud

Facenox Desktop recognizes faces and records attendance on the computer. Facenox Cloud adds browser access to synced records, reports, and administration. Connecting Cloud does not move face recognition to the server.

Correction, October 23, 2026: The previous article overstated privacy boundaries, key-storage guarantees, performance, and compliance. This version separates local processing from hosted data and explains the server's access to template keys.

What the computer processes

The recognition workflow processes camera frames locally without saving or uploading raw face photos. It stores numerical face templates for matching and local attendance records.

Face templates are sensitive biometric data, even when encrypted. Limit access to the people who manage enrollment and recognition.

What Cloud receives

Connected computers sync directory information, attendance records, and device/sync metadata. On plans with face-template sync, encrypted templates can also be shared between paired computers at the same location.

Cloud manages location encryption keys. When transferring a member between locations, the server decrypts the template in memory and re-encrypts it with the destination key. This is not a zero-knowledge design.

Free Cloud provides browser access to synced records for one location. Paid plans add PDF and Excel reports, face-template sync, and more capacity. See the plan comparison for member, device, and history limits.

How local keys are stored

Desktop uses Windows DPAPI or an operating-system keyring where available, with file-based fallbacks in some environments. Key storage depends on the operating system and configuration.

Protect the operating-system account, storage, and access to the computer as well as the templates themselves.

Sync, backups, and removal are different

Sync propagates changes and removals. It is not an independent recovery archive. Desktop backup files need their own access controls and retention decisions.

A paired computer must receive a removal before its copy is updated. Removing a member does not delete attendance history or copies in exported backups.

Deployment responsibilities

Before enrollment, establish the organization's privacy notices, processing grounds, access rules, and retention practices. Local processing and encryption support these practices but do not replace them.

See the privacy documentation, local key-storage implementation, and Cloud privacy notice.