Most of the panic around non-disclosure agreements over the past two years came from a single confusion: people assumed the Federal Trade Commission's headline-grabbing rule was about NDAs. It was not. The rule that made news in 2024 targeted non-compete clauses, and it never made it into force. NDAs in the United States remain governed by ordinary contract law, state trade-secret statutes, and a handful of federal carve-outs, exactly as they were before. What did change is the climate around any agreement that quietly functions like a non-compete, and that distinction now decides whether your confidentiality language holds up or collapses in front of a judge.
This guide is written for the people who actually sign and draft these documents: founders protecting a product roadmap, employers onboarding a sales team, contractors handed a one-sided form before a project. It separates what the FTC actually did from the rumors, and it tells you which NDAs are still solid and which ones are quietly worthless.
What an NDA does, and what it never could do
A non-disclosure agreement is a contract that obligates one or both parties to keep specified information secret. It protects trade secrets, client lists, source code, pricing models, unreleased products, and the contents of a deal under negotiation. It does not, on its own, stop someone from working for a competitor; that job belongs to a non-compete, and the two are routinely conflated to everyone's cost.
The line matters because the law treats them very differently. Courts across the country enforce a tailored NDA without much hesitation, because keeping a secret is not the same as keeping a person unemployed. A non-compete, by contrast, faces hostile scrutiny almost everywhere and is flatly void in California, North Dakota, Oklahoma, and Minnesota. The trouble starts when an NDA is drafted so broadly that it stops being a secrecy promise and starts behaving like a leash. An agreement that bars a former employee from using any information acquired on the job, including general skills and publicly available knowledge, does not really protect a secret. It prevents the person from doing their work anywhere else. That is the kind of NDA most exposed to challenge today, and it is the precise scenario the FTC singled out.
The legal framework after the FTC's non-compete rule
On April 23, 2024, the FTC issued a final rule under Section 5 of the Federal Trade Commission Act declaring most employer-employee non-competes an unfair method of competition. It was scheduled to take effect on September 4, 2024. It never did. In Ryan LLC v. FTC, the U.S. District Court for the Northern District of Texas set the rule aside nationwide on August 20, 2024, holding that the Commission lacked authority to issue substantive competition rules and that the ban was arbitrary under the Administrative Procedure Act. The FTC appealed, then reversed course: it voluntarily dismissed its appeal in September 2025, and in February 2026 formally removed the rule from 16 CFR Part 910 to conform the regulation to the court's decision. The agency's own guidance now states plainly that the rule is not in effect and not enforceable.
For NDAs specifically, the headline was always misleading. The rule never categorically prohibited non-disclosure agreements, and it never prohibited non-solicitation agreements either. What it reached was narrower and survives as a useful warning even though the rule is dead. The Commission defined a non-compete to include any term that "prohibits," "penalizes," or "functions to prevent" a worker from taking another job, and it warned that an NDA spanning such a wide swath of information that it effectively blocks a person from working in their field would be treated as a de facto non-compete. The Congressional Research Service confirmed the point: the rule did not touch ordinary NDAs. You can read the agency's current position on the FTC's official non-compete rule status page, which records the litigation history and the rule's removal.
So where does that leave enforceability? Squarely back with state law, where it has always lived for NDAs. Confidentiality agreements rise and fall on basic contract principles, on each state's adoption of the Uniform Trade Secrets Act, and on the federal Defend Trade Secrets Act of 2016. The FTC episode did not rewrite any of that. It mainly taught drafters a lesson that good lawyers already knew: an overbroad NDA is a liability, not extra protection.
Which NDAs still hold up, and which collapse
A confidentiality agreement that defines its secrets with care is on firm ground. Courts want to see a clear category of genuinely confidential information, a legitimate business reason for protecting it, and a scope that does not smother the signer's ability to earn a living. An NDA covering a company's unreleased algorithm, its supplier pricing, and its customer database will be enforced in nearly every state, because each item is a real secret and none of them prevents the former employee from practicing their trade elsewhere.
The agreements that fail share a common flaw: greed in the drafting. When confidentiality is defined to include everything the worker ever learned, "including publicly available information," a court reads it as an attempt to control the person rather than the information, and several state courts now strike such clauses as disguised non-competes. California is the most aggressive on this front, voiding confidentiality language that functions to restrain trade even where the word "non-compete" never appears. The practical effect is counterintuitive: the broader you write the NDA, the less it protects you, because an unenforceable clause protects nothing at all.
One drafting detail trips up even careful employers. Under § 1833(b) of the Defend Trade Secrets Act, an NDA that governs trade secrets must include a notice of the whistleblower immunity that shields people who disclose secrets to the government or in a sealed court filing. Omit it, and you forfeit the right to recover punitive damages and attorney's fees in a federal trade-secret suit. It is a single paragraph, and leaving it out quietly downgrades your remedies. If your business handles employees and confidential information together, it is worth coordinating your NDA with your broader employment agreements and confidentiality terms so the documents reinforce rather than contradict one another.
Mutual, employee, and deal NDAs are not interchangeable
The word "NDA" hides three quite different instruments, and using the wrong one is a common and expensive mistake. A mutual NDA binds both sides to secrecy and suits two companies exploring a partnership, a joint venture, or an acquisition, where each will see the other's confidential material. A one-way NDA protects a single disclosing party, the usual choice when an employer or client shares secrets with someone who has nothing comparable to give back. An employee or contractor confidentiality agreement is built into the working relationship and almost always pairs cleanly with an independent contractor agreement or an at-will employment contract.
Founders face the sharpest version of this. Investors rarely sign NDAs at the pitch stage, so the real protection for an early company sits in the agreements among the people building it and the contractors touching the code. A confidentiality and IP assignment agreement does double duty here, locking down secrets and making sure the company actually owns what its team creates. Pairing that with the right business and corporate documents is what turns a loose group of collaborators into a defensible business.
Drafting a defensible NDA on Captain.Legal
You do not need a lawyer on retainer to produce a confidentiality agreement that a court will respect, but you do need one that fits your state and your situation rather than a generic form pulled off a search result. On Captain.Legal you start by telling the assistant what you are protecting and who is signing, and the document assembles around those answers. You choose whether the obligation runs one way or both ways, you name the categories of confidential information instead of reaching for "everything," and you set a duration that matches the sensitivity of the material rather than an indefinite term that invites a challenge.
The generator handles the parts people forget. It folds in the Defend Trade Secrets Act whistleblower notice so your federal remedies stay intact, it keeps the confidentiality scope tied to genuine secrets so the clause does not read as a hidden non-compete, and it adapts the governing-law and exclusions language to the state you select. When you are finished you download a clean file in Word to edit and in PDF to sign, ready immediately, with no account required. Because the templates track changes in federal and state law, you are working from the current standard rather than a form that predates the FTC saga.
Mistakes that quietly void a confidentiality agreement
The most damaging error is the one that feels like extra safety: writing the confidentiality scope as broadly as possible. Defining secrets to include general skills, industry knowledge, or public information does not strengthen the NDA, it converts it into a de facto non-compete that a court in California and a growing list of other states will refuse to enforce. The second common failure is the perpetual term. An NDA that never expires looks aggressive on paper but reads as unreasonable to a judge, and a finite term tied to how long the information stays valuable holds up far better.
Three more mistakes recur in practice. Employers routinely omit the § 1833(b) whistleblower notice and only discover the cost when they try to claim enhanced damages and cannot. Many copy a single template across every relationship, using a one-way employee NDA for a two-company negotiation where a mutual agreement was needed, which leaves one side unprotected. And almost everyone forgets to specify governing law, which matters enormously when NDA enforceability swings so sharply from one state to the next; a clause that is routine in Texas may be partly void in California. None of these flaws is visible until the agreement is tested, which is exactly when it is too late to fix them.
Frequently asked questions
Are NDAs still legally enforceable in the US after the FTC rules?
Yes. The FTC rule that drew attention in 2024 targeted non-compete clauses, not NDAs, and it never took effect. A federal court vacated it nationwide in Ryan LLC v. FTC, the FTC dropped its appeal in 2025, and the rule was formally removed from the regulations in early 2026. NDAs have always been governed by state contract law, state trade-secret statutes, and the federal Defend Trade Secrets Act, and that remains true today. A confidentiality agreement that protects genuine secrets and does not block the signer from working in their field is enforceable in virtually every state.
Did the FTC ever ban non-disclosure agreements?
No. The FTC explicitly stated that its non-compete rule did not categorically prohibit NDAs or non-solicitation agreements. The only NDAs it flagged were those drafted so broadly that they effectively prevented a worker from taking another job, which the Commission treated as de facto non-competes. An ordinary NDA covering trade secrets, client data, or unreleased products was never within the rule's reach, and even that rule has since been struck down and removed.
What makes a confidentiality agreement unenforceable?
The usual culprits are overbreadth and indefinite duration. An NDA that defines confidential information to include general skills or publicly available knowledge reads as a disguised non-compete, and courts, led by California, strike such clauses. A perpetual term, a missing governing-law provision, or the absence of the Defend Trade Secrets Act whistleblower notice can also weaken or partly invalidate the agreement. A defensible NDA names specific secrets, sets a reasonable time limit, and identifies the state whose law applies.
Can I download an NDA in Word and PDF?
Yes. On Captain.Legal you answer a few questions, the agreement builds itself around your answers, and you download it in both formats. The Word file lets you make final edits, and the PDF is ready to sign as is. Both are available instantly with no account required, so you can have a finished, signature-ready document in minutes rather than waiting on a law firm to return a draft.
How long does an NDA last?
It depends on what you are protecting, and you set the term when you create the document. Confidentiality obligations commonly run from two to five years after the relationship ends, though true trade secrets can be protected for as long as they stay secret. Avoid an indefinite term for ordinary business information, because courts may view a perpetual restriction as unreasonable. A duration tied to how long the information actually retains value is both more enforceable and easier to defend if challenged.
Do I need a mutual or a one-way NDA?
Use a mutual NDA when both parties will share confidential information, such as two companies discussing a partnership or acquisition. Use a one-way NDA when only one side discloses secrets, the typical situation for an employer sharing material with a worker or a business briefing a contractor. Choosing the wrong type is a frequent mistake: a one-way agreement leaves the second discloser unprotected, while a mutual agreement imposes obligations a one-sided relationship does not require.
Does state law really change whether my NDA holds up?
Significantly. NDA enforceability turns on state contract and trade-secret law, and the standards vary widely. California scrutinizes confidentiality clauses for any restraint-on-trade effect and voids those that function as non-competes, while other states enforce reasonably tailored agreements with little friction. Because of this, naming the governing law in the agreement is not a formality; it decides which set of rules a court applies if the NDA is ever tested.
Will the FTC try to ban non-competes again?
Possibly, though not through the vacated rule, which is gone. After dropping its appeal, the FTC opened a public inquiry into non-competes and has pursued individual enforcement actions under Section 5 against employers using especially restrictive agreements. None of this affects ordinary NDAs. For confidentiality agreements, the practical guidance is unchanged: keep the scope tied to real secrets, set a reasonable term, and the document stays firmly enforceable under state law.