Data governance
Clear scope. Traceable permissions.
How sources, participant choices and buyer uses fit into the proposed collection process.
The source is part of the record.
A collection brief needs to specify both the information required and how it will be obtained. User-uploaded exports, connected devices and commissioned measurements are distinct acquisition routes.
Participant exports
Files a participant exports and chooses to upload. Assess their contents, source terms and intended uses; preserve the original source and import history.
Direct integrations
Access through a platform or device API. Its permissions and contractual restrictions remain part of the source assessment.
Commissioned capture
Measurements, recordings and check-ins collected to a defined protocol, with capture instructions and source metadata.
Define the use before the release.
The proposed workflow links a release to a specific protocol, permission version and buyer use schedule. Consent to use a consumer app is not consent to join a study or license its data.
- Specify participants, data categories, collection windows and approved acquisition routes.
- Set out recipients, training or evaluation purposes, access method and onward-use restrictions.
- Assess source agreements and applicable legal or research requirements alongside participant permissions.
- Keep original observations, derived fields and reviewer decisions distinguishable.
Access should fit the task.
An export and a controlled workspace expose data differently. The access method, retention and recipient restrictions would be agreed for each pilot before release.
Versioned delivery
A defined release with its source manifest, data dictionary, quality report and permitted-use schedule.
Restricted access
Where required, scope a controlled environment and recipient permissions. This is a proposed option, not an operating workspace.
Downstream use
Resolve training, evaluation, model artifacts, publication, derived datasets and redistribution explicitly in the buyer agreement.
Participation is a separate decision.
A future programme needs a clear invitation, study-specific permissions, compensation terms and a practical way to ask questions or withdraw. No participant programme is accepting data through this site.
Existing consumer-app records are not automatically part of a research collection. Any new programme needs its own reviewed permissions and an assessment of existing commitments.
Participant informationExplain what happens at each stage.
The proposed process distinguishes stopping future collection, removing controlled copies, notifying recipients and handling already released data. Retention duties and the treatment of trained artifacts need an explicit, lawful agreement.
Do not assume either that a perpetual licence removes all participant rights or that every trained model can be made to forget a record. The actual process must be settled before recruitment.
A scoped launch, not a blanket promise.
No launch geography or clinical panel is confirmed. Eligibility, source access, staffing, cross-border access and any necessary ethics review are assessed for the particular protocol.
Discuss a cohort