Your clients' data stays yours.
What DocuWeave does with your paperwork, your templates and your documents, stated plainly. Everything on this page is in place today.
Your documents stay in the UK
Your documents and everything in them are stored and processed only in the UK, on Amazon Web Services in London. Every other service we use is listed, with where it is, on our sub-processors page.
Paperwork read on your device
Your paperwork is read in your browser and only its text is sent. The files themselves are never uploaded or kept.
Each organisation kept apart
One organisation can never reach another's templates or documents. We test it.
A record of every approval
A person approves every document, and the record shows who, when and exactly what.
What is sent, what is kept
Paperwork is the client material you fill a document from. Templates and documents are your own work. They are handled differently, and we say exactly how.
Your paperwork
Emails, certificates, notes and the rest you drop in
- Read on your device. Files are read in your browser, and only their text is sent.
- Never uploaded or kept. The paperwork files themselves are never uploaded to DocuWeave or stored.
- Short quotes kept as evidence. For each value it fills, DocuWeave keeps the short passage it came from with the document, so anyone reviewing can see why.
Your templates and documents
What you upload to build a template, and what you make with it
- Template files are stored. The document you upload to make a template, and your logo, are kept in your organisation's own storage area.
- Documents are kept with their history. Each document, its values, its versions and its approval record stay in your organisation's account.
- Not used to train AI models. Your templates, paperwork and documents aren't used to train AI models.
A person stays responsible
DocuWeave fills documents; a person decides what goes out.
A person approves every document
Downloads open only after approval, and the approval records who, when and exactly what was approved.
A guidance check before approval
Every clause is checked against the guidance written on it, and anything possibly not followed is shown with the passage.
No silent changes
Editing an approved document starts a new version that needs approving again. The approved one stays on record.
Signing in
How people get into your organisation's account, and how you shut the door.
Sign in by email link
No passwords to reuse or leak. You sign in from a link sent to your email address.
Two-step sign-in
Codes from an authenticator app. Repeated wrong codes lock further attempts for a while.
Compulsory for your organisation, if you choose
An organisation can require two-step sign-in. Anyone without it sets it up before they can do anything else.
Sign out everywhere
End every session on every device in one step.
What we log, and what we don't
An audit log
Sign-ins, approvals and security changes are logged. The log holds no document content.
Analytics without content
We record which features are used, never what your documents say.
Start with a document you already send.
Upload one, check what DocuWeave found, and publish it. Nothing is used until you do.