# Privacy Mechanism

#### Core Philosophy

Privacy is not a feature — it is the foundation of EvoPay. Our architecture is built to ensure no user is forced to expose wallet addresses, transaction metadata, or identity when sending or receiving crypto. EvoPay achieves this without pooling funds, using mixers, or relying on centralized relayers.

#### Private Send Flow

1. The user selects "Private Send" in the bot.
2. The bot requests a recipient username or system ID.
3. A new mediator wallet is created, unique to the transaction.
4. The user sends ETH to this temporary wallet.
5. Once received, the bot routes funds through a privacy relay and forwards the ETH to the recipient’s address.
6. The original sender and receiver never see each other’s wallets.

#### Private Receive Flow

1. The user selects "Private Receive."
2. The bot shows a unique EvoPay handle (e.g. @username or r2-313).
3. Senders can use this handle to send funds privately.
4. The bot manages mediator wallet generation and the anonymization relay.
5. The final ETH is delivered to the user with no link to the sender.

#### Relay System Design

Each mediator wallet is stateless, created on demand and deleted after use. These wallets act as a privacy layer without holding funds long-term. EvoPay avoids pooled mixers entirely. Instead, each transaction is independently routed, minimizing traceability.

#### Identity Obfuscation

* No usernames or Telegram IDs are ever stored or displayed during private transactions.
* EvoPay uses short-lived transaction IDs (e.g. r2-313) to facilitate routing without revealing origin or destination.
* All private transactions are logged on-chain through randomized transfer patterns.

#### Future Enhancements

* ERC-20 token support for private sends and receives
* Time-locked transactions with delayed delivery
* Optional gas anonymization via sponsored relays
* Reputation-safe identity systems with zero knowledge proof modules (ZK badges)


---

# 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://docs.evopay.me/privacy-mechanism.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.