Legal
MenuMindBot is a restaurant menu and chatbot service at menumindbot.com. This policy explains what we collect, why, who we share it with, and how you can delete it. Privacy questions: contact@menumindbot.com.
The service is for restaurant and food-truck operators. It is not directed at children. You must be 18 or older to create an owner account. We do not knowingly collect personal information from anyone under 13. If you believe a child gave us information, write us and we will delete it.
Account. Email, your name, and a password we store as a hash — or, if you choose Continue with Google or Continue with Apple, your name, verified email, and a Google or Apple account id so you can sign in again. Apple may share a Hide My Email relay (including @privaterelay.appleid.com or @private.icloud.com) instead of your personal inbox. We do not receive your Google or Apple password.
Restaurant profile. Name, public page address, hours, phone, cuisine, description, and location (street, city, state, ZIP, optional landmark, and GPS coordinates if you use Get my current location). You can hide location from the live page; we still keep it in your dashboard until you change or delete it.
Menu and photos. Menu items, dietary tags, daily specials, header photos, dish photos, and gallery photos you upload. If you photograph a printed menu, we send that image to SpaceXAI / xAI so we can read dishes and prices. Edit with Imagine is on Pro, up to 10 photo edits a month. If you use it, we send the photo and your instruction to SpaceXAI / xAI to generate a new image, then store the result you approve.
Guest questions. Questions guests ask the bot, and the answers, so you can see analytics. The bot is given the menu you stored for that location only.
Share email. If you send a share email from the dashboard, we send that message to the addresses you type.
Billing. Stripe processes payments. We store plan, trial dates, and Stripe customer or subscription ids. We do not store full card numbers.
Referrals. If you use a referral link, we store who referred whom so we can credit a free month.
You type it, upload it, or tap a control in the dashboard. Sign-in providers send us an id and email when you choose that button. Get my current location uses your browser’s location permission, then we send those coordinates to OpenStreetMap Nominatim to turn them into an address. Guests type questions on your live page. We do not scrape other restaurants or buy lists of people.
To run your public page and QR, answer guest questions from the menu you stored, show analytics, process subscriptions, and email you about your account. If you ask for account help, we email that address with your sign-in email and, when the account uses a password, a short-lived reset link. Accounts that only use Google or Apple get a reminder to sign in that way — there is no password to reset. We send ourselves a notice when a new account is created so we can support the product. We also run Google Ads and load a Google tag on every page so we can measure whether an ad led to a visit or a sign-up.
We do not sell your menu or guest questions. We do not use one restaurant’s menu to answer for another. Upgrade prompts stay in the dashboard, never on the guest menu page. We do not sell your data. Google may use the tag for ads measurement as described in Google’s policies.
We use a sign-in cookie so you stay logged in, and a location cookie so Pro accounts stay on the kitchen you last opened. During Continue with Apple we set a short-lived cookie so the sign-in can finish after Apple posts back to our site. If you turn on notifications, we store a push token or web-push subscription so we can tell you when a guest asks a question. On the website we load Google’s gtag.js (including live guest menus) so Google Ads can measure visits and sign-ups; that tag may set cookies Google uses for conversion measurement and ads. We do not load that tag in the iOS app or the Android app. Guests do not need an account to read a menu or ask the bot.
We share data with these processors only to provide the service. Each is required to protect it at least as carefully as we describe here:
You choose when those AI and location requests happen (asking the bot, uploading a menu photo, Edit with Imagine, or Get my current location). We do not send guests to third-party ordering or reservation marketplaces. Print-ready QR files are yours to download; we are not taking print-product orders on the site right now.
We may disclose information if the law requires it, or to protect the service from abuse.
Dish photos and the live gallery are on Growth and Pro. If you unsubscribe and return to the free Starter plan, we remove dish photos and gallery photos from every location on the account. The header photo on the live page stays unless you delete it.
You can edit or delete menu items, photos, and location in the dashboard. You can change your name, email, and password in Settings. You can hide location from guests. You can unsubscribe on Billing (that cancels Stripe and returns the account to Starter). You can revoke Google or Apple access in that provider’s account settings; you can also delete your MenuMindBot account.
To delete your account and the personal data we keep with it, use Delete account in Settings in the dashboard, or email contact@menumindbot.com. Deletion removes the owner account, sessions, password-reset tokens, restaurants, menus, photos, guest questions, and referral records we are not legally required to keep. If a paid plan is active we cancel it with Stripe first. We aim to finish deletion within 30 days and will confirm by email when we can.
We keep your data while your account is open. Pro accounts can archive a location (it leaves the live site but stays saved) or delete an archived location for good. After you delete an account we keep only what the law requires, such as a billing record Stripe already holds.
Passwords are stored as a hash. Sign-in cookies are http-only. The live site uses HTTPS. No method of transmission or storage is perfectly secure.
The MenuMindBot iOS app is a native shell for this same website. It opens on Log in. Subscriptions are not sold in the App Store; if you upgrade, Stripe checkout opens in Safari. The app may ask for camera (photograph a printed menu or a dish), photos (header, dish, or gallery), location (Get my current location), and notifications (new guest questions). We do not load the Google Ads tag inside the iOS app. Sign in with Apple is available in the app the same way it is on the website.
The MenuMindBot Android app is a native shell for this same website. It opens on Log in. Subscriptions are not sold in the app. Starter is free. If an account already has Growth or Pro from the website, those features stay available after you sign in. The app may ask for the camera (photograph a printed menu or a dish), photos (header, dish, or gallery), and location (Get my current location). We do not load the Google Ads tag inside the Android app.
The site is hosted in the United States. If you use MenuMindBot from another country, you understand that information is processed there.
Apple, the Apple logo, and Sign in with Apple are trademarks of Apple Inc. Google and the Google logo are trademarks of Google LLC. We use the official Continue with Apple and Continue with Google buttons so you can sign in. That is not an endorsement of MenuMindBot by Apple or Google.
If this policy changes in a material way we will update this page and the date below.
Last updated October 2026.
