Trust
Availability, compliance, privacy, and security — Dohos's full trust posture in one place, including exactly what's settled, what's a design commitment, and what genuinely isn't set yet.
A restaurant, an IT reviewer, or a procurement contact asking "can we trust Dohos with our calls and our customers' data" gets the same answer everywhere on this site: read the actual pages, not a badge. This center is organized into four wings — reliability, regulatory framework, data handling, and platform security — each answering a different slice of that question in its own register, plus two documents that pull the whole library together for someone doing a formal review.
Every claim on every page below is held to one of two standards, stated plainly rather than blurred together. A small set of facts — that a card number is never meant to reach Dohos's own systems, that every operational record is scoped to its restaurant location, that access follows four defined roles — trace to the product's own build specification, and are stated as settled architecture. Everything else traces to Dohos's internal security, privacy, and compliance policy library, which is itself an unapproved draft describing the company's target state — those pages are written as policy and design intent, not as a report of an audited operating history Dohos hasn't had the chance to build yet.
This center describes Dohos's own processing and its own platform. It is not a substitute for the legal library, which carries the versions of these same facts written as an actual notice or contract, nor for a specific restaurant's own independent policies for its customers. A question this center doesn't answer can go to /contact/security.
Reliability is what happens when something breaks — the fallback behavior, the continuity plan, and the honest state of the uptime commitment. Compliance is the regulatory surface a phone that talks and takes payment actually sits inside — one framework at a time, never a single badge. Privacy is whose data this is, who decides why it exists, and how long it's kept. Security is how the platform itself is built and defended — access, encryption, infrastructure, and how to report a problem.
Two pages exist specifically for someone working through this material as a checklist rather than reading wing by wing.
Trust FAQ
The questions your IT reviewer will ask.
OPEN →PLATE Nº 069Vendor packet
Everything procurement needs, in one document.
OPEN →Nothing in this center has a last-reviewed date yet, because no document-control process has run for any of it — that omission is consistent across every page here, not a gap on any one of them. A question not answered by a specific page, or a request for something not yet published, can be sent to /contact/security.