Do NDA Agreements Expire? (w/Examples) + FAQs

Yes, most NDAs expire, because nearly every one names a fixed term of one to five years. Secrecy duties end when that term runs out, according to Rocket Lawyer's contract guidance. The exception is trade secrets, which many NDAs protect for as long as the details stay secret, sometimes forever. Confusing the two kinds is the top reason people accidentally violate an old agreement.

An old signature can bind you if its clause never expired. A departing employee or a wound-down vendor deal often forgets which promises survive. Startups, contractors, investors, and anyone who signed one during a job or a deal all face the same question eventually: has this thing run out, or am I still on the hook?

What Determines Whether Your NDA Expires

This article reflects general contract and trade-secret guidance as of August 2026. Rules below vary by state, so confirm your state's approach and your NDA's exact wording before you rely on any of it. An NDA is a contract, and it expires when its own text says so, not on some universal timeline. Look for a section titled Term, Length, or Confidentiality Period, because that clause controls how long you are bound, not your memory of the deal.

Most drafters split secret details into two kinds. Missing that split is where confusion starts. Normal details, like a client list or a marketing plan, often carry a stated end date. Trade secrets, like a formula or a factory process, often get a longer or open-ended clause instead, since their whole value depends on staying secret.

Not knowing which kind applies has costs: say you assume your whole NDA expired after three years because the cover page implied it. If the trade-secret clause survives forever, you can still be liable for disclosing that one protected detail years later. The reverse mistake, believing an NDA never expires when it already had a hard end date, can cost you a fair shot at a deal. Read the Survival section closely, since it lists which promises outlive the main term.

A common mistake is that leaving a job or ending a deal automatically ends the NDA, but it does not. According to BrewerLong's contract-law team, most NDAs state that secrecy continues "for a term of five years" or similar, counted from signing or sharing. That clock keeps running whether or not the deal itself has ended. So pull the document, find the Term and Survival sections, and write down the real date or trigger, rather than relying on what you assume the deal implied.

The fix here is quick and it works each time. Grab the actual NDA file, not the memory of it. Search the text for the word "Term," then read the sentence that follows it word for word. That one line almost always settles the question.

How Long Do Most NDAs Last?

Real-world NDA terms cluster into a few predictable bands, and knowing them helps you sanity-check whatever you signed. Short one-year terms show up in fast-moving conversations, like an early sales pitch or a preliminary vendor call. That fits because the shared details tend to lose value quickly. A two-to-three-year term is the default for normal business exchanges: vendor onboarding, contractor NDAs, and early-stage partnership talks.

Higher-value details tend to get a three-to-five-year window. That is the range BrewerLong reports as most common overall for business NDAs. This band fits financial details, business plans, and customer data that stay competitively sensitive well past a single deal. Then there is the open-ended tier, reserved almost exclusively for trade secrets, where the duty runs for as long as the details stay secret.

None of these bands are fixed by law; they are norms that shift with leverage and industry habit. A larger company sharing routine vendor details can often push a counterparty toward the shorter end. A founder disclosing a core process to one investor has good reason to ask for the longer end, or an explicit trade-secret carve-out. Renewal clauses add another layer, letting either side extend the first term instead of drafting a brand-new agreement.

The threshold is not a fixed number of years; it is whether the shared material counts as a trade secret under your state's law. A recipe or client database can lose that status the moment it becomes public through no fault of the receiving party. That is why even an "open-ended" clause has a built-in off-ramp. An old NDA covering details that have since become common industry knowledge is toothless, even if the paper clause never technically expired.

Trade Secrets: The Duty That Doesn't Expire

Federal law treats trade secrets differently from any other thing an NDA might protect, which is why "does my NDA expire" rarely has one clean answer. The Defend Trade Secrets Act lets a company sue in federal court for misuse. That remedy exists because the underlying details stay valuable only as long as they stay secret. There is no federal filing that "protects" a trade secret like a patent does; the protection is the secrecy itself, so the duty has no fixed end date.

State law layers on top of that federal baseline, and this is where your state's rules matter. Most states apply a version of the Uniform Trade Secrets Act, which defines what counts as a trade secret and what remedies apply for misusing one. The exact standards, damages rules, and injunction procedures still differ from state to state. A handful of states have historically leaned on their own common-law approach instead of the uniform act, so check your specific state rather than assume the same rule applies everywhere.

Here is the misconception that trips people up most: assuming a five-year main term also caps the trade-secret carve-out at five years. In practice, a well-drafted NDA states plainly that "trade secrets shall be kept secret forever," apart from the main term. That is the exact structure BrewerLong's sample language suggests, and a former worker who assumes their whole duty lapsed after five years can still face a federal trade-secret claim over the one detail the NDA singled out. Read the trade-secret clause as its own promise, confirm which law governs your state, and treat any clearly "open-ended" wording as exactly that.

Age alone does not end a trade secret's protection. A ten-year-old formula can still be a live trade secret if the owner kept it locked down the whole time. What ends the duty is the secret leaking out, not the calendar. So an old NDA can bind you today, even though it feels ancient.

Which Situation Applies to You?

Vendors and Contractors

A vendor or contractor NDA should match the length of the project, not an arbitrary default. Say you are sharing pricing or system access during a six-month stint; a one-to-two-year term often covers the project plus a fair buffer. The risk is a generic template that runs far longer than the relationship needs, which can limit you from working with a rival long after the project wrapped up. Check whether the NDA requires you to return or destroy files when it ends, since that duty often outlasts that term itself.

Vendor NDAs also tend to be mutual, meaning both sides owe each other secrecy. Read your own duties as carefully as the other side's. A mutual clause can bind you to a longer term than expected, if the counterparty's details turn out to include a trade secret. A short renewal note in your calendar, set for the term's end date, is a cheap habit that prevents a forgotten duty from becoming a dispute.

Employees Leaving a Job

An employee's NDA typically survives the job itself. The clause is written to protect the details the company shared while you worked there, not to end when your badge stops working. If you later wrote or reviewed owned code or client data, that exact material may fall under a trade-secret clause with no expiration at all. Before joining a rival, pull your old employment NDA and keep the main term apart from anything labeled a trade secret, since only the second kind is likely to bind you years later.

A departing employee's biggest blind spot is assuming an exit interview resets the clock on the first NDA. It does not. The separation paperwork simply reaffirms duties already running under the earlier NDA. If your new role touches anything close to your old employer's core product, ask an employment attorney to compare both documents before you start, not after a dispute begins.

Investors and Buyers in Due Diligence

Investor and buyout NDAs need to protect financial forecasts and plans without slowing down the deal. These often fall in the same three-to-five-year band common for higher-value NDAs. That length is long enough to cover the talks and the early post-deal period. The practical question is what happens to your notes if the deal falls through, since a well-written NDA spells out a return or destroy duty for exactly that case.

A founder talking to multiple investors at once should check each NDA. Some block you from discussing the same idea with a rival fund. Overlapping promises can box a founder into a corner during a fast raise. Naming the deal team, and setting a clear end trigger like a signed term sheet, keeps everyone's duties easy to track.

Startups Protecting a Trade Secret

A startup sharing its core algorithm or process with an investor or factory partner should treat that share as a trade secret from the first talk. That means drafting language that keeps that one item's duty open-ended, even if the surrounding NDA carries a shorter main term. A founder's real limit is often time and legal budget. So the efficient move is a short, targeted trade-secret clause layered onto a standard template.

Founders also need internal discipline, not only a good contract. A trade secret loses its legal protection the moment the company itself stops treating it as secret. Limiting access on a need-to-know basis, labeling sensitive documents, and logging who has seen the process all strengthen a later misuse claim. Courts weigh a company's own security habits when deciding whether details ever qualified as a trade secret at all.

Worked Example: Finding Your NDA's Exact Expiration Date

Here is a copyable method for checking whether your own NDA has expired. Priya signed a mutual NDA with a former client three years ago, while she worked on a software project for them. Now she wants to know if she can share it as a case study. Her first step is finding the effective date, which the signature block often states in plain terms, apart from any later date named elsewhere in the text.

Her second step is finding the Term clause, which in her NDA reads "secrecy shall continue for three years from the Effective Date." Her effective date was June 2023, so the main term ran out in June 2026. That means the plain details she shared are no longer covered as of this article's writing. Her third step, the one most people skip, is checking the Survival section for any carve-out that keeps running past that date.

Priya's Survival clause names one item, a piece of code she helped build, as a trade secret with no end date, apart from the normal three-year term. That means she can now share the shape of the project, since the main term has lapsed. She cannot describe that one piece of code, because that promise never had an end date at all. The same three-step method, find the date, read the Term clause, then check Survival, works for any NDA no matter who drafted it.

If Priya's NDA had used trigger-based language instead of a fixed term, the same three steps would still work. Step two would instead point her to an event, such as a project handoff or a written notice, rather than a date. Writing down her conclusion, and the exact words she relied on, gives her proof if the former client ever disputes her account. That record costs a few minutes now and can save weeks of back-and-forth later.

Where NDA Disputes Start

The Engineer Who Assumed the Clock Had Run Out

A mid-career engineer left a hardware company four years after signing an employment NDA with a stated three-year main term. He assumed the whole NDA had lapsed by the time he joined a rival. He was right about the normal secret details, like org charts and marketing plans. He was wrong about the exact factory process the first NDA flagged as a trade secret in its Survival section, and the company sent a cease-and-desist letter within weeks of his new job posting describing his prior work.

The Founder Who Signed an Investor's Boilerplate

A first-time founder signed an investor's standard NDA before a due-diligence call. She assumed, incorrectly, that it ran the same short one-year term she had used with earlier vendor conversations. This NDA was silent on a fixed end date and instead used trigger-based language ending "when the deal closes or is formally ended in writing." The deal stalled without either side sending that written notice, so her duty stayed active for over two years after the talks had stopped.

The Vendor Relationship That Never Formally Ended

A small marketing agency signed an NDA with a client that included a return-or-destroy clause. It required all shared files to be deleted and certified within thirty days of the project ending. The project wound down slowly over several months, with no clear end date and no signed proof ever sent, so the duty to destroy files was never triggered. When the client later disputed an invoice and demanded proof the files were destroyed, the agency had no records, turning a small billing disagreement into a drawn-out compliance argument.

The lesson here differs from the first two. It is not about a misread clause, but about a clause with no clear closing act. A term that ends "on completion of the project" is only as clear as everyone's view on when the work truly finished. Sending a short written notice, even a one-line email confirming the project's close, creates the paper trail that a purely informal wind-down never does.

Mistakes to Avoid

• Assuming the whole NDA expired because the main term did. Trade secret and Survival clauses often keep exact promises alive long after the main term ends, and missing that split is the top source of accidental violations.
• Never checking the Survival section at all. This is the clause that lists which duties outlive the NDA, and skipping it means guessing about your exposure.
• Reusing a generic NDA template for every situation. A one-size-fits-all NDA rarely matches the sensitivity of the details at hand, leaving too little protection or an unnecessarily long limit.
• Treating "the relationship ended" as the same thing as "the NDA ended." Most such clauses run from signing or sharing, so quitting a job or finishing a project does not automatically end anything.
• Failing to return or destroy documents as required. Many NDAs make this an explicit condition of winding down cleanly, and skipping it can leave you unable to prove compliance later.
• Assuming a trigger-based NDA ends on its own. An NDA that ends "when the deal closes or is ended in writing" needs an actual event or notice; silence does not end it.
• Ignoring which state's law governs the NDA. Trade-secret standards and how courts treat open-ended terms vary enough between states that the same disclosure can carry very different exposure.
• Not updating an old NDA as the underlying secret evolves. A clause written for an outdated version of your trade secret may not clearly cover the current one.

Do's and Don'ts for Any NDA You Sign

Before you sign or rely on an NDA, run through a short list. It keeps your exposure clear. None of these steps take more than a few minutes. Skipping them is how people end up bound by a clause they never read closely.

Do

• Read the Term, Duration, and Survival sections before signing, because those three clauses, not the cover page, determine your real duties.
• Separate everyday details from trade secrets in your own notes, so you know which promises expire and which do not.
• Keep a copy of every NDA you sign, with the effective date clearly marked, since you will need it years later to answer exactly this question.
• Confirm which state's law governs the NDA, because trade-secret rules and enforcement standards differ meaningfully across state lines.
• Ask for return-or-destroy language with a clear deadline, so winding down the relationship has a defined, provable end point.

Don't

• Don't assume a relationship ending automatically ends the NDA, since most such clauses run on their own calendar, independent of the underlying deal.
• Don't sign a trigger-based NDA without asking who sends the ending notice, or the duty can drag on forever by default.
• Don't rely on memory instead of the document, because duration clauses are specific and easy to misremember years later.
• Don't discuss or reuse details from an old NDA without re-reading the Survival section first, even if you are confident the main term has lapsed.
• Don't treat every NDA as either permanent or short-term, since the real answer depends entirely on the specific clause in front of you.

Pros and Cons of Signing a Long or Indefinite NDA

Pros

• Stronger protection for sensitive material, because a longer or open-ended term matches the real, lasting value of a trade secret or core process.
• Fewer redone deals over time, since a well-drafted long-term clause avoids the burden of repeatedly extending a short agreement.
• Clearer signal to courts about intent, as an explicit open-ended trade-secret clause helps show a company actively guarded that secret.
• Better alignment with slow-moving industries, where a formula or process can stay competitively valuable for a decade or longer.
• Reduced risk of accidental early disclosure, because a longer term keeps a wider set of collaborators bound while people forget the deal.

Cons

• Broader limit on your future work or conversations, since a long or open-ended term can limit what you discuss publicly for years after a relationship ends.
• Harder to track over time, because an NDA signed a decade ago is easy to forget entirely, raising the odds of an unintentional breach.
• Uneven how well it holds up across states, since some courts scrutinize a very long general term more skeptically than a clearly justified trade-secret clause.
• Can chill legitimate teamwork, as an overly broad open-ended term may discourage former employees or partners from working in the same field at all.
• Harder to prove ongoing value, because if the "secret" quietly becomes industry-standard knowledge, an open-ended clause offers a false sense of continued protection.

What to Do Next

1. Pull the actual NDA document, not your memory of the deal, and locate the Term, Duration, or Confidentiality Period section.
2. Read the Survival clause closely, and write down any duty, especially around trade secrets, that continues after the main term ends.
3. Note the effective date and any trigger events, such as "ending of the NDA" or "closing of the deal," that could end the duty early or extend it.
4. Check whether documents must be returned or destroyed, and follow that process with written confirmation if the NDA requires it.
5. Confirm which state's law governs the NDA, since trade-secret standards and enforcement approaches differ meaningfully by jurisdiction.
6. Bring in a business attorney for anything ambiguous, especially a trade-secret carve-out or a dispute over an old NDA, since this article is educational and not a substitute for advice on your specific situation.

Frequently Asked Questions

How do I find the duration clause in my NDA?

Look for a section titled "Term," "Duration," or the like, often near the end of the document. If none of those headings appear, check the definitions section for language on when secrecy begins and ends.

Can a company still enforce an NDA after I quit my job?

Yes. Leaving a job does not end an NDA, because most such clauses run from the signing or sharing date, not your employment status, and any trade-secret carve-out can remain open-ended.

What happens if my NDA doesn't list an end date?

It depends on the language. Some silent NDAs default to a "fair period" that courts determine case by case, while others use trigger-based endings tied to a deal closing or a formal written ending.

Are non-compete agreements and NDAs governed by the same rules?

No. A non-compete restricts where you can work, while an NDA restricts what details you can share. They often appear in the same contract but expire under separate clauses.

Can I get out of an NDA early?

Rarely, without agreement. Most NDAs require mutual consent to modify or end early, though some include a clause ending duties once the details become public through no fault of the receiving party.

Does an NDA still apply if the other party breaches it first?

Often, yes. Many agreements are written so your duty survives even if the other party violates their own duties, though a serious breach may give you separate legal claims.

How long can a company wait before suing over an NDA violation?

It depends on your state's statute of limitations for written contracts, which commonly runs three to six years, so a company cannot wait forever after learning of a breach.

Do NDAs need to be notarized to expire on schedule?

No. Notarization has no effect on an NDA's duration. The expiration date or trigger is controlled entirely by the Term and Survival language the parties agreed to.

What is a survival clause in an NDA?

It's the section listing which duties, most often secrecy on trade secrets and the duty to return documents, continue after the NDA's main term has otherwise ended.

Can an NDA be enforced in a different state than where I signed it?

Yes, often. Most NDAs include a governing-law clause specifying which state's rules apply, regardless of where the signing happened, though courts occasionally decline to enforce an unreasonable choice.

Does information becoming public end my duty early?

Often, yes, for details that become public through no fault of the receiving side. Most NDAs exclude public details from ongoing duties.

Should I get a lawyer to review my NDA before signing?

It depends on the stakes. A short vendor NDA rarely needs review, but any NDA involving trade secrets, equity, or a long-term relationship is worth a business attorney's time first.