Ohio ·Standard & Professional editions

Ohio Software License Agreement Template

Ohio’s definition of improper means is a short list with no mention of reverse engineering or independent development, so an Ohio licence sits in the same position as a Florida one: the contract is the only source of the ban. The Ohio Software License Agreement adds no Ohio rule to clause 2.5 and uses the page to explain its liability limits. Ohio is the selection that adds the Ohio schedule, though clause 2.5 itself is unchanged.

Start your Ohio Software License Agreement

Ohio rules built into this template

  • Improper means: a short list of theft, bribery and similar conduct (Ohio Revised Code section 1333.61).
  • Silent: neither reverse engineering nor independent development is mentioned in the definition.
  • Liability cap: clause 8.1 caps each party’s aggregate liability at a stated sum, except for excluded matters.
  • Exclusions: clause 8.2 leaves fraud, willful misconduct and unlimitable matters outside the limit.
  • Consequential damages: clause 8.3 excludes indirect, incidental, special and consequential damages except where prohibited by law.
  • Dates: write the full date next to each signature on the Ohio document.
  • Not stated: Ohio licence tax, audit rights, export controls and open-source terms.

What the Ohio definition contains

Division (A) of section 1333.61 of the Revised Code gives a short list under improper means, from theft and bribery to espionage through electronic or other means. Nothing in the definition addresses reverse engineering or independent development.

Ohio’s edition therefore leaves clause 2.5 in its general wording.

The cap, its exceptions and consequential damages

Clause 8.1 caps each party’s aggregate liability at a stated sum except for excluded matters, and clause 8.2 explains that neither party excludes liability for fraud, willful misconduct or matters that cannot be limited under applicable law. Clause 8.3 adds that neither party is liable for indirect, incidental, special or consequential damages except where prohibited by law.

A licensee that expects to suffer lost profits from a failure should price that against clause 8.3.

Where the Ohio text came from

Ohio licence tax, audit rights, export controls and open-source terms were all not covered, and a user should confirm them on the current official code.

Assignment and mergers in the Ohio document

Clause 11.3 bars either party from assigning the licence without the other’s consent, except to a successor in a merger or in a sale of substantially all of its assets. A licensee that expects to be acquired should check which of those routes the deal will use.

The edition covers no Ohio statute on assignment of a software licence.

Who may use the software under an Ohio licence

Clause 2.1 grants a non-exclusive, non-transferable right, and clause 2.2 caps use at the number of authorised users the parties named. Clause 2.3 allows installation on the devices the licensee controls, and clause 2.4 permits a reasonable number of backup copies for archival use only.

An Ohio company that adds staff beyond the named count should amend the licence first, because use over the cap falls outside the grant.

What the Software License Agreement includes

  1. Parties and Software
  2. License Grant
  3. Restrictions
  4. License Fee and Taxes
  5. Term
  6. Delivery and Installation
  7. Source Code
  8. Ownership and Confidentiality
  9. Support and Updates
  10. Warranties
  11. Intellectual Property Indemnity
  12. Limitation of Liability
  13. Audit and Compliance
  14. Termination
  15. Governing Law

Frequently asked questions

Does Ohio’s trade secrets statute mention reverse engineering?
The definition of improper means does not, so the edition states no Ohio rule on it.
What limits liability in the Ohio document?
A stated cap under clause 8.1 and an exclusion of consequential damages under clause 8.3, with fraud and willful misconduct outside the limit.
Is fraud capped in the Ohio document?
No. Clause 8.2 leaves fraud and willful misconduct outside the limitation.
Does the Ohio page cover open-source terms?
No. They are not covered for Ohio.
What does an Ohio user see in clause 2.5?
The general wording, since the Ohio statute read is silent on reverse engineering.
What is the difference between the Standard and Professional Software License Agreement?
The Standard edition is a complete, state-aware Software License Agreement for common situations. The Professional edition adds longer clause coverage, schedules, and optional modules for more complex matters. You can preview either edition free before you pay.

Software License Agreement templates for other states

DraftMyDocu provides self-help document templates only. We are not a law firm and do not provide legal advice.

Start your Ohio Software License Agreement