Every record, three links back.

A delivered record traces to the supplier agreement it came in under and the buyer licence it went out under, written into a per-record manifest.

rest
manifest entrysample · illustrative values
dataset_id
QD-7K2Pthe listing
rights_basis
owner_held_rightswhy it could be licensed
sha256
9f2c…e41athe file delivered

Read the manifest schema

Checked before anything is listed

Where rights are unclear, a listing goes back to review rather than ahead. An owner who isn't sure what they hold can still start a conversation; we work it out together first.

  1. 01OwnershipWho owns the recordings, studies or reports, and who else has a claim to them.
  2. 02Notices and consentWhat customers or patients were told, and whether it covers licensing to third parties.
  3. 03Client contractsContracts between the owner and its own clients that may restrict use, common for BPOs.
  4. 04ApprovalsHospital and ethics approvals for imaging and clinical data.
  5. 05Rights clear?yes · listedno · back to review
An unclear answer is not a no: the owner fixes notices or contracts, and the listing comes back through review.

What a licence allows

  • TrainingAllowed. When the licence says so
  • EvaluationAllowed. Including held-out test sets
  • Internal researchAllowed. Inside the licensee's organisation
  • RedistributionNot allowed. Never: no resale, sharing or publishing
  • Re-identification or linkageNot allowed. Never, in every licence

Takedown and deletion

An owner, or a person who believes their data is in a dataset, can ask for it to be withdrawn. Quarry delists it and tells every buyer, who are bound by their licence to delete it.

How to make a request
requestowner or personQuarry delistslisting pulledbuyer 01buyer 02buyer 03
01 A request names the data02 Quarry delists it and finds every licence that holds it03 Each buyer is notified and bound to delete04 Deletion confirmed, logged against the manifest
Last updated 15 October 2026Questions? trust@quarrydata.ai