| Scope | Email stores, shared drives, document systems, code repositories, and other internal operational records the estate can lawfully convey |
|---|---|
| What the estate grants | A copy license under a defined scope |
| What the estate keeps | Every record the case requires. We take possession of no system you must retain |
| Out of scope | Pure consumer products, scraped public web sets, and materials the estate cannot assign |
| Process | Intake. Free estimate. Diligence with counsel. License. Technical handoff. Payment |
| Intake to estimate | A few business days |
| Confidentiality | NDA before detailed diligence. No estate named without approval |
| Payee | The estate, the trustee, or the payee your order names |
| Payment schedule | As written in the license |
| Fits | Sale, 363, and assignment processes counsel already runs |
Can the estate license IP-heavy materials?
Yes when the estate holds the rights or can obtain them. We diligence chain of title with counsel before close. Open-source components are carved out or handled under their licenses.
What about employee personal data?
Employment records and HR files need a lawful basis and often redaction or exclusion. We scope the license to business records the estate can convey. Counsel sets the boundary.
What about customer data?
Customer content and regulated personal data are included only if the estate has rights to license and the agreement allows it. Many deals exclude or narrowly limit customer PII.
How is open source treated?
Open-source code stays under its licenses. We do not re-license third-party OSS as estate-owned proprietary code. Disclosure of OSS use is part of diligence.
Do you use escrow?
Payment and data handoff can run through escrow when counsel wants it. Terms follow the license and any court order.
Summary only. The signed license governs.