Privacy Policy

• Your quiz answers: 12 multiple-choice answers about how your restaurant runs, the country you pick and your browser's time zone (so report dates match your calendar). On our website, the free preview is calculated in your browser; your answers are only sent to us when you continue to checkout or use a prepaid code, and two of them (your type of restaurant and sales range) when you press the button to be introduced to a partner company (section 4). When you continue to checkout, we pass your answers, your restaurant's name and time zone, and where your visit came from to Stripe with your order, so your report can be written once you've paid. If you leave Stripe's payment page with its back arrow, its link back to our website carries your answers and country after the “#” in the address, a part your browser doesn't send to us, so your free result opens again; the page then removes them from the address bar.
• If an AI assistant, such as Claude or ChatGPT, runs our free check for you: the 12 answers and the country it sends to our server. Our tool asks for nothing else, such as your name or email address. We use them only to work out your free result and don't store them; we only count how many checks are run each day. The assistant can give you a link that opens your result on our website: it carries your answers after the “#” in the address, a part your browser doesn't send to us, and the page removes them from the address bar when it opens.
• If an AI assistant costs a recipe for you with our recipe tool: the recipe it sends to our server, and any prices you gave it. We use them only to work out your draft and don't store them; we only count how many drafts are made each day. The link to your draft carries the recipe after the “#” in the address in the same way.
• If an AI assistant runs one of our free calculators for you: the figures and answers it sends to our server, such as your sales, costs or prices; for a dish, its name and ingredients; and for the FICA tip credit, card fees and booking fee checks, answers such as your state, how your business files its taxes, who processes your cards or which booking app you use. For the cash-out, tip-out and par sheets: the drawer, sales and tip figures, the names or jobs given for each tip share, and the item names on a par list. We use them only to work out the answer and don't store them; we only count how many calculator runs are made each day. The link to a calculator carries them after the “#” in the address in the same way, a part your browser doesn't send to us; the link to a sheet is its plain address and carries none of them.
• If an AI assistant runs our guided consult, “Fix my prime cost”, for you: the figures and answers it sends to our server, such as your type of restaurant, sales, costs, wages and hours, and each dish's price, plate cost and number sold, never its name. We use them only to work out the next step and don't store them; we only count each step as one calculator run. The link to the calculator it gets back carries the figures after the “#” in the address, a part your browser doesn't send to us.
• If an AI agent buys the full report, an online check or a pack of report codes for you through our paid MCP server: what it sends to prepare it. For the report, that's the 12 answers, your country, your restaurant's name and your email, and whether it asked for the premium report or the Fix Kit; for an online check, the name and town it searches, which go to Google Maps Platform to find the restaurant, and the restaurant it picks; for a pack of codes, the email address the codes go to. We keep this with the payment link for 7 days. Once the link is paid, we keep the id of the Stripe payment too. A report bought this way, with its Fix Kit and any real numbers you add, is stored like any paid report, and a pack like one bought on our website: the email address, the pack size, the amount and currency, the Stripe payment id and the date, and the codes with whether and when each was used.
• If an AI assistant lists your restaurant's deadlines with our deadline calendar tool: the state and the answers it sends, such as whether you have staff or sell alcohol, how the business is set up and how it pays its payroll taxes. We use them only to work out the dates and don't store them; we keep only the day's count.
• If an AI assistant checks your restaurant's website with our website tool: the address it sends to our server. We read that public page (and its menu page, if it links one, and its robots.txt file) and send the address to Google PageSpeed Insights for its phone speed test. We don't store the address or what the page says; we only count how many website checks are made each day.
• If an AI assistant searches our library with our tools (our guides, blog posts and sourced restaurant knowledge): the words it searches for, the kind of entry it lists, and the id of any entry it reads. We use them only to find the entries and don't store them; we only count how many searches (a list counts as one) and reads are made each day.
• If an app or an AI tool runs our free check, recipe tool, calculators, guided consult, sheets, deadline calendar or library through our free web API (restaurantdoctorai.com/api/tools) instead: the same things it would send through our MCP server, listed above. We use them the same way, only to work out the answer, and don't store them; we count the runs with the MCP server's, and our server's log keeps the tool's name, the time and whether it answered, not what was sent. The network address it came from counts toward a limit on calls a minute, and that count is cleared out soon after.
• If an AI agent searches our library through our A2A address (restaurantdoctorai.com/api/a2a): its message, whose text we use only as the words to search for, and the settings that come with it. We use them only to find the passages and answer, and don't store them; we only count how many searches come this way each day, and our server's log keeps the method's name, the time and whether it answered, not what was sent. The network address it came from counts toward a limit on calls a minute, and that count is cleared out soon after.
• Recipes you give our plate cost calculator. A pasted recipe is read in your browser and isn't sent to us. If you have it read a photo or PDF of a recipe, the file goes through our server to Google's Gemini API, which reads the ingredient lines and sends them back to your browser. We don't keep the file or what's read from it; we only count how many are read each day. Send only the recipe: anything else in the photo goes to Gemini too.
• If you use How AI sees your website, our online check: what you type to find your restaurant, which goes to Google Maps Platform to suggest places, with your rough area (worked out by our hosting provider from your connection and rounded to about a kilometer, a city, not a street) so places near you come first, and the restaurant you pick. We then read its public Google listing and the public website that listing names, ask Google Maps Platform where the restaurant ranks for two searches in its town (such as “Cafe in Sacramento”), and send the website's address to Google PageSpeed Insights for its phone speed test. To your browser alone, we also send a short excerpt of the website's words and the picture of its page that Google's speed test returns, for you to see. The listing's other details and what we read on the website, including its phone numbers, street addresses and hours, go to your browser only sealed, encrypted with a key only our server holds, for at most two hours, and come back to our server, which compares them with the listing and works out your result; none of these goes in an email or to any AI. Of all this the free part keeps only the day's count of checks; your area, the listing, the website's words and picture, what we read from it, and the result aren't stored.
• If you buy the full report of How AI sees your website: Google's id for the restaurant you picked (it goes to Stripe with your order), your email address (from Stripe Checkout), the Stripe session and payment ids, when the private link's email went, and how many times the link was opened. The report itself isn't stored: each time you open the link it's made fresh, the way the free part is. Your email holds only the link, none of Google's content.
• If you unlocked your full online check before November 3, 2026, when that was free: the email address you typed, your check's score and grade, the names of the three fixes it put first, Google's id for the place, and, if you answered it, whether the restaurant is yours or a client's (someone checking for a client gets a note about our report code packs in that email). If you asked for the reminder or tips, we also keep the grade and our fixes for each part of the check, in our own words, until the email with your check has gone out, so we can send it again if the first try fails. For a restaurant in the United States, we keep your email address until we send the one reminder 30 days later, which the unlock box told you about, and then erase it. We send that reminder, and any tips, only after you press the confirm button in the email we sent you with your check; if you don't press it within 7 days, we erase your address. If you ticked the box for tips and confirmed, we keep your address with the exact words you agreed to and the time you pressed the button. Otherwise we keep only a scrambled (hashed) form of your address, to count requests for our limits against abuse. It can't be read back as your address, but someone who already has your address could check it against the scrambled form.
• If you use our deadline calendar: your answers (your state and yes/no answers such as whether you have staff or sell alcohol) and any dates you add from your own licenses and permits are worked out in your browser and aren't sent to us. If you ask for reminders or a calendar link, we keep those answers and dates to rebuild your calendar, and for reminders your email address, whether you ticked the box for tips (with the exact words you agreed to), and three random keys: one for your calendar link, one for your private link to change or delete it, and one for unsubscribing. We also note when your calendar app last read the link, and which reminder emails we've sent.
• If you ask our AI restaurant expert questions: your questions and the conversation so far go through our server to Google's Gemini API to be answered, and the question with its answer then goes to TypeSafe, which double-checks it. We don't store your questions or the answers. We keep a random id in a cookie (rd_assistant), and for that id how many questions it asked each day and what the answers cost us, so we can apply the free and daily limits. If you've taken our free check on this device, your 12 answers and country go with your questions, unless you tap Don't use it in the chat, and our server turns them into a grade and estimates for Gemini to read; they aren't stored either. Tapping Was this helpful? adds one to a count for that day, with nothing about you, the question or the answer. If you're signed in to an AI phone line, the expert comes with it: we read your sign-in cookie to see that, and count that line's questions and their cost each day instead.
• If you run “Fix my prime cost”, our AI restaurant expert's guided consult: the figures you type stay in that browser tab while our calculators work on them there, and nothing goes to us. If you make its one-page plan, your answers, with any dish names you typed, go to our server only to draw it, and aren't kept. We read your 30-day pass or your AI phone line's sign-in cookie to see that the plan comes with it, and count how many plans that pass or line made this hour. If you then ask a question with your result left on, your type of restaurant, the period, the percentages worked out from your figures and which fix the consult named go with it through our server to Gemini, unless you tap Don't use it, and aren't stored. Your dollar figures and dish names stay in the tab. TypeSafe receives the question and the answer, as with any other question, and the answer can quote those percentages.
• If you use our AI phone line for your restaurant: your restaurant's name, menu, opening hours, staff phone number and email, and the Stripe subscription id. When a guest calls the restaurant's AI number, we receive the call's transcript (never a recording of the voice), the caller's phone number, and any order they place (the items, a name for the order and their number). Calls are answered by Retell AI; the conversation is handled by an AI model through Retell, and your menu goes to Google's Gemini API if you upload a photo or PDF of it to be read. We keep transcripts and guests' names and numbers 90 days, then delete them; we never identify callers by their voice. On our public demo number, the AI says a 4-digit code at the start of each call: whoever types it on our phone ordering page sees that call's words and its order while it runs and for 10 minutes after (never the caller's number), and we delete that copy after a day. If you upload your own menu on our phone ordering page to hear the demo line take an order from it, the photo or PDF goes to Google's Gemini API to be read and isn't kept; we keep the menu it read, with the restaurant's name, for a day and then delete it, together with what the demo call that used it kept of it (the order taken from it, the call's words and summary, and what our AI was told on that call). So that your call reaches your menu, you give the US phone number you'll call from: we keep only a scrambled copy of it (made with a secret key, so it can't be looked up), and only until that call starts, or for about an hour if you don't call; the call itself is kept like any call to our demo number. We also keep a scrambled copy of your email, of the restaurant's name and of a random key in your browser for 90 days, only so each restaurant gets one try: never the address itself, and we send nothing to it. If you sign in to the dashboard by email, we keep the address you typed and when you asked, to limit how many links are sent, and delete it a day after the link expires; an address that isn't signed up gets no email. If you type a question into Ask on your dashboard, it goes through our server to Google's Gemini API with what your dashboard shows that it needs: your restaurant's details, its counts and totals, call summaries and the names and notes on orders, with callers' phone numbers cut to the last 4 digits. A call's transcript is sent only when you ask about that call, at most two for one question, with phone numbers cut the same way. Google keeps it up to 55 days to check for abuse and doesn't use it to train its models. We keep only how many questions were asked and what they cost, unless you send us an answer you think is wrong, which we keep 30 days with names removed.
• If your restaurant uses table bookings on our AI phone line: we keep a guest book for your restaurant, on its behalf. It holds each guest's name and phone number, their bookings (the day, time, party size, seating, and whether they replied to a reminder), the days they visited, what they ordered by phone, notes your staff write, and their text consent and opt-out records. A note about an allergy or an access need is kept only on its booking. Texts to guests go out through Twilio from your restaurant's own number, only with the guest's yes: a confirmation, a reminder an hour before, and promotions only after the guest texts YES; every text says how to stop. To register that number with the phone carriers, the business details you type in your bookings app (legal name, EIN, address, website and a contact) go to Twilio and, through it, to the carriers. If you type a question into Ask in your bookings app, it goes through our server to Google's Gemini API with the book's guest names, party sizes and notes, never full phone numbers; Google keeps it up to 55 days to check for abuse and doesn't use it to train its models. We keep only how many questions were asked and what they cost, unless you send us an answer you think is wrong, which we keep 30 days with names removed. A restaurant's guest book is never shared with another restaurant and never sold.
• If you subscribe to Review Watch: the same as for a reading, plus the Stripe subscription id; each week we fetch the restaurant's newest public Google reviews through Outscraper and, for each new unhappy one, send it to Google's Gemini API to draft a reply, which we email you. If you buy an advisor pack: your email address (from Stripe Checkout) and its codes; a reading made with a code is kept like a bought one, and its link goes to the pack's email address.
• If you buy a review reading: the Google place id of the restaurant you pick (it goes to Stripe with your order and to Outscraper, which fetches that restaurant's newest public Google reviews; to compare, we also ask Google Maps for up to three places of the same kind nearby, sending the restaurant's location and type, and Outscraper fetches their newest public reviews), your email address (from Stripe Checkout), the reading's private key, the Stripe session and payment ids, and the reading itself (the stars and reply counts, how many reviews mention each topic, the summary, the rules and fixes shown, reply drafts, the dishes and first names guests mention, the places nearby with their counts, and short quotes from the reviews). The reviews go through our server to Google's Gemini API to be read, and with the reading's summary to TypeSafe, which double-checks the writing; we don't store the reviews themselves.
• If you buy the AI restaurant expert's 30-day pass: your email address (from Stripe Checkout), the pass's private key, the Stripe session and payment ids, and when the pass started and ends. Opening the pass's private link keeps its key in a cookie (rd_assistant_pass) on that browser until the pass ends.
• Your restaurant's name.
• If you add the Fix Kit, at checkout or after paying, or upgrade to the premium report after paying: that your order has the kit, when its email was sent and how many tries failed, the time of the upgrade, and the ids of the Stripe payments for what you bought later. A kit or upgrade added after paying is its own Stripe payment page, opened with the email address you paid with already filled in.
• If you buy a pack of report codes: your email address (from Stripe Checkout), the pack size, the amount and currency, the Stripe session and payment ids and the date, and the codes with whether and when each was used. Wrong codes typed are counted for the whole site per minute, the minute and the count only, with no IP address or browser details, and counts older than an hour are cleared out.
• If you use a prepaid code: the email address you type with it (it can be your client's), your restaurant's name, the 12 answers, the country and your browser's time zone, and any real numbers added afterwards. It is stored like a paid premium report, with no payment attached.
• If you press the button to be introduced to a partner company: the details listed in section 4, and the exact words you saw when you pressed it.
• Anonymous counts of clicks on paid links (section 4): the day, the page the link was on, the company and a number. Nothing about who clicked.
• If you buy the $19.99 report: any figures you choose to add about last month (sales, food and drink purchases, payroll, rent and utilities, delivery app sales and payouts, guests). At its check-up: which fixes you started, your updated answers and any new figures, for your plan's first full month.
• At checkout: your email address, name, billing address and payment details. Stripe collects these on its payment page. We receive your email address and the status and amount of your payment, never your full card details.
• The report we create for you from your answers.
• Your feedback, if you give it: how useful you found your report or your action plan, and any comment you add.
• Basic technical information when you visit, such as your IP address and browser type, in our hosting provider's server logs.
• Unless you turn it off: how you use the website, through Google Analytics, as described in section 5.
• Anything you tell us when you contact us.

The quiz doesn't ask for personal information about your staff or guests.

• To calculate your results and write your report.
• To take your payment through Stripe and deliver your report on screen and by email.
• To send you one email a few days after your purchase, asking how your action plan went. If you bought the $19.99 report, we also send one email on the 1st of the month after your plan's first full month, when your included check-up opens. These are the only follow-up emails we send, apart from the email that delivers what you bought (your report, the Fix Kit's workbooks and their PDFs, or a pack's codes), the one email that asks for your numbers when an AI agent buys a premium report or spends a report code for you, and any you ask for, such as your check-up link, which we email to the address you paid with when you ask for it.
• If someone uses a prepaid code for you: to send your report, and then the same check-in email and check-up reminder, to the email address they typed.
• To email you the private link to a full report you buy, once. For a check unlocked before November 3, 2026: to email it to you, once; for a restaurant in the United States, one reminder 30 days later to check again; and, only if you ticked the box for them, occasional tips to cut costs and bring in more guests. The reminder and the tips are sent only after you press the confirm button in that first email. Every reminder and tips email has a link that stops them all.
• If you ask for deadline reminders: after you confirm from the first email, a list of the month's dates on the 1st and a reminder before each date, and, only if you tick the box for them, occasional tips. Every email has a link to change your answers, stop the emails or delete the calendar, and one that unsubscribes you.
• To pass on an introduction you ask for, as section 4 describes, and to email ourselves about each introduction, each pack sold and each full report sold or paid for twice, so we can act on it.
• To improve the report, using your feedback. We only quote a comment publicly with your permission.
• To answer your questions and handle refunds.
• To keep the service secure and prevent fraud and abuse.
• To meet our legal, tax and accounting obligations.

We don't use your information for advertising, and we don't send you marketing emails unless you ask for them: the one reminder our online check told you about when you unlocked it and you confirm, the deadline reminders you confirm, and tips if you tick a box for them and confirm. The emails that deliver what you bought have no offers in them.

If you are in the European Union or the United Kingdom, we rely on these legal bases: performing our contract with you (creating and delivering your report), our legitimate interests (security, fraud prevention and improving the service) and our legal obligations (tax and accounting records).

We share information with the providers that run the service, and only what each of them needs. The one other place your details go is a partner company you ask us to introduce you to (section 4):

• Stripe, including its Link service, processes your payment as the reseller and merchant of record of your purchase (for one an AI agent pays with Stripe's machine payments, Stripe processes the payment and we are the seller), and handles your payment details under its own privacy policy.
• Google (Gemini API) helps prepare your report. It receives your answers, any figures you add and your restaurant's name, not your email address or payment details. If you have our plate cost calculator read a recipe photo or PDF, it receives that file too, and if you ask our AI restaurant expert a question, it receives your question and the conversation so far, and, if you ran a guided consult and left its result on, your type of restaurant, the period and those percentages. If you buy a review reading, it receives the restaurant's reviews. If a restaurant asks Ask on its dashboard, it receives what that question needs from the dashboard, as section 1 says.
• TypeSafe double-checks what our AI writes. Before your report is sent, it receives the report's text, its figures and your answers, which can include your restaurant's name, and if it finds a claim the figures don't support, our AI writes the report once more; if you ask our AI restaurant expert a question, it receives the question and the answer; and if you buy a review reading, it receives the restaurant's reviews with what our AI wrote about them. It never receives your email address or payment details, and it says it doesn't use customer data to train its models. It never changes your figures or your grade.
• Twilio sends the texts of a restaurant that uses table bookings, from that restaurant's own number, and registers the number with the phone carriers: it receives the guest's phone number, the texts and replies, and the restaurant's business details for the registration.
• Retell AI answers the calls to a restaurant's AI phone line, if the restaurant uses it: it receives the call's audio while it's live, to understand and speak, and the restaurant's menu answers our system gives it. It's set to keep no transcripts or recordings of its own; it sends us the transcript, which we keep 90 days.
• Outscraper, a review data company, fetches the newest public Google reviews of the restaurant you pick when you buy a review reading. It receives only that restaurant's Google place id, and those of up to three places nearby for the comparison, never your email address or payment details.
• Google (Maps Platform and PageSpeed Insights) powers our online check and the review reader: it receives what you type to find your restaurant and the restaurant you pick (on the review reader, to show its rating, places like it nearby and Google's review summary before you pay; for a review reading, its location and type too, to find places like it nearby), and PageSpeed Insights receives your website's address. Google handles these under its own privacy policy. It never receives your email address.
• Resend sends your report, the follow-up emails described above, the Fix Kit's workbooks and their PDFs, a pack's codes, and the email that asks for your numbers after an AI agent buys a premium report or spends a code for you, emails you the private link to a full report you buy, and emails you the online check you unlocked before November 3, 2026. It also sends us the emails our site writes to us about an introduction you ask for, a pack that was bought or a full report that was bought or paid for twice, which hold your email and the details in section 4, about the feedback you give (with your email, your restaurant's name, your comment and your report's link, so we can reply and look at it), and about an order that failed to deliver (with your email and your restaurant's name, so we can fix it).
• Google Analytics, unless you turn it off (or, in the EU, EEA, UK and Switzerland, only if you allow it), shows us how people use the website (see section 5).
• Vercel hosts the website, and Neon hosts the database where we keep orders and reports.
• Zoho Mail runs our support inbox, so it holds the emails you send us and our replies, and the emails our site sends us about introductions, packs, your feedback and orders that failed to deliver.
• A partner company, only if you press the button to be introduced to it, receives what section 4 lists and handles it under its own privacy policy. It isn't one of our service providers.

Our Service providers page lists each of them with what it handles and where, and we update it before we add or replace one.

If an AI assistant runs our free check, costs a recipe, runs a calculator, checks a website, lists your deadlines or searches our library for you, the company that provides the assistant (for example Anthropic or OpenAI) isn't one of our providers: it handles your conversation, including anything you tell the assistant, under its own privacy policy. We receive only the answers and country it sends to our free check, the recipe and prices it sends to our recipe tool, the figures and answers it sends to a calculator or our guided consult, the website address it sends to the website check, the state and answers it sends to the deadline calendar, or the words, kind or id it sends to our library, plus the usual technical details of the request (such as the IP address it came from), which our hosting provider keeps briefly in its logs.

We may also disclose information when the law requires it, to protect our rights or others' safety, or as part of a sale or reorganization of our business, in which case this policy continues to apply. We don't sell your personal information to data brokers or share it for targeted advertising. An introduction you ask for is the one case where your details go to another company, and because we may be paid a fee if you sign up, some privacy laws would call it a sale or sharing of your information. That is why it happens only when you press the button, and you decide each time.

Under your biggest problem on your free result, and in your report, we sometimes show companies whose products are made for it, such as online ordering, payroll or inventory software. We may be paid by these companies, in two ways that work differently. We show them only to visitors in the United States, chosen by your biggest problem and never by what a company pays, and a fee never changes your grade or what we write about your restaurant.

• Paid links. A link marked “Paid link” goes through an address on our site that adds one to an anonymous daily count of clicks and sends you on to the company's own website. We set no cookie, the count holds no name, email address, IP address or answers, and we send the company no details about you; it sees only that you came from restaurantdoctorai.com. If you sign up, the company pays us a fee. What you do on its website, including any cookies it or its affiliate network sets, is theirs, under their own privacy policies. The link is the same in your report's PDF, where a click is counted the same way. See Paid links.
• Introductions. For some companies you can also ask to be introduced. Nothing is sent until you press the one button that says “Yes, send my details to” and the company's name, which sits directly under words that say what is sent. If you press it, we send that company your name, your email address, your restaurant's name, your city (only if you enter one), your type of restaurant, your sales range and your biggest problem, so that it can contact you by email about it. We ask for no phone number. On your free result the form starts with the restaurant name you typed in the quiz, and on your report with the email address and restaurant name from your order. You can change them, and nothing leaves until you press the button. The company uses the details under its own privacy policy, and we may be paid a fee if you sign up with it. Introductions are for restaurants in the United States only: when you press the button, we also check which country your connection comes from, and keep nothing of it.
• How an introduction reaches the company: our site emails the details, through Resend, to our support inbox at Zoho Mail, and we put them into the company's own referral form by hand. We don't send anything to a company automatically.
• What we keep: a record of the request, with what you sent, the company, the time, whether you pressed the button on the free result or in the paid report, and the exact words you saw, so there is proof of what you agreed to. We store no IP address, browser details or cookie with it. If the same email address asks for the same company again within 90 days, we record it once. We don't check that the email address is yours, so enter only your own.
• Nothing goes to a company because you looked at a page, clicked a paid link, bought a report or used a prepaid code. Only the button does it.

We count anonymous visits and quiz steps by where they came from (for example an ad link), without cookies or anything that identifies you, and the steps of the plate cost calculator's recipe tool, the answers to the food donation guide's poll and the steps of “My restaurant” (something saved, filled in, opened, copied or forgotten, never what it holds) the same way. Your browser remembers where you came from only until you close the tab, and if you buy, your order notes it too, so we can count sales the same way. We also count how many free checks AI assistants run with our tool each day: only the number, nothing about you or your answers. We count the recipe drafts they make the same way, with nothing about your recipes, the calculator runs, with nothing about your figures or answers, the website checks, with nothing about the website, the deadline calendars, with nothing about your answers, and the searches (a list counts as one) and reads of our library, with nothing about what was looked up.

We also use Google Analytics, which shows us how people use the website: the pages they visit, how far they get in the quiz and which report they choose. It runs when you visit, and you can turn it off at any time with “Cookie settings” and “No thanks”. If you're in the EU, the EEA, the UK or Switzerland, or your browser sends a Global Privacy Control signal, it doesn't run unless you choose “Allow analytics” in the banner at the bottom of the page. To know whether to ask you, we check which country your connection comes from, and keep nothing. After “No thanks”, it doesn't load at all and nothing is sent to Google. It never runs on your report, check-up or feedback pages, whose addresses contain your private link. Google sets cookies, such as _ga, to recognize your browser on later visits. It receives your IP address, which it uses to estimate your general location and says it doesn't store. We've turned off Google signals and ad personalization, so this information isn't used for advertising. Google handles it under its own privacy policy.

Your browser keeps your choice, without a cookie, so we don't ask again on every page. You can change it at any time with “Cookie settings” here or at the bottom of our home page and guides. If you switch Google Analytics off, we also remove its cookies from your browser.

Our free check and calculators, and the number forms of the $19.99 report and its check-up, can remember your restaurant's answers and numbers in your own browser when you press “Remember on this device” or tick “Also remember these numbers on this device”, so our other tools can fill them in and you don't type them twice. They're kept in your browser's storage on that device only, and never sent to us. We read them only to fill in our tools, and we don't pass them to Google Analytics (which, as described above, runs by default outside the EU, EEA, UK and Switzerland) or to anyone else. Google Analytics, where it's on, runs on the pages that keep them (our home page, our calculators and the guides with a calculator in them); like any script on a web page, it has access to what that page keeps in your browser, so we add no other outside scripts to these pages. What reaches us is still only what you send: your answers when you go to checkout, use a prepaid code or ask for an introduction, as section 1 says, never the numbers behind them, and the numbers in the $19.99 report's form or its check-up when you press its button. “Save a copy” puts a small file on your device, which “Open a copy” adds to another browser; we don't receive the file, and anyone who has it can read it. You can remove one restaurant or everything with “Forget” in “My restaurant”, or by clearing this site's data in your browser. Safari deletes them after 7 days of Safari use without a tap, click or typing on our site, and a private window forgets them when it closes.

Prices you type in the plate cost calculator's recipe tool can be saved in your own browser, so your next recipe fills them in; they never reach our servers, and you can remove them with “Forget my saved prices”, with “Forget everything” in “My restaurant”, or by clearing this site's data in your browser.

Our deadline calendar keeps the dates you add from your own licenses and permits in your own browser as you add them, so they're there when you come back. They aren't sent to us unless you save your calendar for reminders or a calendar link (section 1). You can remove each one with the × beside it, or by clearing this site's data in your browser; “Forget everything” in “My restaurant” doesn't remove them. Until November 3, 2026, unlocking an online check left a note in your browser saying you had, and nothing else. It no longer opens anything, and our page removes it the next time it loads.

Our AI restaurant expert sets two cookies of its own, only when you use it, and only our server reads them:rd_assistant, a random id that counts your free questions (it holds nothing about you), and, if you open a 30-day pass's private link, rd_assistant_pass, which keeps the pass on in that browser until it ends. They're needed for the feature to work, so they aren't part of “Cookie settings”.

That expert's guided consult keeps your answers and its result in that browser tab's own storage, so a reload doesn't lose them. They go when you close the tab or press “Clear my figures”. If you tap “Open it in the calculator”, a new tab opens with your figures in the part of its address that browsers don't send to anyone, and they stay in that tab until you close it. They aren't sent to us unless you make the plan, only the percentages can go with a question (section 1), and we don't pass them to Google Analytics or anyone else. Google Analytics, where it's on, runs on that page too; like any script on a web page, it has access to what the page keeps in your browser.

Hearing the demo line take an order from your own menu sets rd_menu_preview, a random key kept 90 days so each device gets one try; we keep only a scrambled copy of it. Our AI phone line sets two more, for restaurants that use it: rd_phone_session, when you sign in to your dashboard with a link we email, which keeps that device signed in for 90 days or until you sign out; and rd_kitchen_device, when a kitchen tablet is paired with a code from the dashboard, which keeps it showing the restaurant's orders until the owner signs all tablets out. Each holds only a random key, and we keep only a scrambled copy of it. They're needed for the feature to work, so they aren't part of “Cookie settings”.

Stripe's payment page uses its own cookies for security and fraud prevention, and so can the websites of partner companies once you are on them (section 4). Because we don't track you across other websites, our site doesn't respond differently to “Do Not Track” browser signals.

• A restaurant's guest book (table bookings): a guest card is deleted 18 months after the guest's last booking, visit or phone order; a guest who booked once and never came is deleted once 90 days have passed since that booking; notes about allergies or access needs are deleted once 90 days have passed since their booking. A guest's text consent and opt-out records are kept while the restaurant uses texting, so a guest who said stop is never texted again, even after their guest card is deleted. A restaurant can delete any guest sooner, and download its guest book anytime.
• Orders, answers, reports and feedback: for as long as your report link should keep working, and for our tax and accounting records, generally up to 7 years, unless you ask us to delete them sooner. If you do, we delete your answers and report and keep only the payment records the law requires.
• Introduction requests: until you ask us to delete them. We don't delete them automatically, and we keep them as the record of what you agreed to. The company you were introduced to keeps its own copy under its own policy, so ask it too.
• Pack and code records: for as long as the codes can still be used, which is for good because they never expire, and for our tax and accounting records. Wrong-code counts: cleared out after an hour. Paid-link click counts: as daily numbers with nothing about who clicked.
• Online check: the day's count. A full report you buy: your email address for 90 days, then deleted, when its link also ends; the place's Google id and the payment's record stay for our tax and accounting records. The email our site writes to us about the sale holds your address too, and stays in our inbox until we delete it, or you ask us to.
• Unlock requests made before November 3, 2026: until you ask us to delete them, with your email address erased once the reminder is sent, you unsubscribe, or 7 days pass without you pressing the confirm button, unless you asked for tips and confirmed. You can stop the reminder and tips anytime with the unsubscribe link in any of them, or by writing to us.
• Deadline calendars you save: until you delete them with your private link or ask us to. Stopping the emails, or 7 days passing without you pressing the confirm button in the first email, erases your email address but keeps your calendar link working until you turn it off or delete it; a scrambled form of the address stays, to count requests for our limits against abuse.
• Answers an AI assistant sends to our free check: not kept once your result is worked out; we keep only the day's count of checks.
• Answers an AI assistant sends to our deadline calendar tool: not kept once the dates are worked out; we keep only the day's count.
• Recipes: not kept. Recipes an AI assistant sends to our recipe tool, and recipe photos and PDFs our plate cost calculator reads, are gone once your draft or reading is done; we keep only the day's counts.
• Answers and numbers you remember on your device: we don't hold them. They stay in your browser until you forget them, clear this site's data, or your browser deletes them.
• Figures and answers an AI assistant sends to our calculators: not kept once the answer is worked out; we keep only the day's count of calculator runs.
• Figures and answers an AI assistant sends to our guided consult: not kept once its next step is worked out; each step adds one to the day's count of calculator runs.
• What an AI agent sends to buy something for you: 7 days with its payment link if the link isn't paid; once it's paid, as long as the purchase's other records.
• Website addresses an AI assistant sends to our website check: not kept once the check is worked out; we keep only the day's count of website checks.
• Words, kinds and ids an AI assistant sends to our library: not kept once the entries are found; we keep only the day's count of searches (a list counts as one) and reads.
• Questions to our AI restaurant expert, and a guided consult's figures and plan: not kept. The daily counts of questions per random id, and what the answers cost: deleted after 90 days. How many plans a pass or phone line made this hour: used only for that hour's limit, and cleared out some time after the hour ends, the next time our limits tidy up.
• 30-day pass records: for our tax and accounting records, like orders, unless you ask us to delete them sooner.
• Review Watch: your email address, the restaurant's Google place id and name, the Stripe subscription id, when it last looked at your reviews and its readings (each kept 90 days, like any reading), until the watch ends; once it has ended for 90 days, the email address and the name are erased and the subscription's record stays for our tax and accounting records. The reviews it looks at each week are not kept.
• Advisor packs of review readings: your email address, the codes and which were used, for as long as the codes can be used (they never expire) and for our tax and accounting records.
• Review readings: the reviews themselves are not kept. A reading you bought, and your email address with it: 90 days, then deleted; the payment's record stays for our tax and accounting records.
• Server logs: for a short time, as our hosting provider keeps them.
• Messages you send us: for as long as we need them to help you, and for our records.

We use encrypted connections (HTTPS), keep access to our database limited, and never see or store full card numbers. Anyone with the link to your report can open it, so share the link only with people you trust. No way of storing or sending information is completely secure, but we work to protect yours.

• You can ask for a copy of your information, ask us to correct it or ask us to delete it. Email support@restaurantdoctorai.com from the address you paid with, and we'll respond within 30 days.
• If you are in the European Union or the United Kingdom, you can also object to or restrict some uses of your information, ask for it in a portable format, and complain to your local data protection authority.
• If you live in California or another US state with a privacy law, you have similar rights to know about, correct and delete your information, and we won't treat you differently for using them.
• To have an introduction request removed from our records, email us from the address you used. A company you were introduced to holds its own copy, so ask it as well.
• For payment details, you can also contact Stripe directly; it can delete the data it holds about your purchase.

We are based in the United States, and our providers process information in the United States and other countries. When information from the European Union, the United Kingdom or Switzerland is transferred, our providers use recognized safeguards such as standard contractual clauses.

RestaurantDoctorAI is for businesses and isn't meant for anyone under 18. We don't knowingly collect information from children.

We'll post any changes on this page with a new date. If a change is significant, we'll say so clearly at the top of this page.

Gomorra Labs LLC, a Wyoming limited liability company
Email: support@restaurantdoctorai.com

See also our Terms of Service and Help & support.