Trust

Trust starts with saying exactly where things stand.

DocuPrivé is developed by DocuPrive, Inc. and is not yet available. It does not hold anyone's documents today. This page sets out who is responsible, what exists in the development build, what is only designed, and how this website handles the email addresses of people who subscribe.

Reviewed 28 October 2026

What each part of DocuPrivé covers today

This website

In operation. Operated by DocuPrive, Inc. Collects only what you choose to send: a sign-up or an email.

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.

1Who 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)

The company is founder-led and in development. You can read about the company and its founder on the Company page.

2Where 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 stageEvery stage and capability with its status, reviewed 28 October 2026.

3How we design

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

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.

4This 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 website; our email provider manages the update list and sends the emails. Each receives only what its function requires.
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. All documents in force, and those prepared for the platform: Legal.

5How 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. 1A statement on any page, with its label in place
  2. 2One status source behind every label on this site
  3. 3The status page lists each statement, dated
  4. 4Real views from the development build where one exists

6Raising a concern

If you believe you have found a security issue with this website, write to security@docuprive.com. This contact is also published at /.well-known/security.txt. For anything on this site that you believe is inaccurate, write to support@docuprive.com. Please do not include sensitive documents in your message.

Questions about how DocuPrivé will handle documents?