Key takeaway
A possible retained license right does not by itself keep an API, future feed or support team operating.
Do not treat bankruptcy as ordinary license expiry
A recipient depends on more than the wording of a grant: it may need files, credentials, new deliveries or a running service. If the licensor enters bankruptcy, identify the governing proceedings and get specific advice before assuming the contract has vanished, stopping payments or continuing every use. Ordinary termination instructions do not decide bankruptcy rights.
The accessible official US Code text for this review was the 2024 annual edition, read on 11 October 2026; current House code pages were under maintenance. Section 365(n) provides a conditional mechanism for certain intellectual-property licensees following rejection. Section 101(35A) supplies a specific IP definition. This edition-limited agenda holds elections, payment decisions and legal conclusions for current counsel and applicable case orders.
Complete a right-and-dependency map
This hypothetical recipient uses a fixed historical package and a monthly feed under one agreement. The source includes a compilation asserted to contain protected authorship, ordinary factual measurements and a third-party manual. No legal classification is established. The recipient has the fixed package locally, while the feed depends on the licensor’s hosted API and staff.
The map distinguishes a claimed right from the practical ability to exercise it. A document saying perpetual use cannot prove that every component is protected IP, that the licensor granted the third-party rights, or that future operations will run. Give counsel the exact agreement/version and the material actually delivered.
| Hypothetical item | Right/copy evidence | Continuity question |
|---|---|---|
| Fixed compilation | Defined grant; local version held | Does qualifying IP/right fall within applicable protection? |
| Factual sensor measurements | Facts included with compilation | Do not assume every raw fact qualifies as statutory IP |
| Monthly new feed | Future deliveries promised | Which performance obligations and remedies remain? |
| Hosted API | Credentials exist; no full local replica | Can licensed use operate if service stops? |
| Third-party manual | Embedded attachment; authority uncertain | Separate source-rights hold remains |
Distinguish the Court’s principle from the statutory mechanism
In Mission Product Holdings v. Tempnology, the Supreme Court analyzed rejection as breach rather than rescission. The opinion concerned a trademark license. It does not mean every dataset, service promise or requested remedy receives identical treatment. Counsel must identify the contract rights, applicable law and bankruptcy posture in the real matter.
The 2024 statutory text’s IP mechanism also has specific conditions: retained rights, contract duration/extensions as of right, royalties and limitations on other remedies. The recipient should not selectively use the retention idea while ignoring payment obligations or the scope of the election. Record the questions for advice instead of writing a universal rule that bankruptcy leaves all data licenses unchanged.
Confirm which embodiments and operations exist
Section 365(n)’s text includes provisions concerning written requests for IP embodiments held by the trustee, to the extent provided by the contract. That is a reason to inspect the agreement and delivery evidence, not a promise that a complete future dataset, running server or new engineering team will be supplied. Describe the existing artifacts and the service dependency separately.
For the invented recipient, the locally held package can be identified by version and delivered-file evidence. The hosted feed has no equivalent local copy. A technical owner should document what a lawful, authorized fallback would need without taking new copies or bypassing access restrictions. Preserve relevant records under counsel’s directions, including excluded material and any restrictions that continue to matter.
Keep third-party restrictions visible during continuity work
The embedded manual remains a source-authority question even if some rights in the compilation survive. A continuity plan cannot enlarge the licensor’s original authority or silently change the recipient’s permitted purpose. Map the product features and outputs that rely on each component, then identify which remain held pending advice.
In the hypothetical case, the recipient documents its local historical package and the feature dependency on the monthly API. It holds a new public-output feature and the manual’s reuse question. The next action is an informed legal and operational review of the particular case, not automatic deletion, unrestricted continuation or an unreviewed demand to the trustee. This worksheet makes no election or filing.
Return a continuity brief with explicit holds
The completed artifact contains proceedings/jurisdiction, contract version, claimed rights, material classification questions, copies held, royalty/payment questions, service dependencies and the decision owner. It supports separate advice on retained rights and a realistic plan for operations if services are interrupted. Neither topic is resolved by a generic survives-bankruptcy clause.
Due diligence can organize evidence requests; Offer comparison can retain ongoing service and payment terms. The ordinary termination and assignment guides cover different events. VOID’s introduction does not provide bankruptcy representation or legal clearance, and any actual licensing decision remains with the parties and their advisers. No recovery value, buyer demand or continuity outcome is promised.
Use this review agenda with your legal and privacy advisers. Requirements depend on the records, jurisdictions and intended use.