Restaurant Guest Data Ownership: What You Can Export From Your POS, Delivery App and Loyalty Tool

Restaurant guest data ownership comes down to one test: can you pull a file of your guests' emails, phones and visit history today, without asking anyone's permission? Most owners can for part of the list and not for the rest. This post gives you a question-by-question export audit you can run this week across your POS, delivery apps and loyalty tool. It is one piece of the larger plan in restaurant loyalty program software and guest data for South Jersey restaurants and bars. Run it before the spring rush, because the cheapest time to learn a file is missing is not the week you switch vendors.

The three places your guest list actually lives

Your guests are not in one list. They are scattered across three kinds of systems, and each one treats you differently.

• Your POS (point-of-sale system). It captures the check, and often the email or phone attached to it. You usually have an export button, but the file may be narrower than the screen.
• Delivery and marketplace apps. The app owns the customer relationship. You see an order, a first name or initial, and a delivery address for the driver. The terms differ by app and change over time, so read your current agreement instead of trusting a forum post, including ours.
• Your loyalty tool. It holds points balances, sign-ups and redemptions. Sometimes that lives inside the POS and sometimes in a separate vendor's database.

The fourth place, the one most restaurants lack, is a database you hold yourself. That is the only place where "ownership" is not a matter of reading someone else's help page.

A word on what ownership means here. Having a legal right to a list is one question. Being able to get it out in a usable file is another. We cover the second. For consent, privacy law and what you may send to whom, ask your own attorney.

The export audit: eight questions to answer this week

Do these in order. Write down the answer, the date, and who has the login. Each should take one short sitting, unless the answer is "I don't know," which is the finding.

1. Who is the account owner? Check whose email is the primary login on the POS, loyalty tool and delivery dashboards. If it is a former manager or a vendor rep, fix that first.
2. Can you export all guests, or only the ones who opted into email? The two numbers are rarely the same.
3. Which fields come out? Email, phone, first and last name, last visit date, visit count, average spend, order source.
4. Where are birthdays and anniversaries? If you collect them on a sign-up form, find out which system stores them and whether they are in the export.
5. Is consent recorded per guest? You want a field that says how and when each person agreed to hear from you.
6. How far back does history go? Some tools limit what they import or keep.
7. What happens to the data if you cancel? Check the agreement for an export window and a deletion date.
8. Can you export on a schedule, not just by hand? A manual download works once. A nightly feed is what lets another system stay current.

Score each system yes, partly or no on every row. A grid like this one keeps the answers in one place.

Export audit grid: fill in one column per system

Data point	POS	Delivery app	Loyalty tool	Your own database
Email	Check	Check	Check	Check
Phone	Check	Check	Check	Check
Visit history	Check	Check	Check	Check
Birthday	Check	Check	Check	Check
Consent record	Check	Check	Check	Check
Scheduled export	Check	Check	Check	Check

What a POS export gives you, using Toast as the worked example

We use Toast here because its help center is public, so you can check every claim yourself. Other POS vendors will differ, and the audit questions stay the same. We read these pages on October 11, 2026, and vendors edit them without notice.

The good news: a real guest list is exportable

According to Toast Support, Guestbook is the master list for a restaurant group. It combines contact info, order history, bookings, feedback, loyalty activity and marketing engagement. The profile lists order date, number of orders, average spend per check, order source, loyalty status and marketing preference. You can filter, then use Download list to get a CSV.

One detail trips people up. The same page says the download link is emailed to the logged-in user and expires after 72 hours. So the person who runs the export needs a working inbox they actually read.

The catches: scope, the six-month window and what gets dropped

The Toast Support email marketing FAQ says that when you first start Email Marketing, Toast imports guests who gave an email and visited within the last six months. Older addresses are skipped because they may be stale or flagged as spam. That is a sensible default, but it means the email tool's list can be smaller than your loyalty database. Do not assume the number on the marketing dashboard is your whole list.

Imports run the other way too. Toast's page on managing your email marketing audience says that when you upload guest emails from a previous service, only the email address is imported. Names and any other columns are discarded. If your old list had first names, visit counts or birthdays, that detail does not survive the upload. Keep the original file.

Birthday is the field to watch. The Guestbook profile list we read does not name it. If you collect birthdays through a sign-up form, confirm in writing where they are stored and whether they appear in an export.

Scheduled exports exist, but you have to ask

Toast Central documents automated nightly exports for systems that need a regular feed. You contact Toast Customer Care to get access, and a third-party system needs its own SSH key (a secure login credential) added on your side. Each file covers the previous business day. A nightly feed is how a database you hold yourself stays current without anyone downloading CSVs.

If your next step is emailing the list, our comparison of email marketing services for restaurants covers what each option does with an imported file.

Delivery apps: the list you mostly never see

Delivery apps are the hardest case. On most marketplaces, a guest who orders is the app's customer first. You fulfill the order. The app typically holds the account, the email and the order history across every restaurant, and sets the rules on who may market to that person.

What you typically get is order-level detail needed to make the food and get it out the door. Whether you can see a repeat customer, get a marketing opt-in, or export anything beyond sales reports depends on the app, your plan and the current terms. We could not confirm any app's current policy in time for this post, so we are not going to state one. Open your merchant dashboard and answer the audit questions from what is on the screen.

Two practical points hold regardless of the app:

• Treat marketplace orders as rented traffic. Counting them as "our guests" overstates your list.
• Give delivery guests a reason to come direct. A card in the bag with a sign-up link, or a direct-ordering page on your own site, puts the email in a system you control.

The second one is a web and ordering question as much as a marketing one. Your site has to make signing up a one-step action, which is where our restaurant and bar software work starts: a guest profile that connects reservations, events and follow-up.

Loyalty tools: whose database holds the points?

Loyalty is where "ownership" gets blurry. If the program is built into your POS, the data is probably in the POS export above. If it is a standalone app, the vendor's database holds sign-ups, balances and redemptions, and your export rights are in the contract.

Ask the vendor these questions, and get the answers by email:

• Can I export every member with email, phone, join date, points balance and last visit?
• Is the export self-serve, or do I file a request? How long does a request take?
• If I cancel, how long do I have to pull data before it is deleted?
• Are birthdays and consent timestamps in the export?

Pricing and ownership are linked. A cheap plan that keeps your member data behind a support ticket costs more than it looks. Our breakdown of what restaurant loyalty software costs in 2026 shows where the line items hide. If your audit says you must switch, follow the winter cutover checklist for changing your POS or loyalty system so the export happens before the old contract ends.

Building a copy you hold yourself

Once you have the exports, the question is where they go. A shared spreadsheet is a start and breaks fast: duplicates, no consent field, nobody sure which copy is current. A database you hold yourself fixes three things.

• One profile per guest. Merge the same person across POS, reservations and sign-up forms. Even Toast offers a merge tool for duplicate profiles, which tells you how common the problem is.
• Source and consent on every record. Where the guest came from, what they agreed to, and when.
• Fields your vendors do not give you. Birthday, party-size habits, event interest, allergy notes, who on staff knows them.

This is what a CRM (customer relationship management system) is for. We have built the same idea for another hospitality business, the booking site and captain's CRM we built for Sand Bar Joe's, where bookings and guest records live in a system the business controls. A restaurant version would pull from your POS's nightly export and your sign-up forms.

You do not have to build this to benefit from the audit. Plenty of owners stop at "I have a current export saved in a folder with two people who can reach it." That alone is worth doing.

What we do not know

We do not know your vendor contracts, your delivery apps' current terms, or what your POS plan includes. Vendors change export features, and a help page can be out of date by the time you read it. We also cannot tell you what consent your existing list carries. That is a question for your own attorney.

What we can say: an export you have never run is an export you do not know works. Run it, open the file, and count the rows.

Frequently Asked Questions

Who owns restaurant guest data, the restaurant or the POS company?

It depends on your contract, which is why we avoid a blanket answer. In practice, ownership means you can export the data in a usable file and keep using it if you leave. Read the data section of your POS and loyalty agreements, and ask your own attorney about rights and consent.

Can I export my guest list from my POS system?

Most modern POS systems allow some export. In Toast, for example, Toast Support documents a Download list function in Guestbook that produces a CSV. Check which fields come out, whether it covers all guests or only opted-in ones, and how long the download link lasts.

Do delivery apps share customer emails with restaurants?

Often they share little beyond what you need to fulfill the order, and marketing access varies by app and plan. We could not confirm any app's current policy for this post. Check your merchant dashboard and agreement, and build a direct sign-up path so delivery guests can join your own list.

What should a restaurant guest database include?

At minimum: name, email, phone, first and last visit, visit count, average spend, order source, birthday if collected, and a consent record with date and method. Add one profile per guest, merged across systems, so a regular who orders online and dines in is not counted twice.

Run the audit, then decide what to build

Start with the eight questions and the grid. If every row has a yes, save the exports and move on. If rows say no or "I don't know," you have a short list of things to fix or replace. When the answer is a database of your own, a custom CRM built around how your restaurant already runs is the route we would scope with you. Hosting, third-party subscriptions and ongoing support are scoped separately in a proposal. Send us your audit grid through the contact form on iolab.co and we will tell you plainly whether you need a build or just a better export habit.