Last updated: January 30, 2026
Introduction
FaceClock (“we”, “our”, or “the app”) is a workforce time-tracking Android application that uses on-device facial recognition to verify employee attendance. This Privacy Policy describes what the app collects, how that information is used, where it is stored, and how it is protected.
Information we collect
Biometric data
- Facial images — captured during employee registration and at clock-in/clock-out.
- Facial embeddings — mathematical representations of facial features generated locally for identity verification.
Employee information
- Employee names
- Employee identification numbers
- Profile photographs
Time and attendance data
- Clock-in and clock-out timestamps
- Shift duration records
- Photographs taken at clock-in/clock-out events
Device information
- App settings (screen timeout, maximum shift hours, etc.)
How we use this information
We use the collected information solely to:
- Verify employee identity at clock-in and clock-out
- Record attendance and shift data
- Generate time-tracking reports
- Manage employee profiles within your organization
Data storage
Local storage only
All data is stored exclusively on the device that runs the app. FaceClock operates entirely offline and does not:
- Transmit data to external servers
- Use cloud storage services
- Share data with third parties
- Require internet connectivity
Data is stored in:
- A local SQLite database within the app’s private directory
- The app’s private file storage for photographs
Data security
- All data is stored in the app’s private storage area, inaccessible to other applications
- Photos and database files are protected by Android’s application sandboxing
- The app does not request network permissions
No remote access
The developer has no ability to remotely access, view, modify, or delete any data stored by the app, because FaceClock:
- Does not connect to the internet
- Has no server infrastructure
- Stores all data exclusively on the local device
The developer cannot assist with data recovery, remote data deletion, or access to stored information under any circumstances. All data management must be performed directly on the device where the app is installed.
Data retention
Automatic cleanup
- Shift records and associated photographs older than 90 days are deleted automatically
- The cleanup process runs periodically in the background
- Employee profiles and registration photos are retained until an administrator removes them
Manual deletion
- Administrators can delete individual employee records at any time
- Uninstalling the app removes all stored data from the device
Biometric data disclosure
In accordance with biometric-privacy regulations:
- Purpose. Facial recognition is used solely for employee identity verification during time tracking.
- Storage. Biometric data (facial embeddings) is stored only on the local device and is never transmitted externally.
- Retention. Biometric templates are retained for as long as the employee profile exists in the system.
- No sale or sharing. We do not sell, lease, trade, or otherwise profit from biometric data.
- Protection. Biometric data is protected using Android’s built-in application security model.
Google Cloud backup
By default, Android may back up app data to Google Cloud. We recommend:
- Disabling backup for this app in your device settings if you have concerns about biometric data in cloud backups
- Consulting your organization’s data-protection policies regarding cloud backup of employee information
Children’s privacy
FaceClock is intended for workplace use by adults. We do not knowingly collect information from children under 13 years of age.
Your rights
Because all data is stored locally on the device and the developer has no access to it, requests regarding personal data must be directed to the device administrator or the organization that operates the FaceClock installation.
The device administrator can:
- Show you what data is stored about you in the app
- Delete your employee profile and all associated data
- Uninstall the app to remove all data completely
Data controller
The organization or individual that deploys FaceClock on their devices acts as the sole data controller. They are responsible for:
- Obtaining appropriate consent from employees
- Complying with applicable privacy laws
- Managing data-subject requests
- All data management and deletion
The developer (Evgenii Lazarev) is not a data controller or processor, as no data is transmitted to or accessible by the developer. The developer provides the software application only.
Changes to this Privacy Policy
We may update this Privacy Policy from time to time. Any changes are reflected in the “Last updated” date at the top of this page. Continued use of the app after changes constitutes acceptance of the updated policy.
Compliance
The app is designed to support compliance with:
- General Data Protection Regulation (GDPR)
- California Consumer Privacy Act (CCPA)
- Illinois Biometric Information Privacy Act (BIPA)
- Other applicable biometric and data-protection laws
Organizations deploying this app are responsible for ensuring their use complies with local regulations.
Contact
For questions about this Privacy Policy or the app’s data practices:
- Developer: Evgenii Lazarev
- Email: eslazarev@gmail.com
- GitHub: github.com/eslazarev/faceclock
Summary at a glance
| Data type | Collected | Stored locally | Sent to servers | Retention |
|---|---|---|---|---|
| Facial images | Yes | Yes | No | Until deleted |
| Facial embeddings | Yes | Yes | No | Until deleted |
| Employee names / IDs | Yes | Yes | No | Until deleted |
| Shift records | Yes | Yes | No | 90 days |
| Shift photos | Yes | Yes | No | 90 days |
Key points:
- All data stays on the device.
- FaceClock never connects to the internet.
- The developer cannot remotely access or delete your data.