Can an employer enforce a perpetual NDA in South Dakota for software developers?
Can South Dakota employers enforce perpetual NDAs for software developers? Learn the legal reality and how to protect your interests with TermScore.
Can an Employer Enforce a Perpetual NDA in South Dakota?
In South Dakota, a perpetual Non-Disclosure Agreement (NDA) is highly unlikely to be enforceable against a software developer. South Dakota courts generally require restrictive covenants to be reasonable in scope, duration, and geographic reach. A perpetual restriction is typically viewed as an unreasonable restraint of trade unless it is limited strictly to bona fide trade secrets that never lose their value.
The Legal Standard for NDAs in South Dakota
South Dakota law balances the employer's right to protect proprietary information against the employee's right to pursue their profession. While the state is generally employer-friendly regarding non-competes, NDAs are subject to the "reasonableness" test. If an NDA is drafted so broadly that it prevents a developer from using their general knowledge, skill, or experience, it will likely be struck down.
Key Factors for Enforceability
- Legitimate Business Interest: The employer must prove the NDA protects a specific trade secret or confidential process, not just general industry knowledge.
- Duration: Perpetual terms are rarely upheld. Courts prefer timeframes that align with the shelf-life of the technology (e.g., 1–3 years).
- Scope of Information: The definition of "confidential information" must be precise. Blanket definitions that include public knowledge are usually unenforceable.
- Undue Burden: The agreement cannot effectively prevent the developer from working in their field of expertise.
Key takeaway: If your NDA defines "confidential information" to include your general coding skills or common programming languages, it is likely overbroad and legally vulnerable.
The Uniform Trade Secrets Act (UTSA)
South Dakota has adopted the Uniform Trade Secrets Act (SDCL 37-29). This statute provides the primary framework for protecting intellectual property. Under this act, information is only protected if it:
- Derives independent economic value from not being generally known to the public.
- Is the subject of efforts that are reasonable under the circumstances to maintain its secrecy.
If an employer fails to take reasonable steps to keep information secret, they cannot claim it as a trade secret, regardless of what the NDA says. This is a critical defense for developers facing aggressive enforcement.
Comparison: Perpetual vs. Limited NDAs
| Feature | Perpetual NDA | Limited/Reasonable NDA |
|---|---|---|
| Duration | Indefinite | Defined (e.g., 24 months) |
| Enforceability | Low/Highly Risky | High/Standard |
| Scope | Broad/Vague | Specific/Narrow |
| Legal Standing | Often viewed as restraint of trade | Generally upheld as protective |
Red Flags in Software Developer NDAs
When reviewing your contract, look for these common red flags that suggest an overreaching agreement:
- "All-Encompassing" Definitions: Language that claims all code written, regardless of whether it relates to the employer's business, is confidential.
- Lack of Carve-outs: Failure to exclude information that is already in the public domain or independently developed.
- Non-Compete Overlap: NDAs that function as de facto non-competes by preventing you from working for competitors under the guise of "protecting trade secrets."
- No Termination Clause: The absence of a sunset provision for the confidentiality obligations.
Actionable Steps for Developers
- Audit the Definition: Ensure "Confidential Information" is clearly defined and excludes your general programming knowledge.
- Request a Sunset Clause: If you are signing a new agreement, negotiate a specific duration (e.g., 2 years post-employment).
- Document Your Skills: Keep a record of your technical skills and methodologies that were developed prior to your employment.
Key takeaway: Always request that the NDA explicitly excludes "general skills, knowledge, and experience" gained during your tenure. This is the most effective way to protect your future employability.
How TermScore Can Help
Navigating the nuances of South Dakota contract law can be complex, but you don't have to do it alone. TermScore uses advanced AI to instantly analyze your employment contracts, flagging overbroad definitions, unreasonable perpetual clauses, and potential conflicts with state law. By uploading your agreement to TermScore, you can identify high-risk language in seconds and gain the clarity needed to negotiate with confidence.
Check a suspicious clause under South Dakota 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
Can an employer enforce a perpetual confidentiality agreement in Arizona?
NDA Rights by State
What are the limitations on perpetual NDA confidentiality in Rhode Island?
NDA Rights by State
How do Montana's wrongful discharge statutes affect NDA confidentiality scope?
NDA Rights by State
Do state labor laws in Tennessee override NDA confidentiality regarding workplace safety?
NDA Rights by State
How do state-level trade secret laws in North Carolina impact the enforceability of perpetual confidentiality clauses?
NDA Rights by State
Are there specific state statutes in Ohio that limit the scope of NDAs for independent contractors?