ZenotiHelp

Device & data security

ZTZenoti Docs Team Updated July 13, 2026 7 min readGuide

Zenoti Biometrics protects locally stored fingerprint data and attendance records through automatic encryption, integrity checking, and audit logging. This article explains how those protections work and what operators should do when a security or connectivity error occurs.

Audience: Center managers and IT administrators who oversee Zenoti Biometrics deployments.


On this page


Before you begin

Permission: You need an active Zenoti employee account with access to the center where the device is deployed. The application does not define its own roles β€” access is governed by your existing Zenoti account and center assignment.

  • Zenoti Biometrics must be installed and configured on the Windows device. See Installation, setup, and application lifecycle.
  • The center must have biometric attendance enabled at both the organization level and the center level, with Zenoti Biometrics selected as the scan type at Configuration > Employee > Employee attendance > Specify the type of authentication you want to use.
  • You need an active Zenoti employee account with access to the center where the device is deployed.
  • To review audit logs, you need access to the Settings screen inside the Zenoti Biometrics application.

Note: The security behaviors described in this article are automatic. No operator action is required to activate encryption, key rotation, or integrity checking β€” these run continuously in the background.


How Zenoti Biometrics protects local data

Zenoti Biometrics applies several layers of protection to fingerprint templates and other sensitive data stored on the device.

Device-bound encryption

Enrolled fingerprint templates and other locally stored sensitive data are encrypted in a form that is bound to the specific device on which they were created. If the data files are moved to a different device, they cannot be read or reused. This prevents fingerprint data from being extracted and replayed on another machine.

Application integrity checking

Each time the application runs, it checks whether its own files have been altered without authorization. If a modification is detected, the application blocks further use and displays a security error. The application cannot be dismissed from this state by the operator β€” it must be reinstalled to resume normal operation.

Important: If you see a security error on startup, do not attempt to work around it. Reinstall Zenoti Biometrics following the steps in Installation, setup, and application lifecycle.

Automatic encryption key rotation

Zenoti Biometrics periodically refreshes the encryption keys used to protect locally stored data. This rotation happens automatically, without any action from the operator and without interrupting attendance scanning or enrollment. You do not need to schedule or trigger key rotation manually.

Note: When a key rotation is in progress, the application displays a Security update required screen. The screen shows an estimated time, a progress indicator, and a deadline. Do not close the application during this process β€” it will restart automatically when the update is complete.

Audit trail

The application records enrollment events, attendance check-in and check-out events, and security-relevant events β€” such as a detected tampering attempt β€” to an internal audit trail. This trail is available for security review and compliance purposes.

To export the audit trail:

  1. Open the Zenoti Biometrics application and sign in.
  2. Navigate to Settings.
  3. Select Logs.
  4. Click Export Audit Logs.

The export creates a CSV file containing all active and archived audit records, including logins, attendance actions, and configuration changes.

To archive older audit records and improve performance for viewing current logs:

  1. In Settings > Logs, click Archive Audit Logs.
  2. Confirm the action. Logs are automatically exported to your Documents folder before archiving.
  3. Check the confirmation checkbox and click Archive Logs.

Note: Archived data is preserved and remains accessible when you export audit logs in the future.


Respond to a security error

A security error appears when the application detects that its files have been altered without authorization.

Steps

  1. Read the error message displayed on screen. The message describes the specific condition that was detected.
  2. Do not attempt to dismiss or bypass the error β€” the application blocks all further use until it is reinstalled.
  3. Reinstall Zenoti Biometrics on the affected device. Follow the installation procedure in Installation, setup, and application lifecycle.
  4. After reinstallation, re-enroll any employees whose fingerprint data was stored on the device. See Fingerprint enrollment.

Important: Reinstallation removes locally stored fingerprint templates. Employees must be re-enrolled before they can use biometric attendance on the reinstalled device.

Worked example

A center manager arrives in the morning and finds the Zenoti Biometrics device showing a security error. The message indicates that application files were altered. The manager does not attempt to unlock or dismiss the screen. Instead, they uninstall and reinstall the application, then re-enroll the 12 employees assigned to that center before opening for the day.


Respond to a connectivity error

A connectivity error appears when the application cannot reach Zenoti Cloud. Attendance and enrollment actions that require a network connection are paused until connectivity is restored.

Steps

  1. Read the error message. The message identifies the condition β€” for example, that Zenoti Cloud is unreachable.
  2. Check the network connection on the device (Wi-Fi or Ethernet).
  3. Wait for connectivity to be restored. The application resumes attendance and enrollment actions automatically once the connection is re-established.
  4. Retry the interrupted action after connectivity is confirmed.

Note: Fingerprint identification against locally stored templates can continue without a network connection. However, recording the resulting check-in or check-out event always requires a live connection to Zenoti Cloud. Events are not queued for later submission β€” retry the action once connectivity is restored.


Review the audit trail

Use the audit trail to investigate security events, verify enrollment history, or confirm attendance records.

Steps

  1. Open the Zenoti Biometrics application and sign in.
  2. Navigate to Settings.
  3. Select Logs.
  4. In the Recent Activity section on the home screen, use the Search by employee name or center name field to filter records.
  5. To export all records, click Export Audit Logs. The export creates a CSV file in your Documents folder.
  6. To view system diagnostic logs (errors, warnings, debug information), click Export System Logs. This creates a compressed archive of decrypted daily log files.

Audit trail columns

The audit trail includes the following information for each event:

Column Description
Date Calendar date of the event
Time Time of the event
Center Center where the event occurred
Action Type of event (for example, enrollment, check-in, check-out, security alert)
Status Outcome of the event

Recover after encryption key revocation

If the organization's server-side encryption keys for a center are revoked, all locally stored fingerprint data for that center becomes permanently inaccessible. Affected employees must be re-enrolled before they can use biometric attendance.

Steps

  1. Confirm with your Zenoti administrator that the encryption keys for the affected center have been revoked.

  2. On the Zenoti Biometrics device, navigate to Settings > Employee Management.

  3. For each affected employee, click Permanently Unenroll to remove the inaccessible fingerprint data.

    Important: Permanent unenrollment deletes all biometric fingerprint data for the selected employee. This action cannot be undone.

  4. Re-enroll each affected employee. See Fingerprint enrollment.

  5. Confirm that each re-enrolled employee can successfully check in using the biometric scanner.

Note: Key revocation is a server-side administrative action. If you are unsure whether keys have been revoked, contact your Zenoti administrator before proceeding.


Tips

  • Export audit logs regularly. Schedule periodic exports of audit logs to an external location so that historical records are preserved independently of the device.
  • Keep the application updated. Zenoti Biometrics applies security updates automatically. When the Update Available screen appears, install the update promptly. Critical security or stability fixes are marked on the update screen.
  • Monitor the scanner status. The home screen displays the current scanner status. If the scanner shows as Inactive, check the physical connection before starting attendance mode.
  • Use duplicate detection. In Settings > Biometric Device Settings, enable Enable duplicate detection to prevent the same fingerprint from being enrolled for multiple employees. This reduces the risk of attendance fraud.
  • Set an appropriate match accuracy level. The default match accuracy is 75%. If valid employees are being rejected, lower the threshold slightly. If incorrect matches are occurring, raise it. The recommended range is 70%–80%.

Troubleshooting

  • The application shows a security error on startup and will not open. The application has detected that its files were altered. This state cannot be dismissed. Reinstall Zenoti Biometrics and re-enroll affected employees. See Installation, setup, and application lifecycle.
  • Attendance events are not being recorded even though the scanner is active. The application requires a live connection to Zenoti Cloud to record check-in and check-out events. Check the device's network connection. Once connectivity is restored, the application resumes recording automatically β€” retry the attendance action.
  • An employee's fingerprint is no longer recognized after a device change. Fingerprint data is encrypted and bound to the specific device on which it was enrolled. Data from one device cannot be read on another. Re-enroll the employee on the new device. See Fingerprint enrollment.
  • The "Security update required" screen appeared and the application is unresponsive. A key rotation is in progress. Do not close the application. The screen displays an estimated time and a deadline. The application will restart automatically when the update completes. If the update fails, click Retry Update. If the issue persists, contact Zenoti support.
  • Audit log export produces an empty file. If no attendance or security events have been recorded in the selected period, the export file will contain only column headers. Verify that attendance mode has been active and that events have occurred. If events are expected but missing, check the Recent Activity section on the home screen for any error entries.
  • After encryption key revocation, employees cannot check in. Locally stored fingerprint data is permanently inaccessible when server-side keys are revoked. Permanently unenroll affected employees using Settings > Employee Management > Permanently Unenroll, then re-enroll them. See Recover after encryption key revocation.

Was this article helpful?
Your feedback helps us improve our documentation.