Legal & Procurement Overview

License Summary & Usage Framework

This page summarizes the baseline licensing framework for Origin Data Lab’s custom real-world data programs, including feasibility pilots, buyer-defined collection scopes, and commercial data engagements.

Final rights, restrictions, responsibilities, and permitted uses are defined in the executed agreement for each project.

Request Licensing Review Review Data Structure →

Additional licensing, provenance, delivery, and procurement documentation may be shared during qualification or under NDA where appropriate.

At a glance

Licensing is aligned to the purpose, delivery scope, and intended use of each data program. The baseline framework supports technical evaluation and defined commercial workflows while allowing project-specific terms to be agreed where necessary.

Baseline framework

  • Non-exclusive rights unless otherwise agreed
  • Usage tied to the approved project scope
  • No unrestricted resale or redistribution

Supported programs

  • Feasibility pilot and model evaluation
  • Buyer-defined collection missions
  • Commercial and long-term data supply

Customizable by agreement

  • Expanded commercial usage rights
  • Project-specific licensing scope
  • NDA-based procurement documentation

Permitted use

The baseline license is designed to support approved technical and commercial workflows within the agreed project scope. Specific permissions depend on the delivery purpose, buyer requirements, and executed agreement.

  • Internal evaluation — model fit assessment, ingestion testing, workflow validation, and technical review
  • Research and development — internal R&D, scenario analysis, model improvement, and controlled experimentation
  • Benchmarking and testing — internal performance evaluation, failure analysis, and model comparison
  • Feasibility pilot use — use within the agreed validation purpose, data scope, geography, and delivery structure
  • Approved model development — training or development workflows where commercial usage rights are included in the executed agreement

Usage requiring additional agreement

Certain expanded rights are not part of the baseline framework and require specific negotiation, commercial alignment, and written approval.

  • Resale of delivered data — requires explicit written authorization
  • Redistribution to third parties — requires an agreed recipient scope and transfer terms
  • Sub-licensing — requires project-specific licensing provisions
  • Exclusive or region-specific rights — subject to separate commercial and operational review
  • Expanded production deployment — requires alignment on intended use, deployment scope, duration, and commercial terms

Redistribution & resale

Delivered data is licensed for use within the agreed buyer scope. Internal collaboration is generally supported, while onward transfer, resale, or public distribution requires explicit written agreement.

Internal use generally supported

  • Access by approved engineering, product, legal, and procurement teams
  • Internal sharing across authorized project stakeholders
  • Technical integration, model evaluation, and controlled development workflows
  • Internal review by approved contractors where permitted by the executed agreement

Additional agreement required

  • Resale or commercial distribution of raw delivered data
  • Transfer to affiliates, customers, partners, or external third parties
  • Public release, publication, or marketplace listing of delivered assets
  • Sub-licensing or creation of independently transferable dataset products

We support responsible commercial use under mutually agreed terms. The permitted recipient scope, transfer rights, and handling responsibilities should be defined in the final agreement.

Internal evaluation & commercial model development

Internal evaluation is the usual starting point. Commercial model development may also be supported where the intended use, deployment context, and usage rights are defined in the executed agreement.

  • Internal evaluation — model fit assessment, ingestion testing, scenario review, and technical validation
  • Internal model development — controlled training, fine-tuning, error analysis, and model improvement within the approved scope
  • Commercial model development — may be supported subject to the agreed license, intended deployment, and commercial terms
  • Production use — addressed through project-specific rights, operational scope, and procurement review

This public summary does not grant rights by itself. Commercial permissions should be confirmed against the executed agreement for the applicable data program.

Feasibility pilot scope

Feasibility pilot deliveries are designed to help buyers validate data fit against a specific model gap, operational design domain, or collection requirement before moving into a broader custom production program.

  • Buyer-defined objective — aligned to a specific validation question, model limitation, or target scenario
  • Scope-limited delivery — defined by the agreed geography, scene conditions, capture requirements, and review purpose
  • Representative package — may include curated video, metadata, schema documentation, sample annotations, and QC materials
  • No automatic expansion — broader usage rights, continuity, or production-scale supply require further agreement
  • Path to custom production — validated requirements may progress into a dedicated collection mission or long-term supply program

Documentation available during review

Legal, procurement, security, and engineering teams may require additional information before approving a pilot or custom data program. Relevant materials can be shared during qualification, contract review, or under NDA where appropriate.

Licensing & commercial terms

  • Detailed license or data supply agreement
  • Permitted use and recipient scope
  • Commercial rights, duration, and renewal terms
  • Project-specific restrictions or exceptions

Delivery & data handling

  • Delivery package and file structure overview
  • Data handling and access responsibilities
  • Retention, transfer, and storage expectations
  • Quality assurance and acceptance materials

Provenance & diligence

  • Collection scope and provenance information
  • Consent, privacy, and operational controls overview
  • Compliance and procurement responses
  • NDA-based supporting documentation where applicable

The exact documentation set depends on the project stage, buyer requirements, collection scope, and mutual confidentiality protections.

Common review questions

Does this page replace the final contract?

No. This page is a public summary only. Final rights, restrictions, responsibilities, and commercial terms are defined in the executed agreement and any related procurement documents.

Can legal or procurement teams review terms before purchase?

Yes. Public summary information is available here, and more detailed licensing, delivery, provenance, or data handling materials may be shared during qualification or under NDA where appropriate.

Is commercial use always included?

Not automatically in unlimited form. Commercial usage rights depend on the agreed project scope, intended deployment, recipient structure, and terms of the executed agreement.

Can licensing terms be defined for a custom collection program?

Yes. Licensing can be aligned to the collection mission, geography, intended use, delivery structure, commercial scope, and any project-specific procurement requirements.

Ready to review your data program?

Tell us your intended use, collection requirements, deployment context, and procurement constraints. We can help define an appropriate licensing, delivery, and commercial framework for a feasibility pilot or custom production program.

Request Licensing Review Review Data Structure