Feazio Attendance Privacy Policy
Effective date: October 9, 2026
Status: Draft — complete the publication checklist at the end before publishing.
This Privacy Policy describes how Feazio Attendance (the “App”) handles personal information when restaurant managers set up an attendance kiosk and employees use it to record work time. The App sends information to Feazio’s attendance service at and makes it available to the restaurant account authorized to use the service.
Who is responsible for your information
[LEGAL BUSINESS NAME], doing business as Feazio (“Feazio,” “we,” “us,” or “our”) operates the App and attendance service. The restaurant or employer that sets up the kiosk decides how employee attendance information is used for its workforce. Depending on applicable law and the parties’ agreements, the restaurant may be the controller/business and Feazio may process information on its behalf.
For privacy questions or requests, contact [email protected] or write to 250, Janak MargHanuman Nagar Extension, Officers Campus, Jaswant Nagar, Jaipur, Jaipur Nagar Nigam Area, Rajasthan 302012. Employees should also contact their restaurant or employer, which can access and administer attendance records.
Information handled
Depending on how the restaurant configures and uses the App, it may handle:
- Account and sign-in information: the restaurant identifier and the manager’s email address, phone number, or employee code and password entered to sign in. The App uses credentials to authenticate the manager; it stores session tokens on the device, using the platform secure-storage facility on iOS and Android.
- Employee and workplace information: employee names, employee codes, profile images, role, department, contact details, outlet/branch assignments, and PIN verification information made available to authorized managers.
- Attendance information: clock-in and clock-out times, break start and end times, the associated employee and outlet, manager-entered corrections, and related attendance status.
- Optional responses: answers to employer-configured questions, whether a break was received, and an optional end-of-day mood response.
- Kiosk information: the kiosk name, its restaurant and outlet association, and an authentication token used to identify and authorize the registered kiosk.
- Punch photos, if enabled: the App can take a still photo using the device’s front camera during an attendance punch. It resizes the image on the device before sending it. If the restaurant has enabled photo capture but has not enabled photo retention/upload, the image is not included in the punch request; it may be shown temporarily on the device as punch confirmation. When photo upload/retention is enabled, the photo is sent with the punch and can be viewed by authorized managers.
The App’s code sends punch identifiers with optional follow-up responses. The App labels the mood question “anonymous,” but the client implementation alone does not establish whether the service removes the association to the punch or employee. Do not treat or describe these responses as anonymous until that server-side behavior has been verified.
Camera and other device permissions
- Camera: requested when the active punch type is configured to take a photo. It is used for a still attendance photo and not for continuous recording. If camera access is denied or unavailable, the App can submit the punch without a photo.
- Internet access: used to sign in, register and operate the kiosk, and exchange attendance and configuration data with the service.
The inspected mobile app does not request microphone, contacts, location, photo-library, or advertising-tracking permission. It does not include an advertising or cross-app tracking SDK in the inspected app dependencies. The client code inspected does not implement face recognition or create a biometric face template. Face-related options are present in manager settings; any server-side face detection or processing must be separately verified and disclosed if enabled.
How information is used
Information is used to:
- authenticate managers and registered kiosks;
- record, display, correct, and administer employee attendance and breaks;
- show staff and attendance details to managers with the restaurant’s authorization;
- support optional workplace questions and feedback configured by the restaurant;
- secure, troubleshoot, and maintain the attendance service; and
- meet legal obligations and resolve disputes.
The restaurant/employer is responsible for deciding whether and how to enable optional questions, mood feedback, face-related settings, and photo capture, and for providing any required employee notices or obtaining any required permissions or consent.
How information is shared
Information is shared with:
- The restaurant or employer that operates the kiosk and its authorized managers, as needed to provide attendance functionality.
- Feazio and service providers that host, maintain, protect, or support the attendance service, subject to applicable agreements and instructions.
- Authorities or other parties when required by law, to protect rights and safety, or in connection with a business transfer, as permitted by law.
The App does not sell personal information or share it for third-party advertising based on the app code and dependencies inspected for this draft.
Retention
Attendance and employee records are retained according to the restaurant’s configuration, instructions, and legal obligations. The manager settings in the App describe uploaded punch photos as being kept for 90 days. This client-side code does not verify that the service deletes photos on that schedule. The service’s photo deletion behavior and retention periods for other records must be confirmed before this statement is published as a guarantee.
Unregistering a kiosk removes its authorization key from the device/service workflow; it is not an in-app request to delete attendance records. The App does not provide a self-service employee account or attendance-record deletion feature.
Security
The App uses authenticated requests to the Feazio service and stores native session tokens using platform secure storage. No method of transmission or storage is completely secure; the restaurant and Feazio should apply appropriate safeguards to the systems and records they control.
Your choices and privacy rights
You can deny camera access in the device’s settings; punches can still be submitted without a photo. A manager can configure whether photo capture and retention are enabled for the kiosk.
Depending on where you live, you may have rights to access, correct, delete, or restrict certain personal information, or to object to or export its use. Contact your restaurant or employer for employee attendance records and [email protected] for Feazio-related requests. We may need to verify your identity and coordinate with the restaurant that controls the records.
Children’s privacy
The App is a workforce attendance tool and is not designed for children to use as a consumer service. The restaurant/employer is responsible for ensuring its use is lawful for its workforce.
International processing and changes
Information may be processed in the countries where Feazio and its service providers operate.
We may update this Policy when the App or its data practices change. We will post the revised version with a new effective date and provide any additional notice required by law.
Publication checklist — remove this section after completing it
- Replace the legal business name, privacy email, and postal address above.
- Confirm the restaurant/Feazio controller and processor roles, hosting countries, service providers, and applicable data transfer terms.
- Verify server-side photo deletion within 90 days and set out retention periods for attendance records, responses, account information, and security logs.
- Verify whether mood responses are detached from punch/employee identifiers before storage and who can access them. If not genuinely anonymous, change the in-app claim and disclose the association.
- Verify what the
faceDetectandrequireFacesettings do on the server. Disclose any face analysis or biometric processing and ensure the App Store privacy disclosures and required consent match the actual behavior. - Publish this policy at a stable, publicly accessible HTTPS URL and use that URL in the Apple App Store and Google Play Console. Complete each store’s privacy/data-safety disclosures separately and verify that the iOS
PrivacyInfo.xcprivacydeclarations match the data the App sends to the service. This document alone does not guarantee store approval.