ambiContact Ambi ↗
THE DETAILS / PRIVACY

Your details.
Handled with purpose.

This notice describes the data handled by this Ambi website. Updated 19 October 2026.

When you send an enquiry

We store the name, restaurant name, business email, optional phone number, plan preference and message you submit, along with an enquiry reference and the submission time. We use this information to review and respond to your request and discuss the service you have asked about.

Please do not send customer lists, payment details, sensitive personal information or private guest data in the message field. Submitting an enquiry does not subscribe you to unrelated marketing.

Storage and service providers

Enquiry records are stored server-side in a private Vercel Blob store through the Vercel hosting platform. They are not displayed publicly. Hosting providers process technical request information to deliver, secure and operate the website. The enquiry application does not store your IP address in its lead records.

The interactive demo

Dish preview counts, pairing counts, search text, category choices and calculator inputs in the demo stay in the page’s temporary browser memory. They reset when you reload the page and are not included in an enquiry submission. We do not use these sample counters to build a customer profile or record restaurant sales.

Restaurant images are loaded from the Vesna and OCCO websites; those servers receive the network requests needed to display their images. The homepage uses published OCCO and Vesna food photographs within illustrative Ambi interfaces. Ambi brand assets and fonts are served from this website.

Optional visitor analytics

When Google Analytics is configured, we ask before loading it or setting analytics cookies. Accepting helps us measure visits to public pages and successful enquiry submissions. Google processes device and browser information, cookie identifiers, approximate location and engagement information to produce these reports. Analytics does not identify visitors to us by name or provide us with their contact details.

We send only recognised public page paths, without URL query strings or fragments. Referrer information is reduced to the referring website’s origin. We do not send your name, email, phone number, venue name, message, enquiry reference, demo searches or calculator inputs to Google Analytics. The successful-enquiry event records that an enquiry was saved, without the form’s contents. Advertising features, Google signals and ad personalisation are disabled in our tag.

You can decline analytics and still use the whole website and send an enquiry. The Cookie preferences button lets you change your choice at any time. If you withdraw permission, we stop analytics, remove this website’s analytics cookies and reload the page. This stops future collection; it does not erase events already collected.

Cookies and access

We save your analytics choice in this browser’s local storage for up to 180 days so that we can respect it. Optional analytics cookies use the ambi_ga prefix and expire after up to 180 days, renewed while analytics remains enabled. You can also remove cookies and local storage through your browser settings. Where browser storage is blocked, your choice may apply only to the current page.

Google Analytics is supplied by Google and may process information outside your country. See Google’s Privacy Policy and how Google uses information from partner sites. The hosting platform may use authentication or operational cookies where access protection is enabled. External portfolio links lead to separate websites with their own data practices.

Questions, corrections and deletion

You can use the enquiry form to request a correction, ask about an earlier enquiry or request deletion. Include the enquiry reference if you have it. We may need to verify that the request relates to you before changing or deleting records. Keep the message limited to information needed to identify your request.

Enquiry information is used for the conversation you initiate. A documented retention period and direct business privacy contact will be provided when the operating business details are finalised for the public launch.

Restaurant menu projects

Data collection for a restaurant’s own deployed menu is agreed separately with that restaurant. The website’s sample report does not mean that the linked portfolio menus currently use the same reporting configuration.

Back to the experience ↗