How to Prove a Breach of Confidentiality Claim in Washington, D.C.

Washington, D.C. .as adopted a statutory trade secrets framework, which gives trade secret claims in the District a codified foundation that many states lack. Under D.C.'s trade secrets statute, protected information includes any formula, pattern, compilation, program, device, method, technique, or process that derives independent economic value from not being generally known and is subject to reasonable efforts to maintain secrecy. The federal Defend Trade Secrets Act applies in parallel.

For confidential information that does not qualify as a trade secret, protection rests primarily on contract. D.C.'s trade secrets statute supersedes conflicting tort and restitution claims, but preserves contractual remedies. Courts in the District look at whether the owner treated the information as secret and whether the circumstances gave the recipient reason to understand that expectation. Information shared openly, stored without access controls, or distributed to third parties without conditions generally falls outside what a court will protect, regardless of how it was labeled internally.

A formal agreement is not required for information to qualify as confidential. That said, written documentation shifts the analysis substantially. Without it, courts rely on conduct and context, and the outcome becomes harder to predict.

To succeed on a breach of confidentiality claim in Washington, D.C., a plaintiff must establish three things. First, a confidential relationship must have existed at the time of disclosure, whether arising from contract, professional status such as attorney-client or employer-employee, or the circumstances of the disclosure itself. Second, the plaintiff must show that a reasonable expectation of confidentiality was communicated or implied, looking at how the information was shared and whether the recipient acknowledged any restrictions on its use. Third, the defendant must have used or shared the information in a way that exceeded any authorized purpose.

Each element is independent. A confidential relationship with no unauthorized use does not establish a breach. An unauthorized disclosure where no prior confidential relationship existed is a different kind of claim entirely.

Trade secrets are the most frequently litigated category. When an employee departs with pricing models, client lists, or product development files, both D.C.'s trade secrets statute and the federal Defend Trade Secrets Act may apply. The two frameworks carry different procedural tools and remedies, and which one to pursue depends on the facts of the taking. For cases involving active trade secret misappropriation, the federal route often offers broader options, including ex parte seizure orders not available under the D.C. statute alone.

Washington, D.C.'s concentration of government agencies, contractors, and policy organizations also gives rise to confidentiality claims involving categories less common elsewhere: government contract bid information, regulatory strategy and draft policy analyses, lobbying communications, and internal assessments shared among partner organizations under an expectation of confidence. These categories typically rely on contract and common law rather than the trade secrets statute, and the evidentiary burden depends heavily on how the information was classified and restricted in practice.

The burden of proof rests with the plaintiff, and D.C. .ourts require more than an assertion that a relationship was confidential. Useful documentation includes:

• Signed NDAs or confidentiality provisions in employment and vendor agreements, specifying what information is covered
• Written internal policies identifying protected categories, distributed and acknowledged by employees
• Access logs or electronic controls showing who could view the information and when
• Direct evidence that the defendant had access to the specific information at issue, not just information in the same general area

Establishing damages requires the same standard. Speculative revenue losses do not satisfy it. A plaintiff must connect the specific disclosure to a specific financial consequence, whether through lost contracts, measurable unjust enrichment, or documented mitigation costs.

Preliminary injunctions and temporary restraining orders are usually the first relief sought when disclosure is ongoing or a departure raises concern that information is about to be used. These applications may be filed in D.C. Superior Court or, where federal claims apply, in the U.S. District Court for the District of Columbia. The court weighs whether irreparable harm would follow without the order, whether the plaintiff has a likelihood of success on the merits, and whether the balance of equities favors restraint. Delay in seeking injunctive relief tends to work against the plaintiff; courts read urgency as a signal of how seriously the plaintiff views the threat.

On the damages side, what is available depends on the nature of the breach:

Where the confidential information was covered by a written agreement, a breach of contract claim can run alongside the confidentiality claim, potentially expanding the available theories at trial. In cases involving deliberate misappropriation of trade secrets, criminal liability may arise under the federal Economic Espionage Act or, in limited circumstances, under D.C. .riminal provisions governing unauthorized disclosure of confidential information, though criminal exposure in commercial disputes is uncommon and turns heavily on the specific facts.

Several defenses are well recognized in D.C., and each turns on documentation.

A defendant can argue that the information was already in the public domain at the time of the alleged breach. Courts examine whether the plaintiff actively maintained secrecy, not just whether someone could theoretically have found the information with enough effort. If the plaintiff shared the same information freely elsewhere, that significantly weakens the claim.

Independent discovery is a separate argument: a defendant who developed the same information through its own legitimate research has not committed a breach, even if the result looks identical to the plaintiff's protected material. The defendant bears the burden of demonstrating that the development process was genuinely independent, which usually means contemporaneous documentation predating any exposure to the plaintiff's information.

Consent and waiver are the third recognized defense. Explicit authorization for a disclosure defeats the claim outright. Conduct can also constitute implied waiver, particularly when a plaintiff distributed information widely without restriction and then seeks to treat it as confidential in litigation.

Effective prevention starts with contract language. An agreement that defines confidential information broadly without specifying what actually qualifies is harder to enforce; courts give more weight to provisions that identify what is covered, how long the obligation runs, and what uses are permitted. Vague clauses tend to shift litigation toward scope disputes before the underlying breach is addressed.

Beyond drafting, protection requires two things that organizations often skip. A written classification system tells employees what information is confidential and how to handle it. Documented training, with signed acknowledgments, establishes that employees understood their obligations when those obligations arose. Both carry weight if a dispute reaches litigation.

When an employee departs and raises concern, a prompt written reminder of ongoing confidentiality obligations, together with a request for return of company materials, creates the evidentiary record for any future claim. Waiting until after misuse is confirmed typically makes the case harder to prove and the remedies harder to obtain.