Data rights and access

THOR's open-source mission supports shared foundations alongside private customer data and licensed technology. Access to source material, rights over annotations and permission to reuse review records must be defined for each resource or project.

Public resources

A public dataset, model or hardware design should carry clear terms explaining what others may use, modify and redistribute. A THOR release should identify the licence and source conditions that define its reuse rights.

Private commercial work

The buyer and THOR must agree who may access approved material, what work is authorised and how delivered output may be used. Contributors receive access according to the permissions required for their assignment.

The project's access arrangements need to support those agreed permissions before private material is assigned.

Public accountability, private material

The pilot separates public delivery evidence from private source material and submissions. Governance and transparency sets out what THOR will report; customer source material and submissions stay restricted to authorised participants.

Authorised validators should be able to request samples for evaluation. Sample review and any republication follow the project's access and usage permissions.

Reuse of work and review records

Before retaining or reusing examples and evaluation records for future tools, confirm that the applicable licence or project agreement permits it. Customer confidentiality and usage terms govern what can be shared.

Handling arrangements

Before private work is assigned, the project needs documented arrangements for access, storage, retention, deletion and the handling of incidents or requests. Detailed technical controls and standard contractual terms are not specified here.

From brief to delivery places these requirements in the production workflow. Governance and transparency addresses responsibility for operating it.