dohosGet started
PLATE Nº 116 · DOCUMENT

Version Archive

TARGET-STATE DRAFT — NOT APPROVED OR EFFECTIVE
EFFECTIVENot yet — draft
VERSIONNone assigned
DRAFT NOTICEThis page describes how Dohos preserves a superseded version of a legal or trust document, once a document-control process exists to run it and a document has actually been approved and later revised. No document in this library has been approved as effective, so none has been superseded, and the process described below has not yet operated. This draft must not be read as evidence that any version has been recorded.

01What this archive records

Every Dohos legal and trust document that reaches effective status is expected to change over time — a provision gets clarified, a new capability gets disclosed, a jurisdiction gets added. When that happens, this archive is where the version being replaced goes, not where it disappears to.

Each entry, once one exists, records:

  • the document title and the route it lives at
  • the version number and the effective-date range it was in force for
  • the exact text as it was presented and accepted, not a reconstruction
  • a plain description of what changed from the version before it
  • the document that replaced it, and a link forward to the current version

This is the same commitment every document in this library already makes to a reader in its own changes-to-this-document section — this page is where that commitment is kept, not a separate promise.

02How a version gets superseded

Once a document is approved and effective, updating it prospectively follows the same document-control process each document commits to in its own changes section: the new version is assigned its own version number and effective date, the exact text of the version it replaces is preserved rather than overwritten, the material differences are described in plain language, and the record links the specific version a person or restaurant actually accepted to the transaction or release it governed.

A later version does not retroactively change what an earlier one meant, and posting a new version does not by itself authorize a use or acceptance the earlier version didn't cover. Where a document requires renewed consent for a material change, that consent is obtained before the new version takes effect, not assumed from continued use.

03Current status

DOCUMENTVERSIONSUPERSEDEDREPLACED BY
NOTENo Dohos legal or trust document has been approved as effective. A document has to be effective before a later revision can supersede it, so this archive has nothing to record yet — that is a fact about sequence, not a missing feature. The table above has the shape every future entry will take; it has no rows because no document has reached that point.

04Documents currently in force

None of the documents below are approved or effective yet either — every one carries its own draft status, shown here as version 0-draft rather than a real version number, because none has been assigned one. Linked here so a superseded version, when one exists, has a current version to point forward to.

DOCUMENTVERSION
Website and Diner Terms0-DRAFT
Privacy Notice0-DRAFT
Acceptable Use Policy0-DRAFT
AI and Voice Transparency Notice0-DRAFT
SMS and Communications Notice0-DRAFT
Order, Payment, Refund, and Dispute Notice0-DRAFT
Privacy Rights Request Notice0-DRAFT
Product Claims and Service Limitations0-DRAFT
Cookie and Tracking Notice0-DRAFT
Accessibility Statement0-DRAFT
Subprocessor List and Change Notice0-DRAFT
Restaurant Services Agreement0-DRAFT
Data Processing Addendum0-DRAFT
Service Level and Support Schedule0-DRAFT
Vendor and Subprocessor Terms0-DRAFT

The full register, with category and status, lives at /legal; the trust-center pages this library sits alongside are gathered at the vendor packet.