Privacy

Last updated 12 October 2026

This notice explains how Experience handles information when you browse a menu, contact us or work with us as a restaurant.

Who we are

Experience is operated by Dakshsinh Parmar, Surat, Gujarat. Dakshsinh Parmar handles questions and requests about personal information at hello@experience.place.

Guests

Public menus do not require an account or sign-in. The menu code does not set cookies or include advertising scripts. It does not send your presentation preferences to us or use them to build a guest profile.

The appearance you prefer, your dietary type, the allergens you hide and whether nutrition facts show are kept in your phone's browser storage, and clearing your browser data removes them. Your table size and the dishes you save last only until you close the menu.

Cloudflare delivers and protects the site and menus. It processes technical request information, including IP addresses. Security and operational records are separate from aggregate usage statistics and may be available to us for investigating faults or abuse.

We use Cloudflare Web Analytics to measure use of our website, including the sample menu. It measures page views without analytics cookies. We also review aggregate menu-request counts. Cloudflare's automatic analytics script can also appear on error pages.

Restaurants

To publish a menu we store what the restaurant gives us: the brand and branch names, the links it chooses to show guests, the dishes with their descriptions, dietary marks, allergens, nutrition facts, prices and photographs. This can include personal information, such as a proprietor's name or a contact link the restaurant chooses to publish. We use the names and contact details of the people we work with to build and change the menu, keep in touch and review results together. We also keep the name and phone number of the owner who accepted our terms, and the message in which they accepted them.

We hold this data because the restaurant gives it to us for that purpose. We keep published menu versions so a restaurant can inspect their contents. Our database keeps no history of which version was live on a given day, though our setup notes may record when one went live. The text of its published versions stays in our private records, along with any contact link the restaurant chose to publish in them, subject to applicable law. The proposals prepared for its menu, published or not, stay in our private records as published versions do. Contact records are deleted on request, except where we need to retain them as part of the restaurant's acceptance of our terms, publication approvals or a legally required record. On request we also delete the record of setting up the menu: the working folder on our own computer, any current copy in our private repository, and the setup records and original files in our private storage, subject to legal preservation requirements. Earlier saved versions of that private repository may still mention the restaurant. They are not public; service providers we authorise to operate the repository may have access to them. We retain the restaurant's acceptance of our terms and its publication approvals as evidence of the permissions and instructions under which we published its menu. Whole-database copies hold every restaurant's data together and cannot be edited for one restaurant. Data removed from active records may remain in these copies until they expire or are removed under the applicable storage and backup retention settings. We restrict their use to recovery and required preservation. Our database provider keeps its own backups under its retention policy.

When a restaurant leaves, we delete everything we published for it: its menu pages and their earlier versions, photographs, logo and links. Its QR codes and menu address then lead to experience.place and show nothing of the restaurant. Cached copies may remain until they are purged or expire. We also delete its private files, the originals and sales exports it gave us and our working copies, subject to legal preservation requirements. The history of what its menu said, the owner's approvals of it and its acceptance of our terms stay in our private records, as proof. We cannot remove copies that other people have independently saved.

Sales figures and point-of-sale exports a restaurant shares with us are used only to set up, review and improve its menu. We process them with the AI tools named below and keep them in our private storage for as long as we work together. They and our working copies of them are deleted when we part or earlier on request, and never published or shared with other restaurants.

Menu data is stored with our database provider, PlanetScale, in Mumbai, India, and published menus and photographs are stored with Cloudflare, as are the original files a restaurant sends us and new setup records, in private storage. Shared operating procedures and earlier setup records are held in a private repository hosted by GitHub. Cloudflare serves pages from its network worldwide. These providers may process information outside India under their applicable terms and privacy policies; the Mumbai location describes our database, not every copy or service.

We use AI tools from OpenAI and Anthropic to help prepare and update menus, and they process the files a restaurant gives us, sales exports included. We have switched off model-training settings in our ChatGPT and Claude accounts. These providers process and retain information under the terms and settings of the plans we use.

We do not sell restaurant data. We use service providers as described here, and may disclose information when required by law or a binding order. Menu content and photographs are published as part of the service.

If you email us or message us on WhatsApp or Instagram, your mail provider and ours, or Meta, carry the message under their own terms; we keep the conversation to answer you and to set up your menu.

Your rights

You can ask about the personal information we hold about you, request a correction or deletion, or complain about its handling. You can withdraw consent to processing that relies on your consent; this may affect our ability to provide the service. We handle these requests subject to applicable law and any records we are legally required to keep. Write to our Grievance Officer, Dakshsinh Parmar, at hello@experience.place. Please explain the request and identify the relevant page or restaurant where possible. We may ask for information needed to verify your identity or authority. We resolve privacy complaints within one month of receiving them, or sooner where applicable law requires. This does not affect your right to approach a competent authority or court under applicable law.

Security

Menus and this site are served over HTTPS. Access to restaurant data is limited to the people who build and change menus, and every version of a menu's dishes, prices and arrangement is recorded.

Children

Experience is offered to restaurants. We do not ask guests for names, ages or contact details to browse menus.

Changes

When this notice changes, the date at the top changes with it. Restaurants we work with are told of any change that affects them.