SMS Opt-In: How Consent Is Collected

This page documents the complete opt-in experience for Ginger Restaurant Notifications, the strictly transactional SMS program operated by YSK Technologies LLC ("Ginger"), a restaurant point-of-sale platform. The program sends order confirmations and order-ready alerts, reservation confirmations, reminders and cancellation notices, and waitlist notifications — each triggered by a transaction the customer themselves initiated. No marketing or promotional messages are ever sent on this program.

Phone numbers enter this program in exactly five ways, all documented below with the verbatim disclosure shown at each. Ginger never purchases, rents, imports, or shares phone numbers; the only numbers used are the ones customers themselves provide (or call from) in the flows below.

1. Phone orders through the restaurant's AI line (verbal opt-in)

Where customers find the number

Each restaurant publishes its own ordering number the way restaurants always have: on its public website, its printed menus and flyers, its storefront signage, and its Google Business Profile. The number the customer sees is the number Ginger's AI answers. A live, publicly verifiable example — Koto Japanese Steakhouse publishes (260) 482-4288 on its website:

Ginger's own hosted pages for each restaurant display the same number — for example the booking page below shows the restaurant's phone in its header and as "Prefer to call?". The customer is never given a special or separate number for SMS enrollment; they simply call the restaurant.

What happens on the call

1. The customer dials the restaurant's published number to place a takeout order. Ginger's automated system answers and takes the order.
2. After the order is complete, the system asks for the customer's name.
3. The system then asks for SMS consent, reading this script aloud, word for word:

“Would you like a text confirmation of your order sent to this number? It's one message per order. Message and data rates may apply. You can reply STOP anytime to opt out, or HELP for help. Should I send it — yes or no?”

4. A confirmation text is sent only if the customer answers “yes.” A customer who declines receives no message and is not asked again on that call.
5. The answer is recorded and stored with the order — timestamp, consent source, and the script that was read — as the durable record of consent.
6. Consent is not a condition of purchase; the order is placed either way. Messages go only to the number the customer is calling from.

A representative exchange from the end of an order call:

2. Online reservations (written disclosure at the phone field)

Customers booking a table online — via the restaurant's website or its Ginger-hosted booking page (for example app.gingerserve.com/reserve/sakura, reachable from the "Book a Table" button on the restaurant's site) follow this flow:

1. The customer opens the restaurant's website and taps "Book a Table", or opens the booking page directly.
2. They pick a party size, date, and time.
3. On the details step they enter their name and mobile number. Directly beneath the phone field, before the confirm button, this disclosure with linked Privacy Policy and SMS Terms is displayed:

4. Tapping "Confirm reservation" submits the booking with that consent; the consent event is stored with timestamp, the wording shown, IP, and user agent.

3. Online ordering checkout (written disclosure at the phone field)

Customers ordering pickup or delivery online (for example app.gingerserve.com/order/sakura, or the restaurant's own domain) follow this flow:

1. The customer builds a cart and proceeds to checkout.
2. The checkout form requires name and phone number for the order. Directly beneath the phone field, with linked Privacy Policy and SMS Terms:

3. Placing the order submits that consent, stored with timestamp, wording, IP, and user agent.

4. In-store self-service kiosk

Customers ordering at an in-store self-service kiosk follow this flow:

1. The customer builds their order on the kiosk touchscreen and taps Checkout.
2. The kiosk asks for their phone number for order contact. The entry screen displays, above the keypad (in English or Chinese):

3. Entering a number and continuing records the consent with the order.

5. Host-stand waitlist

A guest joining the waitlist in person follows this flow:

1. The guest asks the host for a table; the host offers to text them when it is ready.
2. If the guest agrees and gives their number, the host enters it on the waitlist form. Beside the phone field the form displays (in English and Chinese):

3. Providing a number is optional; guests who decline are simply called by name and receive no texts.

Disclosures given at opt-in

• What is sent: transactional notifications about the customer's own order, reservation, or waitlist entry.
• Message frequency: varies with the customer's own activity — e.g., one confirmation per order; a confirmation and an optional reminder per reservation; up to two messages per waitlist visit.
• Cost: message and data rates may apply.
• Opt-out and help: reply STOP to opt out, HELP for help.

The messages customers receive

All messages follow the registered formats below — one GSM-encoded segment, restaurant-branded, transactional only:

Every message names the restaurant and the Ginger brand. Three formats use a shortened suffix (STOP + rates) to stay within one message segment; HELP is disclosed at opt-in and always answered by the HELP auto-reply.

Links are short links on Ginger's own domain (app.gingerserve.com), which open that order's status page or that reservation's manage page (view and self-cancel). No third-party URL shorteners are used.

Opting out and getting help

Replying STOP to any message immediately unsubscribes the customer; no further messages are sent to that number. Replying HELP returns:

Support is also available at info@gingerserve.com.

Consent records

Every consent event is stored with its timestamp, the channel it was collected on, and the exact disclosure wording the customer was shown or read; web-collected consent additionally records the requesting IP address and browser user-agent. STOP is honored per program and recorded the same way.

Privacy and terms

Mobile numbers and SMS consent are never sold, rented, or shared. No mobile information will be shared with third parties or affiliates for marketing or promotional purposes. Full details:

• Privacy Policy — section 5, “Customer Contact & SMS Privacy”
• Terms of Service — section 6a, “SMS Messaging Terms”