Model improvement
For dviilo. Draft — not published, and not in force.
Unpublished draft
This document is a draft. It has not been reviewed by a lawyer, it has not been published, and it is not in force. Nothing on this page binds anyone, and no product links to it as a term of use.
Not written as its own document. Section 4 of the Privacy Policy and clause 5 of the dviilo terms are operative.
What applies today
Two documents already say all of this, and they are the ones that bind:
- Section 4 of the Privacy Policy — what is used, what is redacted before it is stored, what audio is used for, and what it is never used for.
- Section 5 of the Privacy Policy — recognising a returning caller, which is a separate question and a separate switch.
- Clause 5 of the dviilo terms — the permission itself, and its limits.
Why a separate document is wanted
The answer an administrator needs before flipping the switch is currently spread across two documents and three sections. None of this is in force.
- One page an administrator can read before turning it on, and send to their own reviewers.
- A worked example of a redacted turn: what is kept, what is replaced by a description of its shape, and what the audit note records.
- The honest limits, stated once — identifiers are not replaced consistently, and redaction is not anonymisation.
- What happens to text already folded into a training set when the switch goes off.