Prospective supplier review

Make your human dataset easier for serious AI buyers to evaluate and license.

NaraDatum reviews organisations that hold or can lawfully license human data. This form is how you ask to be considered for that review.

It asks who you are, what you hold and in which languages. Provenance, rights, consent, metadata, quality control and intended-use fit are reviewed on each dataset separately. No dataset is treated as supply-ready until the review is complete and the required licensing authority, availability and transaction terms can be established.

What the process does for a dataset that holds up

Buyer review can stop when rights cannot be traced, consent cannot be evidenced, or intended-use fit cannot be tested. This process records the evidence and gaps before a commercial discussion. It is not a promise of demand or a purchase.

Qualified requirements, not enquiries

Buyers submit a structured requirement: use case, languages, speaker structure, volume and timeline. Your data is matched against a stated brief rather than a browse.

A structured Dataset Passport

What was reviewed, what was established and what was not, in one document a buyer’s legal and technical reviewers can read without a call. See an illustrative Dataset Passport.

Controlled sample access

Evaluation material is shared under agreed conditions with a named recipient, rather than posted to a catalogue where anyone can take a copy.

Rights and provenance evidence, recorded clearly

Chain of title, permitted use and consent scope are reviewed in a private process and the evidence position is recorded for the relevant dataset. Review does not create, transfer or expand licensing rights, and a buyer may still conduct its own diligence.

Buyer-facing evaluation

Fit is assessed against the buyer’s actual use case (ASR, voice agents, TTS, benchmarking), so a set is judged on the job it is for, not on a single quality score.

Commercial protection and managed transaction

Terms, permitted use and delivery controls are handled as part of the transaction. Your rights position is not weakened to close a deal, and a buyer licence never exceeds what you actually hold.

What this application is, and what it is not

  • Applying is not verification.

    Submitting this form records an application. It does not verify your organisation, your claims, or your data.

  • Supplier approval does not verify every dataset.

    An approved supplier is an organisation we are willing to review datasets from. Each dataset is still reviewed on its own before it can be used.

  • Declared inventory is not verified inventory.

    Everything you write below is a declaration by you. Until we have reviewed evidence, it stays a declaration and is treated as one internally.

  • NaraDatum reviews provenance, rights, consent, metadata, quality control and intended-use fit before any dataset is considered.

    A material gap in any dimension can prevent a dataset from being considered. The review records what evidence supports each conclusion and what remains unresolved.

  • This application creates no obligation on either side.

    It is not a listing, not an approval, not an offer, and not a commitment to buy, license or engage commercially.

Who should apply

A good fit

  • You own human speech, conversational or multimodal data, or you hold documented authority to license it.
  • You can explain where the data came from and how the people in it agreed to its use.
  • You can produce contracts, consent records or release evidence later, under a controlled private process.
  • You run, or are willing to run, a defined quality process over what you deliver.

Supplier-owned data remains supplier-owned unless a written agreement says otherwise.

Not a fit

  • Data scraped or harvested without a lawful basis for the use you are proposing.
  • Data where the chain of rights cannot be traced back to a source you can name.
  • Synthetic or model-generated material presented as human data.
  • Individual contributors offering their own voice. That is a different route. See applying to contribute.

What NaraDatum reviews

Provenance

Where the data actually came from, through every hand it passed, and whether that chain can be evidenced rather than asserted.

Rights

Who holds them, what they permit, and whether they extend to commercial AI training and to the licence a buyer would need.

Consent

What the people recorded were told, what they agreed to, and whether that agreement covers the intended use.

Metadata

What is labelled, how consistently, and whether the labels mean the same thing across the dataset.

Quality control

How defects are found and corrected before delivery, and what happens to material that fails.

Intended-use fit

Whether what you hold fits the use a buyer has stated, and whether the evidence supports that use.

What happens next

Applications move through the stages below. Not every application reaches every stage, and progressing through one stage does not imply the next.

  1. 01Application receivedYour declarations are recorded. Nothing is verified at this point.
  2. 02Initial fit reviewWe read what you sent against current and expected buyer requirements. This is an internal fit assessment, not proof of demand.
  3. 03Information requestIf there is potential fit, we ask specific follow-up questions in writing.
  4. 04Controlled evidence reviewContracts, consent records, identity documents and sample material are exchanged through a private, agreed process, never through this website.
  5. 05Dataset-specific reviewEach dataset is assessed on its own provenance, rights, consent, metadata, quality control and intended-use fit.
  6. 06Commercial discussion where there is real fitTerms may be discussed where a reviewed dataset could fit a specific buyer requirement. Buyer interest is not a purchase commitment or proof of wider demand.
  7. 07Approval, conditional approval, or declineConditional approval means named conditions must be met before anything proceeds.

Do not send evidence through this form

This form accepts typed answers only. There is no file upload on this page, and there is no way to attach anything to it.

Contracts, consent records, identity documents, audio, transcripts and datasets are handled later, in a controlled private process that we agree with you first. Please do not paste them here, and please do not include links to them.

Describe what exists in words. That is enough for this stage.

The application

Nine short steps. Seven questions about your organisation and your data are required, as are the four acknowledgements near the end. Everything else is optional at this stage.

1. Organisation

The legal entity that would hold any agreement, and the person we would correspond with.

2. Supplier type

Choose the description closest to your relationship with the data. This shapes which rights questions matter most.

3. Data and language coverage

Describe what you hold or can produce. Everything here is a declaration, not verified inventory. Describe availability in words. Do not link to or paste any actual data.

Describe the kind of speech or conversation you hold, in your own words. This is the answer that decides whether a review is worth opening.

The examples are illustrative, not exhaustive. Describe any languages, regional variants or multilingual combinations you hold.

4. Existing supply

Optional at this stage

Useful if you have it to hand. Leaving any of these blank does not hold up a review.

Speaker structure you hold today (optional)

Existing inventory only. What you could collect is the next question. They are recorded separately and are never treated as the same thing.

5. Collection capability

Speaker structure you could collect to specification (optional)

Capability, not inventory. Tick these only where you could run the collection, whether or not you hold any of it today.

6. Accompanying material

What travels with the audio you hold (optional)

Tick only what the existing material actually carries. Anything ticked here is a declaration and is reviewed against the material later.

7. Rights and provenance

Answer honestly. “Not sure” and “Depends on dataset” are real answers and are far more useful to us than an optimistic “Yes”. Nothing here is verified at this stage. Detailed rights and consent review happens later, on each dataset separately. No dataset is treated as supply-ready until the review is complete and the required licensing authority, availability and transaction terms can be established.

Does documented rights or chain-of-title evidence exist for this data? (optional)

Answer if you can. If you would rather establish this once we are talking, leave it blank.

8. Acknowledgements

All four are required.

Supplier-owned data remains supplier-owned unless a written agreement says otherwise.

9. Review and submit

Check that your typed declarations are accurate. Submission starts an application review. It is not verification, approval, a listing or a commercial commitment.

Typed answers only. There is no upload on this page and nothing can be attached to it.