Platform · Development status
Development status
This is the one page that lists every stage and capability of DocuPrivé with its status. DocuPrivé is in development and is not yet available for use. Today's development build covers Rooms, issued Requests and verified access to Request details. It does not yet accept, preview, store or deliver document files.
- In our development build
- 2 of 9 stages, Request details only
- Designed, not yet built
- 7 of 9 stages, and Hold
- In use by anyone
- Nothing yet: DocuPrivé is not yet available for use. No dates are published.
What the labels mean
In our development build
Exists in the development build, shown with genuine example-data captures. Not available to anyone.
Designed, not yet built
Approved design direction. Not built.
The nine stages, and Hold.
Hold is a control across every stage, not a stage.
| Stage | What it means | Status | Described on |
|---|---|---|---|
| 01Request | Issue a Request from inside a Room: a title, instructions, the one person it is for, and the exact date and time access ends. | In our development build | Request & Receive |
| 02Receive | Documents arrive in the context of the Request they answer, not a general inbox. | Designed, not yet built | Request & Receive |
| 03Classify | Material is recognized for what it is and how it should be handled. | Designed, not yet built | Request & Receive |
| 04Control | Request details stay with a verified recipient, for a defined access period. | In our development build, for Request details | Share & Recall |
| 05Use | People work with the documents a task needs, and no more. | Designed, not yet built | Share & Recall |
| 06Retain | Material is kept for a period set by policy, not left by accident. | Designed, not yet built | Lifecycle & Evidence |
| 07Review | Before anything ends, the right people can look again. | Designed, not yet built | Lifecycle & Evidence |
| 08Dispose | When the time comes, material is brought to a considered end. | Designed, not yet built | Lifecycle & Evidence |
| 09Evidence | A proportionate record of what was decided, kept with privacy in mind, from the first Request to the end. | Designed, not yet built | Lifecycle & Evidence |
| ControlHoldacross every stage, not a stage | While a hold applies, material is not brought to an end, whatever stage it is in. A hold is placed when circumstances require it, for example a dispute, by an accountable person. | Designed, not yet built | Lifecycle & Evidence |
Capabilities, statement by statement.
Every product statement on this website comes from this list, at this status.
Requests and recipient access
Read moreIssue a Request from inside a Room: a title, instructions, the one person it is for, and the exact date and time access ends.
In our development buildOnce issued, a Request's details are fixed. Issue, identity verification, current access and email notification are each recorded separately.
In our development buildAccess to a Request can be revoked, and the notification can be resent.
In our development buildThe recipient sees only that Request: who asked, what is needed and when access ends. They do not join the requesting organization.
In our development buildRecipient access starts with a verified receiving email address.
In our development buildThe recipient view works on a phone.
In our development buildRequest details stay with a verified recipient, for a defined access period.
In our development build, for Request details
Library and search
Read moreEvery document keeps a stable identity. Renaming or moving it changes how it is labeled and where it sits, never who can access it.
Designed, not yet builtA folder is where a document sits, not a permission. Access comes from the work it belongs to.
Designed, not yet builtNaming rules help documents arrive with consistent, readable names, and you confirm before anything is saved.
Designed, not yet builtA document's date is recorded with where it came from, and is never quietly set to today.
Designed, not yet builtFinding material is designed to respect the same boundaries as access: you find what you are allowed to see.
Designed, not yet builtAutomated suggestions can propose a name or place. They do not move documents on their own.
Designed, not yet built
Recall and links
Read moreRecall is designed to end access that DocuPrivé controls. It cannot reach copies already downloaded, or change permissions in someone else's system.
Designed, not yet builtA file held in DocuPrivé and a link to material held elsewhere are different things, with different controls. A link does not make DocuPrivé responsible for the other system.
Designed, not yet built
Records and decisions
Read moreDocument content and lifecycle records are designed to be kept separately, each with its own access and retention rules.
Designed, not yet builtAutomated assistance will not decide on its own to hold, keep or dispose of material. Those decisions have an accountable person.
Designed, not yet built
Commitments about customer documents
Read moreCustomer documents are not sold, used for advertising, or used to train general-purpose AI models.
Designed, not yet builtEncryption and access will be described exactly as built. Nothing will be called end-to-end encrypted or zero-knowledge unless it is, and we can show it.
Designed, not yet built
Hear when a stage moves.
Status changes are announced by email, never with dates we cannot keep.