> For the complete documentation index, see [llms.txt](https://suiverify.gitbook.io/suiverify/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://suiverify.gitbook.io/suiverify/audit-and-compliance/security-and-access-control.md).

# Security & Access Control

Security and granular access control are fundamental to the system's design.

#### Document Access Rules

The rules for accessing sensitive user documents are strict and enforced on-chain:

1. User: Can always decrypt their own documents.
2. Government: Whitelisted government addresses can decrypt any user's documents for audit and compliance.
3. Third-Party Protocols: Can only verify the status of a user's DID (e.g., "is this user over 18?"). They cannot access the underlying documents.

#### Encryption Flow

1. Documents are encrypted client-side using Seal, with the `Government Whitelist` contract ID as a parameter.
2. The encryption key is derived from the whitelist ID and a unique nonce.
3. All addresses in the government whitelist are automatically granted decryption rights.
4. The user's own address is added as an approved address for their specific documents, ensuring they retain access.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://suiverify.gitbook.io/suiverify/audit-and-compliance/security-and-access-control.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.