# Privacy-Respecting AI Layers

In an era where data privacy is often sacrificed for intelligence, AGENFI is built differently. Our architecture is designed around **user-first privacy** — ensuring that no identifiable information is exposed or stored unnecessarily while still delivering powerful AI-driven insights.

AGENFI’s AI system uses a **privacy-respecting, zero-leak framework** where your on-platform actions are processed **locally or anonymously**, and your portfolio data is never shared, sold, or externally exposed.

***

<figure><img src="/files/nwGUOF9b3yGVBlfSjr5n" alt=""><figcaption></figcaption></figure>

#### 🔐 **How Privacy Is Protected**

**🧭 Client-Side Processing**

* Sensitive interactions (e.g. wallet analysis, personal watchlist scoring) are computed **on the user's device** or inside an encrypted session
* No raw wallet history is transmitted to external AI services

**🧱 Pseudonymized Data Models**

* When behavior data is used for AI training, it is **fully anonymized** and stripped of user-specific identifiers
* Data is aggregated in cohorts to protect individuals while improving system intelligence

**🧬 Zero-Knowledge-Enhanced Signals**

* Signal explanations and portfolio insights use **zero-knowledge principles**, meaning:
  * The AI proves why it triggered an alert
  * Without revealing the user’s full transaction context

**❌ No Third-Party Profiling**

* No cookies, fingerprinting, or advertising profiling
* User data is not accessible to third parties — even AGENFI team members have **no access to private user metrics**


---

# 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.agenfiai.com/3.-agenfi-ai-intelligence-layer/privacy-respecting-ai-layers.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.