Privacy Policy

Version 2.8 · Last updated October 21, 2026

This document describes what OrderInsider actually collects and holds, on the website and in the app. OrderInsider is operated by OrderInsider LLC, a North Carolina limited liability company, which is responsible for the information described here. It has not been reviewed by an attorney and is not legal advice.

Without an account

You can use OrderInsider without an account, and we do not ask for your name, email, or phone number to do so. Your phone or browser is given a random device identifier. The app keeps it in your phone’s secure storage; the website keeps it in a cookie of our own that lasts 400 days from your last visit, and records the browser details each time it hands one out. We use no advertising or tracking cookies. When you pick a dish, we store the pick with that identifier, the time, your IP address and browser or app details. We keep those details to stop one person casting many picks and to investigate manipulation; they are never shown to anyone. We also record which restaurant pages a device opened, what was shown on its For You page, and the dishes and restaurants you choose, save or hide there, so recommendations improve over time.

Searches and taps. When anyone searches, we record the words searched, how many results came back, which result was opened, and whether it was on the website or the app, but not the device identifier or IP address of whoever searched. When anyone opens a restaurant’s directions, website, phone number or similar, we add one to an anonymous count for that restaurant. These are counts, not records of who did what, and they are what restaurants see in their dashboards and OrderInsights reports.

The Charlotte feed. Picks made in the last week appear on a public feed in the app, grouped by restaurant and by day, never by time of day. They show the dishes and the restaurant, and no name, photo or other detail about who picked them unless that person has an account with the feed switch on (see Your first name in public, below), which shows their first name.

Comments. If you comment on a pick, we store the comment, any display name you type, and the same device, IP and browser details. Comments and names you choose to add are public on that restaurant’s page, and the restaurant can reply.

Dish photos. If you add a photo to a pick, your phone resizes it and removes its location and other metadata before sending it. An automated AI check reviews the photo before it is posted (see Automated checks below); a photo that doesn’t pass is not stored, and we keep only a note of the device, the dish, the reason and the IP address. Posted photos are public on that restaurant’s page and on the Charlotte feed, with the same name rules as your picks. You can remove your photo at any time, and other guests can report one.

Check numbers. If you enter the number from your check, we look it up in the restaurant’s point of sale system to show what your table ordered. We keep a record that a lookup happened and whether it matched, not the number or the order.

With an account

An account is optional, but you need one to post a bite, add friends, join a table or make plans. It needs your email address, which we use to send your sign in code, plus any emails you choose to get (see Notifications and email below). Each time a code is requested we log the email address and IP address, to stop abuse. Signing in links your devices, so your picks follow you to a new phone. Your profile has a first name, and optionally a last name and a photo. Your last name is shown only to friends and people at your tables. Your photo is shown to them too, and beside your first name on bites you share with Charlotte, when the switch below is on.

Your first name in public. A switch in your profile, “Show my first name on the Charlotte feed”, decides whether your first name (and, on bites, your photo) appears on the public Charlotte feed and on bites and picks shown to everyone. It sits next to your name and starts on when you first make your profile; you can turn it off at any time, and then your picks show without a name. Restaurants never see who picked.

Friends you add through an invite link can see your name, photo and your picks. Plans you make store the restaurant, time, note, how many seats, who was invited and how they answered, visible to the people in that plan. A plan posted to one of your tables is open to everyone at that table, who see the restaurant, time, note, and the first names of the host and everyone going.

My Table. You can start a table (a group with a name and an emoji or picture) or join one through its invite link. We store the table, who is at it, who invited whom, and when they joined. Anyone with the link can join, up to 50 people. Everyone at a table sees each other’s first and last name, photo, and the picks and notes they made in the last 30 days, and can add each other as friends from there. A table’s picture is stored in public file storage under a random name. The invite page shows the table’s name, picture, how many people are at it, the first name of the person who shared it, and a few of their photos. You can leave a table at any time, and the person who started it can remove people.

Your table. When you choose friends to eat with, we compare everyone’s picks to suggest places that suit the whole table. Each person at the table sees how well each place fits each of you, and the dishes each of you has picked there. Only friends and people you share a table with can be added, and nothing about the comparison is stored afterwards.

Insiders

Insiders are guests we have invited to make their picks public; nobody becomes one without agreeing to it. An Insider’s profile shows their handle, first and last name, photo, short bio, follower count, a list of ten places they chose, their picks and comments from the last twelve months, and the bites they share with Charlotte, to anyone (last name only if they gave one). Unless an Insider chooses “Right away” in their settings, these reach public pages two hours after they are made, so a post says where they ate, not where they are now; friends and tables see them at once, and pick counts update straight away without a name. Everyone else’s picks stay as described above.

You can follow an Insider without an account. We store the follow with your device identifier and record when an Insider’s link or profile is opened, followed, or used to open a restaurant, so we can count real followers. Insiders see their follower count, not who their followers are. We do not pay Insiders and cannot see any arrangement an Insider has with a restaurant; see Section 10 of the Terms.

Notifications and email

In the app, notifications are off until you turn them on. If you do, we store your phone’s notification address (a token from Apple or Google, delivered through Expo) with its device identifier, and which kinds you want. We send: a Sunday recap at 5 PM (your week’s picks, or a short reminder on a week without any, which stops after two in a row); dinner plans (an invite, a friend’s answer, a plan posted to one of your tables, a plan called off, a reminder on the day, and the next morning a question about what you ordered, unless you’ve already added it); friends (when someone uses your invite link); and bites (when a bite of yours that was held for review goes up, and when it reaches 3 and then 10 saves, never for views). We send at most two a day, apart from plan invites and cancellations. The recap has its own switch in the app and plans and friends share another, and you can turn all of them off in your phone’s settings. We keep a record of each one sent and whether it was opened, and its title and text, to get the timing right.

The notifications list. Each of these is also kept in the app’s notifications list (the bell on Social), whether or not notifications are switched on, so nothing is missed. We store what it said, who it was for, and when you read it. Entries are deleted after 30 days.

By email, the Sunday recap is sent only if you ask for it, and a plan invite is emailed when a friend invites you. Every email has a one click unsubscribe link, and both can be switched off from your account. If you have the app, it tells us so (it sends its device identifier when it opens), and we send these as notifications there instead, never both.

Blocking

You can block anyone whose comments, photos or picks you see. We store who blocked whom so their posts stay hidden from you on every device you use, and remove any friend connection between you. They are not told. You can unblock from your profile.

Reports. When you report a comment, photo, bite or something wrong on a page, we store what you wrote, which item it was about, your device identifier, IP address and browser details, and your account if you are signed in, so we can follow up and spot abuse of the report button. We do not tell the person you reported who you are.

Bites (short videos)

If you post a bite, we store the video and its sound, the dishes you tagged, your caption, who you chose to show it to (Charlotte, Friends, Groups), when you posted it, and the device and network details it was sent from. Bites are streamed through Mux, which also writes an automatic transcript of the sound; it isn’t shown to anyone and is used only to check what’s said. Before a bite goes up, a few still frames, the caption, the dish names and, once it’s ready, the transcript are checked by an AI model (Anthropic’s Claude) for content that breaks the rules; a bite it isn’t sure about is held for a person to look at. On a bite shared with Charlotte, your first name and photo show only if your feed switch is on; on a bite shared only with friends or groups, they show to those people.

What we count. When someone watches a bite we record, against their device and not their name: a view (after two seconds, once per device), whether they watched to the end, whether they saved it, shared it, or tapped through to the restaurant or a dish. The poster sees their own view count and everyone sees how many people saved a bite. Restaurants see totals for their own bites and dishes, never who posted or who watched. Saving a bite also adds its restaurant to your Saved list. Which bites you saved is shown only to you.

How long bites stay. A bite shows while a dish it’s tagged to is on the restaurant’s menu, for up to 12 months; after that only you can see it, for 90 days, and then it’s deleted. A bite you delete is taken off at once and its files are deleted right away, unless it was held for review, hidden after reports, or has a report we haven’t looked at yet; then, like a bite we take down, its files are deleted after 30 days; we keep a record of it without the video (caption, transcript, dishes, when, and the device and network details) as evidence of what was posted. Bites we are legally required to report are kept, with the account and email address that posted them, for as long as the law requires (currently one year) and then deleted. If we stop an account from posting, we keep its email address so it can’t simply sign up again.

Location and photos in the app

If you allow it, the app uses your location to show how far away each restaurant is, to list restaurants near you when you post a bite, and to tell whether you are at the restaurant, which decides whether a bite’s dishes count as picks. All of that happens on your phone: your location is never sent to us or stored by us. A clip you film and save to post later keeps where it was filmed on your phone only, until you post or delete it. Maps in the app are drawn by Apple Maps, which loads the map for the area on screen. The app uses your camera or photo library only when you add a dish photo, post a bite, or choose a profile picture, and only what you choose is uploaded. The microphone is used only while you record a bite.

Automated checks and AI

We send some of what you post to Anthropic, which runs the Claude AI model, to check it before anyone sees it: each dish photo; for each bite, a few still frames, the caption, the dish names and the automatic transcript of what is said. The check only decides whether the post can go up; a photo that fails is not posted, and a bite it isn’t sure about waits for a person. We also send the text of recent guest comments on a restaurant, without names or any identifier, to write that restaurant’s monthly OrderInsights summary. None of this includes your email, name, device identifier or location. Voyage AI receives only menu text (dish names and descriptions), never anything about guests. We do not use AI to make decisions about you beyond whether a post goes up, and you can ask us to look at any automatic decision again.

Review data

We hold a copy of restaurant reviews that were published publicly on the internet, including the reviewer’s public display name, star rating, review text, and date. We use it privately, to understand which dishes guests talk about and to prepare reports for restaurants. It is not shown on OrderInsider. We do not sell it, build profiles of reviewers, or try to identify or contact them.

If you wrote a review and would rather it not be held here, email hello@theorderinsider.com with enough detail to find it and we will delete our copy. You do not need an account and you do not need to explain why.

Restaurants

For restaurants we hold: the listing itself (name, address, menu, and related details); consent records (the name, email, and role of the person who chose a listing option, the date, the version of the terms they accepted, and the IP address and browser the acceptance came from, kept as evidence the agreement happened); claim requests(the name, role and contact phone of someone claiming a page, how they chose to have it confirmed, and any note they add, used only to confirm they work there); the email of anyone who signs in to manage a restaurant; reports a restaurant’s managers send us about guest content; the email addresses that asked for our daily or weekly restaurant emails, each of which has an unsubscribe link; and, for subscribers, billing details handled by Stripe. We never see or store full card numbers. Restaurants see counts and the public comments on their page, never who picked, searched or watched.

Service providers

We share information only with the providers that run OrderInsider: Supabase (database, sign in and file storage), Vercel (hosting), Stripe (payments), Resend (email), Expo (delivering app notifications through Apple and Google, and app updates), Apple (maps in the iPhone app), Google (maps in the Android app and on restaurant listings on the website, and delivering Android notifications), Mux (storing, streaming and captioning bites), Toast (check lookups at restaurants that use it), Outscraper (the vendor we obtain restaurant details and public review data from), Anthropic (the checks described above, and reading menus and review text) and Voyage AI (comparing menu items, using menu text only). Each gets only what it needs for that job. Our information is stored and processed in the United States. We do not sell personal information, we do not share it for advertising, and the app contains no advertising or third party tracking. We may publish or share aggregate statistics, such as which dishes or cuisines Charlotte is picking on which days, but only as totals that cannot identify any person.

Retention and deleting your account

You can delete your account at any time from the account screen in the app, or by emailing us. Deleting it removes your email, name, photo, friends and friend invites, the plans you made and your answers to other people’s, your notifications list, your bite rules agreement, any Insider profile, and any restaurant claim or team role. It takes you out of every table you are at (a table you started passes to the person who has been there longest, and closes if you were the last one). A restaurant you alone manage is deleted too, and its subscription cancelled. Your dish photos are deleted, and the names on your comments are cleared. Your bites come down at once and their files are deleted, except a bite that is held for review, was hidden after reports, or has a report we haven’t looked at yet, whose files are deleted after 30 days, and a bite we must keep for a legal report (see Bites above).

Your picks stay on the boards as anonymous counts, and your comments stay without a name, so a restaurant’s numbers do not change when somebody leaves. Records kept by device (picks, saved bites, follows, blocks, views and notification settings) stay with your phone’s old random identifier, which is no longer linked to any account; the app replaces it with a new one when you delete. The IP and browser details stored with picks, comments, photos and bites are kept for integrity purposes.

Notifications list entries are deleted after 30 days. Logs of sign in code requests, notifications sent, device identifiers handed out, rejected photos and reports do not yet have a fixed deletion date; ask and we will delete what is about you unless we need it to deal with abuse or the law requires us to keep it.

Listings are kept while a restaurant is listed and for a reasonable period after. Consent records are kept indefinitely, including records of restaurants that asked to be removed, because deleting a removal record would risk that restaurant being listed again by mistake.

Your choices

Anyone may ask what we hold about them, ask for it to be corrected, or ask for it to be deleted, by emailing hello@theorderinsider.com. That includes diners, review authors, and restaurant staff. You can also ask for a copy of what you gave us. Several states, including California, Virginia, Colorado, Connecticut, Texas and Oregon, give residents these rights by law, plus the right to opt out of the sale of personal information, targeted advertising and profiling. We do none of those three, and we give everyone the same rights wherever they live. We may ask you to confirm the request from the email on your account, and we answer within 30 days. If we turn a request down, we will say why, and you can reply to ask us to reconsider. Using these rights never changes how OrderInsider treats you. Restaurants can have a listing removed at any time under Section 5 of the Terms.

Security & children

We use reputable providers and reasonable safeguards, though no system is perfectly secure. If we learn of a breach that affects your information, we will tell you as the law requires. OrderInsider is a general audience restaurant service. You must be 13 or older to use it, and it is not directed to children under 13. We do not knowingly collect information from children under 13; if we learn we have, we delete it and the account. A parent who thinks their child has given us information can email us and we will delete it.

Changes & contact

We may update this policy; the version and date above will change. Earlier versions are archived: version 2.7, version 2.6, version 2.5 and version 1. Questions or requests? Email hello@theorderinsider.com or call 703-939-0996.