Task privacy

Store devices and employee access

A manager pairs a device to a restaurant location and creates employee access using a name, store assignment, role, and PIN. Task PIN access is separate from a personal Opvera email and password account.

Task uses necessary device and employee session cookies to maintain pairing and PIN access. The service stores protected PIN verifiers and device/session token verifiers, rather than storing raw PINs in its database. Work you submit is attributed to your employee identity and store.

Information used in Task

• Employee names, store assignments, roles, access status, and activity timestamps.
• Checklist answers, notes, submitted photos, drawn signatures, QR scan evidence, and manager reviews.
• Temperature readings, sensor identifiers and installation details, operational alerts, and acknowledgements.
• Store logbook notes, training assignments, quiz responses, completion records, and sign-offs.
• Food-date label content, print attempts, and reported print results. The native app saves printer connection settings on the device.
• Push notification device tokens when enrolled, and linked phone contacts and consent choices used for operational SMS alerts.
• Employee data request status and an optional contact email for manual follow-up, information you provide when requesting support, and server request and error information needed to operate and secure the service.

Your restaurant may also provide recipes, procedures, images, videos, and documents for its team to view.

How information is used and shared

We use this information to provide store workflows, record completed work, manage access, deliver enabled operational alerts, and support security and troubleshooting. Authorized people in your restaurant can view records permitted by their roles and location access.

Service providers process information needed for hosting, databases, file storage, push notifications, and operational SMS. Checklist photos and training files are served through access-controlled storage and Task routes. Opvera’s Privacy Policy describes the wider service and its providers.

Device permissions and choices

Camera access supports store pairing, checklist QR scans, and photos you choose to submit. Local Network and Bluetooth access support compatible printers. Notification permission supports alerts you enable. You can change these permissions in device settings; features that need a permission may then be unavailable.

Task’s web app does not request microphone or geographic location access. A restaurant location assignment identifies the store where you work, rather than a GPS position. You can change linked SMS consent in Task; operational SMS also supports STOP to opt out.

Access removal and employee data requests

A manager can clear a PIN, deactivate employee access, or revoke a paired device. These actions stop access; they do not automatically erase the employee’s name or historical work records.

Use Request personal data removal with your own PIN session to submit an employee data request and view a receipt, due date, and status while your PIN access remains active. Submission starts a manual process; it does not immediately delete information. A contact email is optional and used privately for operator follow-up. Before removing PIN access, the operator arranges verified contact or an in-person follow-up to confirm completion.

For access or correction requests, or if you can no longer use your PIN, contact support@ourprovision.com. Include your name and restaurant or location. Do not send your PIN, password, or pairing code. We verify the request and review the shared operational records and any applicable retention obligations.

The personal Opvera account deletion process applies to email and password accounts. PIN-only Task employees use the Task employee data request process above.

Questions

For privacy questions, contact support@ourprovision.com. For device and workflow help, visit Task support.