Data rights & provenance
Provenance your
legal team can verify.
Datoric's collection model establishes consent, licensing scope, and origin at the source, giving buyers a rights record to review before delivery.
The principle
Rights are collected with the data, not added afterward.
The open web was not built for training. Rights are unclear, consent is missing, and model teams inherit legal and reputational risk they never chose. Datoric takes the opposite approach: we work directly with contributors under clear agreements, so consent and licensing exist before a single sample is captured.
Establishing provenance at the source creates a reviewable record. Buyers can inspect the origin, consent documentation, and license scope defined for the dataset or collection program before delivery.
What provenance means here
Four controls built into collection programs.
№ 01
Explicit consent
Contributor agreements define how collected material may be used before recording begins, with the applicable consent record included in dataset review.
№ 02
Clear licensing
The license states the permitted AI-development use and engagement scope before production delivery.
№ 03
Traceable origin
Managed collection programs record the source and collection path instead of relying on unknown third-party aggregation.
№ 04
Documented redaction
Where personal or sensitive material is in scope, redaction requirements are defined in the dataset specification and QA record.
Questions
Rights & provenance
- Where does the data come from?
- We source at the origin, directly from consented contributors who record to a specification, rather than scraping the open web. That is what lets provenance travel with each sample.
- What rights come with the data?
- Rights are established with the contributor at the point of collection and scoped per engagement. Licensing terms are documented and confirmed in writing before delivery. See our licensing overview for how scope is set.
- Can we review the provenance record?
- Yes. The computer-use offer includes chain-of-custody and consent documentation in licensing review. Custom programs define the corresponding record with the collection specification.
Continue
More of the record
How it works
From spec to delivery: the end-to-end collection and review workflow.
Quality methodology
Modality-specific checks for datasets and benchmarks.
Security & privacy
Request-based access, privacy handling, and program safeguards.
Licensing
Commercial license scope and the terms buyers review.
Custom data collection
Build-to-spec programs for data that does not exist yet.
About Datoric
Company identity, research group, and contacts.