Are perpetual confidentiality clauses for software developers enforceable under Rhode Island law?

Are perpetual confidentiality clauses enforceable in RI? Generally, no. Rhode Island courts disfavor indefinite restrictions. Use TermScore to audit yours.

November 5, 2026TermScore Legal Intelligence GroupStatutory & Corpus Verified600 words

Are Perpetual Confidentiality Clauses Enforceable in Rhode Island?

In Rhode Island, perpetual confidentiality clauses are generally unenforceable unless they specifically protect legitimate trade secrets. Rhode Island courts apply a 'reasonableness' standard to restrictive covenants; indefinite duration clauses are typically viewed as overbroad and contrary to public policy, as they unfairly restrict a developer's ability to utilize their general knowledge and skills.

Key takeaway: If a contract does not distinguish between trade secrets and general confidential information, a perpetual term is a major red flag that will likely fail judicial scrutiny in a Rhode Island court.

The Legal Framework: Reasonableness and Public Policy

Rhode Island law follows the common law tradition of disfavoring restraints on trade. When a court evaluates a confidentiality agreement, it balances the employer's interest in protecting proprietary information against the employee's right to earn a living. A perpetual clause fails this balance because it creates an indefinite burden on the developer.

The Rhode Island Uniform Trade Secrets Act (RIUTSA)

It is critical to distinguish between trade secrets and confidential information. Under the Rhode Island Uniform Trade Secrets Act (R.I. Gen. Laws § 6-41-1 et seq.), trade secrets are protected as long as they maintain their status as secrets. If your contract defines 'Confidential Information' to include things that are not actually trade secrets—such as general coding practices, common software architectures, or public knowledge—a perpetual restriction is legally vulnerable.

  • Trade Secrets: Protected indefinitely by statute, provided they derive independent economic value from not being generally known.
  • General Confidential Information: Requires a 'reasonable' duration. Courts typically look for timeframes between 12 and 36 months.

Action Item: Review your contract to see if 'Confidential Information' is defined broadly. If it includes 'all information learned during employment,' it is likely overbroad and unenforceable.

Comparison: Perpetual vs. Time-Limited Clauses

FeaturePerpetual ClauseTime-Limited Clause (e.g., 2 Years)
EnforceabilityLow (unless trade secret)High (if reasonable)
Judicial ScrutinyStrict/HostileBalanced/Deferential
Developer RiskHigh (career limitation)Low (predictable)
Employer ProtectionExcessiveSufficient

Red Flags in Software Development Contracts

When reviewing your employment or contractor agreement, look for these specific indicators that the confidentiality clause may be unenforceable:

  • Lack of Exclusions: The clause fails to exclude information that is already public, independently developed, or received from a third party.
  • Overly Broad Definitions: The definition of 'Confidential Information' includes general programming languages, frameworks, or methodologies.
  • No 'Reasonable' End Date: The contract uses terms like 'forever,' 'in perpetuity,' or 'without limitation' regarding the duration of the obligation.
  • Lack of Severability: The contract lacks a clause allowing a court to 'blue-pencil' or modify an unreasonable restriction, potentially voiding the entire agreement.

How to Negotiate Better Terms

If you are presented with a contract containing a perpetual confidentiality clause, you should advocate for modifications that align with industry standards. Follow these steps:

  1. Request a Sunset Provision: Propose a specific duration, such as 24 months post-termination, for non-trade secret information.
  2. Narrow the Definition: Explicitly exclude 'general skills, knowledge, and experience' acquired during the engagement.
  3. Carve Out Public Domain: Ensure the contract states that information that becomes public through no fault of the developer is no longer confidential.
  4. Reference RIUTSA: Clarify that the perpetual obligation applies only to information meeting the statutory definition of a trade secret under Rhode Island law.

Key takeaway: Never sign a contract that treats your general professional knowledge as a perpetual trade secret. Always negotiate for a clear expiration date on non-proprietary information.

The Role of TermScore in Contract Analysis

Manually identifying overbroad clauses in complex software development agreements is time-consuming and prone to error. TermScore uses advanced AI to instantly flag perpetual confidentiality clauses, compare your contract terms against Rhode Island legal standards, and provide actionable suggestions for negotiation. By using TermScore, you can ensure your agreements are fair, enforceable, and protective of your professional future without needing to parse through dense legal jargon yourself.

Instant Clause Diagnostic

Check a suspicious clause under Rhode Island 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