Consent Ledger
P3 research consent · Atlas data basis · Revocation impact · Immutable record
P3 CONSENTED
Research consent · Atlas data basis
P3 COVERAGE
P3 as % of P1 product consents
REVOCATIONS (30D)
0
P3 revocations trigger data removal from Atlas vault
CONSENT LEDGER STATUS
● Immutable · Append-only
Deletion prohibited at database level
Atlas Consent Architecture
P1 — PRODUCT CONSENT
Required for all product access · Gates session recording · Caregiver must consent before first session · Revocation suspends product access immediately
[ Separate opt-in required ]
P0 — TRAINING CONSENT
Opt-in · Permits de-identified markers for model training · Separate from P1 · Revocation removes data from future training runs
[ Further separate opt-in ]
P3 — RESEARCH CONSENT
Opt-in · Permits aggregated data for Atlas licensing · Highest consent tier · Revocation triggers Atlas vault data removal · Cell size >5 enforced
Atlas operates exclusively on P3-consented data. P3 consent is layered above P1 and P0 — it is not implied by either. A learner may have P1 consent (product use) without P3 consent (research licensing). Only P3-consented, cell-size-verified, fully de-identified data enters the Atlas Vault.
P3 Consent Register
Aggregate view · No individual records displayed
| MARKET | P3 CONSENTED | P1 TOTAL | COVERAGE % | LAST UPDATED | STATUS |
|---|---|---|---|---|---|