The Chain of Custody Cannot Belong To a Platform

Hero Bg Shape Image

The content provenance ecosystem has a backing of companies that make cameras, editing software, and AI, so customers and investors ask what is left for anyone else to do. While these large enterprises are helping proliferate the technology that everyone will soon need, their focus is either AI compliance or baking authentication into their own products. The real answer, though, is that a chain of custody is only as valuable as the party authenticating it. Each platform can of course vouch for its own step. But the record that follows an asset across every vendor, partner, and handoff has to exist independently of all of them, and provide value, and often identity, outside of those systems to the end user. It never sits with the camera, or the editing software, or even the DAM.

That is not to say that these vendors aren't savvy to produce a provenance record. In fact, some of them are our customers. But we need to be clear that provenance does not belong to a vendor. That completely misses the point. And as AI adds more tools and more automated handoffs to every workflow, that record matters more, not less. Do you care if GPT made a photo? No. But you care that your authentication department saw the provenance chain, signed off on it, and inside the DAM, you know it's a safe, authenticated asset. This means that every decision you make regarding said asset, human or agentic, has a verifiable chain of custody and provenance that drives whatever happens next.

The question we hear most

When Google joined the C2PA steering committee in February 2024, it sat alongside Adobe, the BBC, Intel, Microsoft and Sony, among others (C2PA announcement). C2PA is the open standard behind Content Credentials, and its backers include the companies that build the tools most content passes through. Buyers and investors reasonably ask why an organization would need anything beyond the support those tools already offer, and why they would not build the capability themselves.

Platforms verify their own part of the chain

A camera can (and should) sign a capture. An editor can (and should) record an edit. A platform can show a label. But none of them own the process for the enterprise that ingests, checks, and orchestrates that content. A broadcaster's or advertiser's content moves through cameras, editing suites, asset managers, review tools, publishing systems and partners, often from vendors that compete with each other. Many departments, and even more workflows exist the bigger the enterprise. The record has to continue across every one of those handoffs, and no vendor in the middle is the right choice to hold it for the others.

Swimlane diagram of one asset moving through a customer, Limbo cloud and third parties: Limbo verifies evidence, records lineage and approval, a watermark is added, the manifest is signed, and the asset publishes with its manifest.
One asset moving between a customer, Limbo and third parties. Limbo checks and records at each handoff, and the signed record travels with the file. This image carries Content Credentials signed by Limbo: hover over the badge to see them.

A chain of custody needs an independent custodian

While media workflows didn't used to have much overlap with evidence chains, nowadays, the parallels are essential to keeping track of trust in content. In evidence handling, the person who keeps the chain of custody is not a party to the dispute. Digital content needs the same rule. Email authentication, login and electronic signatures followed a similar path: large platforms support the standard and check their own side, and organizations that need one trusted record across many systems turn to a neutral layer. These cases are not identical to content provenance, but they show a pattern. When parties who compete must trust the same record, it has to sit outside every one of them, while ensuring that the signal is durable and portable throughout the entire process.

The substrate therefore needs to exist independently of the vendors. It should keep its value when a customer changes cameras, editors or asset managers. It should rest on an open standard that anyone can verify. It should hold the record of an asset's origin and handling, while the asset itself stays with the customer.

AI raises the stakes

A signed record of origin and handling does not depend on an estimate. Every change, and especially every human review, make that record more valuable as AI use grows. Every AI tool added to a workflow adds a handoff, so the number of places where a chain can break rises with adoption. AI agents act on content at a speed no person can review. To decide whether an asset can and should be used, licensed, or published, an agent needs a machine-readable answer about where the asset came from and how it was made.

The rules are also arriving. EU AI Act Article 50 transparency obligations apply from August 2026 (our regulations paper explains the timing). The IAB's AI Transparency and Disclosure Framework (August 2026) sets voluntary best practice for advertising and names verification as future work. Google Ads (July 2026) now permits AI labels inside image and video ads, and Microsoft Advertising holds advertisers responsible for disclosures and for preserving watermarks, metadata and provenance information. Each of these asks organizations to declare what they know about their content. A chain of custody is the evidence behind the declaration.

Why organizations buy rather than build

Organizations that consider building their own chain of custody tend to underestimate five things.

  1. It is a program, not a feature. Key management, certificate lifecycle, trust lists, verification, audit and retention are continuing work, and the standard keeps developing. How do you maintain this, at scale, between 10 different departments and 5 different software vendors?
  2. A record the organization builds and holds itself is, in effect, self-issued evidence. Partners, insurers and regulators tend to give more weight to a record kept by a party with a specific stake in the outcome.
  3. The integrations take the most time. Submitting product requirements to asset managers, editing tools and broadcast workflows takes months, and each connection needs maintenance as those products change.
  4. Exchange needs shared rails. Two organizations passing an asset between them cannot rely on 6 disconnected private systems between their different vendors.
  5. Starting date matters. Assets created before a record begins cannot be fully documented afterward, so the gap stops growing only from the day the provenance record starts.

What the record does not prove

A chain of custody records origin and handling. It does not prove that the content is true, that a claim a person makes about it is accurate, or that a particular court would accept it as evidence. Courts and counsel decide legal status. Limbo records facts and gives guidance on the decisions a customer asks it to support, and the customer decides what to do with that guidance.

Where this goes next

Our view is that rules and platform policy will keep moving from asking for declarations toward asking for verification, and that organizations and their AI agents will rely on records they can check. Future briefs will cover customer experience, pilot results and technical detail.

To talk through how this applies to your workflow, get in touch at trylimbo.com/contact or hello@trylimbo.com.

Related reading

Sources

C2PA, "Google to join C2PA to help increase transparency around digital content" (February 2024). EU AI Act, Article 50. IAB, AI Transparency and Disclosure Framework (August 2026). Google Advertising Policies Help, "Updates to AI labeling requirements (July 2026)". Microsoft Advertising, "AI-generated and synthetic content in advertising".

Hero Bg Shape Image