Skip to content
Welcome back Continue →

Document Software: Confidentiality Checklist

Published · Updated · Reviewed by Clausery editors · Automating Word templates · 5 min read

Professional confidentiality duties and data protection law both expect you to know where client information goes when you use software. These are the questions worth asking any vendor, including us.

Start with a mutual NDA — free See the Word template

Where is the data processed?#

  • Is the information you type sent to the vendor's servers, or processed on your own device?
  • In which countries are those servers? Are there transfers outside your jurisdiction?
  • Is it used to train AI models, or shared with an AI provider?

Who can access it?#

  • Can the vendor's staff read your documents? Under what circumstances?
  • Which sub-processors (hosting, email, analytics, AI) receive it?
  • What happens if the vendor receives a subpoena or suffers a breach?

How is it protected?#

  • Is data encrypted in transit and at rest? Who holds the keys?
  • What independent assurance exists (for example SOC 2 or ISO 27001 reports)?
  • How are user accounts protected (single sign-on, two-factor authentication)?

Retention and exit#

  • How long is data kept after you delete it or cancel?
  • Can you export everything in an open format?
  • Will your templates keep working if the vendor disappears?

How Clausery answers these#

Clausery was designed so that most of these questions have a short answer: documents are built in your browser and stored on your device, so there is no vendor server holding client data, no sub-processor for your content and nothing to breach on our side. Your templates are ordinary Word files and your data exports are plain JSON. The details, including what the web host can see, are in the security overview and the data processing statement. You can try it with a free template or open the app.

How to use the checklist#

Ask every question of every tool that will touch client or employee information, including the one you already use. A vendor that cannot answer a question in writing is a risk, and "we take security seriously" is not an answer. Score each item as answered, partly answered or not answered, and keep the responses with your vendor review.

Questions people forget

  • Backups. Where are backups stored, how long are they kept and are they encrypted? A deletion request that leaves the data in a backup for a year is not a deletion.
  • Support access. Can support staff read your documents? Under what approval, and is that access logged?
  • Sub-processors. Which other companies process the data, where are they, and how will you be told about a new one?
  • Breach notice. How quickly will the vendor tell you about an incident, and what will they tell you?
  • Location and transfer. Which country stores the data, and what transfer mechanism applies if it leaves yours?
  • Training and confidentiality. Are staff who can see client data bound by confidentiality and trained on it?
  • Exit. Can you export every template and answer set in a usable format, and what happens to the data when the contract ends?

Questions to ask about the documents themselves

Security is not only where the data is stored. Ask whether the tool can generate a document without sending its contents to a server, whether previews and PDFs are produced locally, and whether the template file leaves the device when it is uploaded. A tool that encrypts data at rest in its own cloud still has the data; a tool that never receives it cannot lose it.

An email you can send#

Subject: Information security questions before we proceed

Hello,

We are reviewing [tool] for use on confidential client matters. Could you answer the following in writing?
1. Where is document content stored and processed?
2. Which sub-processors can access it, and in which countries?
3. How long are deleted documents kept in backups?
4. How quickly do you notify customers of a security incident?
5. Can we export all templates and answers, and in what format?
6. Do you have a current penetration test or ISO 27001 report you can share?

Thank you,
[Name]

What good answers look like#

Specific answers with dates and documents: a data processing agreement, a sub-processor list, a retention table, a breach notification clause with a number of hours, and a recent independent test. Vague assurances, missing sub-processor lists and a refusal to put commitments in the contract are all reasons to look elsewhere.

This checklist is general information, not legal advice. Your professional rules and data protection obligations depend on your jurisdiction.

Download a starter template#

Questions

Do we need a data processing agreement with every vendor?

If the vendor processes personal data on your behalf, data protection law usually requires a written contract covering instructions, confidentiality, sub-processors, security and breach notification. Check the local rules for your jurisdiction.

Is a self-hosted tool automatically more private?

Not necessarily. Self-hosting moves the responsibility to you: patching, access control, backups and incident response become your job. It can be the right choice for a firm with the resources to run it, but it is a different risk, not the absence of risk.

What should we do if a vendor cannot answer these questions?

Treat it as a finding, not a formality. Ask for the missing documents in writing and set a deadline. If the vendor still cannot explain where client data goes, do not put client data into the tool.

More on automating Word templates

Browse all guides by topic

Helpful?

Start with a mutual NDA, free →
Continue drafting Top