Enclave Overview
—
E
EpitoMe Private Preview
Human-Centered Co-Creation Portal & Secure Personal Workspace
Human-Centered Co-Creation Portal & Secure Personal Workspace
Your secure personal data estate status and identity information.
Full estate metrics load in Phase 2.
Your post-quantum Decentralized Identity credentials and key management.
Verifiable credentials issued to your identity.
ML-DSA-65 and ML-KEM-768 post-quantum key lifecycle.
USCDI-compliant patient health records synced from your health portal.
zkPass TransGate uses 3-party TLS to privately prove you have access to data at a health portal — without revealing the data itself. Your browser runs the verification locally; only a cryptographic proof is sent to EpitoMe.
This zkPass integration is a deliberate interim step — not the end-state UX.
EpitoMe's long-term architecture uses sMPC — secure Multi-Party Computation — a cryptographic protocol where multiple independent compute nodes each hold encrypted fragments of your data. No single node ever sees the full dataset. Queries (e.g. "does this patient meet trial eligibility criteria?") are computed across the shards without any node learning the answer. The result is revealed only to the authorized requester, only in the form the consent policy permits.
sMPC is the right end-state because it means EpitoMe itself never holds plaintext — your data is mathematically distributed such that even a complete breach of EpitoMe's infrastructure reveals nothing usable. This is fundamentally stronger than encryption-at-rest.
zkPass TransGate is the bridge. It uses zero-knowledge proofs over a 3-party TLS connection to prove facts about your health data to a verifier — right now, today — without requiring bespoke MPC infrastructure. It answers the same question ("can I prove I have access to and ownership of this health record?") using a proven cryptographic mechanism: ZK proofs over TLS rather than secret sharing across MPC nodes.
This milestone matters because it validates the complete pipeline — identity → health data verification → cryptographic proof anchoring — end-to-end. Every piece of that pipeline carries forward into the sMPC implementation. When sMPC ships, the UX will be invisible: no extensions to install, no browser sessions to manage. The proof happens server-side, distributed across nodes you choose.
Secure VCF sequence storage and private variant analysis.
Encrypted DICOM MRI and CT imaging records.
Chronological view of your health events and encounters.
Your Personal Data Estate compartments and visual explorer.
Control which research cohorts and partners can access your data.
Incoming and outgoing data access requests.
Immutable cryptographic log of all actions on your data estate.
Your private local AI for health intelligence and data insights.
AI-powered oncology analysis from your genomic and clinical data.
Track and visualize key biomarkers over time.
Contribute anonymously to drug discovery research pools.
Hypergraph metagraph state and data provenance tracking.
USDC yield settlement on Base L2 from UDI pools.
Active and historical data licensing orders.
DAG and USDC balances in your secure wallet.
Interactive REST API documentation for your enclave endpoints.