Are perpetual confidentiality clauses for tech employees enforceable under Idaho trade secret law?

Are perpetual confidentiality clauses enforceable in Idaho? Learn how Idaho trade secret law limits indefinite restrictions and how to protect your firm.

November 13, 2026TermScore Legal Intelligence GroupStatutory & Corpus Verified720 words

Are Perpetual Confidentiality Clauses Enforceable in Idaho?

Perpetual confidentiality clauses are generally unenforceable in Idaho to the extent they attempt to restrict an employee's general knowledge, skills, or experience. While Idaho law protects actual trade secrets indefinitely, courts will strike down overbroad clauses that prevent former employees from using their professional expertise in future roles.

The Legal Framework: Idaho Trade Secrets Act (ITSA)

Idaho operates under the Idaho Trade Secrets Act (ITSA), codified at Idaho Code § 74-201 through § 74-208. The statute defines a trade secret as information that derives independent economic value from not being generally known and is subject to reasonable efforts to maintain secrecy.

Distinguishing Trade Secrets from General Knowledge

The primary point of failure for many tech employment contracts is the conflation of "proprietary information" with "general skill." Idaho courts follow the common law principle that an employee has a right to their own labor and experience. You cannot contractually prohibit an employee from using the general knowledge they acquired during their tenure.

  • Trade Secrets: Algorithms, source code, customer lists, and proprietary manufacturing processes. These are protectable indefinitely.
  • General Knowledge: Industry standard coding practices, general project management methodologies, and soft skills. These are not protectable.

Key takeaway: If your confidentiality clause is so broad that it effectively functions as a non-compete agreement, Idaho courts are likely to invalidate it under the public policy favoring employee mobility.

Action Item: Audit your current employment agreements to ensure they explicitly exclude "general knowledge, skills, and experience" from the definition of Confidential Information.

Enforceability Criteria for Confidentiality Clauses

To maximize the likelihood of enforcement in an Idaho court, your confidentiality provisions must meet specific criteria. Vague, "catch-all" definitions are the leading cause of litigation failure.

FeatureEnforceable ApproachUnenforceable Approach
DurationLimited to the life of the trade secretPerpetual/Indefinite
ScopeSpecific, defined categories"Any and all information"
ExclusionsExplicitly excludes public domainSilent on public domain
PurposeRestricted to business protectionRestricted to preventing competition

The "Reasonableness" Test

Idaho courts apply a reasonableness test to restrictive covenants. Even if a clause is labeled "confidentiality," if it imposes an undue burden on the employee’s ability to earn a living, it will be scrutinized. A perpetual clause is inherently "unreasonable" if it covers information that loses its value over time (e.g., outdated software versions or temporary marketing strategies).

Action Item: Replace "perpetual" language with "for as long as the information remains a trade secret under applicable law."

Drafting Best Practices for Tech Employers

When drafting agreements for software engineers, data scientists, or product managers, precision is your best defense. Use the following steps to structure your agreements:

  1. Define Confidentiality Narrowly: Use an exhaustive list of what constitutes a trade secret rather than a broad, open-ended definition.
  2. Include a Severability Clause: Ensure that if a court finds one part of the confidentiality provision overbroad, the rest of the agreement remains intact.
  3. Explicitly Acknowledge Employee Rights: State clearly that the agreement does not prohibit the employee from using their general knowledge or skills in future employment.
  4. Tie Duration to Value: If the information is not a trade secret, set a specific "sunset" period (e.g., 12 to 24 months) after which the information is no longer considered confidential.

Key takeaway: A narrowly tailored agreement is significantly more likely to be upheld in court than a broad, "one-size-fits-all" perpetual clause.

Action Item: Review your "Confidential Information" definition against the actual data your employees handle. If it covers everything they touch, it is likely too broad.

Common Red Flags in Idaho Employment Contracts

If you are reviewing existing contracts, look for these common "red flags" that signal potential unenforceability:

  • The "Everything is Secret" Clause: Any contract that defines all information shared with an employee as "Confidential" is legally suspect.
  • Lack of Consideration: In Idaho, restrictive covenants must be supported by adequate consideration (e.g., a signing bonus, promotion, or continued employment).
  • Overlapping Non-Competes: If your confidentiality clause is being used to bypass Idaho's strict requirements for non-compete agreements, it will be viewed with extreme skepticism by the judiciary.

Action Item: If you identify these red flags, consult with local counsel to amend the agreements to align with current Idaho standards.

Streamlining Contract Compliance

Manually reviewing hundreds of employment contracts for overbroad confidentiality clauses is time-consuming and prone to human error. TermScore provides an AI-powered solution that automatically analyzes your contract templates against Idaho’s specific legal standards, flagging perpetual clauses and overbroad definitions before they become a liability. By using TermScore, you can ensure your agreements are both protective and enforceable, allowing you to focus on scaling your tech business with confidence.

Instant Clause Diagnostic

Check a suspicious clause under Idaho law

Paste a sentence or clause from your nda rights by state to get an immediate statutory risk audit.

0/3000
§

TermScore Legal Intelligence Group

Audited for 2026 Standards

Researched and cross-referenced against statutory codes, judicial rulings, and TermScore's proprietary Corpus of 100,000+ analyzed contracts. Our intelligence unit continuously audits contract enforceability and predatory clause variance across all 50 US jurisdictions.

Methodology: Empirical Corpus + Statutory CodeEditorial Standards & Methodology →

Get the contract red-flag checklist

Join landlords and freelancers getting clause breakdowns and benchmark data. No spam.

Keep reading

Don't guess. Get your TermScore.

Upload your lease, employment contract, or agreement and let our AI flag every risk in seconds.

Score my document free