Your records are AES-256-GCM encrypted with your key. Conceptual Health stores the
ciphertext only — we cannot read your records. Sign in once and the same session
works across Guardian Orb, Datavault, Wallet, and Clinical.
Every clinical document, image, lab, journal entry, and CH snapshot you've ever produced. AES-256-GCM encrypted with your key — Conceptual Health stores opaque ciphertext only. The contents are unreadable to the server, to our staff, and to any subpoena that targets us instead of you.
Your vault populates when one of the following writes an encrypted entry to it:
iOS / Android app — every dream entry, journal, nutrition log, vital sign, lab result, and prescription you record through the mobile app encrypts locally and syncs here.
Clinical encounters — when a clinician signs an encounter note, it lands here under your scope.
Health Connect / HealthKit — wearable + watch sync push vital signs (HR, HRV, sleep, steps) into encrypted vital-sign entries.
Provider imports — lab results, imaging (DICOM), and discharge summaries from connected providers.
Manual upload — PDFs, images, audio of encounters, anything you want to seal under your key (iOS app for now; browser upload in a future release).
id {String(e.id).slice(0, 8)}… · v{e.sync_version || 1}
{e.data_type}
{e.last_modified ? new Date(e.last_modified).toLocaleString() : '—'}
Encrypted
);
})}
Contents are AES-256-GCM ciphertext. Decryption happens only on the iOS / Android client that holds your key. The browser shows metadata only — by design.
No active provider grants. When you authorize a clinic or clinician to read part of your vault, the grant will appear here with full scope detail. Revocation is one click and immediate.
{s.consent_date ? new Date(s.consent_date).toLocaleDateString() : '—'}
{s.expires_at ? new Date(s.expires_at).toLocaleDateString() : 'No expiry'}
))}
)}
);
const AuditTab = ({ audit }) => (
Audit log
Every read, every write, signed to chain.
{audit.length === 0 ? (
No vault-access events recorded yet. Every read of an encrypted entry — by you, by a clinician you've granted access to, or by an automated sync — appears here HMAC-chained so anomalies are detectable.