# https://docuprive.com/ Document Lifecycle Infrastructure # The right documents. The right people. A clear next step. DocuPrivé is being built to help professional teams request, receive, control, share and recall important documents, and keep a record of each decision. In development. Not yet available. Each capability on this site shows where it stands. [Explore the platform](https://docuprive.com/platform/) [See what exists today](https://docuprive.com/platform/status/) Once issued, the details are fixed. Issue, identity verification, current access and email notification are each recorded separately, and access can be revoked. Once issued, the details are fixed. Issue, identity verification, current access and email notification are each recorded separately, and access can be revoked. The recipient sees only this request: who asked, what is needed and when access ends. They do not join the requesting organisation. The same recipient view on a phone. Pause View full screens Views from our development build Close Once issued, the details are fixed. Issue, identity verification, current access and email notification are each recorded separately, and access can be revoked. The recipient sees only this request: who asked, what is needed and when access ends. They do not join the requesting organisation. The same recipient view on a phone. From our development build, with example data. It does not yet accept, preview, store or deliver document files. What it is for ## Three things professional teams need from every document request. - **Define the request.** 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](https://docuprive.com/platform/request-receive/) - **Keep work in context.** Documents arrive in the context of the Request they answer, not a general inbox. A folder is where a document sits, not a permission. Access comes from the work it belongs to. Designed, not yet built [Library & Search](https://docuprive.com/platform/library-search/) - **Control the intended access.** Request details stay with a verified recipient, for a defined access period. In our development build, for Request details [Share & Recall](https://docuprive.com/platform/share-recall/) The platform ## Four capabilities, from the first Request to a considered end. Four capabilities follow a document from the first Request to a considered end. Hold applies across all of them, and a record is kept throughout. [See the full lifecycle](https://docuprive.com/platform/) - [01 Request & Receive Request Receive Classify Ask one named person for exactly what the work needs, with an exact end to access. Explore](https://docuprive.com/platform/request-receive/) - [02 Library & Search Organizing Finding A stable identity for every document, and finding only what you are allowed to see. Explore](https://docuprive.com/platform/library-search/) - [03 Share & Recall Control Use Access for a defined task and period, ended when the work ends. Explore](https://docuprive.com/platform/share-recall/) - [04 Lifecycle & Evidence Retain Review Dispose Evidence Kept, reviewed and brought to a considered end, with a record of each decision. Explore](https://docuprive.com/platform/lifecycle-evidence/) **Hold** a control across every stage: while it applies, nothing is brought to an end. **Evidence** a proportionate record, from the first Request to the end. For professionals ## Built for people who look after other people's documents. [All use cases](https://docuprive.com/solutions/) - [Legal and advisory Matter intake: ask an external adviser for identity documents, with access that ends. See the workflow](https://docuprive.com/solutions/legal-advisory/) - [Accounting and audit The yearly records cycle: one clear Request per person, reviewed when the file closes. See the workflow](https://docuprive.com/solutions/accounting-audit/) - [Focused due diligence Each person sees what their part of the review needs, until the review closes. See the workflow](https://docuprive.com/solutions/#due-diligence) - [Private-client teams Personal and family papers, asked for exactly and kept no longer than needed. See the workflow](https://docuprive.com/solutions/#private-clients) Why it matters ## A document is more than a file. It is a responsibility. DOCUPRIVÉ — Beyond the Share The responsibility doesn't end when the document is shared. Sharing takes seconds. The copy then sits in inboxes, shared folders and other people's systems for years. DocuPrivé is designed for everything around that moment: how a document is asked for, who can see it, for how long, and what happens at the end. Privacy & Trust ## Responsibility, stated plainly. [Your privacy shapes how we build.](https://docuprive.com/trust/) ### Who is responsible DocuPrivé is developed by DocuPrive, Inc. The same company operates this website and answers for what it says. [Company](https://docuprive.com/company/) ### What exists, and what does not Today's development build covers Rooms, issued Requests and verified access to Request details. Everything else is designed, not yet built. [Development status](https://docuprive.com/platform/status/) ### This website and your data This website sets no cookies of its own. Cloudflare Turnstile keeps one essential security entry when you use the sign-up form. No analytics, no advertising. [Website privacy notice](https://docuprive.com/privacy/) [Partnerships Partnership enquiries Professional firms, advisers and technology teams can talk with us about how document requests, access and retention work in practice. Areas for discussion, and how an enquiry proceeds. How enquiries work](https://docuprive.com/partners/) Resources [All resources](https://docuprive.com/resources/) - [Podcast · EP02 Beyond the Share: “Your AI Meeting Notes Say You Agreed. You Didn't.”](https://docuprive.com/resources/beyond-the-share/) - [Guide A file or a link? What changes when you share each.](https://docuprive.com/resources/file-vs-external-link/) - [Guide What recall can and cannot do.](https://docuprive.com/resources/what-recall-can-and-cannot-do/) Where the build stands 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. Status reviewed 28 October 2026. [Development status, stage by stage](https://docuprive.com/platform/status/) Product updates ## Follow what comes next. Occasional product news, platform updates and launch announcements from DocuPrivé. - A few emails, when there is something worth saying. - No account is created and no access is reserved. - Unsubscribe from any future email, at any time. Sign up for product updates at https://docuprive.com/updates/ (double opt-in). Questions? [support@docuprive.com](mailto:support@docuprive.com) --- # https://docuprive.com/platform/ Platform # One platform for the working life of a document. DocuPrivé follows a professional document through nine stages: Request, Receive, Classify, Control, Use, Retain, Review, Dispose and Evidence. While a hold applies, nothing is brought to an end. Today's development build covers the first part, issuing a Request to one verified person for a defined period. The rest is designed and not yet built. [The four capabilities](#capabilities) [Development status](https://docuprive.com/platform/status/) From the Request record in our development build: Once issued, the details are fixed. Issue, identity verification, current access and email notification are each recorded separately, and access can be revoked. Four capabilities ## Each one answers a different question about a document. - 01 · Request · Receive · Classify **[Request & Receive](https://docuprive.com/platform/request-receive/).** Ask for exactly what the work needs, from one named person, with instructions and a fixed end to access. Documents are designed to arrive in the context of the Request they answer. Issued from inside a Room - Details fixed once issued - Resend or revoke - Request In our development build - Receive, Classify Designed, not yet built [Explore Request & Receive](https://docuprive.com/platform/request-receive/) - 02 · Organizing and finding **[Library & Search](https://docuprive.com/platform/library-search/).** Every document is designed to keep a stable identity, a readable name and a recorded date, wherever it sits. Finding material respects the same boundaries as access. Stable identity - Folders place, they do not permit - Suggestions never move anything alone - Library & Search Designed, not yet built [Explore Library & Search](https://docuprive.com/platform/library-search/) - 03 · Control · Use **[Share & Recall](https://docuprive.com/platform/share-recall/).** Give the people you choose access to a defined task, for a defined period, and end it when the work ends. External recipients see only what they were asked for. One verified recipient - Exact end to access - Ending access is not un-sending - Control In our development build, for Request details - Use Designed, not yet built [Explore Share & Recall](https://docuprive.com/platform/share-recall/) - 04 · Retain · Review · Dispose · Evidence, with Hold **[Lifecycle & Evidence](https://docuprive.com/platform/lifecycle-evidence/).** Keep material for a period set by policy, look again before anything ends, bring it to a considered close, and keep a proportionate record of the decisions. Policy-set retention - Review with an owner - Hold stops the end - Retain, Review, Dispose, Evidence, Hold Designed, not yet built [Explore Lifecycle & Evidence](https://docuprive.com/platform/lifecycle-evidence/) The lifecycle ## Nine stages, one control across them. Select a stage to read its definition and where it stands. Classify is a stage of its own; Hold is not a tenth stage. The nine stages, grouped by capability **Hold** applies across every stage. While a hold applies, material is not brought to an end. A control, not a stage. [Request & Receive](https://docuprive.com/platform/request-receive/) - [01 Request In our development build](#stage-request) - [02 Receive Designed, not yet built](#stage-receive) - [03 Classify Designed, not yet built](#stage-classify) [Share & Recall](https://docuprive.com/platform/share-recall/) - [04 Control In our development build, for Request details](#stage-control) - [05 Use Designed, not yet built](#stage-use) [Lifecycle & Evidence](https://docuprive.com/platform/lifecycle-evidence/) - [06 Retain Designed, not yet built](#stage-retain) - [07 Review Designed, not yet built](#stage-review) - [08 Dispose Designed, not yet built](#stage-dispose) - [09 Evidence Designed, not yet built](#stage-evidence) **Library & Search** keeps material in order and findable within its boundaries, at every stage. [Library & Search](https://docuprive.com/platform/library-search/) **Evidence** is the ninth stage, and records also arise throughout the earlier ones. In our development build Designed, not yet built [Development status, stage by stage](https://docuprive.com/platform/status/) Request & Receive - **01 Request:** 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 - **02 Receive:** Documents arrive in the context of the Request they answer, not a general inbox. Designed, not yet built - **03 Classify:** Material is recognized for what it is and how it should be handled. Designed, not yet built Share & Recall - **04 Control:** Request details stay with a verified recipient, for a defined access period. In our development build, for Request details - **05 Use:** People work with the documents a task needs, and no more. Designed, not yet built Lifecycle & Evidence - **06 Retain:** Material is kept for a period set by policy, not left by accident. Designed, not yet built - **07 Review:** Before anything ends, the right people can look again. Designed, not yet built - **08 Dispose:** When the time comes, material is brought to a considered end. Designed, not yet built - **09 Evidence:** A proportionate record of what was decided, kept with privacy in mind, from the first Request to the end. Designed, not yet built Across every stage - **Hold a control, 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 Scope ## Clear about what it is not. - **Not a general file drive.** Documents belong to a piece of work, not to a folder that grows forever. - **Not a way to un-send.** Ending access is real; copies already downloaded are outside any platform's reach. [What recall can and cannot do](https://docuprive.com/resources/what-recall-can-and-cannot-do/) - **Not a substitute for professional judgment.** Keeping, holding and disposing of material are decisions with an accountable person; automated assistance will not make them alone. - **Not available yet.** We are building it in stages and will say when each one is ready. Lifecycle records their own access and retention ## Two kinds of information, kept apart by design. A document's content and the record of what happened to it are different things, needed by different people for different lengths of time. Document content and lifecycle records are designed to be kept separately, each with its own access and retention rules. Designed, not yet built ## Continue - [Development status Every stage and capability, with its status and review date.](https://docuprive.com/platform/status/) - [For professionals Example workflows for four practice areas.](https://docuprive.com/solutions/) - [Trust & data responsibility Who is responsible, and what the claims cover.](https://docuprive.com/trust/) ## Follow the build as each stage arrives. [Get product updates](https://docuprive.com/updates/) [Trust and data](https://docuprive.com/trust/) --- # https://docuprive.com/platform/request-receive/ Platform · Request · Receive · Classify # Request & Receive Ask for exactly what the work needs, and receive it in context. Request & Receive is where a piece of work begins in DocuPrivé. You issue a Request from inside a Room to one named person, with a title, instructions and an exact end to access. Issuing, verifying and revoking Requests exist in our development build; receiving and classifying documents are designed and not yet built. Request is in our development build. Receive and Classify are designed, not yet built. In our development build ## Before and after a Request is issued. The form asks for five things. Once issued, they become a fixed record with separate entries for issue, identity, access and notification. 1 Issuing - **Room** the piece of work it belongs to - **Request title** what is being asked for - **Instructions** for the recipient - **Intended recipient email** the one person it is for - **Access ends** an exact date and time Issue a request from inside a Room: a title, instructions, the one person it is for, and the exact date and time access ends. 2 Issued Once issued, the details are fixed. Issue, identity verification, current access and email notification are each recorded separately, and access can be revoked. **See the full screens** Issue a request from inside a Room: a title, instructions, the one person it is for, and the exact date and time access ends. Once issued, the details are fixed. Issue, identity verification, current access and email notification are each recorded separately, and access can be revoked. Requester and recipient ## One Request, one person, one boundary. How a Request connects the requester and one recipient Room The piece of work Every Request is issued from inside a Room, so it sits in the context it belongs to. Request Title, instructions, one person, an exact end Fixed once issued. Issue, identity verification, current access and email notification are recorded separately. Recipient Sees only that Request Recipient access starts with a verified receiving email address. They do not join the requesting organization. **Designed, not yet built:** documents arrive against the Request they answer, then are recognized for how they should be handled. ## Step by step. Seven steps, each with where it stands today. Limits today - 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. - Each Request is issued to one named recipient. - Receiving and classifying documents are designed, not yet built. - **Open a Room for the work.** A Room holds a piece of work, so every Request sits in the context it belongs to. In our development build - **Issue a Request.** 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 - **Details are fixed once issued.** Once issued, a Request's details are fixed. Issue, identity verification, current access and email notification are each recorded separately. In our development build - **Resend or revoke.** Access to a Request can be revoked, and the notification can be resent. In our development build - **The recipient sees only that Request.** Recipient access starts with a verified receiving email address. The recipient sees only that Request: who asked, what is needed and when access ends. They do not join the requesting organization. In our development build - **Documents arrive against the Request.** Documents arrive in the context of the Request they answer, not a general inbox. Designed, not yet built - **Material is recognized for handling.** Material is recognized for what it is and how it should be handled. Designed, not yet built ## Questions 5 answers. More on the [questions page](https://docuprive.com/faq/). **Who can open a Request?** Only the person it was issued to. Access starts with a verified receiving email address, and the recipient sees only that Request: who asked, what is needed and when access ends. **Why is a Request issued to one person?** So that access belongs to the one person the work needs, and the Request record shows exactly who that is. Asking someone else means issuing a separate Request. **What does "access ends" mean?** Every Request carries the exact date and time its access ends. After that, the recipient can no longer open the Request details in DocuPrivé. Access can also be revoked earlier. **Can a Request be changed after it is issued?** No. Once issued, a Request's details are fixed. If something needs to change, the Request can be revoked and a new one issued. **Can a recipient upload documents today?** Not yet. The development build does not yet accept, preview, store or deliver document files. Receiving documents against a Request is designed and not yet built. ## Related - [Share & Recall Access for a defined task and period.](https://docuprive.com/platform/share-recall/) - [Library & Search Keep material in order inside the work.](https://docuprive.com/platform/library-search/) - [Legal & advisory An example matter workflow that starts with a Request.](https://docuprive.com/solutions/legal-advisory/) ## Follow the build as each stage arrives. [Get product updates](https://docuprive.com/updates/) [Development status](https://docuprive.com/platform/status/) --- # https://docuprive.com/platform/library-search/ Platform · Organizing and finding # Library & Search Keep material in order inside the work, and find it without widening who can see it. Library & Search is the part of DocuPrivé designed to keep documents in order within a piece of work. Every document keeps a stable identity, folders place documents without granting access, names follow rules you confirm, dates keep their source, and finding material never widens who can see it. Designed, not yet built: everything on this page. The problem it is designed for - statement_march.pdf statement_march (1).pdf FINAL statement march v2.pdf Three copies, three names, no record of which one the work relied on, where it came from, or who may open it. D-1051 2026-03 Bank statement statement date · Example Trading year-end Designed, not yet built ## Arrange it any way. The document stays the same document. Try the three controls. This example is built for this page to show the design. Nothing in it exists in the development build, and it does not search anything. Documents keep their identity however they are arranged Names As sent Naming rule Who is looking Firm administrator Holdings matter team Example Holdings matter - D-1042 Engagement letter March 2026 · dated by sender Example Holdings matter - D-1043 Passport scan April 2026 · date received Example Holdings matter - D-1052 Funds letter v2 April 2026 · dated by issuer Example Holdings matter Example Trading year-end - D-1051 statement_march.pdf March 2026 · statement date Example Trading year-end - D-1060 Minutes (final) March 2026 · meeting date Example Trading year-end - D-1061 Proof of address April 2026 · date received Example Trading year-end The identity on each card never changes: arranging, renaming or moving a document changes how it is labeled and where it sits, never who can access it. Finding follows the same boundaries as access. Example names only; nothing here is a screen from the product. ## Six design rules. Each one is designed and not yet built. - 01 **A stable identity for every document.** Every 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 built - 02 **Folders place, they do not permit.** A folder is where a document sits, not a permission. Access comes from the work it belongs to. Designed, not yet built - 03 **Names that follow your rules.** Naming rules help documents arrive with consistent, readable names, and you confirm before anything is saved. Designed, not yet built - 04 **Dates that keep their source.** A document's date is recorded with where it came from, and is never quietly set to today. Designed, not yet built - 05 **Finding only what you may see.** Finding material is designed to respect the same boundaries as access: you find what you are allowed to see. Designed, not yet built - 06 **Suggestions, not silent moves.** Automated suggestions can propose a name or place. They do not move documents on their own. Automated assistance will not decide on its own to hold, keep or dispose of material. Those decisions have an accountable person. Designed, not yet built ## Limits Limits, today and by design - No library, search or naming feature exists in the development build. - 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. - This page describes no connectors, desktop companion or editor. - Automated suggestions only propose. Keeping, holding and disposing of material stay decisions with an accountable person. ## Questions 4 answers. More on the [questions page](https://docuprive.com/faq/). **Does a folder control who sees a document?** No. A folder is where a document sits, not a permission. Access comes from the work the document belongs to, so moving it between folders does not change who can open it. **Will DocuPrivé rename my files automatically?** No. Naming rules and automated suggestions can propose a name or a place, and you confirm before anything is saved. Suggestions do not move documents on their own. **Can search show me documents from other work?** It is designed not to. Finding material follows the same boundaries as access, so you find what you are allowed to see and nothing beyond it. **Can I use Library & Search today?** Not yet. Library & Search is designed and not yet built. Today's development build covers Rooms, issued Requests and verified access to Request details. ## Related - [Request & Receive Ask for exactly what the work needs.](https://docuprive.com/platform/request-receive/) - [Share & Recall Access for a defined task and period.](https://docuprive.com/platform/share-recall/) - [The whole lifecycle Nine stages and where each stands.](https://docuprive.com/platform/) ## Follow the build as each stage arrives. [Get product updates](https://docuprive.com/updates/) [Development status](https://docuprive.com/platform/status/) --- # https://docuprive.com/platform/share-recall/ Platform · Control · Use # Share & Recall Give the right person access to a defined task, for a defined period, and end it when the work ends. Share & Recall covers who can see material, for how long, and how access ends. In our development build, Request details stay with one verified recipient for a defined period and access can be revoked. Working with documents, and recalling access to them, are designed and not yet built. Ending access is real; un-sending is not. Control is in our development build, for Request details. Use and recall of documents are designed, not yet built. From the Request record in our development build: who the Request is for, when access ends, and the action that ends it earlier. The boundary ## Ending access is real. Un-sending is not. Switch between the two states. Only what sits inside DocuPrivé's control changes. What ending access can reach Inside DocuPrivé's control **Request details** in our development build Opens for the recipient No longer opens **Documents shared in DocuPrivé** designed, not yet built Open for the task Access ended Access ends 14 Oct 2026, 01:57 UTC, or earlier if revoked Outside it - A copy already downloaded - A copy forwarded by email - Permissions in someone else's system - A printed page or a screenshot Unchanged when access ends. Recall cannot reach these. When access ends, or is revoked earlier, the Request details stop opening for the recipient. Copies that have already left DocuPrivé are outside its reach either way. In our development build ## What the recipient sees. - **Only that Request.** The recipient sees only that Request: who asked, what is needed and when access ends. They do not join the requesting organization. - **A verified address.** Recipient access starts with a verified receiving email address. - **An exact end.** Every Request carries the exact date and time its access ends. Access to a Request can be revoked, and the notification can be resent. In our development build , for Request details The recipient sees only this request: who asked, what is needed and when access ends. They do not join the requesting organisation. The same recipient view on a phone. ## External people stay external. A recipient answers one Request. They do not join the requesting organization, and they do not see its other Rooms, Requests or people. In our development build ## Only what the task needs. People work with the documents a task needs, and no more. Access is meant to relate to a task or a Room, not to everything an organization holds. Designed, not yet built ## Files and links differ. A 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 [A file or a link?](https://docuprive.com/resources/file-vs-external-link/) What Control covers today - Control in the development build covers Request details only: who can open them, and until when. - It does not yet accept, preview, store or deliver document files. - Use, and recall of documents, are designed and not yet built. ## Questions 4 answers. More on the [questions page](https://docuprive.com/faq/). **Does the recipient join our organization?** No. The recipient sees only the Request they were asked to answer and does not join the requesting organization. In the development build, access starts with verifying the receiving email address the Request was issued to. **What happens after access ends?** The recipient can no longer open the Request details in DocuPrivé. Anything already copied outside DocuPrivé is beyond its reach. **Can DocuPrivé delete a copy someone downloaded?** No. Recall is designed to end access that DocuPrivé controls. It cannot reach copies already downloaded, or change permissions in someone else's system. **Is sharing a link the same as sharing a file?** No. A 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. ## Related - [What recall can and cannot do A plain guide to ending access.](https://docuprive.com/resources/what-recall-can-and-cannot-do/) - [Request & Receive Ask for exactly what the work needs.](https://docuprive.com/platform/request-receive/) - [Lifecycle & Evidence Retention, review, holds and the end.](https://docuprive.com/platform/lifecycle-evidence/) ## Follow the build as each stage arrives. [Get product updates](https://docuprive.com/updates/) [Development status](https://docuprive.com/platform/status/) --- # https://docuprive.com/platform/lifecycle-evidence/ Platform · Retain · Review · Dispose · Evidence # Lifecycle & Evidence Decide in advance how material is kept, reviewed and brought to an end, and be able to account for it. Lifecycle & Evidence is the part of DocuPrivé designed for the end of a document's working life: keeping it for a period set by policy, looking again before anything ends, bringing it to a considered end, and keeping a proportionate record of each decision. While a hold applies, nothing is brought to an end. All of this is designed and not yet built. Everything on this page is designed and not yet built. Where this page sits in the lifecycle - 01 Request - 02 Receive - 03 Classify - 04 Control - 05 Use - 06 Retain - 07 Review - 08 Dispose - 09 Evidence Hold applies across every stage Responsibility does not end when a document is shared: it runs until a considered end, and Evidence is recorded along the way. Designed, not yet built ## Every step has someone who decides. Select a step to see who decides and what happens. Switch the hold on to see what it changes. Who decides at each step, and what a hold changes Hold applies: material is not brought to an end, whatever stage it is in. - 06 Retain 06 Retain Your policy, set by an accountable person Material is kept for a period set by policy, not left by accident. You decide the policy; DocuPrivé is designed to apply it. - 07 Review 07 Review The person accountable for the work Before anything ends, the right people can look again. Reviewing is a decision with an owner, not a default left behind. - 08 Dispose 08 Dispose An accountable person, never automation alone When the time comes, material is brought to a considered end. "End" means what DocuPrivé controls: its own copy and its own access. Not brought to an end while the hold applies. **Evidence, 09** A proportionate record of what was decided, kept with privacy in mind, from the first Request to the end. A record shows an event happened in DocuPrivé. It does not prove a person read or understood a document. A hold is placed by an accountable person when circumstances require it; it stops the end from happening and is not described here as stopping anything else. ## What a record does not prove. A record shows an event happened in DocuPrivé. It does not prove a person read or understood a document. It does not prove understanding or agreement either. Even an "opened" event needs care: some email security tools open links automatically to check them, before any person does. DocuPrivé is designed to record what happened, plainly, and to say what each record can and cannot show. ## Content and records, kept apart. Document content and lifecycle records are designed to be kept separately, each with its own access and retention rules. Automated assistance will not decide on its own to hold, keep or dispose of material. Those decisions have an accountable person. Designed, not yet built In our development build ## A first, narrow example today. The Request record in our development build already keeps issue, identity verification, current access and email notification as separate entries. It is a first narrow example of recording what happened, not lifecycle evidence. In our development build , Request record Once issued, the details are fixed. Issue, identity verification, current access and email notification are each recorded separately, and access can be revoked. ## Questions 4 answers. More on the [questions page](https://docuprive.com/faq/). **Will DocuPrivé set retention periods for me?** No. Material is kept for a period set by your policy. DocuPrivé is designed to apply the policy you set, not to choose it for you. **What is a hold?** A hold is a control placed by an accountable person when circumstances require it, for example a dispute. While a hold applies, material is not brought to an end, whatever stage it is in. A hold is not a stage of its own. **Can a record prove that someone read a document?** No. A record shows that an event happened in DocuPrivé. It does not prove that a person read, understood or agreed with a document. **Does "dispose" mean deleted everywhere?** No. Disposal brings material held in DocuPrivé to a considered end. It cannot reach copies already downloaded or held in other systems. ## Related - [Share & Recall Access for a defined task and period.](https://docuprive.com/platform/share-recall/) - [What recall can and cannot do A plain guide to ending access.](https://docuprive.com/resources/what-recall-can-and-cannot-do/) - [Trust & data responsibility Where things stand, and who is responsible.](https://docuprive.com/trust/) ## Follow the build as each stage arrives. [Get product updates](https://docuprive.com/updates/) [Development status](https://docuprive.com/platform/status/) --- # https://docuprive.com/solutions/ Solutions # Built for people who look after other people's documents. DocuPrivé is being built for professional teams that request, share and look after sensitive documents for others: legal and advisory, accounting and audit, focused due diligence, and private-client teams. Each example below describes the recurring work and the lifecycle stages it leans on, with where each stage stands today. ## Four practice areas - [Matter intake and closing Legal and advisory An example matter workflow](https://docuprive.com/solutions/legal-advisory/) - [The yearly records cycle Accounting and audit An example yearly engagement](https://docuprive.com/solutions/accounting-audit/) - [Time-bound review access Focused due diligence Read the example](#due-diligence) - [Personal and family papers Private-client teams Read the example](#private-clients) Matter intake and closing ## Legal and advisory Instructions, evidence and correspondence pass between firms, clients and other parties. Each document belongs with the matter it serves, and the people who need it change as the matter moves. DocuPrivé is designed to keep that material inside the matter: asked for clearly, seen by the matter team for as long as the work needs, and decided on at closing. [An example matter workflow](https://docuprive.com/solutions/legal-advisory/) Stages it leans on - Request In our development build - Control In our development build - Retain, Review, Dispose Designed The yearly records cycle ## Accounting and audit The same records are requested, chased and re-sent every cycle. Year-end statements, ledgers and confirmations travel by email, and copies stay in inboxes long after the engagement ends. A clear Request and a defined period of access bring order to it. Access is designed to end with the engagement, and the file to be reviewed when it closes. [An example yearly engagement](https://docuprive.com/solutions/accounting-audit/) Stages it leans on - Request In our development build - Receive Designed - Retain, Review Designed Time-bound review access ## Focused due diligence A review needs the right material, seen by the right people for as long as it runs, and a clear end when it closes. The list of people involved is often wider than one firm, and it changes during the review. DocuPrivé is designed so that each person sees what their part of the review needs, for a defined period, and so that access ends when the review does. When a matter turns into a dispute, a hold keeps material from being brought to an end. Stages it leans on - Request In our development build - Control In our development build - Use Designed - Hold Designed - Dispose Designed Personal and family papers ## Private-client teams Personal and family papers deserve discretion: identity documents, property records, statements and letters that belong to a person, not to a file share. They are often requested more than once, by more than one adviser. DocuPrivé is designed to ask for exactly what is needed, share it with care, and keep it no longer than it is needed. Each of those decisions has an owner. Stages it leans on - Request In our development build - Control In our development build - Retain, Dispose Designed Common to all four ## The same platform underneath. - [Request & Receive One named person, an exact end to access.](https://docuprive.com/platform/request-receive/) - [Library & Search Material kept in order inside the work.](https://docuprive.com/platform/library-search/) - [Share & Recall Access for a task and a period.](https://docuprive.com/platform/share-recall/) - [Lifecycle & Evidence Kept, reviewed and ended with an owner.](https://docuprive.com/platform/lifecycle-evidence/) ## Follow the build as each stage arrives. [Get product updates](https://docuprive.com/updates/) [How it works](https://docuprive.com/platform/) [Partnership enquiries](https://docuprive.com/partners/) --- # https://docuprive.com/solutions/legal-advisory/ Solutions · Legal & advisory # Documents that belong with the matter they serve. For legal and advisory teams, DocuPrivé is designed to keep client documents inside the matter: requested from the right person with clear instructions, seen by the matter team for as long as the work needs, held if a dispute arises, and decided on at closing. Issuing a Request to one verified person for a defined period exists in our development build; the rest is designed and not yet built. Roles in this example a matter partner an assistant on the matter team the client's external adviser ## Who it is for Law firms, in-house legal teams and advisory practices that collect documents from clients and from the other professionals who act for them. The people who ask for documents, the people who work on them, and the person accountable for the matter when it closes. ## The recurring problem Matter documents arrive by email from several directions: the client, the client's other advisers, counterparties. Each copy lands in a different inbox, and it is rarely clear later who still holds what. At closing, the questions are always the same. What did we receive, and from whom? Who on the team could see it? How long must we keep it, and who decides when it goes? An example workflow ## How this work is designed to run, step by step. 2 of 10 steps exist in our development build; the others are designed, not yet built. This example shows how the stages fit together; the names and steps are generic. - 01 Request Assistant → external adviser **Ask for the identity and source-of-funds documents.** The assistant issues a Request from the matter's Room to the external adviser, with instructions and an exact date and time when access ends. Once issued, a Request's details are fixed. Issue, identity verification, current access and email notification are each recorded separately. In our development build - 02 Control External adviser **The adviser opens only that Request.** Recipient access starts with a verified receiving email address. The adviser sees who asked, what is needed and when access ends, and does not join the firm. In our development build, for Request details - 03 Receive External adviser → matter **Documents arrive against the Request.** Documents arrive in the context of the Request they answer, not a general inbox. Designed, not yet built - 04 Classify Matter team **Recognized for how they should be handled.** Material is recognized for what it is and how it should be handled. Designed, not yet built - 05 Use Matter partner, assistant **The matter team works with what the task needs.** People work with the documents a task needs, and no more. Designed, not yet built - 06 Retain Firm policy **Kept for the period the matter policy sets.** Material is kept for a period set by policy, not left by accident. Designed, not yet built - 07 Review Matter partner **Looked at again when the matter closes.** Before anything ends, the right people can look again. Designed, not yet built - 08 Hold Accountable person **Held if a dispute arises.** While a hold applies, material is not brought to an end, whatever stage it is in. Designed, not yet built - 09 Dispose Matter partner **Brought to a considered end.** When the time comes, material is brought to a considered end. Designed, not yet built - 10 Evidence Throughout **A record of each decision.** A proportionate record of what was decided, kept with privacy in mind, from the first Request to the end. Designed, not yet built In our development build ## What the other side sees today. When a Request is issued to someone outside the firm, this is their view: only that Request, who asked, what is needed and when access ends. What exists today - Issuing a Request from a Room to one named person, with instructions and an exact end to access. - Verified access to the Request details for that person, revoking access and resending the notification. - Receiving, classifying and keeping documents, holds, disposal and evidence are designed, not yet built. The recipient sees only this request: who asked, what is needed and when access ends. They do not join the requesting organisation. ## Related - [A file or a link? What changes when you share a copy instead of a pointer.](https://docuprive.com/resources/file-vs-external-link/) - [Request & Receive How a Request works today.](https://docuprive.com/platform/request-receive/) - [Accounting & audit An example yearly engagement.](https://docuprive.com/solutions/accounting-audit/) ## Follow the build as each stage arrives. [Get product updates](https://docuprive.com/updates/) [Contact](https://docuprive.com/contact/) [All use cases](https://docuprive.com/solutions/) --- # https://docuprive.com/solutions/accounting-audit/ Solutions · Accounting & audit # The same records, every cycle, with an end to access. For accounting and audit teams, DocuPrivé is designed to bring order to the yearly round of document requests: one clear Request per person, access that ends with the engagement, and a review when the file closes. Issuing a Request to one verified person for a defined period exists in our development build; the rest is designed and not yet built. Roles in this example an engagement lead a team member the client's finance contact ## Who it is for Accounting firms, audit teams and finance advisers who request the same kinds of records from clients every period. The engagement lead who is accountable for the file, the team members who prepare the work, and the client's finance contact who supplies the records. ## The recurring problem Each cycle starts with a list of records and a run of emails: requests, reminders, re-sends. Statements and confirmations arrive as attachments and stay in inboxes long after the engagement ends. When the file closes, it is hard to say which copies still exist, who could open them, and when they should go. An example workflow ## How this work is designed to run, step by step. 3 of 9 steps exist in our development build; the others are designed, not yet built. This example shows how the stages fit together; the names and steps are generic. - 01 Request Team member → client finance contact **Ask for the year-end records.** The team member issues a Request from the engagement's Room to the client's finance contact, listing the records needed and the exact date and time access ends. In our development build - 02 Control Client finance contact **The contact opens only that Request.** Recipient access starts with a verified receiving email address. The recipient sees only that Request: who asked, what is needed and when access ends. They do not join the requesting organization. In our development build, for Request details - 03 Request Team member **Resend or revoke when plans change.** Access to a Request can be revoked, and the notification can be resent. In our development build - 04 Receive Client → engagement **Records arrive against the Request.** Documents arrive in the context of the Request they answer, not a general inbox. Designed, not yet built - 05 Use Engagement team **The team works with the records the task needs.** People work with the documents a task needs, and no more. Designed, not yet built - 06 Control Engagement lead **Access ends with the engagement.** Access is designed to end when the work does, so records are not left open after the engagement closes. Designed, not yet built - 07 Review Engagement lead **A review when the file closes.** Before anything ends, the right people can look again. Designed, not yet built - 08 Retain Firm policy **Kept for the period policy sets.** Material is kept for a period set by policy, not left by accident. Designed, not yet built - 09 Evidence Throughout **A record of each decision.** A proportionate record of what was decided, kept with privacy in mind, from the first Request to the end. Designed, not yet built In our development build ## What the other side sees today. When a Request is issued to someone outside the firm, this is their view: only that Request, who asked, what is needed and when access ends. What exists today - Issuing a Request from a Room to one named person, with instructions and an exact end to access. - Verified access to the Request details for that person, revoking access and resending the notification. - Receiving and keeping records, review at file close, retention and evidence are designed, not yet built. The recipient sees only this request: who asked, what is needed and when access ends. They do not join the requesting organisation. ## Related - [What recall can and cannot do Ending access is real. Un-sending is not.](https://docuprive.com/resources/what-recall-can-and-cannot-do/) - [Lifecycle & Evidence Retention, review, holds and the end.](https://docuprive.com/platform/lifecycle-evidence/) - [Legal & advisory An example matter workflow.](https://docuprive.com/solutions/legal-advisory/) ## Follow the build as each stage arrives. [Get product updates](https://docuprive.com/updates/) [Contact](https://docuprive.com/contact/) [All use cases](https://docuprive.com/solutions/) --- # https://docuprive.com/trust/ Trust # Trust starts with saying exactly where things stand. Your privacy shapes how we build. DocuPrivé is developed by DocuPrive, Inc. and is not yet available. This page sets out who is responsible, where the product stands, the technology DocuPrivé is built on, and how this website handles information. Our practices, documents and service providers each have their own page. Reviewed 29 October 2026 What each part of DocuPrivé covers today This website In operation. Operated by DocuPrive, Inc. You choose what to send us: a sign-up or an email. Technical information needed to deliver and protect the website is handled as the [Website Privacy Notice](https://docuprive.com/privacy/) describes. Development build Rooms, Requests and verified access to Request details. Not available to anyone. Documents Designed, not yet built. DocuPrivé holds no one's documents today. - [Overview](https://docuprive.com/trust/) - [Practices & controls](https://docuprive.com/trust/controls/) - [Documents & resources](https://docuprive.com/trust/resources/) - [Service providers](https://docuprive.com/trust/subprocessors/) [Practices & controls How we review changes to this website, protect it, handle privacy requests and design the platform.](https://docuprive.com/trust/controls/)[Documents & resources The Website Privacy Notice, the platform documents we have prepared and their status, and guides to how DocuPrivé works.](https://docuprive.com/trust/resources/)[Service providers The companies that process information for this website and its update emails, and what each one does.](https://docuprive.com/trust/subprocessors/) **On this page** - [1 Who is responsible](#responsible) - [2 Where the product stands](#status) - [3 The technology behind DocuPrivé](#technology) - [4 This website and your data](#website-data) - [5 How we talk about status](#labels) - [6 Raising a concern](#concern) On this page - [1 Who is responsible](#responsible) - [2 Where the product stands](#status) - [3 The technology behind DocuPrivé](#technology) - [4 This website and your data](#website-data) - [5 How we talk about status](#labels) - [6 Raising a concern](#concern) ## 1 Who is responsible DocuPrivé is developed by **DocuPrive, Inc.**, which also operates this website. - **Operator address:** 8 The Green, Dover, DE 19901, United States - **UK GDPR representative:** BlackCores and Partners LLP, First Floor Office, 3 Hornton Place, London W8 4LZ, United Kingdom (info@blackcores.com) - **Contact:** [support@docuprive.com](mailto:support@docuprive.com) The company is founder-led and in development. You can read about the company and its founder on the [Company page](https://docuprive.com/company/). ## 2 Where the product stands 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. **That means DocuPrivé does not hold anyone's documents today.** Nothing on this site asks you to upload a document, and nothing you do here creates a DocuPrivé account. [Development status, stage by stage Every stage and capability with its status, reviewed 28 October 2026.](https://docuprive.com/platform/status/) ## 3 The technology behind DocuPrivé DocuPrivé is built on established infrastructure and designed to fit the document environments professional teams already use. Each entry says what the service does and where things stand. Cloud infrastructure - Amazon Web Services (AWS): Selected as the primary cloud foundation for the DocuPrivé platform. The platform is being engineered for AWS; its production environment and customer-facing services are not yet in operation. Website and communications - Cloudflare: Hosts and delivers this website, protects it, and runs the security check on the sign-up form. - Brevo: Manages the product-update list and sends confirmation and update emails. Document environments professionals use - Google Drive™, Microsoft OneDrive and Microsoft SharePoint - File or link: A Request is designed to accept a file, or a link to a document held in services like these. A link is a reference: the document and its permissions stay with the service that holds it. Designed, not yet built - Connected repositories: Designed to work with material where it already lives, within what each provider supports. Designed, not yet built Names identify the services described and do not indicate a partnership, endorsement or certification. Amazon Web Services and AWS are trademarks of Amazon.com, Inc. or its affiliates. Google Drive is a trademark of Google LLC. Microsoft, OneDrive and SharePoint are trademarks of the Microsoft group of companies. [Service providers for this website](https://docuprive.com/trust/subprocessors/) ## 4 This website and your data This website is a source of information and a way to follow product updates. It does not offer accounts, logins or document uploads. - **What we collect:** If you choose to subscribe, your email address and a record of your consent. If you email us, your message. Nothing else is asked for. - **How sign-up works:** Double opt-in. You are subscribed only after you confirm by email. Unconfirmed requests are deleted after 30 days, and every email lets you unsubscribe. - **Who processes it:** Cloudflare hosts and protects the site, and Brevo manages the update list and sends update emails. [Service providers](https://docuprive.com/trust/subprocessors/) - **Abuse protection:** Sign-up attempts are rate-limited with keyed, one-way hashes instead of storing email or IP addresses in readable form. Expired records are normally deleted within 48 hours. - **Cookies and storage:** This website's own code sets no cookies. On the pages with the sign-up form, Cloudflare Turnstile keeps one essential security entry in your browser. No analytics, no advertising, no third-party embeds or fonts. - **Where sign-up is open:** Product-update sign-up is not yet open in the EEA. Full detail, including your rights where you live: [Website Privacy Notice](https://docuprive.com/privacy/). All documents in force, and those prepared for the platform: [Legal](https://docuprive.com/legal/). ## 5 How we talk about status We use two labels across this site: In our development build and Designed, not yet built. We do not use "available" for anything that is not, and we do not publish dates we cannot keep. If you find a statement on this site that goes further than this page, please tell us. - 1 **A statement** on any page, with its label in place - 2 **One status source** behind every label on this site - 3 **The status page** lists each statement, dated - 4 **Real views** from the development build where one exists ## 6 Raising a concern If you believe you have found a security issue with this website, write to [security@docuprive.com](mailto:security@docuprive.com). This contact is also published at [/.well-known/security.txt](https://docuprive.com/.well-known/security.txt). For anything on this site that you believe is inaccurate, write to [support@docuprive.com](mailto:support@docuprive.com). Please do not include sensitive documents in your message. Privacy questions and requests: [privacy@docuprive.com](mailto:privacy@docuprive.com). ## Questions about how DocuPrivé will handle documents? [Contact](https://docuprive.com/contact/) [Website privacy notice](https://docuprive.com/privacy/) [Get product updates](https://docuprive.com/updates/) --- # https://docuprive.com/trust/controls/ Privacy & Trust # How we work, and what each practice covers. Each practice says what it covers: this website, our company, or the DocuPrivé platform, which is in development. Reviewed 29 October 2026 - [Overview](https://docuprive.com/trust/) - [Practices & controls](https://docuprive.com/trust/controls/) - [Documents & resources](https://docuprive.com/trust/resources/) - [Service providers](https://docuprive.com/trust/subprocessors/) ## 1 Reviewing changes to this website This website - We use a documented process to review website changes before publication. - Each release is approved as an exact set of files, identified by a fingerprint, before it is published. - Publishing is a separate step performed by the company; the tools that build the website are not given publishing credentials. - Statements about the product are checked against a single record of what exists and what is only designed, and that record is reviewed before each release. ## 2 Protecting this website This website - These pages carry no analytics or advertising and load no third-party scripts, except the security check on the sign-up form. - A strict content security policy limits what pages can load and where forms can send information. - Sign-up rate limits use keyed one-way hashes instead of storing email or IP addresses in readable form. - Report a security concern to [security@docuprive.com](mailto:security@docuprive.com). Our security.txt file is at [/.well-known/security.txt](https://docuprive.com/.well-known/security.txt). ## 3 Privacy requests This website and update emails - To use your privacy rights, or to ask how we handle your information, write to [privacy@docuprive.com](mailto:privacy@docuprive.com). [Section 10 of the Website Privacy Notice](https://docuprive.com/privacy/#10-your-rights-and-how-to-use-them) explains your rights where you live. - Every update email lets you unsubscribe. - Writing to us or visiting this website is never treated as consent to marketing. ## 4 Designing the platform DocuPrivé platform, in development These principles shape every part of the product. They are commitments about design; where a principle depends on a stage that is not built yet, it says so. - **Access is for intended people.** It starts with a verified receiving email address, and relates to a task or a Room, not to everything an organization holds. In our development build, for Request details - **Access has an end.** Access is designed to end when the work does; in the development build every Request carries an exact end date and time and can be revoked. In our development build, for Request details - **External people stay external.** A recipient sees only the Request they were asked to answer and does not join the requesting organization. In our development build - **Content and records are kept apart.** Document content and lifecycle records are designed to be stored separately, each with its own access and retention rules. Designed, not yet built - **Decisions have owners.** Keeping, reviewing and ending material are decisions with an accountable person. Automated assistance will not decide on its own to hold, keep or dispose of material. Designed, not yet built - **Records are honest about what they prove.** A record shows that something happened in DocuPrivé. It does not prove that a person read or understood a document, and we will not present it that way. - **Customer documents are not a product.** Customer documents are not sold, used for advertising, or used to train general-purpose AI models. Designed, not yet built - **Security is described as built.** Encryption 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 - **Ending access is not un-sending.** DocuPrivé can end access it controls. It cannot reach copies already downloaded, or change permissions in someone else's system. [What recall can and cannot do](https://docuprive.com/resources/what-recall-can-and-cannot-do/) This page describes our controls by principle and by current status, so you can judge them. It leaves out implementation detail whose main use would be to attack the service. ## 5 Independent assessment Company We list an independent assessment or certification here only once it has been issued, with what it covers, who performed it and when. We do not present our providers' certifications as our own. Security questionnaires and due-diligence requests: [security@docuprive.com](mailto:security@docuprive.com). --- # https://docuprive.com/trust/resources/ Privacy & Trust # Documents and resources Public documents open directly, without registration. Drafts of the platform documents are shared on request. Reviewed 29 October 2026 - [Overview](https://docuprive.com/trust/) - [Practices & controls](https://docuprive.com/trust/controls/) - [Documents & resources](https://docuprive.com/trust/resources/) - [Service providers](https://docuprive.com/trust/subprocessors/) ## 1 Website privacy notices Website privacy notices | Document | Applies to | Version and status | Access | | Website Privacy Notice | This website and product-update emails, including cookies and browser storage | Version 2.0, Effective 29 October 2026 | [/privacy/](https://docuprive.com/privacy/) | | Website Privacy Notice 1.0 | This website and product-update emails, including cookies and browser storage | 1.0, archived, effective 13 October 2026 | [/privacy/2026-10-13/](https://docuprive.com/privacy/2026-10-13/) | ## 2 Prepared for the DocuPrivé platform Seventeen documents, prepared and not yet in force. Published before the platform is offered. Prepared for the DocuPrivé platform | Document | Applies to | Version and status | Access | | Data Processing Addendum | DocuPrivé platform | Prepared | On request | | Security and Shared Responsibility Schedule | DocuPrivé platform | Prepared | On request | | Subprocessors and Processing Locations Register | DocuPrivé platform | Prepared | On request | [All prepared documents](https://docuprive.com/legal/) Legal and compliance teams evaluating DocuPrivé can request the current drafts at [privacy@docuprive.com](mailto:privacy@docuprive.com). ## 3 Product status and guides - [Development status](https://docuprive.com/platform/status/) Status reviewed 28 October 2026. - [A file or a link?](https://docuprive.com/resources/file-vs-external-link/) - [What recall can and cannot do](https://docuprive.com/resources/what-recall-can-and-cannot-do/) - [Questions](https://docuprive.com/faq/) ## 4 Security and plain-text versions - [security.txt](https://docuprive.com/.well-known/security.txt) - Plain-text versions of our public pages, for search engines and AI assistants [/llms.txt](https://docuprive.com/llms.txt) · [/llms-full.txt](https://docuprive.com/llms-full.txt) --- # https://docuprive.com/trust/subprocessors/ Privacy & Trust # Service providers and processing The companies that process personal information for this website and its product-update emails, what each one does and what it receives. DocuPrive, Inc. remains responsible for that information. Reviewed 29 October 2026 - [Overview](https://docuprive.com/trust/) - [Practices & controls](https://docuprive.com/trust/controls/) - [Documents & resources](https://docuprive.com/trust/resources/) - [Service providers](https://docuprive.com/trust/subprocessors/) ## 1 This website and update emails This website and update emails | Provider | What it does | What it receives | | Cloudflare, Inc. | Hosts and delivers the website and provides its security services, including the sign-up endpoint, the short-lived abuse-protection records and the Turnstile check | Technical information (delivery and security data); the sign-up request while it is checked; abuse-protection records | | Brevo | Manages the product-update list and sends confirmation and update emails | Your email address with the consent and subscription information in section 4; confirmation, delivery and unsubscribe records. It may receive technical information when you open a confirmation or unsubscribe link | | A business email service | Receives the messages you send us | Your message and its ordinary email information | Where providers process information is described in [section 8 of the Website Privacy Notice](https://docuprive.com/privacy/#8-international-processing). ## 2 The DocuPrivé platform The DocuPrivé platform does not process customer data yet, so it has no subprocessors. Amazon Web Services is its selected cloud provider. The Subprocessors and Processing Locations Register, prepared for the platform, is published before the platform is offered. --- # https://docuprive.com/resources/ Resources # Questions worth asking. Resources from DocuPrivé: the Beyond the Share podcast, plain-English guides on sharing and recall, answers to common questions, and notes on where the DocuPrivé build stands. - [Podcast](#podcast) - [Guides](#guides) - [Questions](https://docuprive.com/faq/) - [Build notes](#build-notes) Podcast ## Beyond the Share A DocuPrivé podcast Beyond the Share explores the decisions that remain after information is shared. Anna and Kevin talk through workplace technology, document access, privacy, information governance and professional responsibility, in plain language. [About the show and all episodes](https://docuprive.com/resources/beyond-the-share/) - EP02 October 16, 2026 Your AI Meeting Notes Say You Agreed. You Didn't. [Listen on Spotify](https://open.spotify.com/episode/6A87KTIrIL8HYNSEVOL3ur) - EP01 October 16, 2026 Your AI Might Find That Forgotten File [Listen on Spotify](https://open.spotify.com/episode/2WatLCwLLerLQRpOV6iC0V) Guides ## Plain-English guides. Vendor-neutral explanations of what happens to a document after it is shared. - [A file and a link, side by side Send a file You Their copy What you hand over A copy Who controls it after The recipient and their systems Can it be ended? Only by asking Share a link You A pointer What you hand over A way to reach it Who controls it after The system holding the document Can it be ended? Yes, if that system allows it, but not a download Guide A file or a link? What changes when you share each. Sharing a copy and sharing a pointer feel the same. They are not. Who controls access afterwards, and what ending access can actually reach. Read the guide](https://docuprive.com/resources/file-vs-external-link/) - [What ending access reaches Can stop Opening it again through the system that shared it A link or permission that system controls Access on a set date, if it was planned Cannot reach A copy already downloaded or saved A forwarded email or attachment Permissions in someone else's system A printed page, a screenshot, a photo of a screen Guide What recall can and cannot do. Ending access is real. Un-sending is not. What any platform can stop after sharing, and what stays out of reach. Read the guide](https://docuprive.com/resources/what-recall-can-and-cannot-do/) Build notes ## Where the build stands. Our current work is on the foundations: identity, Rooms, Requests, and access for the people you ask. Handling documents themselves belongs to later stages. We will describe each part when it is ready, and we will not publish dates we cannot keep. Status reviewed 28 October 2026. [Development status, stage by stage](https://docuprive.com/platform/status/) [Questions Straight answers. What DocuPrivé is, what the development build covers, how this website handles data, and what product-update emails contain. All questions](https://docuprive.com/faq/) ## Follow what comes next. [Get product updates](https://docuprive.com/updates/) [How it works](https://docuprive.com/platform/) --- # https://docuprive.com/resources/beyond-the-share/ Podcast # Beyond the Share A DocuPrivé podcast about the decisions that remain after information is shared. 2 episodes published · audio on Spotify Latest episode EP02 · October 16, 2026 Your AI Meeting Notes Say You Agreed. You Didn't. [Listen on Spotify](https://open.spotify.com/episode/6A87KTIrIL8HYNSEVOL3ur) ## About the show Beyond the Share explores the decisions that remain after information is shared. Anna and Kevin talk through workplace technology, document access, privacy, information governance and professional responsibility, in plain language. From emerging technology to everyday business decisions, we look at what organizations should understand, question and reconsider. Anna and Kevin are AI-generated voices performing scripts written by the DocuPrivé Studio team. General information only; not legal, security or financial advice. docuprive.com · @docuprive on Instagram and X ## Episodes Published episodes only, newest first. - EP02 October 16, 2026 **Your AI Meeting Notes Say You Agreed. You Didn't..** [Listen on Spotify](https://open.spotify.com/episode/6A87KTIrIL8HYNSEVOL3ur) - EP01 October 16, 2026 **Your AI Might Find That Forgotten File.** [Listen on Spotify](https://open.spotify.com/episode/2WatLCwLLerLQRpOV6iC0V) ## Related guides - [A file or a link? What changes when you share a copy instead of a pointer.](https://docuprive.com/resources/file-vs-external-link/) - [What recall can and cannot do Ending access is real. Un-sending is not.](https://docuprive.com/resources/what-recall-can-and-cannot-do/) - [All resources Guides, podcast, questions and build notes.](https://docuprive.com/resources/) ## Follow what comes next. [Get product updates](https://docuprive.com/updates/) [All resources](https://docuprive.com/resources/) --- # https://docuprive.com/resources/file-vs-external-link/ Guide Updated October 29, 2026 # A file or a link? What changes when you share each. Sharing a copy and sharing a pointer feel the same. They are not. The short answer A file hands over a copy that the recipient then controls. A link hands over a way to reach a document that stays under the rules of the system holding it. Links can be ended; files can only be asked to end, and any download turns a link back into a file. A file and a link, side by side Send a file You Their copy - **What you hand over:** A copy - **Who controls it after:** The recipient and their systems - **Can it be ended?:** Only by asking Share a link You A pointer - **What you hand over:** A way to reach it - **Who controls it after:** The system holding the document - **Can it be ended?:** Yes, if that system allows it, but not a download You attach a document to an email, or you paste a link to the same document. On your screen the two actions take the same few seconds, and the person at the other end can open the document either way. What happens next is very different, and most of it is decided at the moment you choose. This guide explains the difference in plain terms, and ends with a short checklist for choosing between them. ## What you actually hand over When you send a **file**, you hand over a copy. The recipient now has their own instance of the document. It sits in their inbox, then often in their downloads folder, their device backup, perhaps a shared drive at their firm. Each of those is a separate copy, governed by whoever runs that place. When you send a **link**, you hand over a pointer. The document stays where it was. The recipient gets a way to reach it, under whatever rules the system holding it applies: who may open it, whether it can be downloaded, and for how long the link works. A useful test is to ask: if I changed my mind tomorrow, what would still be in their hands? With a file, the answer is the file. With a link, the answer depends on the link, the system behind it, and what the recipient did while they had access. ## Who controls access afterwards A sent file is controlled by its recipient. Your firm's rules stop at the edge of your own systems. The recipient's firm decides how long its mailboxes keep attachments, who can search them, and how they are backed up. You can ask them to delete a copy, but you are asking, not deciding. A link keeps control with the system that holds the document. That can be a real advantage: access can be limited to named people, given an end date, or withdrawn. It also means the link is only as good as that system's settings. A link that anyone with the address can open behaves, in practice, much like a file that can be passed on. There is one more thing a link quietly carries: responsibility. When you link to material held somewhere else, that other system's rules, security and retention apply to it. Choosing a link is also choosing whose rules govern the document. ## What happens when access ends With a link, ending access is a real action. If the system holding the document supports it, you can withdraw the link or let it expire, and the pointer stops working. The next person who clicks it sees nothing. With a file, there is no equivalent action. The copy you sent does not have an off switch. Some tools offer to retract a message shortly after sending, but whether that works depends on systems you do not control, and it cannot reach a copy that has already been opened and saved. So the honest summary is this: links can end; files can only be asked to end. ## What happens to downloaded copies Links are not a complete answer either. If a link allows downloading, a recipient who downloads the document now holds a file, with everything that implies. Ending the link afterwards stops further access through the link. It does not reach the download. The same is true of anything a recipient copies by hand: a printed page, a screenshot, a paragraph pasted into another document, a photo of a screen. No sharing method can reach those. What a good system can do is make the boundary clear, limit downloading where the work allows, and keep a record of what was shared, with whom and until when. This is why the moment of sharing matters so much. Most of the control you will ever have is the control you choose to keep when you decide how to share. ## Links can travel too A link is a short piece of text, and short pieces of text are easy to pass on. A recipient can forward it to a colleague, paste it into a chat, or save it in a note. Whether the next person can open it depends entirely on how the link was set up: limited to named people, or open to anyone who has the address. Links are also opened by software, not only by people. Email security tools often open links automatically to check them for threats, and messaging apps may fetch a link to build a preview. A record that a link was "opened" can therefore reflect a machine, not a reader. That matters later, when someone asks who saw the document and when. ## When each one makes sense Neither choice is wrong in itself. A file can be the right answer when the recipient genuinely needs their own copy: a signed agreement they must keep, a document they are obliged to retain under their own rules. In that case the honest step is to accept that the copy is theirs, and to record that you sent it. A link usually fits better when the work is temporary: a review that runs for a few weeks, a set of documents for a meeting, material a colleague at another firm needs to see but not to keep. There, the ability to end access is the point. ## A short checklist before you share - **Does the recipient need to keep a copy?** If not, prefer a link that you can end. - **Who exactly should be able to open it?** Prefer access limited to named people over a link anyone can forward. - **For how long?** Decide an end date now, while you still remember why you shared it. - **Should downloading be allowed?** Every download turns a link back into a file. - **Where will the record live?** Know where you can later see what you shared, with whom, and until when. None of these questions needs special software to answer. They do need to be asked before the document leaves, because afterwards most of the answers are no longer yours to give. How this applies ## In DocuPrivé - A 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 - Recall 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 built - Request details already stay with one verified recipient for a defined period, and access to a Request can be revoked. In our development build, for Request details [Development status](https://docuprive.com/platform/status/) ## Keep reading - [What recall can and cannot do Ending access is real. Un-sending is not.](https://docuprive.com/resources/what-recall-can-and-cannot-do/) - [Share & Recall How access is designed to work in DocuPrivé.](https://docuprive.com/platform/share-recall/) - [Legal & advisory An example matter workflow.](https://docuprive.com/solutions/legal-advisory/) ## Follow what comes next. [Get product updates](https://docuprive.com/updates/) [All resources](https://docuprive.com/resources/) --- # https://docuprive.com/resources/what-recall-can-and-cannot-do/ Guide Updated October 29, 2026 # What recall can and cannot do. Ending access is real. Un-sending is not. The short answer Recall can end access that the sharing system still controls: the link, the permission, the next attempt to open the document there. It cannot reach copies already downloaded, forwarded or saved elsewhere, or change permissions in someone else's system. What ending access reaches Can stop - Opening it again through the system that shared it - A link or permission that system controls - Access on a set date, if it was planned Cannot reach - A copy already downloaded or saved - A forwarded email or attachment - Permissions in someone else's system - A printed page, a screenshot, a photo of a screen "Recall" is a reassuring word. It suggests that something sent can be called back, as if it had never left. In practice, recall can do one important thing well, and several things not at all. Knowing which is which is part of handling other people's documents responsibly. ## What "recall" means across tools Different tools use the word for different actions. In one, it means asking a mail system to retract a message that has not yet been opened. In another, it means disabling a shared link. In a third, it means removing a person's permission to a folder or a workspace. Some tools say "revoke" or "unshare" for the same idea. These are not the same action, and they do not have the same reach. Before relying on any of them, it helps to ask a precise question: what exactly stops when I press this button, and what does not? ## What any platform can end A platform can end access that it controls. If a document lives in a system and a person reaches it through that system, the system can stop letting them in. Their link stops working, their permission disappears, their next attempt to open the document fails. That is real, and it is valuable. It is the right way to close access when a piece of work ends, when a person changes role, or when something was shared with the wrong person and has not yet been opened or downloaded. The sooner it happens, the more it protects. A platform can also record that access ended: when, by whom, and for which person. That record is part of being able to account for a decision later. ## What it cannot reach No platform can reach what has already left its control. In particular: - **Downloaded copies.** Once a document is saved to someone's device, it is a separate file under their control. - **Forwarded copies.** If the document or its contents were sent on, each new copy is outside the original system. - **Other systems' permissions.** A platform cannot change who may open a document inside someone else's system, mailbox or drive. - **Screenshots, photos and printouts.** Anything captured from a screen or put on paper is beyond any software's reach. - **What a person has read.** Ending access cannot make someone forget what they saw. None of this is a failure of a particular tool. It is the nature of copies. Every system that holds documents shares the same boundary. ## Why honest wording matters If a client is told that a document "has been recalled", they may believe the matter is closed when it is not. A copy may still sit on a device, in a backup, or in another firm's system. Decisions taken on that belief can make the real position worse. It is more accurate, and more useful, to say what actually happened: "Access through our system ended at 4:10 p.m. The recipient had opened the document once before that." That sentence tells everyone what remains to be done, if anything, such as asking the recipient to delete a downloaded copy and to confirm that they have. The same care applies to records. A record that shows a document was opened shows that an event happened in a system. It does not prove that a person read it, understood it or agreed with it. Some email security tools open links automatically to check them, before any person does. ## What to record when you end access Ending access is a decision, and decisions are easier to account for when they are written down at the time. A short record is enough: - **What** was shared, and with whom. - **When** access started, and when it ended. - **Why** it ended: the work finished, the wrong person received it, or a client asked. - **What happened before** it ended, as far as you can tell: whether the document was opened or downloaded. - **What you asked for next**, such as deletion of a downloaded copy, and the answer you received. Kept plainly, a record like this answers the questions that tend to come later from a client, a colleague or a regulator, without relying on anyone's memory. ## When recall is not enough Sometimes ending access is only the first step. If a document reached the wrong person, or was downloaded before access ended, the remaining copies are outside any system's reach. What is left is ordinary professional practice: contact the recipient, explain what happened, ask them to delete the copy, and ask them to confirm in writing that they have. Depending on what the document contained and who it concerned, your own professional or legal obligations may require further steps, such as informing the person the information is about. Those obligations come from your rules, not from the tool you used, and they apply whatever the tool calls its button. ## Practical steps before you share - **Prefer access you can end** over copies you cannot, when the recipient does not need to keep the document. - **Share with named people**, not with anyone who has the link. - **Set the end now.** Decide when access should stop while the purpose is still clear. - **Think before allowing downloads.** Each download creates a copy that recall cannot reach. - **Say what recall means** in your own instructions, so clients and colleagues do not assume more than it can do. Recall is at its best as one part of a considered process: ask for only what the work needs, share it with the right people for the right period, end access when the work ends, and record each step plainly. Ending access is real. Un-sending is not. Both statements can be true at once, and it helps everyone to say both. How this applies ## In DocuPrivé - Access to a Request can be revoked, and the notification can be resent. In our development build, for Requests - Recall 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 built - A record shows an event happened in DocuPrivé. It does not prove a person read or understood a document. Designed, not yet built [Development status](https://docuprive.com/platform/status/) ## Keep reading - [A file or a link? What changes when you share a copy instead of a pointer.](https://docuprive.com/resources/file-vs-external-link/) - [Share & Recall How access is designed to work in DocuPrivé.](https://docuprive.com/platform/share-recall/) - [Lifecycle & Evidence Retention, review, holds and the end.](https://docuprive.com/platform/lifecycle-evidence/) ## Follow what comes next. [Get product updates](https://docuprive.com/updates/) [All resources](https://docuprive.com/resources/) --- # https://docuprive.com/company/ Company # A document is more than a file. It is a responsibility. DocuPrivé is document lifecycle infrastructure for professional teams, in development by DocuPrive, Inc. It is designed to request, share, govern and bring to an end sensitive documents, with clear boundaries at each stage. DocuPrive, Inc. Develops DocuPrivé · founder-led · in development - **Founder:** Lucen Law - **Correspondence address:** 8 The Green, Dover, DE 19901, United States - **Contact:** [support@docuprive.com](mailto:support@docuprive.com) DOCUPRIVÉ — Beyond the Share Purpose ## Why DocuPrivé exists. The responsibility doesn't end when the document is shared. Professionals are trusted with other people's papers: identity documents, accounts, contracts, family records. Sending them is easy. Knowing who still has them, for how long, and who decided, is not. DocuPrivé is being built for that part of the work. Our principles ## Clear boundaries deserve clear explanations. - 01 **Intended people.** Access is meant for the people you choose, starting with a verified receiving email address. - 02 **Specific work.** Access relates to a task or a Room, not to everything an organization holds. - 03 **An appropriate period.** Access is designed to end when the work does. - 04 **An accountable next step.** Keeping, reviewing and ending material are decisions with an owner, not defaults left behind. How we work today ## Building in stages, with status in the open. - Now **The foundations.** Identity, Rooms, Requests, and access for the people you ask. Today's development build covers Rooms, issued Requests and verified access to Request details. In our development build - Later stages **Handling documents themselves.** Receiving, organizing, keeping, reviewing and bringing documents to an end. We will describe each part when it is ready, and we will not publish dates we cannot keep. Designed, not yet built - Throughout **Status in the open.** DocuPrivé is in development and is not yet available for use. Every capability on this website carries its status, from one source. [Development status](https://docuprive.com/platform/status/) Founder ## Lucen Law Founder, DocuPrive, Inc. Company facts ## Where to find us. - **Company:** DocuPrive, Inc. - **Correspondence address:** 8 The Green, Dover, DE 19901, United States - **Contact:** [support@docuprive.com](mailto:support@docuprive.com) - **Elsewhere:** [LinkedIn](https://www.linkedin.com/company/docuprive/)[Instagram](https://www.instagram.com/docuprive)[X](https://x.com/docuprive) - **Legal information:** [Legal](https://docuprive.com/legal/) · [Website privacy notice](https://docuprive.com/privacy/) ## Get in touch, or follow what comes next. [Contact](https://docuprive.com/contact/) [Partnership enquiries](https://docuprive.com/partners/) [Get product updates](https://docuprive.com/updates/) --- # https://docuprive.com/contact/ Contact # How to reach DocuPrivé. DocuPrivé is reached by email. Questions go to support@docuprive.com, privacy requests to privacy@docuprive.com and security concerns to security@docuprive.com. Product news comes by email sign-up. There is no contact form. ## Questions about DocuPrivé [support@docuprive.com](mailto:support@docuprive.com) Anything about the product, the company or this website. **Include:** Your question, and how you would like us to reply. ## Privacy questions and requests [privacy@docuprive.com](mailto:privacy@docuprive.com) Requests about your information, with "Privacy" in the subject line. Your rights are set out in the website privacy notice. **Include:** What you are asking for, and the email address it concerns. ## Security concerns [security@docuprive.com](mailto:security@docuprive.com) If you believe you have found a security issue with this website. Please do not include sensitive documents. **Include:** What you found, where, and how to reproduce it. ## Partnership enquiries [support@docuprive.com](mailto:support@docuprive.com) Professional firms, advisers and technology teams, with "Partnership" in the subject line. **Include:** Who you are, your organization, and what you have in mind. [How enquiries work](https://docuprive.com/partners/) ## Please do not send documents. Please send only what your message needs. Do not send passwords, identity documents, confidential client files or other sensitive personal information by email or through this website. DocuPrivé is not yet available and cannot receive documents. ## Your message and your data. If you email us, we use your message to reply, as set out in the [website privacy notice](https://docuprive.com/privacy/). Writing to us does not sign you up for product updates. ## Product news. Occasional product news by email, double opt-in. [Get product updates](https://docuprive.com/updates/) ## Also. - [Questions](https://docuprive.com/faq/) Straight answers about DocuPrivé, the development build and this website. - [Company](https://docuprive.com/company/) DocuPrive, Inc., its founder and its correspondence address. - [LinkedIn](https://www.linkedin.com/company/docuprive/)[Instagram](https://www.instagram.com/docuprive)[X](https://x.com/docuprive) DocuPrivé on social media. --- # https://docuprive.com/faq/ Questions # Straight answers. Answers about what DocuPrivé is, what the development build covers today, how this website handles data, and what product-update emails contain. If your question is not here, write to support@docuprive.com. - [About DocuPrivé 4](#about) - [The development build 7](#build) - [Data and privacy 3](#data) - [Product updates 4](#updates) ## About DocuPrivé 4 answers **What is DocuPrivé?** DocuPrivé is document lifecycle infrastructure for professional teams, in development by DocuPrive, Inc. It is designed to request, share, govern and bring to an end sensitive documents, with clear boundaries at each stage. **Can I use DocuPrivé today?** Not yet. DocuPrivé is in development and is not yet available for use. This website introduces the product and lets you follow its progress; it does not offer accounts or document uploads. **Who is DocuPrivé for?** Professionals who request, share and look after sensitive documents for others, including legal and advisory, accounting and audit, due diligence and private-client teams. **Who is behind DocuPrivé?** DocuPrivé is developed by DocuPrive, Inc., a founder-led company. You can read more on the Company page. ## The development build 7 answers **What exists today?** 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. **What do the two status labels mean?** "In our development build" means the capability exists in the development build and is shown with example data; it is not available to anyone. "Designed, not yet built" means it is an approved design direction that has not been built. **Can a Request be changed after it is issued?** No. Once issued, a Request's details are fixed. Access can be revoked and the notification resent. **Can DocuPrivé delete a copy someone downloaded?** No. Recall is designed to end access that DocuPrivé controls. It cannot reach copies already downloaded, or change permissions in someone else's system. **Does a folder control who sees a document?** No. In the Library & Search design, a folder is where a document sits, not a permission. Access comes from the work the document belongs to. This is designed and not yet built. **Can a record prove that someone read a document?** No. A record shows that an event happened in DocuPrivé. It does not prove that a person read or understood a document. **Will automated assistance decide what happens to documents?** Automated assistance will not decide on its own to hold, keep or dispose of material. Those decisions have an accountable person. ## Data and privacy 3 answers **Does DocuPrivé use cookies?** This website's own code sets no cookies. On the pages with the sign-up form, Cloudflare Turnstile keeps one essential security entry in your browser to tell people from automated abuse. There are no analytics or advertising, so there is no consent banner. **What happens to my email if I subscribe?** Your email address and a record of your consent go to our email provider, which sends you a confirmation email. You are subscribed only after you confirm. Unconfirmed requests are deleted after 30 days, every email lets you unsubscribe, and after you unsubscribe we keep only a minimal record so we do not contact you again. **Does this website hold any of my documents?** No. Nothing on this website asks you to upload a document, and DocuPrivé does not hold anyone's documents today. ## Product updates 4 answers **What will the emails contain?** Occasional product-development news, platform updates and launch announcements from DocuPrivé. No third-party marketing. **Does subscribing reserve access to the platform?** No. It is a product-updates subscription, not an access list, a place in a queue or a promise of a release date. **Can I unsubscribe?** Yes, at any time and without giving a reason. Every product-update email includes an unsubscribe link. For anything else, write to support@docuprive.com. **Can I subscribe from the European Economic Area?** Product-update sign-up is not yet open in the EEA. You can still read everything on this website. ## A question we haven't answered? [Contact](https://docuprive.com/contact/) [Get product updates](https://docuprive.com/updates/) --- # https://docuprive.com/privacy/ Legal · In force # Website Privacy Notice How DocuPrive, Inc. handles information on this website and in product-update emails. DP-PN-WEB · Version 2.0 · Effective 29 October 2026 · DocuPrive, Inc. - **Version:** 2.0 - **Effective:** 29 October 2026 - **Responsible:** DocuPrive, Inc. - **Earlier version:** [1.0, effective 13 October 2026](https://docuprive.com/privacy/2026-10-13/) **Contents (14 sections)** - [1. At a glance](#1-at-a-glance) - [2. Who is responsible](#2-who-is-responsible) - [3. Scope](#3-scope) - [4. What we collect and why](#4-what-we-collect-and-why) - [5. Cookies and browser storage](#5-cookies-and-browser-storage) - [6. Service providers](#6-service-providers) - [7. What we do not do](#7-what-we-do-not-do) - [8. International processing](#8-international-processing) - [9. Security](#9-security) - [10. Your rights and how to use them](#10-your-rights-and-how-to-use-them) - [11. Children](#11-children) - [12. Changes and versions](#12-changes-and-versions) - [13. Public pages, search engines and AI assistants](#13-public-pages-search-engines-and-ai-assistants) - [14. Contact and complaints](#14-contact-and-complaints) Contents - [1. At a glance](#1-at-a-glance) - [2. Who is responsible](#2-who-is-responsible) - [3. Scope](#3-scope) - [4. What we collect and why](#4-what-we-collect-and-why) - [5. Cookies and browser storage](#5-cookies-and-browser-storage) - [6. Service providers](#6-service-providers) - [7. What we do not do](#7-what-we-do-not-do) - [8. International processing](#8-international-processing) - [9. Security](#9-security) - [10. Your rights and how to use them](#10-your-rights-and-how-to-use-them) - [11. Children](#11-children) - [12. Changes and versions](#12-changes-and-versions) - [13. Public pages, search engines and AI assistants](#13-public-pages-search-engines-and-ai-assistants) - [14. Contact and complaints](#14-contact-and-complaints) Print this notice This notice covers the docuprive.com website and the product-update emails you can choose to receive. It is written to be read in full: each fact below describes how the website works today. This notice is for information. Where we need your consent, we ask for it separately and specifically. ## 1. At a glance - **We collect very little.** If you sign up for product updates, we collect your email address and a record of your consent. If you email us, we receive your message. Nothing else is asked for. - **No account is created.** Visiting this website or subscribing does not create a DocuPrivé account, and nothing on this website accepts documents. - **No analytics, advertising or tracking on this website.** Our own code sets no cookies. The only browser storage comes from Cloudflare Turnstile, a security check on the pages with the sign-up form. - **We do not sell or share your information for advertising**, and we do not use it to train AI models. - **Two service providers** process website and sign-up information for us: Cloudflare, which hosts and protects the website, and Brevo, which manages the update list and sends confirmation and update emails. ## 2. Who is responsible DocuPrive, Inc. (“DocuPrivé”, “we”, “us”) is responsible for the information described in this notice. - **Correspondence address:** DocuPrive, Inc., 8 The Green, Dover, DE 19901, United States - **Privacy questions and requests:** [privacy@docuprive.com](mailto:privacy@docuprive.com) - **Representative in the United Kingdom** under Article 27 of the UK GDPR: BlackCores and Partners LLP, First Floor Office, 3 Hornton Place, London W8 4LZ, United Kingdom ([info@blackcores.com](mailto:info@blackcores.com)) ## 3. Scope This notice covers only this website (docuprive.com and [www.docuprive.com](http://www.docuprive.com)), the product-update emails, and messages you send us. The DocuPrivé platform is in development and is not covered here. It will have its own privacy notice, published before any account is opened or any document is processed. Visiting this website, subscribing or reading this notice does not create an account and does not authorize any processing of your documents, connection to your systems, use of AI on confidential material, or transfer of the update list into a customer system. Any such processing will require a specific feature, terms and instruction. ## 4. What we collect and why | Information | Why we use it | Legal basis, where the law requires one | Who processes it | How long we keep it | | **Technical information** sent by your browser when a page is requested, such as IP address, page requested, time, browser and device type, and connection details | To deliver the website and protect it from abuse | Our legitimate interest in running a reliable, secure website | Cloudflare, as our hosting and delivery provider | Under Cloudflare’s own log retention; we do not keep a separate copy | | **The Turnstile check**, on the pages with the sign-up form only (the home page and /updates/), when the form comes into view or you select the email field: technical signals from your browser | To tell people from automated abuse before a sign-up is accepted | Our legitimate interest in preventing abuse of the form | Cloudflare (Turnstile runs in your browser and communicates directly with Cloudflare). Cloudflare also uses these signals, under its Turnstile privacy terms, to improve its bot detection. | See section 5 for the one browser storage entry it uses | | **Sign-up data:** your email address; the consent wording version shown, the form it came from and the time of the request; whether you confirmed; any later withdrawal | To confirm your subscription, send product updates you asked for, and stop them when you unsubscribe | Your consent (product-update emails); our legitimate interest in administering the list and honoring an unsubscribe | Brevo, as our email provider | Unconfirmed requests: deleted after 30 days. Confirmed subscription: while you stay subscribed and the update service runs. After you unsubscribe, or after a complaint or a delivery block: only a minimal suppression record, so we do not contact you again | | **Abuse-protection records:** short-lived counters linked to keyed, one-way hashes of the email address and IP address used for a sign-up | To limit repeated or automated sign-ups. The records are kept separately from the update list | Our legitimate interest in preventing abuse | Cloudflare (on our behalf) | Counters cover periods of up to 24 hours; expired records are normally deleted from our active systems within 48 hours | | **Messages you send us**, with your email address, attachments and ordinary email header information, and our replies | To answer you, keep a record of the exchange and manage any business relationship that follows | Our legitimate interest in responding; steps you ask for before a contract; legal obligations where they apply | Our business email service | While we deal with your message, then only as long as needed for follow-up, our records, or a legal obligation or claim. How long depends on the subject and whether it led to an ongoing relationship | Where we rely on legitimate interests, we balance them against your rights and reasonable expectations. Some processing may also be needed to take steps you ask for before a contract, to meet a legal obligation, or to establish, exercise or defend legal claims. If the security check fails, expires or is unavailable, the form will not submit. Automated anti-abuse checks may block or delay a sign-up. They exist only to protect the website and prevent unwanted email; they are not a judgement about you and are not used to make decisions with legal or similarly significant effects. If you believe a sign-up was wrongly blocked, write to [privacy@docuprive.com](mailto:privacy@docuprive.com). Hashed (pseudonymised) information can still be personal information, and we treat it as such. Cloudflare also asks browsers to send it network error reports (Network Error Logging) when a connection to the website fails; these reports contain technical connection details and go to Cloudflare, not to us. Our own sign-up code does not record raw email addresses, IP addresses, form contents or security tokens in its logs. Its logs hold the time, a request reference from Cloudflare, the processing step, the outcome and timing. When a sign-up request arrives, Cloudflare tells our sign-up endpoint which country the request comes from. We use it only to decline sign-ups from the European Economic Area, which is not yet open for product updates, and we do not store it. Product updates cover DocuPrivé’s development, platform news and launch announcements. They are optional. You subscribe by ticking a separate consent box, which is never pre-ticked, and then confirming through the email sent to your address; an address is not added to the update list until it is confirmed. If someone enters your address without your permission, you can ignore the confirmation email: no updates are sent unless the address is confirmed. The update list never requires payment details, documents, professional credentials or proof of identity, and you can use the whole website without subscribing. Please send only what your message needs. Do not send passwords, identity documents, confidential client files or other sensitive personal information by email or through this website. ### 4a. How long we keep information We keep information only as long as needed for its purpose, unless a legal requirement, an unresolved security incident or a legal claim requires us to keep it longer, and then only to the extent needed. Provider logs and backups follow those providers’ own retention periods; information restored from a backup is used only for recovery, with suppression and deletion choices reapplied. Records of consent, withdrawal and privacy requests are kept only as long as needed to show what was requested and how we responded. ## 5. Cookies and browser storage Our own code sets no cookies and uses no other browser storage. There is no consent banner because nothing optional runs: no analytics, no advertising, no social-media embeds and no third-party fonts. | Name | Set by | Purpose | Category | Where | How long | | cf.turnstile.u (local storage, under challenges.cloudflare.com) | Cloudflare Turnstile | Keeps state for the anti-abuse check on the sign-up form | Strictly necessary security | Pages with the sign-up form only, once Turnstile has loaded | Browser local storage has no automatic expiry. It may remain until Cloudflare removes it or you clear it in your browser | When we measured the sign-up form, we observed no cookies. Cloudflare’s security services may set strictly necessary cookies or storage to protect the website, for example when bot protection is active. We will update this table if our configuration changes, and we will ask for your consent before using anything that is not strictly necessary. You can block or clear storage in your browser. The website stays readable without JavaScript; the sign-up form needs JavaScript for its security check and will not submit without it. ### 5a. Email measurement Product-update emails, sent by our email provider, contain standard links and a small image that the provider uses to measure opens and clicks. We have set our account so that opens and clicks are not recorded for subscribers who have not agreed to it, and we do not use opens or clicks to profile anyone. If you follow a link to another service, that service’s own privacy practices apply. ## 6. Service providers | Provider | Role | What it receives | | Cloudflare, Inc. | Hosts and delivers the website and provides its security services, including the sign-up endpoint, the short-lived abuse-protection records and the Turnstile check | Technical information (delivery and security data); the sign-up request while it is checked; abuse-protection records | | Brevo | Manages the product-update list and sends confirmation and update emails | Your email address with the consent and subscription information in section 4; confirmation, delivery and unsubscribe records. It may receive technical information when you open a confirmation or unsubscribe link | | A business email service | Receives the messages you send us | Your message and its ordinary email information | Each provider receives only what its function requires and is bound by appropriate contractual terms. We remain responsible for our own obligations. Our email provider deletes delivery logs after one month and does not keep copies of the emails it sends for us. We may also share relevant information with professional advisers bound by confidentiality; where the law requires it; where necessary to protect rights, safety or security; or in connection with a genuine business transaction under confidentiality and purpose restrictions. Any successor must continue to respect the choices you have made. ## 7. What we do not do - We do not sell information collected through this website, or share it for cross-context behavioral advertising. - We do not use analytics, advertising pixels, session recording, chat widgets, profiling or social-media embeds. - We do not load third-party scripts or fonts, except Cloudflare Turnstile on the pages with the sign-up form. - We do not use subscription or inquiry information to train AI models. - We do not use this information for a materially new purpose without first giving notice and, where required, asking for fresh consent. ## 8. International processing Our providers and their support teams may process information in countries other than your own, including Australia, Canada, Denmark, the European Union, Indonesia, Israel, Japan, Malaysia, Mexico, New Zealand, the Republic of Korea, Singapore, South Africa, Sweden, Switzerland, Thailand, Ukraine, the United Arab Emirates, the United Kingdom, the United States and Vietnam. Where the law requires safeguards for an international transfer, we put appropriate safeguards in place before the transfer, such as an adequacy decision or approved contractual clauses. You can ask [privacy@docuprive.com](mailto:privacy@docuprive.com) for details of the recipients, locations and safeguards that apply. ## 9. Security - We protect information with safeguards appropriate to the risks, including restricted administrative access, protected credentials and review of security issues, and we assess our providers for the functions they perform. We do not publish security configuration in detail where that would weaken it. - The website is served over HTTPS only. - A strict Content Security Policy allows scripts, styles, images, fonts and media only from docuprive.com itself, with one exception for Cloudflare Turnstile. - Turnstile is the only third-party script, and it loads only on the pages with the sign-up form. - Sign-up attempts are rate-limited using keyed, one-way hashes instead of storing email or IP addresses in readable form. - Our own sign-up code keeps no raw email addresses, IP addresses or form contents in its logs. No website or email system is immune to attack. If a security incident affects your information, we will notify you and the relevant authorities where the law requires. To report a security concern, write to [security@docuprive.com](mailto:security@docuprive.com). ## 10. Your rights and how to use them Depending on the law that applies to you, you may have the right to know how your information is processed, to get a copy of it, to correct it, to have it deleted, to restrict or object to its processing, to receive it in a portable format, to withdraw consent at any time, and to appeal a decision about your request. You can object to direct marketing at any time. **How to make a request.** Email [privacy@docuprive.com](mailto:privacy@docuprive.com) with “Privacy” in the subject line, saying which subscription or message it concerns and what you would like us to do. You do not need an account. We verify requests proportionately and will not ask for identity documents for routine requests. If someone acts for you, we will check their authority. We respond within the time the law requires and explain any refusal, extension or appeal route that applies. We do not charge a fee unless the law permits it. **Withdrawing consent.** Use the unsubscribe link in any update email, or write to [privacy@docuprive.com](mailto:privacy@docuprive.com). Withdrawal stops further updates; it does not affect anything done before. Submitting the form again does not reverse a withdrawal; if you want to resubscribe after unsubscribing, contact us. Unsubscribing keeps working even when new sign-ups are paused. Product updates are kept separate from replies to privacy requests, security notices and enquiries, and an enquiry, a website visit or any future document invitation is never treated as consent to marketing. **Where each law applies:** | Where | What applies | | European Economic Area | Product-update sign-up is not yet open in the EEA. If EU data-protection law applies to information we hold about you, for example from an email you sent us, you have the rights above and may complain to a supervisory authority, in particular where you live or work or where an alleged infringement occurred | | United Kingdom | You have the rights above under UK data-protection law and may complain to the Information Commissioner’s Office. Our UK representative is named in section 2 | | Switzerland | You have the corresponding rights under Swiss data-protection law and may contact the Federal Data Protection and Information Commissioner | | California and other US states | We do not sell or share personal information, and we use no optional tracking, so there is nothing for an opt-out or a Global Privacy Control signal to switch off. Where a state law gives you rights, including an appeal of our decision, you can use them through [privacy@docuprive.com](mailto:privacy@docuprive.com), and we will not discriminate against you for doing so | | Canada | You may request access to or correction of your information and may complain to the Office of the Privacy Commissioner of Canada or the competent provincial authority | | Hong Kong | You have rights of access and correction under the Personal Data (Privacy) Ordinance and may complain to the Office of the Privacy Commissioner for Personal Data | | Singapore | You may request access to or correction of your information under the Personal Data Protection Act and may complain to the Personal Data Protection Commission | You may use any statutory complaint route without first using ours. Our location in the United States does not limit the rights you have under your local law. ## 11. Children The website and product updates are meant for adults working with professional or business documents and are not directed to children. If you believe a child or anyone else has given us information they should not have, write to [privacy@docuprive.com](mailto:privacy@docuprive.com) and we will deal with it promptly. ## 12. Changes and versions We update this notice when our processing or the law changes, and show the version and effective date at the top. We give appropriate notice of material changes, and we will not start a new consent-based use without your consent. | Version | Effective | Summary | | DP-PN-WEB 2.0 | 29 October 2026 | Rewritten for the new website in plain American English, with a single table of what we collect, a cookies and storage table, regional rights by place, and new privacy and security contacts. What the website collects and loads is unchanged. | | DP-PN-WEB 1.0 | 13 October 2026 | First website privacy notice. [Archived version](https://docuprive.com/privacy/2026-10-13/) | ## 13. Public pages, search engines and AI assistants Our public pages, including this notice, are meant to be found and summarized by search engines and AI assistants; we also publish plain-text versions of them for that purpose (llms.txt and llms-full.txt). Subscription records, correspondence, confirmation links and any private systems are not public and are not made available to them. Search engines and AI services decide independently how they rank, summarize or store public content, under their own policies. ## 14. Contact and complaints - Privacy questions and requests: [privacy@docuprive.com](mailto:privacy@docuprive.com), with “Privacy” in the subject line - Security concerns: [security@docuprive.com](mailto:security@docuprive.com) - Everything else: [support@docuprive.com](mailto:support@docuprive.com) - By post: DocuPrive, Inc., 8 The Green, Dover, DE 19901, United States You can also complain to the data-protection authority that applies to you, where there is one; section 10 lists them by region. DP-PN-WEB · Version 2.0 · Effective 29 October 2026 · DocuPrive, Inc. --- # https://docuprive.com/legal/ Legal # Legal One document is in force today: the Website Privacy Notice, which covers this website and product-update emails, including cookies and browser storage. The documents for the DocuPrivé platform are prepared and not yet in force. They will be published before the platform is offered. This website ## In force [Website Privacy Notice This website and product-update emails, including cookies and browser storage Version 2.0 Effective 29 October 2026](https://docuprive.com/privacy/) Earlier version: [Website Privacy Notice 1.0, effective 13 October 2026](https://docuprive.com/privacy/2026-10-13/) (archived). Not yet in force ## Prepared for the DocuPrivé platform Prepared, not yet in force. Published before the platform is offered. - 01 Terms and Conditions Prepared - 02 Document Lifecycle and Disposal Schedule Prepared - 03 Subscription, Cancellation and Refund Policy Prepared - 04 Sanctions, Export Controls and Change-of-Law Schedule Prepared - 05 Acceptable Use Policy Prepared - 06 External Recipient Terms Prepared - 07 Privacy Notice (platform) Prepared - 08 Cookie and Similar Technologies Notice (platform) Prepared - 09 Data Processing Addendum Prepared - 10 Regional Privacy Supplement Prepared - 11 Consumer and Local-Law Supplement Prepared - 12 Security and Shared Responsibility Schedule Prepared - 13 Subprocessors and Processing Locations Register Prepared - 14 Electronic Communications and Records Consent Prepared - 15 Legal Requests, Intellectual Property and Content Complaints Policy Prepared - 16 Service Exit, Portability and Switching Schedule Prepared - 17 Enterprise, Implementation and Authorised Integration Schedule Prepared ## For legal and compliance teams Legal and compliance teams evaluating DocuPrivé can request the current drafts at [privacy@docuprive.com](mailto:privacy@docuprive.com). ## Company information - **Company:** DocuPrive, Inc., which develops DocuPrivé and operates this website - **Address and representative:** Set out on the [Company page](https://docuprive.com/company/) and in the [privacy notice](https://docuprive.com/privacy/) - **Privacy contact:** [privacy@docuprive.com](mailto:privacy@docuprive.com) - **General contact:** [support@docuprive.com](mailto:support@docuprive.com) --- # https://docuprive.com/partners/ Partnerships # Partnership enquiries Talk with us about how document requests, access and retention work in practice. DocuPrivé is in development. Professional firms, advisers and technology teams can contact DocuPrive, Inc. about the areas below. This page explains what we are open to discussing, how an enquiry proceeds, and the words we use for each kind of relationship. [Email a partnership enquiry](mailto:support@docuprive.com?subject=Partnership%20enquiry) [How an enquiry proceeds](#process) - **Enquiry** you write to us - **Conversation** if there is a fit - **Written agreement** before anything is implied - **Described as agreed** in precise words For discussion ## Three areas we are open to discussing. These are subjects for a conversation, not programmes or services. - **Professional practices.** Law firms, accounting practices, due diligence teams and private-client advisers: how you ask for, share and keep client documents today, and where it goes wrong. For discussion - **Advisers and consultants.** Information governance, records and compliance advisers who help organizations decide how long material is kept, who decides, and how it ends. For discussion - **Technology teams.** How DocuPrivé could sit alongside the systems professional teams already use. Connections to other systems are design questions here, not features: this website describes no connector. For discussion Process ## How an enquiry proceeds. - 1 **Write to us.** Email support@docuprive.com with "Partnership" in the subject: who you are, your organization, and what you have in mind. Please do not include client documents or confidential material. - 2 **We read it.** Enquiries are read at DocuPrive, Inc. Where there is a fit, the next step is a conversation. - 3 **Nothing is implied.** An enquiry or a conversation creates no relationship, endorsement or obligation on either side. - 4 **Agreed in writing.** Any relationship is agreed in writing first, and described on this website only in the terms agreed. Precise words ## How we describe a relationship. Different relationships carry different weight. We use each word only for what it means here. - **Supplier:** Provides a service we use to run something, such as hosting this website. Not an endorsement of DocuPrivé, and not an endorsement by us. - **Integration:** A technical connection between DocuPrivé and another system that exists and works. Described only once it is built. - **Advisory conversation:** An exchange of views about how the work is done. No commitment on either side. - **Pilot:** A limited, agreed trial of the product under written terms. Possible only once there is a product to try. - **Formal partner:** An organization with a written agreement that sets out what each side does. - **Customer:** An organization using DocuPrivé under its terms, once it is offered. ## Where the product stands 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. [Development status](https://docuprive.com/platform/status/) ## Your message and your data If you email us, we use your message to reply and keep it as set out in the website privacy notice. An enquiry does not sign you up for product updates. [Website privacy notice](https://docuprive.com/privacy/) ## Start with an email. Write to support@docuprive.com with "Partnership" in the subject. [Email a partnership enquiry](mailto:support@docuprive.com?subject=Partnership%20enquiry) [Contact](https://docuprive.com/contact/) [Company](https://docuprive.com/company/) --- # https://docuprive.com/platform/status/ 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. Status reviewed 28 October 2026. The date changes only when the status is reviewed again. - **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. Status of each lifecycle stage and of Hold, reviewed 28 October 2026 | Stage | What it means | Status | Described on | | 01 Request | 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](https://docuprive.com/platform/request-receive/) | | 02 Receive | Documents arrive in the context of the Request they answer, not a general inbox. | Designed, not yet built | [Request & Receive](https://docuprive.com/platform/request-receive/) | | 03 Classify | Material is recognized for what it is and how it should be handled. | Designed, not yet built | [Request & Receive](https://docuprive.com/platform/request-receive/) | | 04 Control | Request details stay with a verified recipient, for a defined access period. | In our development build, for Request details | [Share & Recall](https://docuprive.com/platform/share-recall/) | | 05 Use | People work with the documents a task needs, and no more. | Designed, not yet built | [Share & Recall](https://docuprive.com/platform/share-recall/) | | 06 Retain | Material is kept for a period set by policy, not left by accident. | Designed, not yet built | [Lifecycle & Evidence](https://docuprive.com/platform/lifecycle-evidence/) | | 07 Review | Before anything ends, the right people can look again. | Designed, not yet built | [Lifecycle & Evidence](https://docuprive.com/platform/lifecycle-evidence/) | | 08 Dispose | When the time comes, material is brought to a considered end. | Designed, not yet built | [Lifecycle & Evidence](https://docuprive.com/platform/lifecycle-evidence/) | | 09 Evidence | 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](https://docuprive.com/platform/lifecycle-evidence/) | | Control Hold across 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](https://docuprive.com/platform/lifecycle-evidence/) | ## Capabilities, statement by statement. Every product statement on this website comes from this list, at this status. ### Requests and recipient access [Read more](https://docuprive.com/platform/request-receive/) - 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 - Once issued, a Request's details are fixed. Issue, identity verification, current access and email notification are each recorded separately. In our development build - Access to a Request can be revoked, and the notification can be resent. In our development build - The recipient sees only that Request: who asked, what is needed and when access ends. They do not join the requesting organization. In our development build - Recipient access starts with a verified receiving email address. In our development build - The recipient view works on a phone. In our development build - Request details stay with a verified recipient, for a defined access period. In our development build, for Request details ### Library and search [Read more](https://docuprive.com/platform/library-search/) - Every 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 built - A folder is where a document sits, not a permission. Access comes from the work it belongs to. Designed, not yet built - Naming rules help documents arrive with consistent, readable names, and you confirm before anything is saved. Designed, not yet built - A document's date is recorded with where it came from, and is never quietly set to today. Designed, not yet built - Finding material is designed to respect the same boundaries as access: you find what you are allowed to see. Designed, not yet built - Automated suggestions can propose a name or place. They do not move documents on their own. Designed, not yet built ### Recall and links [Read more](https://docuprive.com/platform/share-recall/) - Recall 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 built - A 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 more](https://docuprive.com/platform/lifecycle-evidence/) - Document content and lifecycle records are designed to be kept separately, each with its own access and retention rules. Designed, not yet built - Automated 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 more](https://docuprive.com/trust/controls/) - Customer documents are not sold, used for advertising, or used to train general-purpose AI models. Designed, not yet built - Encryption 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. [Get product updates](https://docuprive.com/updates/) [Platform overview](https://docuprive.com/platform/) [Trust & data](https://docuprive.com/trust/) --- # https://docuprive.com/updates/ Product updates # Follow what comes next. Occasional product news, platform updates and launch announcements from DocuPrivé. - A few emails, when there is something worth saying. - No account is created and no access is reserved. - Unsubscribe from any future email, at any time. Sign up for product updates at https://docuprive.com/updates/ (double opt-in). Questions? [support@docuprive.com](mailto:support@docuprive.com) ## What you will receive Double opt-in: you are subscribed only after you confirm through the email we send, and every email lets you unsubscribe. No third-party marketing. Product-update sign-up is not yet open in the EEA. How we handle your email address is set out in the [website privacy notice](https://docuprive.com/privacy/). For anything else, write to [support@docuprive.com](mailto:support@docuprive.com).