Software & SaaS

The AI-era IP audit: 12 ways your software is legally exposed.

Generative AI has cut the cost of reverse-engineering a software product to almost nothing. If you rely on a copyright notice and generic website terms, your interface and frontend have little practical protection. Use these twelve checks to find the gaps before a competitor does.

By K2K Law · Kroub Kolmykov PLLCUpdated

1. The contract: terms of service

Terms of service checks

A breach of terms gives you a contract claim against a user who accepted them. Whether it also amounts to “unauthorized” access under the Computer Fraud and Abuse Act is a separate question. After Van Buren v. United States (U.S. 2021) and hiQ Labs v. LinkedIn (9th Cir. 2022), a terms violation alone generally is not enough, particularly for pages anyone can view without logging in. Design the product so that the contract claim does not depend on the statute.

2. The interface: design patents and trade dress

Design protection checks

A design patent protects ornamental appearance (35 U.S.C. § 171), lasts 15 years from grant (§ 173), and has no maintenance fees. The grace period is in 35 U.S.C. § 102(b)(1). Trade dress is protected under 15 U.S.C. § 1125(a).

3. The evidence: technical defenses and logging

Technical and evidence checks

Have counsel review canary and logging designs before deployment. Evidence is only useful if it was collected lawfully, consistently with your own privacy policy, and preserved in a form a court will accept.

4. Enforcement readiness: registrations

Registration checks

Statutory damages and attorney’s fees generally require registration before the infringement began or within three months of first publication (17 U.S.C. § 412). The registration requirement is in 17 U.S.C. § 411; the Copyright Office explains deposits for software in its circular on computer programs.

5. Advanced: trade secrets and discovery readiness.

AI tools and trade secrets

Trade secret law protects information only if its owner takes reasonable measures to keep it secret (18 U.S.C. § 1839(3)). In Trinidad v. OpenAI Inc., No. 25-cv-06328-JST (N.D. Cal. Jan. 5, 2026), a federal court dismissed a trade secret claim against OpenAI because the self-represented plaintiff said she had developed her frameworks in ChatGPT, which meant she had voluntarily shared them with OpenAI.

That is a single district court decision on unusual facts. The practical point is broader: if engineers paste proprietary logic into an AI tool whose terms include no confidentiality or no-training commitment, you may have weakened your own trade secret position. Check which tools are in use, on which plans, under which terms.

Privilege and large-scale log production

Suing a cloner often means producing large volumes of logs and telemetry in discovery. A court order under Federal Rule of Evidence 502(d) provides that producing privileged material in the case does not waive the privilege, in that case or in other federal or state proceedings. Ask litigation counsel to seek one before large productions begin.

Tick the boxes as you review, or print this guide. Selections are not submitted. A checked box means the item has been addressed in your process, not that a legal conclusion has been established.

Reading your result.

What unchecked items usually mean
Unchecked areaTypical exposureUsual first step
Contract (1–4)No practical claim against a user who scrapes or clones through an account.Redraft the terms for clickwrap acceptance with explicit scraping and AI-training restrictions.
Interface (5–7)A visual clone built with new code may be hard to challenge.Identify signature screens and check filing deadlines against your launch date.
Evidence (8–10)Copying may be difficult to prove even where rights exist.Add canary elements and extend log retention, with counsel’s review.
Registrations (11–12)Weaker remedies and slower enforcement.File trademark applications and register core code and graphics.

No checklist can tell you whether a particular product is protected or whether a particular competitor is liable. It can show you where to look first.

Close the gaps you found.

Share a brief, nonconfidential overview of your product and stage. Please leave source code and confidential documents out of the web form.

Discuss your platform