This is a proposed notice and intake framework for future U.S. privacy requests involving Dohos. It is not current, approved, effective, or evidence that a rights portal, telephone line, email, identity-verification service, appeal process, universal opt-out signal, or Restaurant-routing operation is live. The future Dohos legal entity, contacts, Restaurants, Providers, data inventory, jurisdictions, request history, response timing, and support operations remain unverified. This draft must not be published until every described route works and every activation condition is satisfied.
01Purpose
This notice explains how a person may ask about or exercise an applicable privacy right involving Personal Data processed through an activated Dohos service.
Privacy rights vary by jurisdiction, relationship, data, purpose, and applicable exception. Dohos will evaluate a request under the law that applies to the verified facts. This notice does not create a right that law does not provide or narrow a right that law does provide.
The activated Privacy Notice describes data categories, purposes, disclosures, retention criteria, choices, and roles. This notice focuses on the request process.
02Determine the responsible party
Responsibility depends on why the data is processed.
Restaurant-directed Diner data. For information processed to receive, route, accept, fulfill, support, or evidence an order for a specific Restaurant:
- the Restaurant ordinarily decides why it offers the channel and how it uses information for its customer relationship
- Dohos seeks to process the information for that Restaurant under the activated Restaurant agreement and documented instructions
A request concerning the Restaurant's sale, fulfillment, loyalty, marketing, premises, personnel, delivery, or independent customer records may need to be handled by the Restaurant. Dohos should identify and route the request, assist the Restaurant as required, and avoid forcing the person to start over when enough information already exists.
Dohos's own purposes. Dohos may respond directly for Personal Data it controls for narrow purposes such as:
- Restaurant Account administration and authentication
- Dohos billing and customer relationship management
- security, fraud prevention, service integrity, and incidents
- Dohos support, legal, privacy, and accessibility requests
- Provider and business administration
- legal compliance and dispute records
The activated response must explain the applicable role and any routing without relying on a label that conflicts with actual conduct.
03Who may submit a request
A request may be submitted by:
- the individual to whom the Personal Data relates
- a parent or legal guardian where applicable
- an authorized agent where law permits
- a legally authorized representative
- a person making a household request where applicable law recognizes it
An authorized Restaurant representative asking about Restaurant-controlled data should use the contract/privacy request route identified in the activated Restaurant agreement.
A person does not need a Dohos Account to submit a request when the law or the service permits interaction without an Account.
04Rights that may apply
Depending on applicable law and verified facts, a person may have a right to:
- confirm whether Personal Data is processed
- know or access Personal Data and related categories, purposes, sources, and recipients
- receive a portable copy in the format required by law
- correct inaccurate Personal Data
- delete Personal Data
- opt out of sale of Personal Data
- opt out of sharing for cross-context behavioral advertising
- opt out of processing for targeted advertising
- opt out of certain profiling or decisions producing legal or similarly significant effects
- limit certain uses or disclosures of sensitive Personal Data
- withdraw consent for a consent-based practice
- obtain information about or challenge certain automated decisions
- appeal a denial or partial denial
- receive equal service and not be unlawfully discriminated against for exercising a right
- use another privacy choice established by applicable law
[CORRECTED] Dohos's target launch baseline does not sell Personal Data, share it for cross-context behavioral advertising, use it for targeted advertising, create Voiceprints, infer emotion or sensitive traits, retain raw call audio beyond a Restaurant's separately enabled recording capability, or make high-impact decisions. A role-gated text transcript of each completed call is retained as part of standard service delivery, not as one of those excluded practices — see how call data is retained for the retention detail. These are target restrictions, not verified current-state claims. If actual or historical facts differ, Dohos must respond truthfully and remediate rather than rely on the target statement.
05Other requests and choices
Some requests use a separate operational route but should still be coordinated with privacy intake:
- stop marketing calls, texts, or emails
- stop or correct transaction communications
- report a wrong or reassigned number
- change cookie or tracking preferences
- submit a Global Privacy Control or other recognized universal opt-out signal
- withdraw recording, transcript, biometric, or other consent where a lawful program exists
- close an Account
- correct a Restaurant order or contact record
- report an unauthorized payment or security incident
- request an accessible format or communication method
- report information submitted about a child
Submitting one type of request must not automatically withdraw an unrelated necessary service or legal notice. Conversely, Dohos must not split closely related purposes to evade a person's intended choice.
06How to submit
The activated notice will provide at least the request methods required for the applicable jurisdiction and relationship, which may include:
- an accessible web form or privacy portal
- a monitored email address
- a toll-free or other telephone route
- an Account control
- a postal route
- a browser-based universal opt-out signal
- a Restaurant-specific route
Dohos must not require an Account, notarization, government identifier, payment, or excessive Personal Data unless the verified request and law justify it.
07Information useful for locating a request
To help find the relevant records, the activated form may ask for limited information such as:
- name or preferred name
- contact method used with the service
- Restaurant and location
- approximate interaction, order, Account, or support date
- available transaction, request, message, call, or Account identifier
- the right or outcome requested
- state of residence where needed to determine applicable law
- authorized-agent or representative information where applicable
Provide only what is reasonably necessary. Do not send a full card number, security code, PIN, bank credential, Account password, authentication code, government identifier, raw recording, or unnecessary health/allergy detail through an ordinary privacy form.
Dohos should allow a person to describe a request in their own words and should not deny it merely because the wrong label was selected.
08Acknowledgment and routing
After receipt, Dohos should:
- create a request record and preserve the submitted scope
- acknowledge receipt within the period required by law or the approved service target
- identify the person, relationship, jurisdiction, Restaurant, purposes, roles, and systems involved
- separate multiple rights or parties without losing the original intent
- route Restaurant-controlled and Dohos-controlled parts to accountable owners
- determine verification appropriate to each requested action
- place appropriate preservation, suppression, or processing holds
- communicate next steps and expected timing accurately
A misdirected request should be routed rather than silently closed. Dohos should tell the person which party is handling each material part when law and security permit.
09Identity verification
Dohos must reasonably verify that the requester is the person whose data is involved or is otherwise authorized, using a method proportionate to the risk.
Verification may consider:
- the type and sensitivity of data
- whether the request seeks access, deletion, correction, portability, opt-out, consent withdrawal, or another action
- the risk of unauthorized disclosure or deletion
- information already associated with the interaction
- an Account session or approved authentication method
- Restaurant or transaction evidence
- reliable authorized-agent documents
Dohos should not disclose Personal Data merely because a requester knows a phone number, email, order amount, caller ID, or partial identifier. It also should not demand more data than necessary or create a new permanent identity record solely to verify a low-risk request.
New verification data must be used only for verification, protected, retained for the approved period, and deleted when no longer needed unless law requires otherwise.
10Authorized agents
Where applicable law allows an authorized agent, the activated process may request:
- evidence of the agent's identity
- signed permission or other legally sufficient authority
- enough information to identify the individual and request
- direct confirmation from the individual where permitted
- special authority required for highly sensitive access or deletion
Dohos must accept legally valid powers of attorney or equivalent authority as required and must provide an accessible process.
Agent verification must not be used to discourage a lawful request. Dohos should distinguish a commercial opt-out agent, browser signal, legal representative, household member, Restaurant employee, and informal helper.
11Requests involving children
The target service is not directed to children. If Dohos receives a request involving a child, it should:
- pause unnecessary processing and route it for prompt review
- verify the parent, guardian, child, or other authorized person's status as required
- avoid collecting additional sensitive information unnecessarily
- coordinate with the relevant Restaurant
- assess deletion, consent, notice, and incident duties
- preserve legal and safety evidence only as required
Age must not be inferred solely from voice, device, payment method, order, or writing style.
12Searching for Personal Data
The activated process must search the systems, Providers, and Restaurant-controlled paths reasonably within the applicable scope, including as relevant:
- Account, authentication, and access records
- Restaurant and user administration records
- structured Order Requests and transaction evidence
- communications and consent/suppression records
- payment-related noncredential evidence and Provider identifiers
- support, privacy, accessibility, security, complaint, and dispute cases
- logs, telemetry, exports, analytics, and backups according to the approved scope
- [CORRECTED] AI/voice structured events, the retained completed-call transcript store, and any separately approved audio recording store
- Provider systems and subprocessors
- historical, archived, or deactivated systems subject to retention and feasibility rules
Dohos must not assume that deleting a primary database row deletes Provider, log, backup, analytics, or Restaurant copies.
The search should preserve tenant separation and must not disclose another person's or Restaurant's data.
13Access and portability
An access response should provide the information and categories required by applicable law in an understandable and secure format.
Before disclosure, Dohos must:
- verify scope and identity
- remove another person's Personal Data unless law permits disclosure
- protect trade secrets, security controls, fraud methods, privilege, and legally restricted information
- explain material redactions or exclusions where required
- use a secure delivery method
- preserve what was disclosed, when, to whom, and under which version/rule
Portability does not require Dohos to create an unsafe export, reveal credentials, or disclose data it does not lawfully control, but technical inconvenience alone is not a reason to deny a right.
14Correction
Dohos should correct inaccurate Personal Data within the applicable scope and propagate the correction to relevant Providers or recipients where required.
For Restaurant-controlled menu, transaction, fulfillment, or customer data, Dohos may need the Restaurant to verify the authoritative fact. The system should preserve:
- the original value and source
- requested correction
- evidence and responsible decision-maker
- corrected value and effective time
- downstream propagation
- any dispute or annotation where the fact cannot be resolved
A correction right does not permit changing an accurate transaction record to create a false order, payment, consent, or legal event.
15Deletion
An approved deletion workflow should identify and address:
- active records
- derived or duplicated records
- Providers and downstream recipients
- caches, indexes, exports, and analytics
- backups and restoration protections
- Restaurant-controlled copies
- legal holds, disputes, fraud/security, accounting/tax, payment, and other required retention
- suppression data needed to honor an opt-out
If an exception applies, Dohos should delete the data not covered by the exception and explain the retained category and reason where required. Retained data must be restricted to the exception purpose and deleted when it ends.
Account closure, Restaurant deletion, payment reversal, order cancellation, consent withdrawal, and privacy deletion are distinct processes and must be coordinated rather than assumed equivalent.
16Opt-out and consent withdrawal
An opt-out or withdrawal must be scoped to the covered processing and propagated to every relevant client, server, Provider, Restaurant, and downstream recipient as required.
The activated service should:
- recognize the request through approved accessible methods
- stop future covered processing within required timing
- preserve minimized proof needed to honor the choice
- avoid asking the person to repeat data already held
- not require acceptance of another purpose
- confirm the outcome
- explain any legally permitted transaction/security effect
A later interaction must not silently reset a prior choice. A person may make a new affirmative choice, but the system must preserve scope and version evidence.
17Decisions, denials, and partial responses
Dohos may deny or limit a request only when a verified legal exception, inability to verify, conflict with another person's rights, security risk, privilege, or other lawful basis applies.
The response should explain, as required:
- what was completed
- what was denied or limited
- the reason without exposing protected details
- the responsible party
- any fee and legal basis
- how to correct verification or scope
- how to appeal
- how to contact the applicable regulator where required
Dohos must not use a generic "security" or "Restaurant data" label to deny a request without analyzing the actual data and duty.
18Timing, extensions, and fees
Response periods, extension rights, acknowledgment duties, request-frequency limits, and fees vary by applicable law and request type.
The activated system must calculate deadlines from the verified receipt time, jurisdiction, right, role, verification events, extension rule, and applicable law version. It must provide timely extension notice and reasons where permitted.
Dohos should not charge a fee unless applicable law permits it and the approved standard is met. A complex internal system or Provider arrangement is not by itself a basis to charge or deny.
19Appeals
Where an appeal right applies, the activated response must explain how and when to appeal. The appeal should be reviewed by a qualified person with appropriate independence from the initial decision.
The appeal record should include:
- original request and response
- asserted error or additional information
- applicable law and role
- systems/Providers/Restaurant involved
- reviewer and conflicts
- decision and reasons
- corrective actions and timing
- regulator contact information where required
An appeal route must be accessible and must not require the person to waive another remedy.
20No unlawful discrimination or retaliation
Dohos and the Restaurant must not unlawfully deny service, charge a different price, provide a different quality, retaliate, or otherwise discriminate because a person exercised a privacy right.
This does not prevent a lawful difference reasonably related to the data's value or a service that cannot operate without data genuinely necessary for the requested function, where applicable law permits and the consequence is clearly explained.
A privacy request must not trigger unrelated marketing, profiling, adverse scoring, employee discipline, or suppression of an honest complaint.
21Security and confidentiality
Privacy request records can contain sensitive identity, contact, order, payment, security, disability, or legal information. Dohos must:
- limit access by role and purpose
- secure transmission and storage
- log material access and action
- avoid placing full credentials or unnecessary sensitive data in ordinary tickets
- preserve privilege and legal holds
- prevent cross-Restaurant disclosure
- monitor fraud and abuse proportionately
- apply the approved retention/deletion schedule
The request process is not consent to model training, advertising, unrelated analytics, or another secondary use.
22Accessibility and language
Request, verification, delivery, appeal, and support routes must be available through approved accessible methods. Dohos should provide a reasonable alternative format or method and should not require a visual CAPTCHA, voice call, exact keyword, or online Account when that would unlawfully block the person.
The activated notice must identify supported languages and interpretation/translation support without claiming universal coverage. A language or disability accommodation request should be collected and retained only as necessary to provide it.
23Contact and complaints
The activated notice will provide the Dohos legal entity, privacy contact, appeal route, and applicable regulator information. It will explain how to report an unhonored opt-out, misdirected request, security concern, inaccessible process, or suspected misuse of verification data.
24Changes to this notice
Dohos must update this notice when law, roles, data, Providers, rights, request methods, verification, timing, appeals, or product behavior changes.
The activated notice must identify its version, effective date, covered scope, legal entity, and contacts. Prior versions and request decisions must be preserved at the version archive. A later notice does not retroactively cure a missed or mishandled request.