Privacy Policy
Updated September 12, 2026
This policy describes personal information used by the Beaver Chef mobile app and related web services. Service operator: Twana Dizayee. Your restaurant, school or workplace administers the account it issues to you.
Accounts and service information
Staff create accounts; the app does not offer self-registration. We process account identifiers, login credentials, profile and contact information, and organization permissions to authenticate users and provide access. Depending on your account, the service processes meal orders, kitchen notes, transaction history, balances and billing information, or employee attendance, shifts, leave and payroll information.
Camera and face information
Face enrollment and verification use camera images and face measurements. Images are sent to the service's face-processing system to extract biometric templates and perform enrollment or matching. The backend stores enrollment evidence and face templates associated with the relevant account or person. Face processing is not limited to your device and is not Apple's Face ID. Access depends on the organization and your permissions. If diagnostic snapshot storage is enabled by the operator, failed verification images may also be stored for troubleshooting.
Location
When an employee attendance policy requires it, the app requests location permission and sends latitude and longitude with the attendance request. Location is used to check attendance requirements. You can revoke location permission in device settings; attendance that requires location may then be unavailable.
Notifications and technical information
Push notifications use Firebase Cloud Messaging and, on Apple devices, Apple Push Notification service. The service associates notification tokens with accounts and devices to deliver messages. Requests also involve technical information such as IP addresses and service logs used to operate and troubleshoot the service. You can disable notifications in device settings.
Who processes information
Authorized staff of your organization access information needed to administer their services. Hosting and face-processing infrastructure process service data; Google Firebase and Apple process information needed to deliver push notifications. Information may also need to be disclosed where required by applicable law. Contact the operator for details about hosting locations and the providers used for your organization.
Retention and deletion
Face enrollment images and biometric templates have no fixed expiry and are retained for the lifetime of your account, until your account is deleted. When the service administrator deletes your account or customer record, the application permanently removes its associated face templates, enrollment evidence and identifiable failure snapshots from active storage. Disabling sign-in or revoking camera permission is not account deletion. Temporary enrollment evidence and diagnostic records may be removed sooner through routine cleanup. Order, billing and employment records have separate retention requirements; contact us for details.
Requests must distinguish account access, biometric enrollment, and order, billing or employment records. Records subject to applicable retention obligations may need to be retained. Contact staff to request access, correction or deletion and to learn which records can be removed.
Your choices
You can manage camera, location and notification permissions in device settings. Revoking a permission does not itself delete information already held by the service. Contact your organization if you want to stop using a face-based workflow or request removal of an enrollment.
Contact and updates
Use the contact details below or contact the staff who issued your account. Changes to this policy will be published on this page.
Contact Twana Dizayee
Email: beaverchef23@gmail.com
Your restaurant or workplace staff can help identify the administrator responsible for your account.