People first.
Privacy by design.
A plain-language explanation of the data used in the current TAVORA pilot. The full legal privacy notice must be reviewed before wider commercial launch.
Pilot information notice: This describes the current web implementation, not a final legal privacy policy or a guarantee of regulatory compliance.
What information is involved?
Restaurant owners can supply a name, business profile, contact details, menus, branding assets, staff names, staff photos and staff authentication email addresses. Guests who scan a table can view public restaurant details and, when calling staff, TAVORA may create an anonymous Firebase Authentication identity and a service request.
Where does it go?
The pilot uses Firebase Authentication and Cloud Firestore. Owner and staff permissions are controlled with Firestore security rules. Restaurant logos and photos may be stored as compressed images in Firestore during the pilot.
What is public?
Published restaurant information, menus, table identifiers and waiter display names/photos may be visible to guests. Staff login email addresses should be stored separately from public profiles. Restaurants should avoid uploading unnecessary personal information.
How are tips and payments treated?
Where a restaurant enables an external Paystack tip page, guests are redirected to the provider. The current website does not collect payment card details and does not verify completed tip settlement or distribute tips automatically.
What comes next?
Before broader onboarding, TAVORA needs a reviewed privacy notice, data retention schedule, access-request procedure, incident response process, backup and recovery plan, and confirmation of responsibilities under applicable laws including South Africa's POPIA.