Cookie Policy
Essential browser storage, sign-in cookies and permissions used by Waitiva.
Last updated: 20 November 2026
Essential cookies Waitiva uses an HttpOnly buzzer_session cookie for signed-in venue accounts. Login pages use a short-lived waitiva_login_csrf cookie to defend against forged submissions. A private venue test invitation may also set a temporary access cookie. These are used for required service and security functionality.
Guest ticket storage and permissions Browser-local information may help a customer reopen an active ticket. An enabled deposit checkout may save a short-lived recovery reference locally to reopen a paid ticket after returning from Stripe. Camera access is requested only for the selfie needed to join a Restaurant queue. Browser push notifications are optional and require user permission. Removing local site data can remove the browser's ability to find its saved ticket.
Analytics and advertising The current application does not need advertising cookies to function. If non-essential tracking is later introduced, a suitable notice and consent controls must be added before such tracking is set, as required by UK privacy and electronic communications law.
Managing choices Use your browser settings to clear cookies and local data or to revoke camera and notification permissions. Blocking essential session cookies can prevent venue sign-in. For more detail about personal information, see the Privacy Policy.
Operator and legal contact
Registered company details and monitored legal contact are pending verification. The legal identity, registered office and contact address must be confirmed before full commercial launch. Venue subscribers should also consult their Stripe invoice and account correspondence.