Draft for review. Do not submit or publish as the final policy yet. The service operator's legal identity, reference-photo and backup retention, and the employer's deletion process still need confirmation.
FaceAttend is an attendance and HR service for adult restaurant employees, managers, and administrators. The service is published under Sryx.dev, a freelance/brand name. Participating employers issue and manage accounts and use the service for workplace records. For questions about why employment information is used, contact your employer's authorized HR representative.
Information processed
- Account identifiers, employee IDs, roles, authentication data, and session-security records. Passwords and PINs are used to authenticate; the server stores credential hashes, not readable credentials.
- Employer-managed profile and work details, which may include name, contact details, department, designation, joining date, and salary.
- Precise device location and accuracy information when an attendance punch is checked. The app does not request background location for continuous tracking. Location is used for server-side punch verification and is not displayed to other app users.
- For employee face-verified attendance, a reference face photo and live camera capture, face-matching and anti-spoofing results, capture-session details, timestamps, and accepted attendance-photo evidence. Managers using the configured manager attendance flow do not submit a face photo for their own punches.
- Leave categories, dates and reasons, approval decisions, week-off choices, attendance history and corrections, and payroll-draft calculations. Free-text leave reasons may contain sensitive information; employees should avoid including details that are not needed for the request.
- Technical and audit information used to secure accounts, record management actions, review rejected attempts, and diagnose service problems. Host and network logging can depend on the deployment and service providers.
How information is used
FaceAttend processes information to authenticate users, apply role permissions, verify attendance location and identity, maintain employer records, handle leave and week-off requests, display attendance and payroll drafts, send optional leave notifications, and protect the service. Payroll calculations are drafts only; the app does not transfer money or issue finalized payslips. The service does not contain advertisements.
Access and service providers
Employees can access permitted personal information. Authorized employer managers and administrators can access information allowed by their roles, including employee profiles, attendance, leave, and payroll records. Employers control account provisioning and management permissions.
The owner reports that the API, database, and face-verification service run on a private Windows device in India. App traffic reaches that host through HTTPS and Cloudflare Tunnel. Cloudflare and Android/Google platform services may process network, security, or diagnostic information needed to provide their services. Provider logging, access, and retention depend on the configured services and must be reviewed before this draft is finalized. Face images are sent to the employer-configured server for attendance verification; they are not represented as remaining only on the device.
Permissions and notifications
Camera and precise-location permissions are used for the applicable attendance workflow. Denying either permission can prevent that workflow; employees should ask their employer about an alternative attendance process. Optional leave notifications use periodic authenticated checks, not background location tracking. Notifications can be disabled in the app or Android settings and may be delayed by device, network, or battery settings.
Security and retention
App-to-service traffic uses HTTPS/TLS. Profile and reference-photo data is held in the employer-configured database, while accepted attendance images are stored in private server storage. Access controls, hashed credentials, session invalidation, and private service authentication are implemented. Encryption of host disks, databases, and backups, as well as host administration and recovery practices, depend on operator configuration and are not certified by this statement.
The owner reports that attendance image data is manually cleaned up approximately every six months. This reported practice does not yet specify whether reference photos or backup copies are included. Retention periods for other employment, attendance, leave, payroll, security, and audit records have not been confirmed. The employer's retention rules and applicable legal requirements may affect how long records are kept.
Access, correction, and deletion requests
Employees can submit a request for access, correction, account assistance, or deletion by contacting their employer's authorized HR representative and [email protected]. Include the employee ID and the request; do not email a password, PIN, face photo, or other authentication secret. The request may need to be verified with the employer. Some employment, security, or audit records may need to be retained under the employer's policies or applicable law. Deactivating an account is not the same as deleting its records, and deletion from backups may take longer. The operator and employer must confirm their request-handling and backup procedures before this draft is finalized.
Children
FaceAttend is intended for adult restaurant employees and is not designed for children. Employers should not create accounts for people under 18.
Contact and changes
For privacy questions, contact [email protected] and your employer's authorized HR representative. The final policy should be published at this address with its effective date updated after operator and employer review.