> ## Documentation Index
> Fetch the complete documentation index at: https://docs.moca.network/llms.txt
> Use this file to discover all available pages before exploring further.

# Data Privacy

> Privacy-by-design in Moca Network — where user data lives, what is encrypted, who has access, and how data minimization is enforced across the stack.

Moca Network follows a privacy-by-design approach. User data is minimized at every layer, and access is gated by cryptographic controls and explicit user consent.

## Data minimization

The default AIR Kit integration stores the minimum data necessary:

| Data type                   | Stored by Moca?                | Notes                                                                                            |
| --------------------------- | ------------------------------ | ------------------------------------------------------------------------------------------------ |
| User email                  | Yes (hashed identifier)        | Used as the AIR Account identifier for cross-partner portability                                 |
| Credential claims           | Encrypted envelope in DStorage | Payloads are encrypted to the holder; AIR stores opaque ciphertext and metadata, never plaintext |
| Private keys                | No                             | Keys are split via MPC; no single party holds a full key                                         |
| Verification records        | Off-chain by default           | Recorded on-chain only when a program requires on-chain verification                             |
| PII (ID photos, biometrics) | Only if CAK is enabled         | Encrypted in dStorage, accessible only with user consent                                         |

## Who can access what

### Standard flow (all credentials)

Every credential is signed by the issuer and encrypted to the holder before storage:

* **Issuers** know the data they put into the credential (they are the source of truth) and hold their own signing keys.
* **Verifiers** receive a Verifiable Presentation containing only the claims the program requests. They never see undisclosed claim data.
* **AIR** stores encrypted credential objects and metadata as a blind facilitator. It cannot reconstruct credential content.
* **Users** hold the encrypted credential in their AIR Account and control when and to whom it is presented.

### With CAK enabled

When the Compliance Access Key framework is active:

* **Issuers** encrypt raw data with a user-derived public key before storing it. After issuance, the issuer cannot read it back.
* **Verifiers** can decrypt raw data only after the user grants explicit consent in the SDK UI. Consent is per-verifier and per-session.
* **dStorage** holds encrypted blobs. Storage providers cannot decrypt them.
* **Users** are the only party who can authorize decryption by generating the corresponding private key locally.

See [Privacy & Compliance (CAK)](/learn/advanced-topics/privacy-and-compliance) for the full framework.

## Data residency

* **Encrypted credential payloads** are stored in decentralized storage (DStorage) on Moca Chain as opaque ciphertext.
* **On-chain data** (optional proof records, state anchors) lives on Moca Chain and is globally replicated across validators, and is written only when a program requires on-chain verification.
* **Session tokens and MPC key shards** are stored on the user's device and in secure execution environments. They are not centrally stored.

## User control

Users can:

* **Revoke consent** — If a user previously authorized a verifier, they can deny future requests.
* **Export keys** — Users can export their wallet private key for portability.
* **Delete their account** — Account deletion removes the user's session and local key material. On-chain proofs remain (blockchains are append-only), but they cannot be linked back to the user without the account.

## Compliance considerations

Moca Network provides technical primitives (encryption, consent management, audit trails) that support compliance frameworks such as GDPR, CCPA, and industry-specific regulations. The [Security Checklist](/learn/security/security-checklist) covers integration best practices for maintaining compliance.

<Warning>
  Moca Network provides infrastructure and tooling. Compliance responsibility ultimately lies with the issuer and verifier organizations. Consult legal counsel for your specific regulatory requirements.
</Warning>