SMS and Communications Notice

This is a proposed notice for future U.S. Dohos communications Programs. It is not current, approved, registered, or effective, and it does not show that any phone number, sender, Restaurant, carrier campaign, or marketing Program is active. It is not consent to receive a call, text, or email. The future Dohos legal entity, contacts, Restaurants, numbers, brands, Providers, campaign registrations, message purposes, frequencies, jurisdictions, consent records, and support operations remain unverified. This draft must not be published or used in a call-to-action until every activation condition is satisfied.

01Purpose and scope

This SMS and Communications Notice explains how an activated Dohos-powered Program may send or facilitate:

• order verification and confirmation messages
• Restaurant acceptance, preparation, pickup, delivery, cancellation, refund, or support updates
• account authentication and security alerts
• Restaurant User operational notices
• service, legal, privacy, or incident notices
• separately approved promotional messages

The activated notice must identify the exact Program, sender, Restaurant or Dohos brand, number or sender type, purpose, expected frequency, consent mechanism, STOP/HELP behavior, support contact, privacy notice, terms, and geographic scope.

A general policy page cannot replace the disclosures presented where a person provides a number or agrees to a particular Program.

02Who may send a message

The sender depends on the Program:

• a Restaurant may send or direct transaction messages about its own Restaurant Transaction and customer relationship
• Dohos may send messages for its own Account administration, security, support, billing, legal, privacy, or service purposes
• Dohos may provide technology that routes a Restaurant's approved Program through an authorized Communications Provider
• a Provider or carrier may transmit the message but is not automatically the party requesting consent or responsible for the message content

The activated message and call-to-action must identify the responsible brand and must not make Dohos appear to be the Restaurant or make a Restaurant appear to be Dohos.

Consent, opt-out, and suppression records must remain associated with the correct sender, brand, purpose, channel, number, and Program. They must not be expanded to an affiliate or unrelated Restaurant without a separate lawful basis.

03Target Program types

This table is a target model, not a statement that a Program is operating. A message's actual content and purpose control; calling a promotional message "transactional" does not make it so.

04Transaction messages

An activated transaction Program may send messages reasonably necessary to complete or report a requested or existing interaction, such as:

• a one-time verification code
• receipt of an Order Request
• Restaurant acceptance or rejection
• correction or clarification needed
• preparation, readiness, pickup, or delivery status
• an approved substitution request
• cancellation or refund status
• payment, receipt, fraud, or security information
• a response to support initiated by the recipient

Transaction messages must stay limited to the transaction or service event. Advertising, coupons, loyalty enrollment, cross-selling, requests for promotional consent, or unrelated offers can change the classification.

The sender must not:

• state that the Restaurant accepted an order without the approved acceptance evidence
• state that an item is ready, delivered, cancelled, or refunded without the relevant status evidence
• disclose sensitive order information when the number's recipient is uncertain
• include full payment credentials, authentication secrets, or unnecessary Personal Data
• use urgency or security language deceptively
• keep sending after the transaction purpose ends except for required records or a separately approved purpose

05Marketing messages

Marketing Programs are disabled by default in the target launch model.

If a marketing Program is later proposed, its call-to-action must clearly and conspicuously disclose, as applicable:

• the exact seller or brand seeking consent
• the categories and purpose of messages
• whether automated technology or an artificial/prerecorded voice is used
• recurring nature and expected frequency
• that message and data rates may apply
• how to stop and get help
• links to the applicable privacy notice and terms
• that consent is not a condition of purchasing Restaurant Products or Dohos services, where required
• any state-, carrier-, Provider-, or program-specific disclosure

Consent must be obtained through an affirmative action tied to the exact disclosure and must be stored with the text presented, version, date/time, person/number, source, sender/brand, channel, purpose, technology, and proof of the action.

The following do not by themselves authorize marketing:

• placing or receiving an order
• contacting support
• providing a number for fulfillment
• having an Account or prior business relationship
• visiting a website
• remaining on a call
• silence, a prechecked box, bundled acceptance, or failure to opt out
• consent for a different Restaurant, brand, purpose, Program, or channel
• possession of a purchased, scraped, appended, rented, or shared list

06How enrollment should work

The activated Program may permit enrollment through an approved web form, keyword, Restaurant interaction, written agreement, Account control, or other documented method.

Before the affirmative action, the person must be able to review the material disclosure in an accessible and understandable format. Dohos must preserve:

• the exact call-to-action and surrounding page or script
• the number and person or authority context
• the Restaurant, Dohos, or other identified sender
• Program, purpose, content category, and channel
• date, time, source, IP/session or other proportionate evidence
• disclosure and policy versions
• affirmative action and double opt-in where required or selected
• confirmation or welcome message
• later revocation, suppression, dispute, reassignment, or correction events

Enrollment evidence is separate from acceptance of the Website and Diner Terms, payment authorization, Restaurant acceptance, recording consent, privacy choices, and email consent.

07Message frequency

Transaction message frequency depends on the requested Restaurant Transaction or service event. The activated Program should state the expected pattern without promising an exact count that the workflow cannot honor.

Any recurring marketing or Restaurant User Program must disclose a reasonable frequency description before enrollment and in the confirmation message. A material increase in frequency, purpose, sender, or content category requires review, notice, and renewed consent where required.

Dohos and the Restaurant must apply frequency limits, quiet hours, duplicate suppression, retry limits, and complaint controls appropriate to the Program and jurisdiction.

08Message and data rates; delivery

Message and data rates may apply according to the recipient's carrier and plan. Dohos and the Restaurant do not impose the recipient's carrier charges.

Delivery is not guaranteed. Carriers and Providers may delay, filter, block, throttle, reroute, or reject messages. Devices may be unavailable, numbers may be reassigned, and network conditions may fail.

The sender must not state that a message was delivered, read, or acted upon without the required evidence. A failed message does not automatically cancel or change an Accepted Order, payment, refund, privacy request, or other legal obligation. The approved fallback must determine the next step.

09Stopping messages

The activated SMS Program must support the opt-out keywords and reasonable methods required by current law, Provider rules, and the Program design. It should clearly tell recipients how to stop.

When a recipient sends a recognized stop request, the system should:

• promptly classify the sender, brand, Program, channel, and purpose affected
• suppress messages within the required time
• send no more than the legally permitted confirmation
• propagate the suppression to every relevant system and Provider
• preserve evidence of the request and action
• avoid requiring unnecessary information or repeated requests

A recipient may revoke consent through another reasonable method recognized by applicable law, not only an exact keyword. Misspellings, natural language, voice requests, support requests, and accessibility needs must be handled through the approved interpretation and escalation process.

An opt-out from marketing does not necessarily stop a legally permitted one-time security, transaction, or legally required notice, but the sender may not mislabel promotional content or collapse Programs to evade the opt-out. The confirmation must not market.

If the recipient wants to stop all contact from a Restaurant, Dohos, or Program, the request must be routed to the party that controls the relevant communication and applied as broadly as the person lawfully requests.

10Getting help

The activated SMS Program must support the required help keyword and provide a monitored support route. A help response should identify:

• the sender or responsible brand
• the Program purpose
• how to stop
• a support contact or accessible route
• the privacy notice and terms
• emergency limitations where relevant

11Number ownership and reassignment

By providing a number, a person represents only that they have authority to use it for the disclosed purpose. The number alone does not prove identity, age, payment authority, Restaurant affiliation, or consent to another Program.

Tell the sender if:

• the number is incorrect
• it is shared
• it has been reassigned
• the intended recipient cannot safely receive the content
• authority to use it has ended

Dohos and the Restaurant must use approved reassigned-number, suppression, inactivity, complaint, bounce, and verification controls appropriate to the Program. They must not rely indefinitely on old consent when evidence indicates the number changed hands.

12Privacy and message content

The activated Privacy Notice explains Dohos's processing. A Restaurant may separately control communication data for its customer relationship.

Communications may involve:

• number, email address, and contact identity
• sender, Restaurant, Program, purpose, and consent/suppression evidence
• message content and transactional data
• delivery, failure, carrier, Provider, link, and interaction events
• device, session, fraud, security, and complaint signals
• support, privacy, accessibility, dispute, and incident records

Dohos must minimize message content and previews. Messages should not include full payment credentials, authentication secrets, detailed allergy/health information, or other sensitive data unless necessary, lawful, secured, and appropriate for the recipient risk.

Communications data must not be sold, shared for cross-context behavioral advertising, used for unrelated profiling, or used to train a general model under the target baseline. A separate lawful program and notice would be required for a materially different practice.

13Security and phishing

Dohos and Restaurants should not ask a recipient through an ordinary message to send:

• a full card number or security code
• a bank or wallet credential
• an Account password
• an authentication or recovery code except through the clearly identified secure step
• a government identifier
• unnecessary medical or other sensitive information

Do not trust a message solely because it displays a Restaurant or Dohos name. Use the approved Restaurant or Dohos contact to verify a suspicious request.

The activated notice will provide a security-reporting route. Do not click an unexpected link or respond with sensitive information when sender identity or purpose is unclear. See how to report a vulnerability for the route once one exists.

14AI and automated communications

An activated Program may use automated systems to generate, route, classify, translate, or respond to limited transaction or support messages. The content must remain grounded in approved Restaurant or Dohos information and subject to the AI and Voice Transparency Notice.

An automated system must not:

• falsely appear to be a human
• invent an order, status, price, refund, consent, or Restaurant fact
• continue marketing after revocation
• infer consent, identity, age, or authority from conversational content
• generate deceptive urgency or impersonation
• expose one Restaurant's or person's data to another

Automated classification of opt-outs, complaints, and safety issues must have a practical correction and human escalation route.

15Calls and email

The same core principles apply to activated calls and email: clear sender and purpose, lawful basis, accurate content, appropriate frequency/timing, working opt-out, privacy minimization, security, and evidence.

An activated call Program must separately address:

• live, prerecorded, or artificial/AI-generated voice
• outbound versus inbound calls
• caller ID and number registration
• do-not-call and internal suppression
• calling times and attempt limits
• recording/interception notice or consent, if any
• jurisdiction- and audience-specific requirements

An activated commercial email Program must accurately identify the sender and subject, provide required physical-address and opt-out information, and honor opt-outs within the required period.

16International and location limits

This proposed notice is designed for a future U.S. service only. A U.S. phone number does not prove that a recipient is in the United States, and an international number does not by itself establish the applicable law.

Dohos must not activate cross-border calls or messages until it verifies the recipient/location rules, Provider coverage, consent, sender registration, data transfers, emergency constraints, taxes/fees, and support operations.

17Accessibility and language

Enrollment, disclosure, confirmation, STOP, HELP, support, privacy, and complaint routes must be usable through the approved accessible methods. A person should not lose a right because they cannot use an exact keyword, visual CAPTCHA, small-screen link, or unsupported language.

The activated Program must identify supported languages and provide a practical alternative where required. This draft makes no universal-access, language-coverage, certification, WCAG, or ADA conformance claim.

18Complaints and disputes

The activated notice will explain how to report:

• a message sent without consent or authority
• failure to honor an opt-out
• wrong-number or reassignment contact
• misleading sender identity or message content
• excessive frequency or prohibited timing
• privacy, security, or accessibility concerns
• incorrect Restaurant Transaction status
• carrier or Provider delivery problems

A complaint must not be used to market, retaliate, or obstruct a lawful regulator, carrier, Provider, or court route. Dohos and the Restaurant must determine and disclose which party owns the response.

19Changes and Program termination

The sender may end or change a Program prospectively, subject to law, the applicable agreement, and required notice or renewed consent. A material change to sender, brand, purpose, content category, automation, frequency, number, Provider, data use, or geography requires a documented legal and operational review.

Ending a Program does not erase suppression records, consent disputes, complaints, legal holds, or duties involving earlier messages. Suppression data should be retained in minimized form for the period reasonably needed to honor the choice and legal obligations.

A later notice cannot retroactively authorize prior communications. Superseded versions, once any exist, will be preserved at the version archive.

Related documents

• Privacy Notice — Section 12's cross-reference here — the full description of what Dohos processes about a message and its content.
• Privacy Rights Request Notice — How to actually stop a marketing message or withdraw consent, referenced in Sections 5 and 9 here.
• AI and Voice Transparency Notice — The disclosure rules behind Section 14's AI-and-automated-communications boundary.
• Website and Diner Terms — Section 14 there summarizes the communications rule this notice covers in full.
• Vulnerability disclosure — The reporting route named in Section 13.
• Version archive — Where a superseded version of this notice will be preserved once one exists, per Section 19.