Meta16Labs
Trust

Consent framework

How consent is captured, recorded, honoured and withdrawn across our platforms.

Captured in context

Consent is requested at the moment data is collected, in the language the person is using the service in, with the purpose stated in plain terms.

Specific and unbundled

Separate purposes require separate consent. Consent for care delivery is never bundled with consent for research or communications.

Recorded immutably

Every consent event is stored with a timestamp, the notice version shown, the capture channel and the identity of the person who obtained it.

Enforced at the platform

Consent state is checked at the point of data access, not merely recorded. Absence of valid consent blocks the read.

Withdrawable

Withdrawal is available through the same channel that captured consent, takes effect immediately, and is as easy as granting it was.

Auditable

A complete consent history is available to the institution for audit and to the individual on request.

This page summarises our operating commitments. The governing terms are those in the executed agreement with your institution.