> 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/security-and-privacy.md).

# Security and Privacy

Key Measures

* **Encryption**: Government ID images are encrypted using Seal before storage in Walrus.
* **Secure Signing**: Rust backend uses ephemeral keys for tamper-proof blockchain updates.
* **OTP Security**: Time-bound OTPs prevent unauthorized access.
* **Access Control**: Only whitelisted entities can decrypt and view stored IDs.

**Why It’s Trusted**

* **Privacy-First**: Sensitive data is processed server-side and encrypted.
* **Compliance**: The system is designed to meet regulatory standards.
* **Transparency**: Blockchain records provide verifiable proof of verification.

This commitment to security ensures users can trust the platform with their data.


---

# 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/security-and-privacy.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.