Privacy and POPIA notice

Only what the site actually needs:

• Enquiry details — your name, email address, phone number, preferred date and party size — so that the operator can answer you. Lawful basis: performance of a contract at your request.
• Advertising click identifiers such as gclid and fbclid, captured from the URL you arrived on, so that an enquiry can be attributed to the advert that produced it. These are stored against your enquiry and shared with the advertising platform that issued them only where you have consented to advertising cookies.
• A hashed form of your IP address, used to rate-limit the enquiry form. The raw address is not stored.
• Analytics about how pages are used, only where you have consented to analytics cookies.
• A record of your cookie choice itself, so that you are not asked repeatedly.

We do not sell your information. We do not share it with a booking aggregator, because there is not one — enquiries reach the operator directly.

We do not publish a guest name or a recognisable photograph on this site or our social media without your permission, and the default is not to publish.

A small number of service providers process information on our behalf: Resend, which delivers the confirmation and notification emails; Railway, which hosts the site and its database; Cloudflare Turnstile, which protects the enquiry form from spam; Calendly, only if you choose to book a call through it; and — subject to your consent — Google, Meta and Microsoft for analytics and advertising.

If you tick "Send me occasional updates" on the enquiry form, we may email you about conditions and what is running. Nothing is sent without that tick. Every update can be stopped by replying "unsubscribe", and the choice is kept against your enquiry.

Enquiries and bookings are kept for as long as needed to run the business and to meet record-keeping obligations, and are then deleted. Analytics data is retained according to the settings of the analytics platform.

Under POPIA you may request access to the information held about you, ask for it to be corrected or deleted, object to its processing, and lodge a complaint with the Information Regulator of South Africa (www.inforegulator.org.za).

If you are in the United Kingdom, the European Economic Area or Switzerland, the equivalent rights under the UK GDPR, the GDPR and the Swiss FADP apply. Wherever you are, analytics and advertising only start once you have agreed to them.

Some of the providers above store or process information outside South Africa, including in the European Union and the United States: our hosting and database provider, our email delivery provider, Cloudflare, Calendly if you use it, and — only with your consent — Google, Meta and Microsoft. We use providers that are bound by data-protection terms offering protection comparable to POPIA, as section 72 of POPIA requires.

Nothing beyond what the site needs to work is stored on your device until you choose. This applies to every visitor, wherever you are. Until you accept, Google receives only cookieless signals that cannot identify you, which it uses to estimate visits in aggregate.

You can accept all, reject all, or choose by category, and change your mind at any time with the cookie preferences link at the bottom of every page. Rejecting has no effect on booking or enquiring.

Necessary — always on, because the site does not work without them:

• ad_consent (this site, 6 months): remembers your cookie choice so you are not asked again.
• ad_session (this site, 7 days): keeps the operator signed in to the admin area. Never set for visitors.
• google_oauth_state and instagram_oauth_state (this site, a few minutes): protect the admin area when connecting a calendar or Instagram account. Never set for visitors.

These tell us which pages are read and where visitors come from, in aggregate:

• _ga and _ga_<ID> (Google Analytics, Google, 2 years): distinguish one visitor from another so visits can be counted.
• _clck (Microsoft Clarity, 1 year), _clsk (1 day) and CLID (1 year): show how pages are used — where people scroll and click — so the site can be improved. Clarity masks the text you type.

These measure which adverts lead to an enquiry or booking, and let us show adverts to people who have visited:

• _fbp and _fbc (Meta Pixel, Meta, 3 months): link a visit to a Facebook or Instagram advert.
• _gcl_au (Google Ads, Google, 3 months): link a visit to a Google advert.
• ad_attr and ad_visitor (this site, stored in your browser, 90 days): remember the advert or link that first brought you here, so an enquiry can be credited to it.
• Instagram posts on the home page load Instagram’s own code, which may set Meta cookies. Until you agree, each post is shown as a plain link instead.

If you have agreed to advertising cookies and then send an enquiry or book, we also tell Google and Meta about it directly from our server, so the result can be matched to the advert even when a browser blocks cookies. What is sent is limited to the event, the advert click identifier, your IP address and browser type, and — for an enquiry or booking — your email address, phone number and first name in hashed (scrambled, one-way) form. If you have not agreed, nothing is sent.

Should we add another analytics or advertising tool, it will be listed here before it is switched on.