> For the complete documentation index, see [llms.txt](https://kusuconsult-1.gitbook.io/doerdapp-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kusuconsult-1.gitbook.io/doerdapp-docs/policy/privacy-policy-why.md).

# PRIVACY POLICY/ WHY

Effective Date: 1st February 2026

**Last Updated:** 12th February 2026

### The Philosophy Behind This Policy

DOER DAPP is built on decentralization.

That means:

* We do not custody your funds
* We do not control your wallet
* We do not see your private keys
* We do not intercept your signed transactions

You interact with the blockchain directly.

Our role is to provide execution infrastructure — not surveillance.

### What We Collect (And Why)

We intentionally collect as little as possible.

#### A. Wallet Address

When you connect a wallet, we may collect:

* Your public wallet address

This is necessary to:

* Display account-related data
* Track execution status
* Provide transaction history within the interface

Your wallet address is already public on-chain.

We do not collect your private key. Ever.


---

# 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://kusuconsult-1.gitbook.io/doerdapp-docs/policy/privacy-policy-why.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.