dohosGet started
PLATE Nº 083

Privacy

How Dohos separates a restaurant's own account data from a caller's personal data, and where to find the specific policy that governs each.

PLATE Nº 083 · PRIVACY
TARGET-STATE DRAFT — NOT APPROVED OR EFFECTIVE
FRAMED · INTRODUCTION

Two kinds of interaction produce data that Dohos touches: a restaurant configuring its account, menu, and policies, and a person calling that restaurant's number to place an order or ask a question. This wing is about both, but they're governed differently, and the pages below are organized around that difference rather than around a single undifferentiated "data policy."

For the data that exists to receive, route, confirm, and fulfill a specific restaurant's orders, the restaurant is the one who decides why that channel exists and how the resulting customer relationship is used — Dohos processes it on the restaurant's documented instructions, not on its own judgment. Separately, and narrowly, Dohos is directly responsible for a smaller set of its own purposes: administering restaurant accounts and logins, billing for the service itself, preventing fraud and abuse, keeping the service secure and running, and responding to support, legal, and privacy requests. Those two categories don't blend into each other.

A short list of things are disabled unless a specific, separately reviewed exception turns them on:

  • identifying a caller from their voice — a Voiceprint, or any biometric use of speech
  • inferring health, emotion, or another protected trait from what someone says or how they say it
  • training a general model on a restaurant's or a caller's content
  • using order or account data to build advertising profiles, or selling it
  • combining one restaurant's data with another restaurant's for any purpose

None of these is a feature waiting on a launch date. Each one is a category that stays closed unless it goes through its own legal and product review first — a decision made deliberately, not a gap left open by omission.

DRAFT NOTICEThis wing explains Dohos's target approach to handling data; it is a summary, not a substitute for the pages beneath it or for the underlying policy work behind them. None of the practices described here has been adopted, certified, or independently audited. Where something is described as standard, it is standard in the sense that it is the design Dohos is building to — not evidence that a named auditor has confirmed it operates that way in production.
ONE QUESTION PER PAGE

Each page below answers one specific question rather than trying to cover everything at once — the contract, the vendors, the locations, the schedules, the request process, the caller's record, and the training question, each on its own plate.

PLATE Nº 084

AI training

What is and is not trained on — owner-controlled.

OPEN →PLATE Nº 085

Caller data

What a call leaves behind, and who can see it.

OPEN →PLATE Nº 086

Data residency

Where transcripts and configuration live.

OPEN →PLATE Nº 087

DPA

The data processing agreement.

OPEN →PLATE Nº 088

Retention

Owner-set retention, defaults, and deletion.

OPEN →PLATE Nº 089

Rights requests

Access and deletion requests, handled.

OPEN →PLATE Nº 090

Subprocessors

The approved-subprocessor register — honest about its current state.

OPEN →
WHO THIS WING IS FOR
THE PRIVACY REVIEWERTracing who decides why data exists, and what stays off by default — with each claim's tier stated.
THE CALLERWhat a call actually leaves behind, who can see it, and how to ask about your own record.
THE OWNERA restaurant's own instructions govern its customer data — these pages say exactly where that boundary sits.
LEGAL COUNSELThe DPA's shape and its open gaps, before anyone asks for a signature.

This wing describes Dohos's own processing. It doesn't describe a specific restaurant's independent policies — its own privacy notice, its loyalty program, its marketing — which that restaurant controls and is responsible for on its own. It also isn't the place for the legally binding version of any of this: the Privacy Notice is that version — the same facts, written and structured as the notice a person actually agrees to, once one is in effect. A question about how Dohos itself handles account, billing, or security data starts at /contact/legal.