For data owners

Sell call center recordings for AI

Task-oriented, multi-speaker phone audio is valuable for voice agents and ASR — subject to strict consent and PII handling.

How licensing works

fiund handles consent and de-identification requirements before any licensing; ownership stays with you.

The full pipeline — briefs, rights clearing, delivery — is on the how it works page. Below is what it looks like from the owner's side.

What buyers look for

Licensing your archive shouldn't require guessing what a buyer wants. The diligence questions are consistent, and every item you can already answer strengthens your position:

  • Hours and call counts — task-oriented speech at volume, with real interruptions and real accents.
  • Consent records — your recording notices and the consent basis behind each batch of calls.
  • PII status — what identifying detail the calls contain, and whether it’s already redacted.
  • Channel separation — agent and caller on separate channels is markedly more useful for ASR and diarization.
  • Call metadata — intents, outcomes, queue types, languages, and dates.

How to prepare your archive

None of this has to be finished before you get in touch. But each step below shortens the rights check and sharpens the quote:

  • Inventory the corpus: hours, call counts, date ranges, languages, and the recording setup.
  • Confirm your consent basis — what your recording notices said, and what your policies permit.
  • Catalogue the PII present — names, account numbers, payment details — and its redaction status.
  • Export original audio, dual-channel where it exists, not compressed archival copies.
  • Separate out what you can’t offer: calls under legal hold, regulated categories, client-owned material.

Deal shapes

There is no standard rate card. Rates are set per deal, and fiund negotiates the Buyer Licence under the standing contributor agreement. Common shapes include:

  • Standard buyer licence. fiund can grant defined training rights to multiple buyers; your operations and retention policies are untouched.
  • Redacted subset first. A de-identified, consented slice keeps the risk conversation short and proves the value before the deal widens.
  • Buyer-exclusive, defined scope. Possible for distinctive corpora only through a separate contributor addendum, priced and time-boxed.
  • What fiund negotiates. Scope of use, redaction standard, term, delivery, and audit rights. Rates are set per deal.

The stages of a deal

Every licence moves through the same stages without requiring another contributor approval for the ordinary transaction. How quickly depends on the state of your paperwork:

  1. Review. You describe the corpus — hours, languages, consent basis, PII posture — and get an honest read on whether it’s licensable.
  2. Rights check. Consent basis and PII handling are reviewed against the intended licence; client agreements are checked where you record on someone else’s behalf.
  3. Buyer match. The corpus goes in front of vetted buyers whose use fits the contributor agreement, consent basis, and redaction requirements.
  4. Licence. fiund negotiates and closes the Buyer Licence under the standing contributor agreement.
  5. Delivery. Audio is delivered redacted to the agreed standard, with documentation attached: licence, consent records, provenance.
  6. Payout. You’re paid per the licence terms. The corpus stays yours.

What you keep

  • Ownership — you license, you don't sell.
  • Simplicity — fiund handles ordinary AI-licensing deals without asking you for another signature each time.
  • Control — you can withdraw content from future licensing, and buyer-specific exclusivity still requires a separate addendum. See how payouts work.

Frequently asked questions

How much does call-centre recordings data pay?

Value is set per licence and depends on volume, quality, consent, and demand — with scope and buyer exclusivity priced into each deal. fiund quotes against your actual material rather than a headline rate and records each completed transaction transparently.

Our calls are full of customer PII. Is licensing even possible?

Only with the PII question answered first — which is why it leads the rights check. Identifying detail is catalogued, then redacted or excluded, and material that fails the consent review isn’t licensed at all. No corpus goes to a buyer with that work undone.

We used standard “this call may be recorded” notices. Is that enough?

A recording notice and consent to training use are different questions, and the answer depends on your notices, your policies, and your jurisdiction. Reviewing that is exactly what the rights check is for — before any buyer sees the corpus, not after.

We’re a BPO — the calls involve our clients’ customers. Who can license them?

Your client agreements decide what you can grant, which makes them the first document in the chain-of-title review. Some material can be licensed jointly with clients; some gets carved out entirely. The review tells you which is which.

Can we start with a small, safe subset?

Yes — a redacted, consented slice is a sensible first deal. It keeps the review fast, keeps risk low, and lets everyone see the value before the corpus widens.

Other things you can license

License your library.

Whether you're building a model or sitting on an archive, the first conversation is short and specific.

License your library