Privacy Policy

Restaurant Pro (www.restaurantpro.ai) is operated by [LEGAL ENTITY NAME], [REGISTERED ADDRESS] (“Restaurant Pro”, “we”, “us”). Restaurant Pro is a directory of restaurants and a way to order from, book and message them. The restaurants on it are independent businesses; when you order, the restaurant prepares and sells the food.

Each restaurant also handles the details you send it under its own practices. This policy covers what Restaurant Pro itself does.

• We do not sell your personal information.
• When you order or book, the restaurant gets what it needs to serve you: your name, phone number, email if you gave one, the order, and any allergies or notes.
• Card numbers are entered into Stripe’s payment form and go straight to Stripe. They never reach our servers.
• We only send promotional emails or texts if you tick a box asking for them. Order texts and sign-in codes are separate.
• Messages you type to the AI assistant are stored and sent to OpenAI to write the reply.
• Restaurant pages are built partly from public sources. Owners can claim and correct them, or ask us to take one down.

You do not need an account to search, read menus or look at a map. While you do, we collect:

• A random visitor id stored in a cookie (rp_sid, kept for a year). It is not your name or email. We use it to count views and taps, rank listings, measure adverts, keep your chat thread, and limit abuse.
• Your location, if you give it. A ZIP code, address or city you type, or your device’s location if you allow it, is turned into a map point and kept in a cookie (rp_loc, a year) so results are near you. A street address you type is looked up with the U.S. Census Bureau’s public geocoder. You can clear it from the location picker.
• Diet and allergy filters you set without an account, kept in your browser (rp_prefs) so menus can flag dishes for you.
• What you do on a restaurant page — tapping the phone number or directions, saving it, asking to order where online ordering is not yet open, or asking to be emailed when it opens (in which case we keep that email address). We use these signals to show restaurants that diners want them and to rank the directory.
• Technical information such as your browser type and IP address. For rate limits and advert-click checks we store a one-way hash of the IP address, not the address itself. Some forms run an automated bot check provided by our host, Vercel.
• Analytics. We use Google Analytics to count page views. Google receives your IP address and sets its own cookies.

You sign in with your email address; we email you a one-time code or link, so there is no password to store for diners. What else is in your account is up to you:

• your name and mobile number;
• allergies (including which are severe), diet, likes and dislikes — and, if you add them, the names, allergies and diets of people in your household, so menus and orders can account for everyone at the table;
• places you save, lists, trips the assistant planned for you, saved recipes, ratings and your dining journal. If you are signed in and tap a restaurant’s phone number or directions, we may later ask whether you went; nothing is added to your journal unless you confirm it;
• referral codes and any credit you have earned (a referral code you arrive with is kept in a cookie, rp_ref, for 60 days);
• a shareable map of places you have been, which is off unless you turn it on. The shared copy shows places and states, never notes or dates, and turning sharing off disables the link.

Orders

To place an order you need an account and a mobile number we have confirmed by texting you a six-digit code (we keep only a scrambled version of the code, and it expires after ten minutes). For each order we keep the name on the order, your phone number, your email if you give one, what you ordered, your notes, the allergies and diet you or your household have set, how you paid, and the order’s progress. For delivery we also keep the address you type and the map point you choose. If you report a problem with an order, we keep your report.

Reservations

When you book a table or send a reservation request — on a restaurant page or through the assistant — we keep your name, phone number, email if given, party size, time, occasion, special requests and any dishes you pre-order, and pass them to the restaurant.

Catering

When you post a catering request, restaurants that might cater it see your brief, and we keep the messages and quotes exchanged and the payments made through the platform.

The assistant on restaurant pages and across the site, and the support chat on our contact page, are AI. We keep each conversation — your messages, the replies, any thumbs-up or thumbs-down — linked to your visitor id and, if you are signed in, your account. Messages are screened automatically for abuse and attempts to manipulate the assistant, and flagged messages may be reviewed by our team.

To write a reply we send OpenAI your message, the conversation so far, what is in your cart, and the restaurant’s public information. If you are signed in we also send your first name, your allergies and diet and those of your household (without their names), and dishes you have recently ordered, logged in your dining journal or rated. Only if you have turned on Let the concierge remember you do we also send your likes, dislikes and saved memories. The mobile number and email on your profile are deliberately not sent; a booking made in chat fills them in on our side. Replies are filtered to remove personal details such as phone numbers and emails other than the restaurant’s own.

If the assistant hands your conversation to the restaurant, the restaurant sees the conversation and any name and phone number you chose to give. Memory is off by default; you can see, delete or switch it off in your account at any time.

Some restaurants use our AI phone assistant, Basil, to answer their calls (it is in early access). When you call a restaurant that uses it, the call is handled by our voice-service providers, and is recorded and transcribed. You are told about the recording at the start of the call. We keep your phone number, any name you give, the recording, the transcript and a summary of what you asked for, and the restaurant can see and listen to them in its dashboard.

We may text or call you for three different reasons, and each has its own permission:

• Codes and order updates. Sign-in and verification codes, and texts about an order you placed (for example, that it is ready). These are part of the service you asked for.
• Calls and texts about your orders, including from an AI assistant — only if you tick that box at checkout or turn it on in your account. Not required to order.
• Promotional texts about offers and your saved places — only if you tick that box when you sign up. Not required.

Message frequency varies. Message and data rates may apply. Reply STOP to any text to stop receiving them. For help, [HELP KEYWORD RESPONSE / SUPPORT CONTACT — to confirm].

Whenever you give or withdraw one of these permissions we record the exact wording you saw, the phone number or email, the time, your IP address and your browser type, so we can show what you agreed to.

We do not sell or share your mobile number or your text-message consent with third parties or affiliates for their own marketing. Phone numbers are shared only with the providers that deliver our messages and calls, and with a restaurant or courier when that is needed to fulfil your order or booking.

When you claim a restaurant or work in its dashboard we collect:

• your name, role, email and phone number, and the verification codes we send by text or call to the restaurant’s public phone number to confirm you speak for it;
• the email addresses and roles of team members you invite;
• your menu, photos, hours, offers, notes you give the AI assistant, and your Basil call recordings and transcripts;
• billing records: commission statements, advertising spend and purchases of Basil talk time.

To take card payments, a restaurant opens a Stripe account through Stripe’s own hosted pages. Your legal business details, tax number, identity information and bank account are entered with Stripe, not with us; we keep only the Stripe account id and whether it can take payments and payouts. Purchases you make from us, such as Basil talk time, are paid through Stripe’s checkout page.

We publish pages for restaurants that have not joined yet, so diners can find them. Those pages are built from:

• open map data (Overture Maps) for names, addresses and categories;
• the restaurant’s own website — menus, hours, photos, and the business phone number and email address it publishes there;
• Google’s Places service — ratings, price level, a starting point for opening hours, and photos shown under Google’s terms;
• public health-inspection records published by cities.

Software, including AI, reads menus and suggests likely allergens; until a restaurant confirms them they are labelled as coming from the menu, with a reminder to confirm with the kitchen.

We use a restaurant’s published business email and phone number to invite the owner to claim the page — by email (every email has an unsubscribe link, and one unsubscribe stops all of our email to that address) and sometimes by a call from an AI assistant, which you can end by saying “stop calling”.

Corrections and removal. An owner who claims the page can edit it directly. Anyone can ask us to correct a listing, and an owner can ask us to pause or take one down, through our contact page.

• to run the directory, take orders and bookings, and pass them to restaurants;
• to text, call or email you about what you asked for;
• to personalise menus and suggestions around your allergies, diet and tastes;
• to answer you in the AI assistant and the support chat;
• to prevent fraud and abuse — bot checks, phone verification, rate limits;
• to measure and bill advertising and commissions, and to understand how the site is used;
• to send promotions, only where you have agreed;
• to comply with law and enforce our Terms.

We share personal information only as described here:

• Restaurants you order from, book with, message or ask to cater — the details listed above for that order, booking or conversation. In its customer list a restaurant sees your first name and the last four digits of your phone number.
• Delivery couriers (DoorDash Drive or Uber Direct), when a delivery uses one: your name, phone number, delivery address, map point, instructions and the items.
• Stripe, which processes card payments. A card payment for a pickup order is made to the restaurant’s own Stripe account; Stripe also calculates sales tax and receives your email if you ask for a receipt.
• OpenAI, which generates the assistant’s replies, reads menus and adapts recipes, as described above.
• Voice and messaging providers that carry calls and texts, check phone numbers, and record and transcribe Basil calls (currently Retell, ElevenLabs and Telnyx). [CONFIRM PROVIDER LIST]
• Resend, which sends our email and tells us whether it was delivered, opened or clicked.
• Supabase (database and sign-in) and Vercel (hosting and bot checks), which store and serve the site.
• Google, for Analytics as described above.
• Map services. The map loads its tiles from OpenStreetMap and its code from cdnjs (Cloudflare), so those services see your IP address.
• For legal reasons, when required by law or to protect people, and in connection with a sale or reorganisation of the business. [LAWYER TO CONFIRM SCOPE]

• rp_sid — random visitor id (1 year).
• rp_loc — the location you chose (1 year).
• rp_prefs — diet and allergy filters set without an account (1 year).
• rp_consent — the email and text choices you made at sign-up, held for up to an hour until your account is created.
• rp_ref — a referral code (60 days).
• rp_dash_loc — which of their restaurants an owner last opened.
• Sign-in cookies from Supabase, which keep you signed in.
• Google Analytics cookies.

Your browser’s local storage also keeps your cart, your chat thread and some display settings. You can clear all of these in your browser settings; the site will still work, but you will be signed out and lose your saved location and filters.

• Listing view, advert and claim-tracking records are deleted automatically after about 400 days.
• Phone verification codes expire after ten minutes.
• Records of the permissions you gave or withdrew are kept as evidence of what you agreed to.
• Order and payment records are kept for accounting, tax and dispute purposes.
• Other account information, conversations and call recordings are kept while your account or the restaurant’s account is active. [RETENTION PERIODS FOR CHATS, CALL RECORDINGS AND CLOSED ACCOUNTS — to confirm]

• Every promotional email has a one-click unsubscribe link.
• Reply STOP to any text.
• In your account you can edit your profile, allergies and household, turn calls and texts about orders on or off, turn journal emails on or off, switch concierge memory off and delete what it learned, and stop sharing your map.
• Restaurants can stop claim reminders and catering requests from the link in those emails.
• You can clear your location from the location picker at any time.

To ask for a copy of your information, a correction, or deletion of your account, contact us through our contact page. We do not yet offer a self-service download or account deletion, so a person handles these requests. We may need to confirm it is you, and we may keep what the law requires us to keep, such as order and payment records. [RESPONSE TIME AND STATE-LAW RIGHTS (e.g. California) — lawyer to confirm]

Data is stored with access controls at the database level, sign-in codes and verification codes are short-lived, and card details stay with Stripe. No system is perfectly secure; if something goes wrong that affects you, we will tell you as the law requires.

Restaurant Pro is not directed to children under 13, and we do not knowingly collect personal information from them. [MINIMUM AGE FOR ACCOUNTS — to confirm]

If we change this policy we will update the date at the top, and for significant changes we will tell account holders before they take effect.

Questions or requests: our contact page, or [PRIVACY CONTACT EMAIL], [LEGAL ENTITY NAME], [POSTAL ADDRESS].