How to Audit a browser extension's permissions
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.
Privacy & Security
How to keep legal research privileged and secure — a practical guide for lawyers, paralegals, and legal teams who need to protect attorney-client privilege, work product doctrine, and client confidentiality in their research and documentation practices.
Legal research exists within a framework of legal protections that have specific technical requirements. Understanding these protections is the starting point for implementing practices that maintain them.
Attorney-client privilege protects confidential communications between a lawyer and their client made for the purpose of seeking or providing legal advice. The privilege belongs to the client, can be waived by the client (deliberately or inadvertently), and is lost when confidential communications are disclosed to non-privileged third parties.
For legal research, privilege applies to: communications with the client about the research, legal advice given based on the research, and memoranda to the file that reflect the lawyer's analysis. Privilege does not attach to the underlying facts being researched — only to the lawyer's analysis and the communications about it.
Attorney work product doctrine (derived from Hickman v. Taylor, 329 U.S. 495, 1947, in the US context) protects materials prepared by or for an attorney in anticipation of litigation. The protection covers notes, research summaries, legal strategy documents, and any materials reflecting the attorney's mental impressions, legal theories, and opinions.
Work product doctrine is broader than privilege: it protects materials even when shared with non-attorneys (like experts and consultants working on the case), as long as they were prepared in anticipation of litigation.
The confidentiality obligation: Separate from privilege and work product, attorneys have a professional obligation of confidentiality to clients under the rules of professional conduct (Model Rule 1.6 in the ABA model rules; equivalent rules in other jurisdictions). This obligation applies to all client information, not just privileged communications.
Understanding waiver helps identify what practices put privilege at risk.
Disclosure to non-privileged third parties:
Sharing privileged communications with parties outside the attorney-client relationship waives privilege as to those communications. This includes:
The privilege group typically includes: the attorney and law firm staff, the client and their agents working on the matter, co-counsel, and persons authorized by the client to be included. Third parties (even friendly ones) who aren't within this group are outside the privilege.
Digital-age waiver risks:
The inadvertent disclosure problem:
If privileged documents are produced inadvertently in discovery, the attorney must typically notify opposing counsel immediately and request return of the documents. Whether the privilege is maintained after inadvertent disclosure depends on jurisdiction and the reasonableness of the steps taken to prevent disclosure. This is a significant risk in document-intensive matters.
Matter-based organization:
All research and documents should be organized by client matter. This ensures that documents for Matter A cannot be confused with or inadvertently disclosed in relation to Matter B.
Client matters/
├── Client-A-Matter-001-[Subject]/
│ ├── Research/
│ │ ├── Privileged/ [attorney analysis, legal memos]
│ │ └── Non-privileged/ [public sources, court filings]
│ ├── Client-communications/ [emails, meeting notes with client]
│ ├── Work-product/ [strategy documents, draft pleadings]
│ └── Production/ [documents produced or received in discovery]
├── Client-B-Matter-002-[Subject]/
│ └── [same structure]
Privilege marking:
Documents that are attorney-client privileged or protected work product should be marked as such. While the marking doesn't create privilege (the privilege status depends on the nature of the document and the relationship, not the label), it:
Standard marking: "ATTORNEY-CLIENT PRIVILEGED" and/or "ATTORNEY WORK PRODUCT — NOT FOR DISTRIBUTION" in the document header or footer.
The cloud service problem:
Many standard cloud services are not appropriate for privileged legal research because the service provider has access to stored content. If an attorney stores privileged research in a standard Google Drive, Notion, or Dropbox account (without client-side encryption), the service provider has access to that content. That access doesn't necessarily waive privilege under current law (the provider is not an adversarial party and the sharing may be considered inadvertent rather than voluntary), but it creates risk and is inconsistent with the confidentiality obligation.
Appropriate technology for privileged research:
Law firm-managed systems: The appropriate primary repository for privileged legal research is the law firm's own document management system (DMS) with proper access controls. Standard legal DMS platforms (iManage, NetDocuments, Worldox) are designed for legal confidentiality requirements, with matter-based access controls, audit logging, and privilege management features.
Self-hosted or enterprise-grade alternatives: For smaller firms or solo practitioners who don't use a full DMS, matter-organized folders on a firm-managed server with access controls, full-disk encryption, and regular encrypted backups provide an appropriate foundation.
Local storage with encryption: Research notes and work product stored locally on a firm-issued device with full-disk encryption (FileVault, BitLocker) provide a secure local copy with access control tied to device authentication.
What to avoid:
The use of AI tools in legal research has created a specific privilege risk that requires careful evaluation.
The risk:
AI tools that process document content typically work by sending the content to servers operated by the AI provider. When an attorney uses an AI tool to summarize case law, draft analysis, or review documents, and includes privileged content in the prompt or input, that content is transmitted to the AI provider's servers.
Whether this constitutes a waiver of privilege is an evolving area of law. The more significant risk is the confidentiality obligation: sending client confidential information to an AI provider's servers without proper authorization from the client and without adequate data security measures may violate Rule 1.6 and equivalent rules.
Guidance from bar associations:
Several state bar associations have issued guidance on attorney use of AI tools (California, New York, Florida, Texas, and others have published opinions or guidance as of the time this guide was written). The common themes:
Practical approach:
Before using any AI tool with privileged or confidential research content:
Many AI providers offer enterprise tiers with confidentiality commitments and no training-data opt-in. These should be used instead of consumer tiers for any work involving privileged or confidential content.
Logged-in account research:
Legal research databases (Westlaw, Lexis, Fastcase, Bloomberg Law) require authenticated accounts and log queries. In most legal matters, this query log is not a concern — the researcher's identity and the queries are expected to be visible to the database provider.
For matters where the fact of the research itself might be sensitive — researching an opposing party who has relationships with the database provider, researching a topic where the research queries themselves could be revealing — this logging creates a consideration.
Physical security:
Privileged research materials should not be reviewed in public spaces where screens are visible (coffee shops, public transportation, shared office spaces). A privacy screen filter for the laptop reduces shoulder-surfing risk.
Printed research materials should be managed carefully: shredded when no longer needed (not placed in standard recycling), not left unattended in shared spaces.
Communication security:
Client communications about matters should use the firm's email system, not personal email accounts. Client calls on sensitive matters should be conducted in private. Video calls with clients should use platforms with appropriate confidentiality controls — not consumer video conferencing accounts used for other purposes.
In litigation, a critical moment for privilege protection is document production — when the firm must produce documents to opposing counsel in response to discovery requests.
The privilege log:
Documents withheld from production on privilege or work product grounds must be documented in a privilege log: a list of withheld documents with a description sufficient to allow the opposing party to assess the privilege claim without revealing the privileged content. Privilege log requirements vary by jurisdiction and may be specified in court orders.
A privilege log entry typically includes: document identifier, date, author, recipients, a general description of the document type and subject, and the privilege claimed.
Pre-production review:
Every document in a production set should be reviewed by a licensed attorney for privilege before production. Privileged documents should be removed and logged. Metadata should be stripped (or reviewed) before producing documents electronically.
Clawback agreements:
Clawback agreements (often included in stipulated protective orders) allow parties to retrieve inadvertently produced privileged documents without waiving privilege. These agreements are standard in document-intensive matters and provide an important safety net.
Setup: A solo litigation attorney handles commercial disputes. She needs to keep client research secure, maintain privilege, and comply with professional responsibility rules — on a small firm budget.
Her system:
Client matter organization: She uses a strict folder structure on her MacBook — one folder per matter, numbered and named. The folder is on an external encrypted drive that she backs up to a locally-hosted Nextcloud instance (on a Mac mini in her office, not a cloud provider).
Research notes: She uses Joplin with E2EE for research notes. One Joplin notebook per matter. Notes are marked "[PRIVILEGED WP]" in the title when they contain work product analysis. Joplin syncs to her Nextcloud instance — not to a third-party cloud service.
AI tools: She uses an enterprise-tier AI subscription with a Data Processing Agreement and a no-training-data policy. Before using it for any matter, she checks her state bar's AI guidance (updated semi-annually). She doesn't input client names or identifying details into AI prompts — she describes matters generically.
Email: She uses a firm email domain (not personal Gmail) for all client communications. Her email host provides encrypted storage.
Privilege marking: Any document intended to be work product is created from a template that includes the header: "ATTORNEY-CLIENT PRIVILEGED AND ATTORNEY WORK PRODUCT — NOT FOR PRODUCTION."
Document production: Before any production, she manually reviews the production set for privilege. She uses a clawback agreement in every case.
Device security: Her MacBook has FileVault enabled. Strong passcode. Automatic lock after 5 minutes of inactivity.
Keeping legal research privileged and secure requires practices that align with the legal requirements for maintaining privilege — confidential communications within the privilege group, protected storage, controlled access — and with professional responsibility obligations of confidentiality. Technology choices matter: firm-managed systems with access controls, encrypted local storage, and AI tools evaluated against data handling standards are the appropriate options for privileged work. Consumer tools designed for convenience without confidentiality controls are not. The practices aren't complex, but they require deliberate implementation and consistent application — privilege protection is only as strong as the weakest point in the system, and that weak point is most often in technology choices and document handling habits.
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.