Data Processing Agreement
The core Article 28 processor commitments needed for venue guest data.
Last updated: 20 November 2026
Parties and scope The business location is generally controller and Waitiva's contracting legal supplier is processor for customer queue data. This page describes intended processor terms; a binding agreement identifying the legal supplier and parties must be accepted or signed before live personal data is processed. Waitiva is separately controller of its own billing, account and security records.
Processing description Subject matter: Restaurant, Retail and Events queue management, Restaurant host identification, wait estimates and ticket notification. Duration: the customer relationship and necessary erasure or backup period. Data subjects: guests and relevant staff. Data: guest names, photos, party sizes, notes, queue events, ticket information, and limited technical or push data. Optional notes may contain sensitive information.
Documented instructions and confidentiality The processor handles guest data on the venue's documented instructions except as required by applicable law. Anyone authorised to handle the personal data must be bound by confidentiality. The venue is responsible for its lawful instructions and permissions.
Technical and organisational security Appropriate safeguards include HTTPS, access controls, authentication, password hashing, random ticket tokens, abuse protection, deletion of old queues and proportionate operational procedures. Measures must be reviewed as risk changes.
Subprocessors and restricted transfers Infrastructure hosting and, if selected, push notification delivery can use third parties. The processor must enter compliant terms with its subprocessors, meet applicable notice or approval obligations and implement lawful safeguards for international restricted transfers. The current verified subprocessor list must be provided separately to the venue.
Assistance and incident response The processor will reasonably assist with valid data-subject requests, security obligations, impact assessments and required consultations, taking account of the information available. It must inform the venue without undue delay after becoming aware of a personal-data breach involving the venue's data.
End of service, evidence and audits At termination, the processor must return or delete personal data at the controller's choice where required, unless storage is mandated by law. Operational guest tickets are normally removed at the next 05:00 UK service-day reset. The processor must provide relevant compliance information and permit appropriate Article 28 audits subject to safeguards and proportionality.
Contractual priority Where the parties agree an executed DPA with more specific requirements, that signed agreement takes priority. This website page alone must not be treated as proof that every statutory contract requirement has been completed.
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.