Privacy & Security
How to keep client research confidential — a practical guide for consultants, lawyers, researchers, and agency professionals who collect and store research about clients and need to protect that information from unauthorized access, data breaches, and inadvertent disclosure.
Professionals who manage client research — consultants, lawyers, market researchers, competitive intelligence analysts, public relations professionals, designers, financial advisors — accumulate substantial amounts of information about their clients: their strategies, their competitive positioning, their plans, their vulnerabilities, their financials, and their relationships.
This information is entrusted by the client on the basis of confidentiality. The professional's ability to be trusted with sensitive information is fundamental to their practice. A confidentiality breach — even an inadvertent one — can destroy a professional relationship, expose the client to competitive harm, create legal liability, and end careers.
Despite the clear stakes, client research confidentiality fails regularly through predictable patterns:
Shared cloud storage without access controls: Research files stored in a team Dropbox, Google Drive folder, or shared drive that other team members, contractors, or anyone with the link can access. Research about Client A is visible to staff working on Client B.
Unencrypted email attachments: Client research sent as email attachments. Email is not encrypted in transit unless end-to-end encryption is used. Email attachments on unencrypted email accounts are accessible to the email provider and to anyone who compromises the account.
Consumer note-taking apps: Research captured in Evernote, Notion, or Google Keep — consumer applications where the provider can access stored content, where there are no client-specific access controls, and where a single account compromise exposes all clients' research simultaneously.
Unsecured devices: Research stored on a laptop with no full-disk encryption or a weak device password. A lost laptop becomes a data breach.
Metadata in shared documents: Documents shared with clients or between team members that contain metadata revealing research sources, earlier drafts, or internal opinions about the client or about third parties.
Inadvertent cross-client disclosure: Using a previous client's research structure (a template, a document, a slide deck) as the basis for a new client engagement and inadvertently including confidential information from the previous client.
This guide addresses each of these failure patterns with specific controls.
Client isolation as the organizing principle:
Client research should be organized such that access to one client's materials does not provide access to any other client's materials. This means:
Recommended folder structure:
Professional/
├── Clients/
│ ├── ClientA-[Engagement-Name]/
│ │ ├── Research/
│ │ ├── Deliverables/
│ │ └── Communications/
│ ├── ClientB-[Engagement-Name]/
│ │ ├── Research/
│ │ ├── Deliverables/
│ │ └── Communications/
├── Internal/
│ ├── Templates/
│ │ └── [Template files with no client data]
│ └── Admin/
The template problem:
Templates are a common source of cross-client contamination. A research template that was used for Client A and then reused for Client B may retain snippets of Client A's information in earlier versions, in revision history, or in comments. Practice: maintain clean templates that contain no client data. When starting a new engagement, copy from the template, not from a previous client's document.
The need-to-know principle:
Only individuals who actively need access to a client's research to do their work should have access to it. The default should be restricted access, not open access with exceptions.
This applies especially in team contexts: an analyst working on Client A's engagement doesn't need access to Client B's research files, even if they're at the same firm. A contractor engaged for a specific project shouldn't have access to other clients' materials.
Cloud storage access controls:
Google Drive: Create a separate folder for each client. Share that folder only with the team members working on that engagement. Do not share the parent folder — sharing a parent folder in Google Drive grants access to all subfolders.
Dropbox: Create a separate shared folder per client. Invite only the relevant team members. Separate shared folders are independent — members of Client A's folder don't see Client B's folder.
Microsoft OneDrive/SharePoint: Use separate document libraries or site collections per client, with permissions configured for each.
Self-hosted solutions (Nextcloud, etc.): Configure per-client directories with group-level permissions.
Who has access and for how long:
Access should be granted at engagement start and revoked at engagement end. Former clients' research should not be accessible indefinitely without a retention and access justification.
Local storage with full-disk encryption:
For research stored locally (on a laptop or desktop), full-disk encryption (FileVault on macOS, BitLocker on Windows) ensures that a lost or stolen device doesn't produce a data breach. Full-disk encryption should be enabled by default on all professional devices that hold client information.
Verify that encryption is enabled:
Encrypted cloud storage:
For cloud-synced research that may be sensitive, Cryptomator provides client-side encryption for any cloud storage service. Files are encrypted before leaving the device; the cloud provider stores only encrypted data.
Setup: create a Cryptomator vault in the cloud storage folder for the client engagement. All files saved to the vault are encrypted before sync. Team members access the vault with the vault password, which must be shared through a secure channel (not email).
Password-protected research files:
For individual research documents that are particularly sensitive, password protection adds a layer of access control independent of folder permissions:
Password-protected files remain inaccessible even if the storage location is compromised.
Consumer note-taking applications (Evernote, Notion, Google Keep) are not appropriate for sensitive client research because:
Appropriate tools:
Joplin with E2EE: Create a separate Joplin notebook per client. Enable end-to-end encryption. Notes are encrypted on the device before sync; the provider cannot read content. The per-client notebook structure provides logical organization.
Standard Notes: End-to-end encrypted notes with zero-knowledge architecture. Use tags or folders to separate client research. The provider cannot access note content.
Obsidian (local-only): Create a separate Obsidian vault per client, stored in the encrypted client folder on a full-disk-encrypted device. No cloud sync = no cloud exposure. For team access, share the vault via Cryptomator-encrypted cloud storage.
Dedicated research applications with access controls: Some professional research management tools (Citation management tools like Zotero for research professionals; dedicated intelligence platforms for CI professionals) provide per-client or per-project organization with appropriate access controls.
The browsing trail problem:
When conducting competitive research or market research for a client — visiting competitor websites, researching industry dynamics, investigating specific companies — the browsing trail links the researcher to the subjects of the research. This trail exists in browser history, in ISP records, and in the target website's access logs (which record visitor IP addresses).
In most professional research contexts, this isn't a significant concern. In some contexts it is:
For research where the browsing trail itself is sensitive, use:
Search engine queries for client research:
Searches conducted while logged into a personal Google account are associated with that account. For sensitive client research, conduct searches in a logged-out state or use a privacy-focused search engine (DuckDuckGo, Startpage) that doesn't retain query history.
Research documents prepared for clients — or prepared about clients for internal use — may contain metadata that reveals information that should remain confidential.
Word processor document metadata:
Microsoft Word documents embed: author name, revision history, tracked changes, comments (including deleted comments that may be recoverable), earlier draft content (in some cases), and document statistics.
Before sharing any Word document externally:
PDF metadata:
PDFs may contain: author name, creating application and version, document title, and in some cases tracked changes or comments from a source document.
Use Adobe Acrobat's "Sanitize Document" function (Tools → Redact → Sanitize Document) to strip metadata from PDFs before sharing them with clients or externally.
Spreadsheet metadata:
Excel files may contain similar metadata plus named ranges, data validation rules, and in some cases external data source connections that reveal internal systems.
Email:
Standard email is not end-to-end encrypted. Attachments sent via email are accessible to the email provider and to anyone who compromises the email account. For routine client communications involving non-sensitive information, standard email is generally acceptable. For sensitive research deliverables or confidential analysis, consider:
Client portals:
Some professional service firms provide clients with a dedicated portal where files are shared. This approach provides access controls (only the client, not other clients, can access the portal), audit logging (who accessed what and when), and version control. Tools: Microsoft SharePoint with per-client site collections, client portal features in practice management software, or dedicated secure file sharing platforms (ShareFile, Egnyte).
Retention policy:
Client research should be retained for the period required by the engagement agreement, professional regulations, or applicable law — and then disposed of. Indefinite retention of former client research:
Define retention periods in engagement agreements: "Research materials will be retained for 5 years after engagement completion and then securely disposed of."
Secure disposal:
Digital files: permanently deleted with secure deletion tools (BleachBit on Windows/Linux; secure empty trash options on macOS). Standard file deletion leaves the data recoverable from disk; secure deletion overwrites the storage location.
Physical documents: cross-cut shredded or incinerated.
Former clients' cloud storage access: revoked at engagement end or at the close of the retention period.
Setup: A management consultant at an independent practice works with 3-5 clients simultaneously. She conducts competitive research, market research, and internal analysis for each. She regularly produces Word documents and Excel models as deliverables. She has 2 analysts who share some of her client work.
Her system:
Storage: She uses Google Drive with a separate shared folder per client. Each client folder is shared only with herself and the analyst assigned to that engagement. She does not share the parent folder — each client's folder is shared independently.
Note-taking: She uses Joplin with E2EE for research notes. She has a separate Joplin notebook per client. The E2EE encryption means her Joplin sync provider cannot read her research notes.
Devices: Her laptop has FileVault (macOS full-disk encryption) enabled. She has a strong device password. She uses a VPN when working from public networks.
Documents: Before sharing deliverables with clients, she runs Word's "Inspect Document" function and removes all personal information and revision history. PDFs are sanitized with Acrobat before sharing.
Templates: She maintains a template library in a separate folder with no client data. All new client documents start from templates, not from previous client files.
Research: For competitive research, she uses a dedicated browser profile with no personal logins and DuckDuckGo for search, to avoid linking her research queries to her firm.
Retention: Her engagement letters specify a 5-year retention period for client materials. She schedules an annual review to archive and delete materials for engagements that have passed the retention window.
Keeping client research confidential requires organizational discipline (client isolation, access controls, access revocation at engagement end), secure tool selection (E2EE note-taking, encrypted cloud storage, full-disk encryption on devices), and document hygiene (metadata removal before sharing, clean templates). The failure patterns — shared storage without client isolation, consumer note apps for sensitive research, unencrypted devices, metadata in shared documents — are all preventable with straightforward practices. The underlying principle is proportionate protection: not every client research file requires maximum security controls, but research that is sensitive enough that its disclosure would harm the client or the professional relationship deserves controls that match that sensitivity.
More WebSnips articles that pair well with this topic.
How to Audit a browser extension's permissions — a practical, example-driven guide with honest tool comparisons and a clear place for WebSnips. Written for Lawyers.
How to avoid vendor lock-in with your notes — a practical guide for individuals and teams who want to keep their personal knowledge base portable, format-independent, and recoverable regardless of which application or service they use.
How to back up your notes safely — a practical guide for individuals and professionals who want reliable, secure backups of their personal knowledge base, covering backup strategies, encrypted backup tools, and recovery testing for note-taking applications.
How to capture sensitive research securely — a practical guide for researchers, journalists, legal professionals, and privacy-conscious individuals who need to gather and store sensitive information without creating avoidable exposure through insecure capture tools or storage practices.
How to choose a private web clipper — a practical guide for privacy-conscious researchers, journalists, and professionals who want to clip and save web content without exposing their browsing patterns, source materials, or clipped content to third-party services.
How to comply with GDPR in your knowledge base — a practical guide for teams and organizations who store personal data in their internal wikis, documentation systems, and knowledge management tools, covering data minimization, retention policies, access controls, and subject rights.