Are perpetual confidentiality clauses enforceable for tech employees in Idaho?
Are perpetual confidentiality clauses enforceable in Idaho? Learn the legal standards for tech employees and how to assess your contract risk today.
Are perpetual confidentiality clauses enforceable for tech employees in Idaho?
In Idaho, perpetual confidentiality clauses are generally enforceable only if they are strictly limited to protecting legitimate trade secrets. If a clause is drafted broadly to cover general industry knowledge, skills, or non-proprietary information, Idaho courts will likely strike it down as an unreasonable restraint of trade.
Key takeaway: A perpetual duration is only legally defensible if the information being protected remains a trade secret indefinitely. If the information becomes public or common knowledge, the perpetual restriction becomes unenforceable.
The Legal Framework: Idaho Trade Secrets Act (ITSA)
Idaho law distinguishes between protectable trade secrets and general employee knowledge. The Idaho Trade Secrets Act (ITSA) provides the statutory basis for protecting proprietary information. For a confidentiality clause to survive judicial scrutiny, the information must meet the following criteria:
- Economic Value: The information must derive independent economic value from not being generally known.
- Secrecy: The employer must take reasonable efforts to maintain its secrecy.
- Specificity: The clause must clearly define what constitutes a trade secret rather than using catch-all language.
Action Item: Review your contract to see if it defines "Confidential Information" narrowly. If it includes "all information learned during employment," it is likely overbroad and potentially unenforceable.
Why "Perpetual" is a Red Flag
While many tech contracts include "perpetual" language, Idaho courts view these with skepticism. The primary concern is whether the clause functions as a de facto non-compete agreement. If a confidentiality clause prevents a developer from using their general coding skills or standard industry practices, it violates public policy.
| Feature | Enforceable Clause | Unenforceable Clause |
|---|---|---|
| Scope | Specific algorithms, source code, client lists | "All knowledge gained during employment" |
| Duration | Perpetual (for trade secrets only) | Perpetual (for general skills/methods) |
| Purpose | Protecting proprietary assets | Restricting employee mobility |
Action Item: If your contract contains a perpetual clause, check if there is a "carve-out" for information that enters the public domain or is independently developed.
Criteria for Judicial Review
When an Idaho court evaluates a confidentiality agreement, they apply a "reasonableness" test. Even if a contract is signed, it can be invalidated if it fails these three tests:
- Legitimate Business Interest: Does the employer actually have a trade secret to protect?
- Scope of Restriction: Is the restriction limited to the specific information that provides a competitive advantage?
- Undue Hardship: Does the clause prevent the employee from working in their chosen field or utilizing their general professional skills?
Key takeaway: Idaho courts have the power to "blue-pencil" or modify overbroad contracts, but they are not required to do so. Relying on a court to rewrite your contract is a high-risk strategy.
Distinguishing Trade Secrets from General Skill
Tech employees often worry that their knowledge of specific frameworks or languages will be restricted. Idaho law is clear: an employer cannot own your "general knowledge, skill, and experience."
- Protectable: Proprietary source code, secret formulas, internal customer databases, and non-public business strategies.
- Unprotectable: General programming languages (e.g., Python, Rust), standard industry methodologies, and soft skills developed on the job.
Action Item: Document the specific skills you brought to the job versus those you learned. If a clause attempts to restrict the former, it is legally suspect.
How to Assess Your Contract Risk
If you are currently reviewing an employment agreement, look for these specific indicators of an overreaching clause:
- Lack of Definition: The contract fails to define "Confidential Information" with precision.
- No Public Domain Exception: The clause fails to exclude information that becomes public through no fault of the employee.
- Overlapping Restrictions: The confidentiality clause is paired with a non-compete or non-solicitation clause that is already legally questionable under Idaho law.
TermScore provides an automated, AI-driven analysis of your employment contracts, identifying overbroad confidentiality clauses and potential red flags in seconds. By comparing your agreement against current Idaho legal standards, TermScore helps you understand your obligations and risks without the high cost of manual legal review.
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.
TermScore Legal Intelligence Group
Audited for 2026 StandardsResearched 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.
Get the contract red-flag checklist
Join landlords and freelancers getting clause breakdowns and benchmark data. No spam.
Keep reading
NDA Rights by State
Are perpetual confidentiality clauses enforceable for remote employees in New Hampshire?
NDA Rights by State
Are perpetual confidentiality clauses enforceable in Texas employment contracts?
NDA Rights by State
Are perpetual confidentiality clauses in NDAs enforceable under Texas law?
NDA Rights by State
What are the enforceable duration limits for NDAs in Nebraska for tech employees?
NDA Rights by State
Are there specific state limits on NDA confidentiality duration for tech employees in Maryland?
NDA Rights by State
How do state-level trade secret laws in North Carolina impact the enforceability of perpetual confidentiality clauses?