> For the complete documentation index, see [llms.txt](https://learn.trovemarkets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.trovemarkets.com/misc/legal/privacy-policy.md).

# Privacy policy

## Trove Privacy Policy

Trove ("we," "us," "our," or "Trove") is a decentralized perpetual futures exchange currently running in public testnet phase on the Hyperliquid L1 testnet.

Mainnet has not launched yet — everything you do right now is on testnet, using fake/testnet USDC that, and no real value is at risk.

{% hint style="success" %}
We are committed to maximum privacy and transparency from day one.
{% endhint %}

### 1. What We Do NOT Collect (Now or on Mainnet)

We do not collect, store, or have access to:

* Your name, email, phone number, or any KYC information
* IP addresses (beyond temporary, auto-discarded connection logs)
* Cookies or any form of cross-site tracking
* Browsing history outside of trove.markets
* Any off-chain personal identifiers

Trove is 100% non-custodial on both testnet and mainnet. We never touch your private keys or funds.

### 2. What Is Public (Testnet & Future Mainnet)

All activity on Hyperliquid L1 (testnet today, mainnet tomorrow) is fully on-chain and publicly visible to anyone:

* Your wallet address
* All trades, positions, deposits, withdrawals, PnL, and leverage
* Transaction history

This data is pseudonymous and part of how blockchains work. We never link wallets to real-world identities unless you publicly do so yourself.

### 3. Website & Analytics (Minimal & Privacy-First)

When you visit trove.markets or our perp dex:

* Zero tracking cookies
* Zero third-party scripts (no Google Analytics, Meta Pixel, Hotjar, etc.)
* Only aggregated, anonymous stats (e.g., daily unique visitors, most viewed pages)

### 4. Communication & Support If you reach out via:

* Email (<hi@trovemarkets.com>)
* Twitter/X (@troveMarkets)
* Telegram (@troveMarkets)

We only use the information you voluntarily provide to help you or improve the protocol.\
We do not build marketing lists, sell data, or share it with anyone.You can (and most users do) stay completely anonymous.

#### 5. Third-Party Services

* Hyperliquid L1 Testnet → temporary IP logs may exist at node level for security; Trove has zero access
* Wallet providers (MetaMask, Rabby, etc.) → follow their respective privacy policies
* Block explorers → public testnet data is viewable by anyone

#### 6. Data Security

There is no central database to hack.\
Your security = your seed phrase security. Use a hardware wallet and never share your keys.

#### 7. Changes to This Policy

Any updates will be posted here with a new "Last updated" date.\
Given our fully on-chain model, material changes to privacy practices are extremely unlikely — even after mainnet launch.

#### 8. Contact Us

Email: <legal@trovemarkets.com>

X/Twitter: @troveMarkets\
Telegram: @troveMarkets

We reply fast, usually within a few hours.


---

# 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://learn.trovemarkets.com/misc/legal/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.