Trust fabric · Data governance

Your data. Your terms. Provably.

A Personal Health Cloud is not an unrestricted data lake. Consent is granular, purpose-bound, revocable — and enforced in the access path rather than described in a policy.

Meaningful control

Four questions the individual answers.

What data

Which layers of the twin are shared — molecular, clinical, nutritional, wearable — chosen individually rather than as one switch.

Who can use it

Which institutions, which roles, and which named individuals.

For what purpose

Care, research, or population analysis. Consent granted for care does not implicitly authorise research.

For how long

With expiry, and with revocation that propagates to derived artefacts within a defined period.

Governance properties
ProvenanceEvery observation records origin, method, version, quality flags and the pipeline that produced it.
LineageEvery derived artefact links to the inputs, evidence snapshot and model versions behind it.
Purpose bindingConsent basis is carried by the artefact, so revocation is a traversal rather than a search.
ResidencyConfigurable per deployment, including full operation within a single jurisdiction.
PortabilityA person’s complete twin exportable in open standard formats on request. No customer surrenders portability as a condition of use.
Immutable auditAccess to any record is itself a recorded event, available to the data custodian.
No PHI in telemetryEnforced by automated check in build and at runtime, not by policy alone.
Why genomic data is different

Three obligations ordinary health data does not create.

It cannot be remediated

There is no equivalent of changing a password. A breach is permanent.

It implicates others

A disclosure affects relatives who never consented and cannot be asked.

It creates a standing duty

An interpretation issued today will mean something different in ten years.

Get started

Review our data governance.

Data-processing agreements, control mappings and consent architecture shared under NDA.