Enquiries, orders and appointment requests
When you submit a request, we receive the information in that form. Depending on the service, this may include a name, phone number, optional email or delivery address, notes, requested products and quantities, or the selected service, store, date and time. Staff use these details to follow up the request, confirm arrangements and maintain its status.
Order and appointment records are handled by the website backend and its database service, Supabase. The website is hosted on Amazon Lightsail. General form notes are not intended for medical records, identity-document copies, passwords or payment-card details. Please do not submit those through a general website enquiry.
Cookies and browser storage
The public website stores a language preference, and the shopping cart is kept in the current browser. Temporary retry information may be kept for an unfinished order in the current tab. Order-status access and administrative sign-in use separate security controls; a receipt key must not be shared publicly.
Clearing site data can remove language settings, the local cart and temporary retry information. It does not delete an order or appointment already received by the store. To ask about a submitted record, contact the store rather than assuming browser deletion cancels it.
Hosting, maps and external services
Servers receive request information such as an IP address, requested path, time and browser details, and may record it for service delivery, security and troubleshooting. This is different from a game score stored only on a device.
The contact page includes Google Maps, and site icons may be loaded from an external CDN. These services receive the requests needed to load their content. WhatsApp, Facebook and Instagram links lead to external services when followed; their own notices apply. Please avoid sending sensitive information through a public social-media comment.
Current advertising boundary
The main shopping, alcohol, booking and admin pages do not load a Google advertising SDK or display Google ads. A verification meta tag or ads.txt entry is not an advertisement and does not mean the site has been approved. No customer order or appointment information is supplied by our code for personalised-ad targeting.
The separate learning site has its own privacy notice. Any future Google ad launch requires a new implementation check, appropriate consent controls and updated disclosures before it is enabled. Google explains data use on partner sites at the link below; this notice does not claim that an untested consent mechanism is already operating.
Records, corrections and requests
We have not published a fixed automatic deletion period for all order and appointment records. Ask the relevant store about access, correction or deletion of your submitted details. Staff need to verify the request and the record before making changes; immediate deletion or a particular processing deadline is not promised here.
Contact the store through the contact page and identify the relevant request privately. Do not publish a receipt key or identity document to prove ownership. This notice describes the current website implementation, not an assurance of a completed legal or professional audit.