Privacy Policy
Effective date: September 12, 2026. This Privacy Policy explains how NexClock collects, uses, stores, shares, retains, secures, and deletes information when organizations and individuals use the NexClock workforce and attendance management product, the NexClock iOS and Android apps, and this website. Face data handling is described in the dedicated Face Data / Biometric Data section.
Who we are
NexClock is an independent workforce and attendance management product designed for businesses and organizations. This policy applies to the NexClock website and product experiences operated by the NexClock team.
Information we collect
Depending on how NexClock is used by an organization, we may process information such as account and profile details, employment-related identifiers configured by the organization, attendance records, schedule and shift information, device or app usage data needed to operate the service, and contact details submitted when requesting a demo or contacting support. When an organization enables face verification, face photographs may also be collected as described in the Face Data / Biometric Data section. A profile photo chosen by the user is an account avatar only and is not used as a biometric template.
How we use information
We use information to provide workforce and attendance management features, authenticate and verify attendance activity as configured by the organization, operate the product, respond to demo and support requests, and meet applicable legal obligations. Face photographs are used only for employee attendance identity verification and attendance evidence, as described in the Face Data / Biometric Data section. They are not used to improve the product, for advertising, analytics, tracking, or profiling.
Face Data / Biometric Data
This dedicated Face Data / Biometric Data section explains collection, use, storage, sharing/disclosure, retention, security, and deletion of face data in the NexClock mobile app. Face data is processed only when an organization enables face verification for employee attendance. 1. What face data is collected NexClock collects facial photographs of the enrolled employee only: • Enrollment photos: up to five compressed JPEG photographs (front, left, right, and extra poses) captured during face enrollment in the app. • Attendance photos: one compressed JPEG photograph at each clock-in and clock-out. The photograph may be watermarked with attendance details. The same photograph may first be sent to the organization's NexClock backend to validate identity, then submitted as the attendance record. The mobile app does not collect or store a face print, face embedding, or other biometric template on the device. On-device detection results used only to guide the camera (whether a face is in frame and its position) are computed in memory and discarded immediately. They are not saved or uploaded as face data. Depth maps, ARKit face meshes, and 3D facial geometry are not collected. 2. Purpose of use Face data is used only to verify employee identity as part of attendance (clock-in and clock-out) and to keep a photograph as evidence of that attendance event. Enrollment photos are used by the organization's NexClock backend to create a biometric template so later attendance photos can be matched to the enrolled employee. Face data is not used to identify a person outside this attendance verification feature. 3. Sharing and disclosure (third parties) No. Face data is not sold and is not shared with third parties for their own purposes. It is not shared with advertising networks, analytics companies, data brokers, or commercial cloud facial-recognition APIs. Photographs are uploaded only to the organization's NexClock backend over HTTPS. Google ML Kit Face Detection runs entirely on the device during clock-in and clock-out camera guidance and does not receive uploaded face photographs. Firebase Cloud Messaging is used only for push notifications and does not receive face photographs. Infrastructure providers that host the organization's NexClock servers may process stored images solely as processors to provide hosting, not for their independent use. Organization administrators may view attendance photographs as attendance evidence inside their NexClock workspace. 4. Where face data is stored and how it is secured • Device: enrollment and attendance photographs are written only as temporary files in the app's private sandbox. Biometric templates are not stored on the device. A watermarked attendance photo is saved to the device photo library only if the user explicitly chooses Save to gallery. • Server: uploaded photographs and any biometric template derived from enrollment photos are stored on the organization's NexClock backend (the API host configured for that organization). Security measures include HTTPS/TLS in transit, authenticated API access, private on-device sandbox storage, deletion of temporary face files after upload or sync, and no biometric template stored on the device. Store builds do not enable the in-app network inspector. 5. How long face data is retained • Device enrollment photos: deleted immediately after a successful upload, when the enrollment screen is closed, or when the user signs out. • Device attendance photos in private storage: kept only while a clock-in or clock-out is pending (including the offline queue), then deleted after a successful sync. • On-device camera-guidance results: not retained. • Server enrollment photos and biometric templates: retained only while the employee's face enrollment remains active. They are replaced when the employee updates enrollment, and deleted when face data is deleted in the app, when the employee requests account deletion, or when the organization offboards the employee. • Server attendance photographs: retained with the related attendance record for as long as the organization keeps that record, subject to applicable law. There is no separate advertising or analytics retention period for face data. 6. How face data is deleted When the employee no longer needs NexClock, or wants face data removed: • Profile > Settings > Delete face data: the app requests deletion of server enrollment and biometric template data, deletes leftover face files on the device, and requires new consent before any future enrollment. • Profile > Settings > Update face recognition: a successful new enrollment replaces the previous enrollment. • Profile > Delete Account: requests deletion of face enrollment on NexClock servers, deletes local face files, tokens, and cached data, signs the user out, and notifies NexClock support so the organization can complete deletion of remaining workforce records, subject to applicable law. • Sign out: leftover enrollment and guidance files on the device are deleted. Organization administrators can also offboard an employee, which removes that employee's access and associated face enrollment according to the organization's configuration. Camera permission can be turned off in iOS Settings for NexClock at any time. 7. What face data is not used for Face data is not used for tracking, advertising, marketing, profiling, product improvement, analytics, or identifying a person outside the employee attendance verification feature described in this section. Camera and facial-mapping data from Camera APIs is not used for marketing, advertising, or use-based data mining, including by third parties.
Third-party processors
NexClock does not sell personal data and does not use third-party advertising networks in the mobile app. The mobile app uploads account, attendance, and face photographs to the organization's NexClock API host configured for that deployment. Camera frames used for clock-in and clock-out guidance are processed on the device by Google ML Kit Face Detection and are not uploaded to Google. Face enrollment and attendance identity matching are performed by the organization's NexClock backend, not by a commercial third-party cloud facial-recognition API. The optional in-app AI assistant sends the user's typed or spoken prompt to NexClock's AI service so it can answer workforce questions; it is not used to process face photos. If the user enables voice input, Apple speech recognition may convert speech to text on-device or via Apple before the text is sent to NexClock. Firebase Cloud Messaging delivers push notifications and may process a device token; it is not used for advertising or tracking and does not receive face photographs. Hosting and infrastructure providers that store the organization's NexClock servers may process uploaded images and other records only as needed to provide hosting. Those processors, SDKs, and related entities provide the same or equal protection of user data as stated in this Privacy Policy. We obtain permission through the iOS camera prompt, in-app face-enrollment consent, and organization-provisioned account access before face photographs are collected and uploaded.
Data retention
We retain information for as long as needed to provide the service to the organization, comply with legal obligations, resolve disputes, and enforce agreements. Face data retention, including immediate deletion of enrollment photos on the device after upload, is described in the Face Data / Biometric Data section above.
Security
We apply administrative, technical, and organizational measures designed to protect information processed by NexClock. Face photographs are transmitted only over HTTPS/TLS to the organization's authenticated NexClock API. Temporary face files on the device are stored in the app's private sandbox and deleted after upload or sync. Biometric templates are not stored on the device. Store builds do not enable the in-app network inspector. No method of transmission or storage is completely secure, and organizations should also follow their own access-control best practices.
Your choices and rights
This Privacy Policy is available at https://nexclock.my.id/privacy and inside the NexClock app (login screen and Profile > Privacy Policy). The Face Data / Biometric Data section is at https://nexclock.my.id/privacy#face-data-biometric-data. Revoke consent: you can turn off Camera, Location, Microphone, Speech Recognition, or Photo Library access in iOS Settings for NexClock. The app respects those permission settings. Face attendance, location-based attendance, voice input to the AI assistant, or choosing a profile photo will not work without the related permission. Paid features, if any, are not conditioned on granting these permissions. Delete face data: in the app, open Profile > Settings > Delete face data to remove face enrollment from NexClock servers and leftover face files on the device; or open Profile > Settings to update face enrollment (the previous enrollment is replaced after a successful save); or open Profile > Delete Account. Delete your account: NexClock accounts are created and managed by your employer or organization; there is no public self-serve sign-up. Use Profile > Delete Account in the NexClock app to start deletion. That flow (1) requests deletion of face enrollment on NexClock servers, (2) deletes local photos, tokens, and cached app data on the device, (3) signs you out, and (4) notifies NexClock support so your organization can complete deletion of remaining workforce records, subject to applicable law and the organization's configuration. You may also ask your organization administrator or contact NexClock support via the Support page or WhatsApp.
Contact
For privacy questions, account deletion, or facial-data requests, use Delete Account or Privacy Policy in the NexClock app (Profile), contact your organization administrator, or contact the NexClock team via the Support page or WhatsApp channel listed on this website.
Updates
We may update this Privacy Policy from time to time. The updated version will be posted on this page with a revised effective date when applicable.