Google-Compliant by Design.

Many restaurants get their Google Business Profile suspended — or face FTC penalties — because they offer customers discounts in exchange for reviews. We built Tableside so this is structurally impossible. Every customer who scans the QR gets the same experience and the same value, whether they leave a review or not.

This page explains exactly how, in plain language, so any restaurant owner or compliance lawyer can audit our model in five minutes.

Google's Maps User Generated Content Policy is unambiguous. The exact language from Google:

"Content that has been posted due to an incentive offered by a business — such as payment, discounts, free goods and/or services — is not allowed and will be removed."

Three things matter here:

• There is no dollar threshold. A 5% discount is a violation. A free coffee is a violation.
• Sentiment doesn't matter. Asking for an "honest" review while attaching any reward is still a violation.
• Google's January 2026 update added new bans: on-site review kiosks, asking customers to leave reviews while still on premises, and requesting customers mention staff names.

Penalties scale fast. Google can remove every review tied to a campaign, attach a public warning banner to the profile, suspend the listing, or kill it entirely. The FTC's 2024 reviews rule layered federal liability on top: civil penalties of up to $51,744 per violation for businesses that compensate reviews.

The customer journey we built:

1. Server hands the customer a branded vessel (wet wipe, mint, coaster) at the appropriate moment in service.
2. Customer scans the QR. They land on a custom branded page hosted by us.
3. They watch a 20-second message from the chef or owner. They can download the recipe of the month. These two things are unconditional — every scanner gets them.
4. At the bottom of the page, three optional next steps are presented as equal options: leave a Google review, follow on Instagram, join the regulars list (email/SMS opt-in for events and tasting menus).
5. None of these next steps are tied to each other. None of them gate access to the recipe or video. None of them produce a discount.

The recipe is content. The chef video is content. Content is not compensation. Google's policy bans "payment, discounts, free goods and/or services" given in exchange for a review — a freely- distributed recipe is none of those things, and crucially, it's available regardless of whether the customer reviews.

Some restaurants will ask: can we offer a discount on the next visit through this system? The answer is yes, but only if structured correctly:

• ALLOWED: Every scanner receives a "first-time guest" discount or a birthday-month coupon — same offer, same access, no review required.
• ALLOWED: Loyalty rewards based on visit frequency tracked through the email opt-in list — same as any restaurant loyalty program.
• NOT ALLOWED: A discount that releases only after the customer leaves a review, or that is presented as "leave a review and get X."

Our admin dashboard does not include a "verify review submission to release reward" feature. This is intentional. Building that feature would create the legal exposure we explicitly avoid.

Google's 2026 policy update added a prohibition on pressuring customers to leave reviews while still in the restaurant. Tableside handles this two ways:

• The Google review CTA on the scan page is one of three optional next steps, not the headline. The headline is the chef video and the recipe.
• For restaurants that want to drive review volume, we offer a delayed-send email or SMS option: 24 hours after the scan, the customer receives a "hope you enjoyed your meal — here's that recipe, and if you have a moment we'd love a quick Google review" message. The customer is no longer on the premises.

The FTC's Trade Regulation Rule on Consumer Reviews and Testimonials, effective October 2024, prohibits "providing compensation or other incentives conditioned on the writing of consumer reviews expressing a particular sentiment, either positive or negative."

Tableside is compliant for the same reason it's Google-compliant: no compensation is conditioned on a review. The recipe and video are given to every scanner. Email/SMS opt-in is for the regulars list, not for a review. The Google review button is a button — it's not a transaction.

Even with a compliant tool, restaurants should follow these practices to stay safely inside the rules:

• Train servers to hand the vessel to every table, not just tables they think went well. Selective distribution is a form of review gating.
• Never script servers to say "please leave us a 5-star review" or anything that requests positive sentiment. The right script is "if you'd like the recipe of the month, scan here — there's also a quick message from the chef."
• Never offer the discount-for-review combo in any other channel — email, social, table tents, business cards. Compliance in one place doesn't help if the same restaurant is violating the policy elsewhere.
• Respond to every review (positive and negative). This is allowed and is one of Google's recommended practices.