Facing an NDA Dispute?
Consult with an attorney who can help protect your interests.
Essential documentation to gather and preserve if you're facing an NDA dispute. Proper evidence collection can make or break your case.
The best time to gather evidence is before you need it. Maintain organized records of all confidential information you receive, your prior knowledge, and your independent work.
If the client expresses concern, sends a cease and desist, or you suspect a problem, immediately preserve all communications and documents. Issue a litigation hold to prevent automatic deletion.
Gather evidence that supports your defenses: prior knowledge, independent development, public information, or authorized disclosure. Time-stamped records are critical.
Continue documenting all communications related to the dispute. Keep a detailed log of events, meetings, and any new evidence that surfaces.
Start with the foundational documents that define your obligations.
The original signed agreement, including any exhibits or schedules. Verify you have the final executed version, not a draft.
Any written changes to the NDA, email agreements to modify terms, or subsequent agreements that reference the NDA.
The underlying service agreement may contain additional confidentiality provisions or define the scope of work.
Communications showing what was discussed, any agreed modifications, or representations about how the NDA would be applied.
All written communications may become evidence. Preserve them systematically.
Export complete email chains, including attachments. Use native format (EML/MSG) to preserve metadata.
Export chat logs from collaboration tools. Many have built-in export features. Screenshot if necessary.
Notes from calls, Zoom recordings (if permitted), and calendar invites showing meeting purposes.
If you communicated via text, screenshot or export these conversations with timestamps.
Any discussions about the project with others - these may show what information you disclosed and to whom.
Evidence that you possessed knowledge or skills before the engagement is a key defense.
Code, designs, documents, or other work products created before you signed the NDA.
Repository logs showing when code was written. Commit timestamps can prove independent development.
Evidence of similar work for other clients before this engagement began.
Certificates, course completions, or training records showing you learned techniques independently.
Public content you created showing expertise in the relevant area before the engagement.
Document exactly what confidential information you received and how it was marked.
Create an inventory of all materials explicitly marked as confidential with dates received.
Screenshots or exports showing what systems, files, or folders you had access to.
Any confidentiality training or documentation of what you were told was confidential.
Screenshots, archive.org links, or other proof that allegedly confidential information was publicly available.
If you disclosed information, document that it was authorized.
Emails or messages where the client approved disclosure to specific parties.
Evidence that you were allowed to use work samples or reference the engagement.
If you shared with subcontractors, evidence they signed appropriate NDAs.
Store copies in at least two locations: cloud storage and local backup. Evidence that exists in only one place can be lost.
Timestamps, sender info, and file properties are crucial. Export in native formats rather than screenshots when possible.
Document when and how evidence was collected. This prevents accusations of tampering or fabrication.
Once a dispute is possible, deleting anything - even personal notes - can be considered spoliation with serious legal consequences.
Before collecting evidence from company systems you no longer have access to, get legal advice to avoid unauthorized access claims.
Build a chronological narrative of events. Courts love clear timelines, and they help you identify gaps in your evidence.
Consult with an attorney who can help protect your interests.