Privacy Policy

The short version

• We collect what it takes to run a menu service: your account, your restaurant’s content, your billing status, and the people you invite.
• We don’t sell personal information, we don’t run advertising, and we don’t set tracking cookies — not on our site, and not on yours.
• A guest reading a menu on a restaurant’s website is not profiled. We count views, scans and languages per restaurant, per day; nothing is tied to a person.
• Your data lives in the United States with a short list of providers who process it for us, named in section 5.
• You can see and change most things in your account, export your menu, and ask us to delete everything by email.

1. Who this covers

MenuFramer (“we”, “us”) is operated by MenuFramer, LLC. This policy covers the website at https://menuframer.com, the account area, the menus we serve on restaurants’ websites, our embed script, dish pages and share links, QR codes, staff links, the waitlist and demo bookings, and email we send. It is written for five groups of people, and says which parts apply to each:

• Restaurant owners and their teams — anyone with an account.
• Staff who open a training, recipe or similar link a restaurant shares with them, without an account.
• Guests who read a menu we serve on a restaurant’s website or scan its QR code — section 7.
• People on our waitlist or who book a demo call.
• Visitors to our own marketing site.

Our Terms of Service are the agreement this policy sits under.

2. What we collect, and where it comes from

What you give us.

• Account: your name, email address and password (we store only a hash of it, through our authentication provider). If you sign in with Google, Google sends us your name, email and profile picture; we don’t receive your Google password.
• Restaurant content: the restaurant’s name, address, hours, phone, website, menus, dishes, prices, photos, ingredient and dietary information, translations you type or import, recipes, training questions, branding, fonts you upload, and any text you write about the restaurant. This is the restaurant’s information, and most of it is meant to be public (section 6).
• Imports: the menu file, photo or website address you give us to read a menu from. We keep the import and the draft it produced so you can check and redo it.
• Billing: your plan, billing cadence, subscription status and invoice history. Card details go straight to Stripe; we never see or store a full card number.
• Your team: the email addresses of people you invite, their role, and when they accepted.
• Staff on shared links: the name a person types when they open a training or recipe link, their quiz answers and scores, which recipes they viewed, the language they used, and their acceptance of any staff agreement the restaurant asks them to acknowledge. The restaurant can see all of this; it is the restaurant’s staff record, and we hold it for the restaurant.
• Waitlist: an email address or a mobile number. If you give a mobile number, we store the exact consent sentence you were shown and the time you agreed to it (section 8).
• Demo bookings: your name, email address and restaurant name, used to put the call in both calendars.
• Support: whatever you send us when you email cheers@menuframer.com.

What is recorded as you use the service.

• Activity in your account: what was changed, by whom and when — so an owner can see what their team did, and so we can help when something goes wrong.
• Product events: milestones such as “menu published” or “checkout started”, attached to the restaurant, so we can see where people get stuck in the product.
• Where your menu is installed: when your embed loads on a web page, the page’s origin (for example https://your-restaurant.com — never the full address) is recorded against your restaurant, so your account can confirm the menu is live.
• Counts: QR-code scans per code per day, link clicks per link per day, and the languages guests’ browsers ask for per day. Counts only.
• Site analytics: page views on our own site and on the menus we serve, measured by our hosting provider’s cookie-free analytics: the page, the referrer, the browser type and a coarse location derived from the IP address, which is not stored. We also measure page speed the same way.
• Server logs: the ordinary request logs any web host keeps (IP address, browser, time, page), kept briefly for security and debugging.

We do not collect precise location, biometrics, government identifiers, or anything about your personal life, and we do not buy data about you from anyone.

3. Why we use it

• To provide the service: run your account, store and serve your menu, render it on your website, generate QR codes and links, run staff training.
• To read an imported menu: the file, photo or page you chose is sent to an AI model to turn it into dishes you can edit (section 4).
• To set up your restaurant: a name you type into our restaurant search goes to a place-search provider; a website you give us is fetched so we can find the menu on it.
• To bill you and to detect fraud and abuse.
• To talk to you about your account, your menu going live, your trial ending, billing, security, and changes to the service or these policies.
• To send you news you asked for: waitlist updates and occasional product news, each with an unsubscribe link.
• To keep the service working and improve it: fixing bugs, measuring what gets used, keeping it secure.
• To meet our legal obligations, such as tax and accounting records.

Where the law asks us to name a legal basis: providing the service and billing you are performance of our contract with you; security, fraud prevention and product improvement are our legitimate interests; marketing texts and waitlist messages rest on your consent, which you can withdraw at any time; tax records are a legal obligation.

4. AI models

When you import a menu, the content you chose — and only that — is sent through an AI gateway to a model provider (currently Anthropic’s Claude), which returns a draft. If dish-photo generation is enabled on your plan, the dish names and descriptions you choose are sent to an image model the same way. We do not use your content to train any model, and our providers are engaged on terms under which they do not train on it either. Translations are not produced by AI: you type them or import them from a spreadsheet.

5. Who we share it with

We don’t sell personal information and never have. We share it with companies that process it on our instructions to run the service, each bound by its own contract and privacy terms:

• Vercel — hosting, the cookie-free analytics and speed measurement above, and the AI gateway that forwards imports to a model provider.
• Supabase — our database, authentication and file storage, in the United States (Oregon).
• Stripe — payments and subscriptions. Depending on where you are, the sale is completed by Stripe’s merchant-of-record service, Link, which then holds your billing details as the seller and handles tax, receipts and disputes for the transaction.
• Resend — the email we send, and the waitlist contact list.
• Google — sign-in with Google if you choose it; the Places service when you search for your restaurant; and Google Calendar for demo bookings.
• Komoot’s Photon and OpenStreetMap’s Overpass — the fallback restaurant search when Google’s is unavailable; and CARTO, whose map tiles your browser fetches when a map is shown in your account.
• AI model providers, as section 4 describes.

We may also share information when the law requires it, to protect our rights or someone’s safety, with professional advisers under confidentiality, and with a buyer or successor if MenuFramer is sold or merged, in which case this policy continues to apply and we will tell you. Newcastle Flow, the company MenuFramer grew out of, shares our team and may support us under the same obligations.

6. What is public by design

A menu is for the public. Everything you publish — dish names, descriptions, prices, dietary labels, photos, the restaurant’s name and contact details, and the translations you add — is served openly on your website, on dish pages and share links, and to search engines. Photos and uploaded fonts are stored at public addresses so that browsers can load them. Staff training and recipe links open for anyone who has the link. Unpublished menus, drafts, account data, staff records and billing are private to your restaurant.

7. Guests: the people who read a menu

When our menu appears on a restaurant’s website, we are a processor for that restaurant, and the restaurant’s own privacy notice covers its site. Here is exactly what our part does and doesn’t do:

• No cookies, no profile, no ads. Our embed sets no cookies and does not identify or track a guest across pages or sites.
• Counts, not people. We count that the menu was viewed (cookie-free, as in section 2), that a QR code was scanned, and the language a guest’s browser asked for — as daily totals the restaurant can see. We do not store a guest’s IP address, device, or time of visit against any of them.
• Language choice. If a guest picks a language, the choice is kept in their browser’s session storage for that visit only and is never sent to us as anything but a count.
• Share links. A dish link a guest shares opens a page on our site; from there the guest is sent on to the restaurant’s own site only if that site is the one the restaurant has registered with us. We record nothing about who shared or opened it.
• Fonts and photos load from our own storage, not from a font or image network that could see the guest.

A guest who wants something changed on a menu should contact the restaurant; if a guest contacts us, we pass the message on.

8. Waitlist and text messages

You can join our waitlist with an email address or a mobile number. By joining with a mobile number you agree to receive text messages from MenuFramer about early access; message and data rates may apply, and you can reply STOP at any time to opt out. We store the exact wording you agreed to and when, so that we can prove consent if we are ever asked. Waitlist emails carry an unsubscribe link. We do not text or email anyone who has not asked us to.

9. Cookies and browser storage

We use one kind of cookie: the sign-in cookies our authentication provider sets so you stay logged in and so the service can tell your requests apart from everyone else’s. They are essential and expire when your session does. We store your light/dark theme preference in your browser’s local storage. We use no advertising, social-media or cross-site tracking cookies, and no third-party analytics cookies — which is why there is no cookie banner to click.

10. How long we keep it

• Account and restaurant data — for as long as the restaurant has an account. When you remove a photo or font it is queued for deletion from storage; when you close a restaurant we delete its data, keeping only what the next two lines require.
• Billing records — as long as tax and accounting law requires, typically seven years, after which they are deleted.
• Activity and product events — with the restaurant they belong to, and deleted with it.
• Counts (views, scans, clicks, languages) are aggregate and have no one to delete; they go with the restaurant.
• Waitlist contacts — until you unsubscribe or ask us to remove you, or until the waitlist is retired.
• Server logs — on our hosting provider’s short default retention. Backups — deleted data leaves our backups within the ordinary backup cycle.

11. Security

Every restaurant’s data is isolated at the database level, so one account cannot read another’s. Data is encrypted in transit; passwords are hashed by our authentication provider and are never readable by us; card numbers never reach us. Our own team’s access to customer data is role-limited and logged. No system is perfectly secure, so if we learn of a breach that affects you we will tell you without undue delay, and within any time the law sets.

12. Your choices and rights

Most of your data is yours to see and change inside your account. You can export your menu, and you can leave at any time. For anything you can’t do yourself, email cheers@menuframer.com from the address on your account — or start from the contact page, which sets the subject for you — and we will:

• tell you what personal information we hold about you;
• correct it, or give you a copy in a usable format;
• delete it — your login, your restaurant, or both — except what we must keep for billing and legal records;
• stop sending you marketing, or stop a particular use.

We answer within 30 days and never treat you differently for asking. These rights are offered to everyone, wherever you live, whether or not a law such as the GDPR or the California Consumer Privacy Act applies to us. Because we don’t sell or share personal information for advertising, there is nothing to opt out of on that front. If a restaurant you work for holds data about you on our service — a training record, for example — the restaurant is the one to ask, and we will help them answer. If you are in the EU or UK and believe we have not handled a request properly, you may also complain to your data protection authority.

13. Where your data lives

We are a United States company and our providers store data in the United States. If you use MenuFramer from elsewhere, your information is transferred to and processed in the United States, where privacy law may differ from your country’s. Our providers rely on their own recognised transfer mechanisms for data that originates in the EU, UK or Switzerland. If you need a data processing agreement for your restaurant, email us.

14. Children

MenuFramer is for businesses and is not directed to anyone under 18. We do not knowingly collect personal information from children; if you think we have, tell us and we will delete it.

15. Changes to this policy

When we change what we collect or how we use it, we will update this page and, for a material change, email account holders at least 14 days before it takes effect. The date at the top is the date of the current version.

16. Contact

MenuFramer, LLC, Oklahoma, United States. Privacy questions and requests: cheers@menuframer.com. See also our Terms of Service.