# Privacy Policy

Privacy on the open web can feel paradoxical: blockchains are transparent by design, yet personal identity craves discretion. The Protocol embraces a minimalist, privacy‑respecting philosophy—collect only what is essential, discard it when it stops being useful, and let cryptography shoulder the heavy lifting.

**2.1 Data We Happily Ignore**\
We do not request your real name, your physical address, or your favourite colour. The smart‑contracts care only about wallet addresses, numbers, and cryptographic signatures.

**2.2 Bits We Do Notice**\
When you send a support email or open a help‑desk chat, you choose to share a contact handle. Similarly, the web front‑end may capture anonymised statistics—page load times, button clicks, generic browser fingerprints. These metrics help us polish rough edges and improve responsiveness.

**2.3 Voluntary Compliance Checks**\
In rare cases, optional staking pools may integrate a third‑party zero‑knowledge KYC module. Imagine proving you are “a unique human” without revealing the pages of your passport. Participation is elective; declining simply means you stick to pools that have no additional requirements.

**2.4 Retention & Deletion Rhythm**\
Support tickets linger in encrypted storage just long enough to solve your issue—after twelve (12) relaxing months, they are politely shredded unless legal winds dictate otherwise. Aggregated analytics live in the cloud for no more than twenty‑four (24) months before they, too, fade into oblivion.

**2.5 Your Toolkit of Rights**\
Should you wish to peek at stored data, correct a typo in your email or wave goodbye to it entirely, a signed message from your wallet to privacy\@paddr‑protocol.io starts the process. Turnaround is swift; bureaucracy is minimal.


---

# Agent Instructions: 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:

```
GET https://paddock.gitbook.io/paddock-docs/legal/privacy-policy.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.