Privacy Boundaries & Use Cases

Acceso’s ZK layer is designed around strict privacy boundaries. Secrets stay inside the proving boundary.

Privacy isolation

Sensitive inputs used for proof generation are never persisted beyond execution scope. Only proof artifacts and public signals are retained.

This ensures:

• No leakage of private inputs

• Minimal data retention

• Clear separation between private and public data

If an input must remain private, treat it as a proving input, not a verification input. Verification should only need public values.

Supported use cases

The ZK infrastructure supports use cases such as:

• Private balance assertions

• Membership proofs

• Condition verification without disclosure

These use cases are exposed as composable primitives rather than monolithic features.

Performance considerations

Proof generation is computationally intensive and may have higher latency than standard API calls. Verification is optimized for low-latency validation.

Clients are encouraged to use ZK selectively for privacy-critical workflows.