What Seattle and Chicago Restaurant Groups Should Own Before Buying or Building AI
Seattle and Chicago restaurant groups should own their rules, accounts and exports, and test how guest health notes move under Washington and Illinois law.
In this guide
A Seattle or Chicago restaurant group should control its operating rules, business accounts, usable data exports and the ability to change providers. That does not mean building a custom customer database or owning the source code of every tool. Buy an existing capability when it meets the requirement; commission custom work only for a valuable gap you can maintain.
The distinction matters because owning data, accessing data and operating software are different rights. SevenRooms says restaurants retain ownership of first-party guest data and distinguishes operational access to marketplace reservations from opted-in marketing use. A blanket claim that a vendor can never provide a connected guest record would be wrong.
Washington and Illinois diverge on one kind of guest record: allergy and medical dietary notes. For a Seattle group, Washington's My Health My Data Act can treat such a note as consumer health data, with consent and processor-contract rules. In Chicago, Illinois treats a guest's name combined with medical information as personal information that must be kept under reasonable security, including by any provider it is disclosed to under contract. Either way, the export test and the vendor contract below should cover those notes before you buy or build.
Use the supplier scorecard to test ownership and handover promises.
Write down what “own” must let you do
Start with a practical exit question: if this provider stopped serving the group, could another person recover the records, understand the rules and resume the essential work? A contract saying “your data” is useful, but it does not answer which fields are exported, how histories link or whether the export includes the permissions needed to contact a guest.
Proposed ownership review: evaluate each capability against the control you need, the available product and the responsibility you are willing to take on.
| Capability | Control to retain | When custom work deserves consideration |
|---|---|---|
| POS, payments and reservations | Company-held administrator accounts, configuration records and supported exports | A specific unsupported handoff, rather than replacement of the transaction platform |
| Guest profiles and marketing | Identifiers, provenance, consent status and permitted exports | A documented cross-system need that existing CRM features cannot satisfy |
| Guest allergy and health notes | Where the notes live, who can read them, the consent behind them and the contract terms Washington or Illinois requires of the provider | Only when no product can restrict access to the notes and keep them out of marketing |
| AI call or message handling | Approved content, routing policies, logs and escalation destinations | Important call outcomes require a supported integration unavailable in the product |
| Group reporting | Metric definitions, source mappings and reproducible calculations | Recurring decisions require data across systems with incompatible reporting |
Try a complete export before deciding to build
Ask for a representative export with test or appropriately authorized records. Reconstruct one guest's booking, seated status and associated check without relying on the vendor's dashboard. Include a merged profile, a cancelled booking, a changed phone number, a marketing opt-out and a profile with an allergy note. Verify the relationships rather than counting rows.
Then inspect what is absent. A reservation holder is not necessarily every diner at the table. A shared phone number is not proof that two profiles represent the same person. A matching name alone is too weak a basis for merging histories. Keep uncertain matches separate and give authorized staff a correction path.
Only collect information needed for a defined service or measurement purpose. Copying sensitive guest notes into a new database creates another place to maintain access and deletion controls. Ownership should make the business more capable of honoring those controls, not create a reason to replicate everything.
Marketing permissions have to survive the move. Under the FTC's CAN-SPAM compliance guide, a business must honor an email opt-out within 10 business days, cannot sell or transfer the addresses of people who opted out, and cannot contract away its responsibility by hiring another company to send its email. An export that drops opt-out status turns a provider change into a compliance risk wherever the group operates.
Guest health notes in Washington and Chicago
Both states' laws can reach a guest's allergy or medical note, but through different rules, so the export and the provider contract need different checks in each state.
What Washington law means for a Seattle group
Under the My Health My Data Act, consumer health data is personal information linked or reasonably linkable to a consumer that identifies past, present or future physical or mental health status, including individual health conditions, so an allergy or medical dietary note saved to a guest profile can fall within it. A business may collect such data only with consent for a specified purpose or to the extent necessary to provide the product or service the guest requested, and may share it only with a separate consent or to that same extent (RCW 19.373.030). Disclosure to a processor that serves the purpose the data was collected for is not sharing, but a processor may handle the data only under a binding contract (RCW 19.373.060). The Washington Attorney General says the Act has applied since March 31, 2024 (June 30, 2024 for small businesses), requires a separate consumer health data privacy policy linked from the homepage, and is enforced by the Attorney General and through private action. Because the Act is a state law, a Seattle group's locations in Bellevue or elsewhere in the state follow the same rule. It protects Washington residents and anyone whose health data is collected in Washington, and the Attorney General says out-of-state processors working for a covered business must comply too.
In Chicago
Illinois uses a different test. The Personal Information Protection Act counts a person's name combined with medical information, meaning information about medical history or a mental or physical condition, as personal information, so the same allergy note tied to a guest's name can qualify. A business holding such records must maintain reasonable security measures, and a contract that discloses them must require the recipient to do the same.
The provider contract, side by side
Washington's breach law also counts a name combined with information about a medical history or physical condition as personal information (RCW 19.255.005), so a provider breach reaches these notes in both states.
| Check | Seattle (Washington law) | Chicago (Illinois) |
|---|---|---|
| Before notes move to a new system | Consent, or necessity for the service the guest requested, covers the use, and the provider acts as a processor | The new system keeps reasonable security measures for the records |
| Contract term | A binding processor contract that sets processing instructions and limits | A provision requiring the provider to maintain reasonable security measures |
| If the provider is breached | It must notify you immediately; you notify affected Washington residents within 30 days of discovery when notice is required, and the Attorney General if more than 500 (RCW 19.255.010) | It must notify you immediately; you notify affected Illinois residents in the most expedient time possible, and the Attorney General if more than 500 (815 ILCS 530/10) |
Before exporting guest profiles or connecting a new CRM, identify which notes are in scope, keep them out of marketing segments unless consent covers that use, and confirm the new provider will act as a processor under contract. For Chicago locations, confirm the contract includes the reasonable-security provision and restates the provider's duty to report a breach immediately before the export runs. Whether a particular note qualifies is a question for your counsel.
A report may solve the problem without a new platform
Suppose the buyer's question is which reservation channels produce seated covers. A scheduled export and a documented reconciliation may answer it. There is no automatic need for real-time synchronization, a central customer platform or a language model.
If the question is whether a campaign caused additional visits, a joined dataset still does not prove the answer. Booking-to-check attribution describes observed paths. Incrementality needs a comparison design. Avoid commissioning an expensive data layer under a promise that it will reveal exactly which marketing dollars caused each dinner.
For a first custom project, keep the result narrow: a read-only group report, one reviewed profile merge queue or one draft event-intake handoff. Define the records it reads and writes. Require duplicate protection and a way to reconcile failed updates. Let the existing booking or payment system remain authoritative for its transactions.
Include the next maintainer in the buying decision
A custom integration needs monitoring, credentials, backups, documentation and updates when either connected system changes. Assign a budget owner and an operational owner. Obtain the build instructions, dependency list, source repository rights and support arrangements before accepting delivery.
Evaluate the exit from a subscription with the same seriousness. Ask about export costs, notice periods, access after cancellation, record retention and transition support. A product can offer stronger practical control than a custom system whose only knowledgeable developer has left.
The acceptance test is a handover: a second authorized person should be able to explain the workflow, locate a failed record, correct it and restore normal service using the documentation. Review these requirements alongside the group's restaurant operating priorities. Keep control of the decisions and evidence that matter; choose the simplest dependable way to implement them.
Quick answers
Should a Washington or Chicago restaurant group build or buy its AI tools?
Buy an existing capability when it meets the requirement, and commission custom work only for a valuable gap you can maintain. Either way, keep control of operating rules, business accounts, usable exports and the ability to change providers.
Who owns guest data in a restaurant reservation platform?
It depends on the contract and what the export actually contains. SevenRooms, for example, says restaurants retain ownership of first-party guest data; test a complete export before relying on any such statement.
Why must marketing opt-outs move with guest data?
CAN-SPAM requires honoring email opt-outs within 10 business days and bars selling or transferring opted-out addresses, and the business stays responsible even when another company sends its email.
Do guest allergy notes need special handling in Washington?
They can, in Seattle as anywhere else in the state. Washington's My Health My Data Act covers personal information that identifies a health condition, so check which profile notes are in scope, keep them out of marketing unless consent covers that use, and confirm a new provider acts as a processor under contract.
What does Illinois require when a Chicago restaurant shares guest health notes with a vendor?
Illinois can count a guest's name combined with an allergy or other medical note as personal information. If it does, the business must keep reasonable security measures and its contract must require the vendor to do the same.
Sources
- SevenRooms says restaurants retain ownership of first-party guest data and distinguishes operational access to market… · sevenrooms.com
- the FTC's CAN-SPAM compliance guide · ftc.gov
- My Health My Data Act · app.leg.wa.gov
- RCW 19.373.030 · app.leg.wa.gov
- RCW 19.373.060 · app.leg.wa.gov
- Washington Attorney General · atg.wa.gov
- Personal Information Protection Act · ilga.gov
- a contract that discloses them · ilga.gov
- RCW 19.255.005 · app.leg.wa.gov
- RCW 19.255.010 · app.leg.wa.gov
- 815 ILCS 530/10 · ilga.gov
Revision note · October 6, 2026: Headline simplified; the article body is unchanged.
How we research and review these guides
Put the ideas to work in your business.
We provide AI consulting and implementation for restaurant and hospitality groups. Bring us the process that is slowing your team down and the systems involved. We can assess the problem with you and discuss a practical implementation.
Discuss your project →Still exploring? Explore the Workflow Opportunity Workbook →