Account identity
Clerk provides the account identity and session layer. PATCHES security credentials remain separate from the identity provider.
PPATCHESSECURITY ARCHITECTURE
Privacy protection without impossible promises.
PATCHES is being engineered around separation of identity, security credentials, encrypted customer data, partner access and device capabilities.
Master Code boundary
The PATCHES Master Code is designed as a separate high-entropy security control. Production implementation stores only derived verification material — never plaintext credentials.
Duress / decoy access
A separate duress path can open a believable decoy environment without revealing or decrypting the real Ghost Vault.
Device-aware controls
Sensitive device actions require capability checks, explicit enrollment and strong authorization. PATCHES does not promise controls an operating system cannot provide.
PARTNER ISOLATION
ARMA and future partners get scoped access — not database access.
Partner integrations are designed around explicit scopes, entitlements, auditable events and revocable credentials. Master Codes, Duress Codes, Vault master keys and unrelated customer data are outside the partner boundary.