> For the complete documentation index, see [llms.txt](https://docs.xym.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xym.network/xym-network/our-approach.md).

# Our Approach

Xym Network establishes an independent security layer on mobile devices, separating all Web3 and communication activity from the base operating system. It uses hardware-backed encryption and isolated runtime environments to protect wallets, dApps, and social applications from external interference.

Every transaction, signature, and data exchange is handled inside a secure enclave, ensuring that private keys and messages never leave the protected area. Network traffic is routed through Xym’s internal VPN and DNS shield, blocking unauthorized tracking, phishing sites, and data leaks.

Each app inside Xym Network operates within its own container. There is no shared storage or process access between applications. Users can safely use Telegram, X, or any installed dApp without cross-exposure or data correlation.

For recovery, Xym Network provides two clear paths: a **PIN-based recovery** linked to verified Gmail and phone channels with a time-lock safety window, and an **optional master seed backup** for full sandbox restoration. Both methods ensure users retain control without involving custodial intermediaries.

Xym Network focuses on security by design, not marketing claims. It offers practical, verifiable protection grounded in existing hardware and cryptography standards.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.xym.network/xym-network/our-approach.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.