> For the complete documentation index, see [llms.txt](https://gl-docs.gitbook.io/zkpass/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gl-docs.gitbook.io/zkpass/core-components/trust-models/data-integrity-trust-model.md).

# Data Integrity Trust Model

Imagine you're sending two very important sealed letters through a courier service: one is a signed credential and the other is a signed DVR. You want to be absolutely certain that no one has tampered with these letters by the time they reach their destination. Welcome to zkPass, a service designed to act like that ultra-secure courier for your digital "letters."

In the world of zkPass, these letters go through a process similar to a high-tech, digital wax seal check—something called DSA verification. This ensures that your letters are exactly as you sent them, untampered and intact. Now, this seal check can happen in one of two rooms in zkPass's secure facility.

#### The Trusted Room

In the first room, the seal check happens separately from the main operation, which creates something known as a Zero-Knowledge Proof (ZKP). Think of this as zkPass first unsealing and reading your letters in a secure room, verifying they are legit, and then moving on to another task. This is what's called the Trusted Data Integrity model.

#### The All-in-One Room

In the second room, everything happens at once. The letters are unsealed, verified, and the ZKP is generated, all in one go. This is known as the Trustless Data Integrity model. It's like having a super-efficient clerk who can multitask like a pro.

Now, you might wonder, "Why not always use the All-in-One Room?" Well, the issue is that the seal-checking process is quite demanding. It's like asking the clerk to juggle too many tasks at once, and right now, the zkPass system can't handle that level of multitasking efficiently.

So, for the time being, zkPass recommends using the Trusted Room approach. It's not that it's the best option, but it's the most doable one right now, and it's still pretty secure. But keep an eye out! As zkPass gets better at juggling tasks, we might soon be able to use the All-in-One Room for even greater security.

In a nutshell, zkPass is currently taking a practical approach to keeping your data untampered, but it's always looking to step up its game.


---

# 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://gl-docs.gitbook.io/zkpass/core-components/trust-models/data-integrity-trust-model.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.