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

# CatFee Air Wallet Privacy Policy

Last updated: 2026-06-24

CatFee Air Wallet is a browser extension that connects TRON and EVM DApps to CatFee Offline Signer. Its purpose is to turn DApp connection, message signing, and transaction signing requests into phone-approved QR workflows.

## What the Extension Does Not Store

CatFee Air Wallet does not create, import, store, decrypt, transmit, or back up private keys, seed phrases, backup passphrases, or wallet recovery secrets.

Private keys stay in CatFee Offline Signer on the user's phone.

## Data Stored Locally in Chrome

The extension stores only the data needed to operate the wallet bridge:

* Signer addresses added by the user.
* The currently selected TRON or EVM signer address.
* Selected TRON and EVM network settings.
* Custom EVM RPC network settings added by the user.
* Language preference.
* DApp origins approved by the user and the address selected for each origin.
* DApp origins that the user has disconnected.
* Temporary pending approval state while an approval window is open.

This data is stored locally in Chrome extension storage. It is not used for advertising, profiling, or sale.

## DApp Requests

When a website or DApp sends a wallet-provider request to the extension, CatFee Air Wallet processes the request only for wallet operation. Examples include account connection, message signing, typed-data signing, transaction signing, and signed transaction broadcast.

The extension shows an approval flow before exposing an address to a DApp or returning a signature result. Transaction and message signing requests are converted into QR workflows for CatFee Offline Signer.

## Network Requests

The extension may contact the selected TRON or EVM RPC endpoint to perform wallet functions such as reading chain data, estimating gas, filling transaction defaults, or broadcasting a signed raw transaction.

Users can configure custom EVM RPC endpoints. Requests to those endpoints are controlled by the selected network configuration.

## No Sale or Advertising Use

CatFee Air Wallet does not sell user data. It does not use extension data for ads, cross-site advertising, or behavioral profiling.

## User Control

Users can remove DApp connections from the extension's connection management screen. Users can also remove signer addresses and custom network settings from the extension UI.

Removing the extension from Chrome deletes the extension's local browser storage.

## Security Model

The extension is designed so browser-side DApps do not receive private keys. DApps receive only the connection or signature result needed for the request approved by the user.

Users should still review every DApp request carefully before signing and should only use trusted RPC endpoints for custom networks.

## Contact

For support or privacy questions, use the support contact published on the Chrome Web Store listing or the CatFee website.


---

# 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://wallet-docs.catfee.io/catfee-air-wallet/privacy-policy.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.