Skip to main content
☾ Dar Al Yemen

Privacy Policy

Who we are

Dar Al Yemen restaurant ("we") is the data controller for personal data collected through this website. Contact details are on the Contact page.

What we collect, and why

  • Reservations: name, email address, phone number, party size, date/time and any special requests — to manage and confirm your table booking. Legal basis: performance of a contract (GDPR Art. 6(1)(b)).
  • Catering inquiries & contact form: name, email address and your message — to answer your request. Legal basis: legitimate interest in responding to correspondence (Art. 6(1)(f)).
  • Online orders, deposits & gift vouchers: contact details and order contents — to fulfil your purchase. Payment is processed entirely by Stripe on their secure pages; your card details never reach our servers (Art. 6(1)(b)).
  • Waitlist & newsletter: your email address (double opt-in for the newsletter) — to notify you of a free table or our news. Legal basis: consent (Art. 6(1)(a)), withdrawable any time via the unsubscribe link.

We never sell your data, never share it with third parties for marketing, and use no analytics or marketing cookies at all.

How long we keep it

Reservation and inquiry records are automatically deleted after 12 months. You can request earlier deletion at any time.

Cookies

  • Strictly necessary: the session cookie, your language preference and your consent choice — these need no permission.
  • Optional: the Google Maps embed on the Contact page loads only after you consent; Google then sets its own cookies (see Google's privacy policy).

Your rights

Under the GDPR you may request access to, correction of, deletion of, restriction of, or portability of your data, and you may lodge a complaint with your data-protection authority. To exercise these rights, email us via the address on the Contact page — export and erasure requests are normally fulfilled within 30 days.

Security

Everything is transmitted over HTTPS, staff passwords are stored with Argon2id, and administrative changes are audit-logged. To report a vulnerability, see /.well-known/security.txt.