How can recruitment software add face check-in and liveness to its app?
Embed FaceTagr's SDK in a native Android, iOS, Flutter or React Native candidate app to evaluate on-device matching and passive liveness. Your staffing platform keeps its own shift, consent and approval workflow. Offline biometric results can feed a host-managed queue, with agreed result records synced later; neither a named software integration nor automatic GPS capture is assumed.
Last reviewed: 18 October 2026 · FaceTagr team
What data does the host app receive or retain?
| Item | Integration choice | Responsibility |
|---|---|---|
| Capture photo or video | May be discarded after processing in a configured workflow | Host app defines retention; do not assume universal no-storage |
| Reference and template | Protected local storage and optional agreed sync | Enrolment, lawful basis and deletion |
| Match result | Delivered to the app for its workflow | Threshold, human review and audit |
| Liveness result | Local assessment available to the app | Spoof handling and genuine-user fallback |
| Time, site and GPS | Captured by the host workflow with appropriate permissions | Shift mapping, location policy and sync |
Already have biometric check-in?
Determine whether the current app uses device-level authentication, a selfie comparison or another biometric engine. Device authentication and a match against an employer-enrolled worker reference are not necessarily the same check. Compare on-device behaviour, genuine-user completion, liveness and integration effort in a side-by-side pilot; do not presume your current supplier lacks biometrics.
What does your platform still own?
Step 1
Consent and notice screens, applicable lawful basis and worker alternatives.
Step 2
Authorised enrolment, worker identifiers and assignment rules.
Step 3
GPS permissions, result queues, secure sync and REST API mapping.
Step 4
Retention, access, supervisor approvals and correction of disputed records.
Discuss your app integration
For privacy or deletion requests, contact support@facetagr.com. Read our privacy policy.
Sources
Product capabilities describe FaceTagr's supported workflows, not third-party endorsement. This page is general information, not legal advice. Check your obligations with your data protection officer or adviser.
Frequently Asked Questions
Can it work without a network?
Yes. FaceTagr's mobile SDK supports fully offline 1:1 verification, 1:N identification and passive liveness on Android and iOS. Reporting and integration need a connection when records are synchronised.
Are workers' photos stored?
Configured mobile attendance workflows can avoid retaining check-in photos or video. Enrolment references, templates and attendance records still need a documented retention policy. Customer-built SDK apps and CCTV may store images according to their configuration; confirm the data flow before deployment.