Choose one person at the restaurant to own the privacy notice shown on your website. An owner, general manager, or operations lead can fill that role, provided they have authority to gather information and request changes. Your website and ordering providers should supply details about their services; counsel should advise on the notice and its legal treatment. The restaurant owner remains accountable for making sure the work gets done.
The notice owner does not have to write every sentence or make legal decisions alone. Their job is to keep a reliable record of what the website does, send changes to the right reviewers, and check that the current notice is accessible. This is a content-ownership decision, separate from deciding how consent controls work.
List what the website collects and who can explain it
Start with the actual paths a guest can take. Open the home page, menu, ordering page, reservation flow, contact form, and any marketing signup. Note where a guest enters information and where the experience moves to another provider's page. Also ask your website provider about tools that collect information in the background; those may not be obvious from looking at the site.
For each path, record what information is requested, why the restaurant uses it, which provider operates the tool, and who can confirm the details. A guest ordering dinner may enter a name, phone number, address, and payment details, but the exact flow depends on the setup. Do not assume the restaurant receives or stores every field a guest enters.
- Website and forms: Ask the site provider what form submissions and site-use information are collected, where submissions go, and who can access them.
- Orders and payments: Ask the online ordering and payment providers what each handles, including whether guests leave your site to complete a step.
- Reservations and messages: Identify the booking tool and any service used to send confirmations or respond to inquiries.
- Marketing and measurement: Identify signup tools, advertising or analytics services, and any other tools your team has added.
Include tools the restaurant has stopped using until you know what happened to their information and links. Keep provider names, contact people, account owners, and written answers in an internal record. The public notice may need a different level of detail; ask counsel how to describe the setup accurately.
If an outside agency manages the site, ask who at the agency can make edits and who controls the account. Your domain ownership guide can help you check a related point: control of the domain is useful, but it does not by itself establish who maintains the notice.
Assign one owner and clear update triggers
Pick an owner by responsibility, not by who happens to know the website password. The best candidate hears about new providers, can reach the people who approve changes, and will remain involved after the site launches. At a small independent restaurant, that may be the owner. In a group with several locations, an operations or marketing lead may be better placed to coordinate.
Give that person a backup. Record who can edit the website, who approves the wording, and who answers guest privacy inquiries. Those can be different people. A web designer may publish the notice without being able to verify the restaurant's practices. A lawyer may review wording without knowing that the restaurant changed its reservation tool last week.
Make the handoff part of ordinary purchasing and website work. The notice owner should be alerted when the restaurant:
- Adds, removes, or replaces a website, ordering, reservation, payment, marketing, or analytics provider.
- Changes a form, introduces a new use for guest information, or changes where inquiries go.
- Changes the business contact details displayed to guests or the person responsible for answering them.
- Receives a provider notice about a material change to its service or information handling.
Set a recurring review date as a backstop, too. A calendar reminder alone is not enough: the owner needs a current provider list and a way to learn about changes between reviews. Ask managers and agency partners to route relevant purchase and site-change requests through the same person.
There is a trade-off. Giving an agency full responsibility for publishing may be convenient, but the restaurant still needs a way to tell the agency when its practices change. Keeping all edits in-house gives the team direct control, but only if someone has the access and time to make them. Choose the arrangement that produces an identifiable owner and a workable backup.
Use a change log to coordinate review
A shared document or spreadsheet is enough if the right people can find and update it. Keep the log internal. It should show the change, who must act, and whether the public notice and its links were checked. Keep the published notice's version or date alongside the log so the team can tell which wording is live.
The following is a hypothetical example. A neighborhood restaurant changes its reservation provider. The operations lead owns the notice, an agency edits the site, and counsel reviews proposed wording. The entries illustrate a handoff; they do not establish what any particular provider collects or what a notice must say.
| Event | Owner or contributor | Action | Record to keep |
|---|---|---|---|
| New booking tool selected | Operations lead | Ask the provider how the booking flow handles guest details and where guests are directed. | Provider name, answers, and date received |
| Notice review needed | Operations lead and counsel | Compare the current description and contact details with the new setup; agree on any wording changes. | Reviewer, decision, and approval date |
| Approved text ready | Agency editor | Publish the approved text and tell the operations lead where it appears. | Publication date and notice version |
| Site check | Operations lead or backup | Open the notice links and check the displayed contact details and booking path. | Check date, result, and any follow-up |
The important point in the table is the sequence. The agency does not guess at the new provider's practices, and counsel does not have to discover the change independently. If the operations lead cannot get an answer, the log should show an open question and its owner rather than treating the change as complete.
Do not put guest records or passwords in this log. Store supporting provider communications where the responsible team can retrieve them. When a person leaves, transfer the log, account access, upcoming review date, and unresolved items to the replacement.
Confirm wording, contacts, and links after a change
Before publishing, ask counsel to review how the notice describes the restaurant's information handling and how guests can reach the appropriate contact. Give counsel the inventory, provider answers, and the current notice. Ask which business contact should appear, who will monitor it, and how the team should route an inquiry. Counsel can advise on the wording and any applicable legal questions; the restaurant should confirm that the operational details are true.
Check the contact in practice without sending a real guest inquiry. For example, verify internally that the listed address is spelled correctly, belongs to an account the restaurant controls, and is monitored by an assigned person. Confirm the backup knows where to find incoming requests. Do not publish a personal address simply because it is convenient without considering who will manage it over time.
Once an approved update is live, open the notice from the website footer and any other place where it is linked. Check on a phone and a desktop-sized screen. If the order or reservation flow sends guests to another page, follow the links without placing an order, making a reservation, sending a message, or entering payment information. Check that the intended notice can be reached and that old provider links do not lead guests to the wrong place.
A link check confirms what a visitor can see at that moment. It does not verify every provider's handling of information or replace legal review. If a link fails or the wrong version appears, log the issue, assign it to the site editor, and check again after the fix. The same handoff should happen when a provider changes even if the website's appearance stays the same.
When choosing a new provider, ask who can edit the notice, how updates are published, and what happens to links when an ordering connection changes. The restaurant website builder comparison offers related buying considerations. Use the checklist above on your current setup, then ask Fleksa about its restaurant website and verified US availability if it is relevant to your evaluation.
Frequently asked questions
Should the website provider own the privacy notice?
The provider can explain its service and may publish edits, but assign someone at the restaurant to coordinate the notice. That person can gather information from every provider and arrange review.
When should a restaurant review its notice?
Review it when a relevant provider, information use, or guest contact changes, and set a recurring review as a backstop. Record the trigger, decision, and any publication or link check.
Is checking the privacy link enough?
No. A working link helps guests find the notice, but the content and contact details also need to reflect the restaurant's setup. Ask counsel to advise on wording and relevant legal questions.
