Data escrow is an arrangement in which a neutral party holds the buyer's funds, and sometimes the dataset, while a data sale completes. Signed escrow instructions state the conditions for release. When the delivery passes the agreed acceptance checks, money goes to the seller and data to the buyer at the same closing.
The problem escrow solves
Every data sale has a sequencing problem. If the seller delivers first, the buyer holds a copy of the data and the seller holds a promise. If the buyer pays first, the seller holds the money and the buyer holds a promise. Data makes this worse than most goods, because a delivered copy cannot be handed back. Once a buyer has the files, returning them proves nothing.
Escrow removes the need for either side to go first. A neutral holder takes the buyer's funds before the seller delivers. The seller can see the money is committed. The buyer knows it will not move until the delivery matches what was agreed. The idea is borrowed from property sales, where a closing agent holds the purchase price until the deed is ready to transfer.
Escrow does not decide whether the deal is a good one. It does not set the price or write the license. It only controls the order in which money and data change hands, and it leaves a record of what happened.
The parties and their roles
A data escrow has three roles. The seller, usually called the licensor, owns the data and grants the license. The buyer, or licensee, pays the fee. The escrow holder is neutral: it follows the written instructions and takes no side on commercial terms.
Outrich Data works in two positions. When Outrich Data is the direct buyer, its purchase funds go into escrow before the seller delivers, and a seller who prefers an independent holder for that purchase can ask for one. When two other parties bring their own deal, Outrich Data can act as the escrow company and is not a party to the sale.
| Party | Role | What it provides |
|---|---|---|
| Seller (licensor) | Grants the license and delivers the dataset | Signed license, the dataset, a data card and a checksum manifest |
| Buyer (licensee) | Pays the fee and accepts or rejects delivery | Signed license, the escrow deposit and the acceptance decision |
| Escrow holder | Holds funds, and data where agreed, and releases on instruction | Confirmation of deposit, a record of each step and a closing statement |
| Counsel for each side | Reviews the license and the escrow instructions | Advice to its own client only |
What is held: funds, and sometimes the data
The funds are always held. The buyer deposits the license fee, or the first installment of it, when the agreement is signed. The escrow holder confirms the deposit to the seller. From that point the buyer cannot withdraw the money on its own, and the seller cannot collect it on its own.
The dataset is held only where the parties agree to it. In a two-sided hold, the seller delivers the files to the escrow holder instead of to the buyer. The holder, or a reviewer both sides accept, runs the acceptance checks against that copy. The buyer receives the data only at closing. This protects a seller who does not want the buyer to see the full dataset before the money is certain.
In a funds-only hold, the seller delivers straight to the buyer and the buyer runs the checks. This is simpler, but the buyer has the data during the review. The license should then say what the buyer must do with the files if the deal does not close, such as deleting them and confirming the deletion in writing.
Escrow instructions
Escrow instructions are the short document that tells the holder what to do. Both parties sign them. The holder acts on the instructions and nothing else, which is why they need to be specific. An instruction that says funds release on satisfactory delivery invites an argument. An instruction that says funds release when a named person confirms in writing that a listed set of checks has passed does not.
Instructions sit beside the license, not inside it. The license sets the commercial deal. The instructions set the mechanics of holding and release. Where the two conflict, the documents should say which one controls.
- The parties, the dataset and the license the escrow relates to
- The amount deposited, when it is due and how the deposit is confirmed
- Whether the dataset is also held, and who may access it during review
- The release conditions, stated as checks someone can run
- Who decides whether each check has passed, and how that decision is given
- The cure period and what happens when it ends without a conforming delivery
- How funds are returned if the deal does not close
- How a dispute freezes the escrow and who can end the freeze
Release conditions
A release condition is a fact that must be true before the holder moves anything. In a data sale the main condition is acceptance: the delivered dataset has passed the acceptance checks written into the license. Typical checks cover record volume, schema, time span, de-identification and file integrity.
Good conditions share three traits. They are objective, so two people running the same check get the same result. They are finite, so the review ends on a known date. They name a decision maker, so the holder is never asked to judge the data itself.
Many agreements add deemed acceptance. If the buyer neither accepts nor rejects within the review period, the delivery is treated as accepted and funds release. This stops a buyer from holding the data and staying silent. Some deals also split the release, with part of the fee paid at acceptance and the rest when a later refresh is delivered.
Cure periods
A cure period is the time a seller has to fix a delivery that failed a check. Without one, a single missing file could end the deal. With one, the seller receives a written notice that names the failed check, corrects the problem and delivers again.
The instructions should say how long the cure period lasts, how many attempts the seller gets and whether the review period restarts after a new delivery. They should also say what counts as a failure worth rejecting. A small shortfall in record count is different from personal data left in the files, and many agreements treat the two differently.
If the cure period ends and the delivery still does not conform, the instructions govern the return of funds to the buyer. If the buyer already holds a copy of the data, its deletion duties start at that point.
Disputes
Sometimes the parties disagree about whether a check passed. The escrow holder does not resolve that question. Its duty is to hold. When it receives conflicting instructions, it freezes the escrow and waits for a joint written instruction or a decision from the forum named in the license, such as a court or an arbitrator.
The practical way to avoid disputes is to settle the method of each check before signing. Agree on the tool, the sample size and the pass mark. Then a failed check is a matter of record, not opinion. Some parties also name a technical expert in advance to decide narrow questions about the data, with any legal questions left to the main dispute process.
How it differs from source-code escrow and holdbacks
The phrase data escrow is sometimes confused with two other arrangements. Software source-code escrow protects a customer that depends on a vendor's software. The vendor deposits its source code with an agent, and the code is released to the customer only if a trigger occurs, such as the vendor going out of business. It is a continuity tool that may never be used.
A payment holdback is a part of the price that the buyer keeps for a period after closing to cover later claims. The buyer controls it, not a neutral party. Escrow in a data sale is different from both. It is used on every deal, it runs for the short period around delivery, and neither side controls the release.
| Feature | Data escrow in a sale | Source-code escrow | Payment holdback |
|---|---|---|---|
| Purpose | Exchange money and data safely | Keep software usable if the vendor fails | Secure later claims against the seller |
| What is held | Funds, and sometimes the dataset | Source code and build materials | Part of the purchase price |
| Who holds it | A neutral escrow holder | A neutral escrow agent | The buyer, or sometimes an agent |
| Release trigger | Delivery passes the acceptance checks | A defined vendor failure | A claims period ends without a claim |
| How long it lasts | The period around delivery | The life of the software contract | A set period after closing |