Confidentiality
AES-256-GCM or stronger
Every stored record is encrypted at rest with authenticated 256-bit (or higher) block cipher keys. Data in motion runs over TLS 1.3.
Highest-security digital platform
Encryption you can verify, not just read about
256-bit or stronger block encryption, quantum-resistant key exchange, and every key rotation sealed as a block in an append-only key chain. Same protection for a single senior and for an enterprise tenant.
AES-256-GCMTLS 1.3NIST PQCKey-chain blocksZero-trust access
Defence in depth
Six layers, one sealed record
No single layer is trusted on its own. Data is protected in storage, in transit, in the key material, and in the audit trail.
Quantum resistance
NIST PQC key exchange
ML-KEM (FIPS-203), ML-DSA (FIPS-204) and SLH-DSA (FIPS-205) key encapsulation so a harvested-today, decrypted-tomorrow attack does not open old records.
Integrity
Dual-hash sealing
SHA-512 paired with SHA-3/Keccak on every sealed block. Alter one byte anywhere and the chain stops verifying.
Provenance
Key-chain blocks
Keys are minted, sealed into a block, chained to the block before it, and rotated on schedule — every rotation is provable.
Access
Zero-trust, per record
Access is enforced per record: an entry is visible to its author and workspace administrators only. No standing super-user access.
Availability
Self-healing supervision
Autonomous diagnostics watch the encryption layer, detect a failing key or node, and rotate or repair before a user notices.
Key-chain block technology
Every key leaves a provable history
Rotation is where most breaches hide. Here it is sealed, chained and anchored.
01
Key minted
A 256-bit (or stronger) data key is generated in an isolated boundary and never leaves it in the clear.
02
Block sealed
The key's fingerprint is sealed with SHA-512 + SHA-3 alongside the previous block's hash, forming the chain.
03
Anchored & rotated
The sealed block is anchored, then rotated on schedule — an audit can prove when every key lived and died.
Every record and document is anchored on-chain with quantum-resistant hashing (dual SHA-256 + SHA-512) and written as an immutable block to an append-only ledger. Access is token-gated per record: each entry is visible to its author and to workspace administrators only, with AES-256-GCM or stronger at rest and over TLS in transit, and every key rotation written as a block to the chain. Independent security certification and fixed audit-log retention periods remain roadmap commitments — not claims we make today.
Compliance layer
Your jurisdiction's rules, applied automatically
We read your time zone and language settings — never your IP — pick the matching medical and data-privacy framework, and apply it to everything this workspace does.
Compliance layer active — Global baseline
detecting…
Least-privilege accessPurpose limitationBreach readiness
No specific jurisdiction was detected, so the strictest common baseline applies until you choose your region.
- Breach notice
- Notify affected users without undue delay
- Consent model
- Opt-in before any secondary use
- Data location
- Regional hosting chosen per tenant
01
Purpose limitation
Data is used only for the purpose it was collected for.
02
Data minimisation
Only necessary fields are stored, and they are purged on schedule.
03
Access control
Per-record access, with every read and change auditable.
04
Health-data caution
Clinical content is treated as sensitive by default, whichever region you are in.
The layer applies the rules above; it is not a certification and not legal advice. Qualified counsel confirms requirements for your market before you rely on them.
Secure intake
Send us something sensitive the safe way
Health, legal and identity requests go through this form instead of email. You get a reference code that points to exactly one sealed record.