> For the complete documentation index, see [llms.txt](https://zcloak-hub.gitbook.io/zcloak-ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://zcloak-hub.gitbook.io/zcloak-ai/products/keychain.md).

# Keychain

### What Keychain Is

**zCloak Keychain** is the cryptographic foundation of the system.

It is responsible for:

* Key generation
* Key storage
* Signing operations
* Recovery and rotation

Keychain exists to make **cryptographic identity usable by non-experts**.

***

### Why invisible key management is necessary

Trust in ATP depends on keys. But user-managed keys are fragile:

* loss and theft are common
* UX is too complex for mainstream adoption
* operational burden is high for enterprises

Keychain makes cryptography practical by making it invisible.

***

### For individuals

* **Social login** (email, Apple, etc.) as identity entry point
* **Passkey / biometrics** for authorization
* **Multi-path recovery** by linking multiple credentials

User experience remains familiar: “Sign in with Apple”, then sign actions with FaceID.

***

### For Enterprises and Agents

For enterprises and AI agents, Keychain supports:

* Local key generation
* TEE-based protection
* Enterprise SSO integration
* Key lifecycle management and revocation

***

### Trust Boundary

Keychain does not:

* Interpret data
* Publish events on its own
* Act as a custodian of user intent

It performs **only cryptographic operations**, nothing else.

***

### How it fits in the stack

Keychain powers AI-ID. Users typically do not interact with it directly, but it is foundational to frictionless adoption.