Employee Non-Disclosure Agreement Template | All 50 States

An employee non-disclosure agreement is a written promise from a worker to keep designated company information private, both during employment and for a defined period afterward. It identifies the categories of protected material, sets the boundaries of permitted use, and spells out the remedies an employer can pursue if the promise is broken. The document works in one direction: the employee receives the confidential information and owes the duty, while the company is the disclosing party. That makes it a unilateral NDA, distinct from the mutual version two businesses sign before a joint venture.

People often confuse the employee NDA with a non-compete, and the difference matters in court. A confidentiality agreement restricts the use and disclosure of information; it does not stop someone from working for a competitor. A non-compete restricts where and for whom a person can work, which is why so many states scrutinize or ban it outright. An NDA is far more durable precisely because it protects a legitimate property interest rather than blocking employment. Treat these as separate instruments, because courts that strike down an overbroad non-compete will frequently leave a well-drafted confidentiality clause standing. If your business also needs movement restrictions, the right pairing is a dedicated non-compete and non-solicitation agreement built for all 50 states, kept legally distinct from the NDA.

Trade secret protection in the United States runs on two parallel tracks, and an employee NDA is the connective tissue between them. At the federal level, the Defend Trade Secrets Act of 2016 (18 U.S.C. §1836) created a private right of action allowing employers to sue in federal court for misappropriation of trade secrets used in interstate commerce. Below it, 48 states have adopted some version of the Uniform Trade Secrets Act (UTSA), with New York and North Carolina relying on common law instead. Both frameworks share one demanding requirement: information qualifies as a trade secret only if the owner took reasonable measures to keep it secret. A signed NDA is the single most persuasive piece of evidence that you did. The federal statute and its remedies are summarized clearly in the Cornell Legal Information Institute overview of the Defend Trade Secrets Act.

The DTSA carries a trap that voids a key remedy if you ignore it. Since the statute took effect, employers must include an immunity notice in any agreement governing confidential information, telling the employee that disclosing a trade secret to a government official or attorney solely to report a suspected legal violation carries no liability. Skip this notice and you forfeit exemplary damages and attorney's fees against that employee, even in a clear-cut theft case. Our template embeds the statutory whistleblower language by default.

Enforceability also turns on consideration and scope. When an employee signs at the start of employment, the job offer itself supplies the consideration. When you ask a current employee to sign mid-tenure, several states demand something extra, a raise, a bonus, or continued employment treated as valid in others. Courts further expect the confidentiality period to be reasonable and the defined information to be genuinely proprietary rather than common industry knowledge. A clause that tries to lock down everything an employee ever learned tends to collapse under its own weight.

The clearest trigger is onboarding anyone who will touch sensitive material. Engineers who see source code, sales reps handed the customer database, finance staff who know margins and supplier terms: each should sign before the first login is provisioned. Timing is everything here, because an NDA presented on day one rides on the employment offer for consideration, while the same form handed over six months later may need fresh consideration to bind the worker in stricter states.

A second scenario is the role change. An employee promoted from a junior position into one with access to trade secrets or strategic plans should sign an updated agreement that reflects the new information they will hold. Companies preparing for a financing round, an acquisition, or a new product launch also tighten confidentiality across the workforce, since investors and acquirers conduct diligence on exactly these protections.

Contractors and temporary staff form an edge case worth flagging. A freelancer is not an employee, yet they often see the same confidential systems, so they need a confidentiality instrument too, frequently bundled into the services contract rather than signed separately. Another easily missed situation is the departing employee: an exit interview is the moment to reaffirm continuing obligations and recover company property, and a well-drafted NDA already gives you the leverage to insist on it. Businesses scaling their hiring usually standardize the NDA alongside the rest of their US employment document templates so no new hire slips through without one.

• The definition of confidential information is the engine of the entire agreement. Our template uses a layered definition that names specific categories (source code, customer lists, pricing models, business plans) while keeping a sensible catch-all, because a definition that is either too vague or absurdly broad invites a court to narrow it. We deliberately exclude information that is already public or independently developed, which keeps the clause defensible.
• The scope of permitted use restricts the employee to using confidential material only for performing their job. This is what separates an NDA from a property-transfer document. It lets the worker do their work while making any disclosure to outsiders, or any use for personal benefit, a clear breach.
• The duration of obligations is drafted on two timelines. Ordinary confidential information typically carries a fixed post-employment term of two to five years, while genuine trade secrets remain protected for as long as they stay secret, mirroring how the UTSA itself treats them.
• The DTSA whistleblower immunity notice appears verbatim as the statute requires, preserving your right to seek exemplary damages and fees. Leaving it out is the most common drafting failure we see in homemade NDAs.
• The return-of-property clause obligates the employee to surrender all documents, devices, and copies on separation, and to delete company data from personal accounts. Paired with it, the remedies clause authorizes injunctive relief, recognizing that money rarely undoes a leaked secret.

California treats confidentiality agreements very differently from non-competes. Under Business and Professions Code §16600, California voids most post-employment competition restraints, yet it fully enforces NDAs that protect genuine trade secrets, and the state has its own Uniform Trade Secrets Act at Civil Code §3426. Draft the NDA so it reads as pure confidentiality and never strays into restraint of trade, because California courts will scrutinize any clause that functions as a backdoor non-compete and may invalidate it.

Texas enforces confidentiality agreements readily and adopted the Texas Uniform Trade Secrets Act (Civil Practice and Remedies Code Chapter 134A). Texas courts uphold reasonable confidentiality terms and even view a promise to disclose proprietary information as valid consideration for a current employee's signature, which makes mid-employment NDAs easier to enforce here than in many states.

New York stands out as one of the few jurisdictions without a statutory trade secret act, relying instead on common law shaped by decades of case law and the Restatement of Torts. Courts apply a multi-factor test to decide whether information truly qualifies as secret, so a precise contractual definition does real work in New York. The state also recently moved to restrict certain employer practices around employee speech, making careful drafting more important than ever.

Florida offers strong protection through the Florida Uniform Trade Secrets Act (Chapter 688, Florida Statutes) and a generally employer-friendly posture. Florida courts will enforce confidentiality obligations and, unlike with non-competes, do not require the tight durational limits the state imposes on movement restrictions, giving employers more latitude in how long the secrecy duty runs.

You begin by identifying the parties, entering the legal name of your company and the full name of the employee who will receive the confidential information. From there the form asks you to select the state that governs the agreement, and it adjusts the consideration language and any state-specific notices accordingly. The next step is the heart of the document: you describe the categories of confidential information your business actually holds, choosing from common presets like customer data, source code, and financial records, then adding anything specific to your industry.

After defining the information, you set the duration of the post-employment confidentiality obligation and confirm whether the worker is a new hire or a current employee, since that choice changes how consideration is handled. The template automatically inserts the DTSA whistleblower immunity notice and the return-of-property terms, so you do not have to remember them. You then review the assembled agreement, make any edits in the editable sections, and download it in Word and PDF. Most employers store the signed copy alongside the rest of their onboarding paperwork; if you need a broader set, the full catalog of US legal document templates covers the related forms.

The most damaging error is defining confidential information so broadly that a court refuses to enforce any of it. An NDA claiming that everything an employee sees is secret signals to a judge that the employer never seriously classified its information, and overbroad definitions are routinely struck down. The fix is specificity paired with a reasonable catch-all. A close second is omitting the DTSA immunity notice, which quietly strips you of exemplary damages and attorney's fees against the very employee you are suing. Employers also stumble on consideration: asking a long-tenured worker to sign without offering anything new can leave the agreement unenforceable in states that demand fresh consideration.

Another frequent failure is treating the NDA as a substitute for a non-compete. Confidentiality language cannot stop someone from joining a rival, and drafting it to do so risks invalidation, especially in states like California. Keep the two instruments separate and purpose-built. Finally, many businesses sign the agreement and then never enforce their own secrecy program, leaving documents unmarked and access uncontrolled. Courts look at whether you actually behaved as though the information was secret, so a signed NDA paired with sloppy handling can still fail. Pairing the NDA with a written data-handling policy, such as the approach in a CCPA and CPRA-compliant privacy policy, reinforces that the protection is real.