Control your
TAVORA information.
Information for restaurant owners, staff, rewards members and guests using the TAVORA restaurant platform.
Request deletion
A monitored TAVORA contact and an account-deletion process are awaiting confirmation. This page does not submit a request, collect personal details or delete an account. It must be completed before it is used as the app-store deletion resource.
For information kept independently by a restaurant, ask that restaurant directly through its published business contact details. Removing a staff member from a restaurant roster does not by itself remove their Firebase sign-in account or all related records.
What a request should cover
You should be able to request deletion of your TAVORA account and associated personal information, or ask about particular data without deleting the whole account. When the request channel is enabled, identify the account email or service identifier and the relevant restaurant. Guests can include the table and approximate time of a service request to help locate it. No app reinstallation should be needed to make a web request.
Never send your password, one-time code, bank-card details or identity-document photographs. Any identity check should use a secure, proportionate method.
Data to remove or anonymise
- Account information: the sign-in account, identifiers and profile information associated with it.
- Staff information: linked staff profile, public portrait, private login assignment, staff-login directory entry and access credentials, where applicable.
- Guest and rewards records: linked service requests, visit claims, identifiable points records and other associated personal information.
- Owner information: personal information in the restaurant workspace and public pages, with any legitimate business-record transfer or retention explained separately.
- Provider copies and backups: applicable service-provider deletion requests and a disclosed backup expiry process.
A restaurant may need to keep separate receipts or employment records under its own obligations. Any exception to deletion must identify the information retained, the lawful reason and how long it will be kept. A general possibility of a legal obligation does not justify keeping every record indefinitely.
Timing and confirmation
The TAVORA operator must confirm its deletion response and completion times before activating this page. The process should acknowledge a request, explain any necessary identity check or lawful exception, and confirm completion. This draft does not promise immediate deletion or an unimplemented automatic expiry period.
Signing out and uninstalling
Signing out, clearing browser data and uninstalling an app remove local access or local data. They do not erase the TAVORA account, restaurant records or other information already stored on a server. Temporarily disabling an account is also different from deleting it.