Skip to content
Outrich Data

The four meanings of data escrow, and which one applies to an AI data deal

Published 2026-11-17 · Updated 2026-11-17 · 7 min read · By the Outrich Data team

Data escrow has four established meanings: software source-code escrow, domain registry data escrow, backup escrow for hosted applications, and an academic design for running computations on data without releasing it. None of them describes a data licensing transaction. For an AI data deal, escrow means funds held until delivery passes agreed checks.

One phrase, four different things

Search for data escrow and the results describe four arrangements that share a name and little else. Each one is real and well established in its own field. A company that has been offered money for its data, and wants to know how escrow would protect it, will not find its situation in any of them.

What they share is the core idea of escrow: a neutral party holds something of value and releases it only when a stated condition is met. What differs is what is held, who the parties are, and what the condition is. This post goes through each meaning and then the one that applies to a data licensing transaction.

Meaning 1: software source-code escrow

This is the oldest use and the one most search results cover. A business licenses software it depends on but does not receive the source code. To protect the customer, the software vendor deposits the source code and build materials with an escrow agent under a three-party agreement.

The deposit is released to the customer only if a condition named in the agreement occurs. Typical conditions are that the vendor ceases to trade or stops maintaining the product. If nothing goes wrong, the customer never sees the deposit.

The purpose is continuity. Money is not what is being protected, and nothing is being sold through the escrow. The escrow is insurance against the vendor disappearing.

Meaning 2: domain registry data escrow

The second meaning comes from the domain name system. ICANN states that registry operators are required by their registry agreements to escrow certain registration data with an ICANN-approved data escrow agent. The format of those deposits is set out in RFC 8909, the Registry Data Escrow Specification, published by the IETF in November 2020.

The RFC states the purpose directly: the goal of data escrow is higher resiliency of registration services, for the benefit of Internet users. A deposit holds the minimum data a third party would need to resume operations if the registry cannot function. The specification defines full, differential and incremental deposits, and names three roles: the registry that submits deposits, the escrow agent that receives and guards them, and a third-party beneficiary that would receive them under extraordinary circumstances.

RFC 8909 covers the format and contents of deposits. It states that non-technical issues are outside its scope, so the question of when a deposit is released is left to the registry's agreements, not the technical specification. Again the purpose is continuity of a service, and no sale is involved.

Meaning 3: backup escrow for hosted applications

The third meaning is a newer variation on the first. When software is delivered as a hosted service, the source code alone would not help a customer if the provider failed, because the customer's own data lives in the provider's systems. In this arrangement, copies of the customer's data, and sometimes the running environment, are deposited with a third party on a schedule.

The release condition is again a failure of the provider. The customer is recovering access to its own data, not receiving something new. As with source-code escrow, the terms are set by each agreement, so what is deposited and how often varies from one arrangement to the next.

Meaning 4: data escrow in privacy research

The fourth meaning comes from computer science research and describes a system, not a contract. In a 2023 paper, researchers describe Data Station as a data escrow designed to enable the formation of data-sharing consortia. Data owners place data with the escrow, and users send their computations to it, so that queries run without the data first being released to the user.

A later paper from the same research group, Enabling Personal Dataflow Sovereignty via Bolt-on Data Escrow, applies the idea to individuals: platforms delegate computation to a trusted escrow instead of collecting the personal data themselves.

Here the escrow is software that controls what can be computed on data. There may be no release at all. It is a design for sharing the use of data while keeping the data in place, which is a different problem from closing a sale.

The four meanings side by side

The table sets the four established meanings against the one this site uses.

MeaningWhat is depositedWho the parties areWhat triggers release
Software source-code escrowSource code and build materialsSoftware vendor, customer, escrow agentA condition in the agreement, typically the vendor ceasing to trade or to maintain the product
Domain registry data escrowRegistration data, as full, differential or incremental depositsRegistry operator, approved escrow agent, a beneficiary such as a backup registry or regulatorExtraordinary circumstances in which the registry cannot function, as set by the registry's contracts
Backup escrow for hosted applicationsCopies of the customer's own data, sometimes the hosting environmentService provider, customer, escrow agentFailure of the provider, as defined in the agreement
Research data escrowData placed in a controlled computing systemData owners, data users, the escrow systemOften none: approved computations run and only results leave
Escrow for a data licensing transactionThe buyer's funds and, where the parties agree, the datasetBuyer, seller, escrow companyDelivery passes the acceptance checks written into the escrow instructions

What escrow means in a data licensing transaction

The first three meanings protect one party against the other party failing at some unknown future date. A data sale has a different problem, and it happens on a known date: someone has to go first. The seller worries about delivering and not being paid. The buyer worries about paying for data that does not match the sample, or that the seller had no right to license.

That is the problem property sales solved long ago, and the escrow we mean is the property kind. As our escrow page describes it, the buyer deposits the fee, both parties sign escrow instructions that state the release conditions and the cure period, the dataset is delivered and tested against the acceptance checks in the license, and funds release to the seller and data to the buyer together.

Two things travel with it. Before the escrow is funded, a data title search examines whether the seller has the right to license the data. After delivery, both sides receive a closing statement and the record. The longer explanation is in data escrow explained, and the short definition is in the glossary entry for data escrow.

How to tell which one someone is offering

If a provider or a counterparty uses the phrase, four questions sort out which meaning is on the table.

  • What is being held: code, a backup copy, live data in a computing environment, or money?
  • What event releases it: a failure at some point in the future, or a delivery that passes stated checks?
  • Is a sale or license taking place, or is the arrangement only a safeguard for an existing service?
  • Who signs the instructions, and do both sides receive the same written record at the end?

What escrow does not replace

In any of its meanings, escrow is a holding arrangement. It does not make an unlawful transfer lawful, and it does not replace the license agreement, where the representations and indemnities between buyer and seller stay. The guide to representations and warranties covers that side.

For a data sale, the checks that trigger release need to be specific enough to test. The acceptance criteria guide and the acceptance criteria template in templates show what that looks like, and the free delivery manifest builder and delivery verifier turn the delivery check into a comparison of SHA-256 hashes that either party can run.

Common questions

What is data escrow?
The phrase has several meanings. In software it is a deposit of source code or backups released if a vendor fails. In the domain system it is the registration data registries must deposit with an approved agent. In a data licensing transaction it is a neutral holding arrangement in which the buyer's funds, and sometimes the dataset, are released only when agreed conditions are met.
Is data escrow the same as source-code escrow?
No. Source-code escrow protects a software customer if the vendor stops supporting a product, and nothing is sold through it. Escrow in a data transaction protects both sides of a sale: the buyer's funds are held until the delivered data passes the agreed acceptance checks.
What is registry data escrow?
It is the requirement, stated by ICANN, that registry operators escrow certain registration data with an ICANN-approved data escrow agent. RFC 8909 specifies the format and contents of the deposits. Its stated goal is higher resiliency of registration services.
Which meaning applies when a company sells data to an AI lab?
The transaction meaning. The buyer's funds are deposited before the seller delivers, both parties sign escrow instructions with release conditions and a cure period, and funds and data release together once delivery passes the acceptance checks.
Can two companies use Outrich Data as escrow when it is not the buyer?
Yes. Any buyer and seller trading data can close through Outrich Data as the escrow company. On those deals Outrich Data is not a party to the sale.

Find out if your data qualifies.

Eleven questions, about five minutes, no call required. You get an answer on screen and a written follow-up.

esc