Legal
Privacy policy
What rtp.fun collects, where it lives, and what RTP collects only when a feature needs it.
This Privacy Policy describes what rtp.fun (“RTP”, the “Service”) collects, where it lives, and what RTP does not collect by default.
1. Design principle
The Service minimizes data collection by architecture: much of what you do stays in your browser. This Policy describes what RTP processes. It does not use “non-custodial” as a description of the whole Service.
2. What RTP does not collect by default
- Private keys and recovery phrases for a wallet you control — RTP does not collect them on those paths.
- Analytics or behavioral tracking — RTP embeds no analytics, advertising, or fingerprinting scripts.
- A server-side trading-history profile — positions and profit-and-loss records you keep in the interface live in your browser’s local storage, unless a specific enabled feature says otherwise.
A wallet created in your browser is stored in browser storage on your device. Export anything you intend to keep before clearing site data.
3. What is stored on your device
| Storage | Contents | Sent to RTP? |
|---|---|---|
| Browser local storage | Interface settings, RPC preferences, positions and profit-and-loss records, signal filters, documentation theme | No |
| Session memory | Wallet signing results, transaction parameters | Only at signing or submission |
Clearing your browser’s site data removes local storage items for this site.
4. What RTP’s servers process
- Infrastructure logs: IP address, request path, and timestamp — used for rate limiting, abuse prevention, and fault diagnosis.
- Public market data you request through the terminal: token metadata, prices, and similar public facts, so the interface can render them.
- Optional features you use, once enabled: materials you supply for a launch, handled according to that launch option’s own hosting and specs (for example, to produce an on-chain metadata record, which is permanent); fee event reports carrying a transaction hash; access checks involving your public wallet address and a proof of control.
Launch uploads, fee reports, and access checks are not enabled in the current build. They will not run until the corresponding product path is on.
5. Third parties
- Sign-in and wallet providers: your login wallet’s provider is subject to its own privacy policy. RTP does not copy its cookies.
- Network, market-data, and partner platform providers: public market data and platform-specific hosting you use may be fetched by RTP’s servers or by your browser; their policies apply to that traffic.
- RTP does not sell, rent, or share personal data with data brokers.
6. Retention
Server logs rotate automatically. Launch metadata written to a permanent on-chain record cannot be changed once published — do not upload anything you are not prepared to make permanent and public under that launch option’s rules.
7. Your controls
Clear your browser’s site data to delete local storage. Contact RTP through Contact for log-related requests. Sign-in, when provided by a third party, may keep its own records under its own policy — RTP does not operate a general trading-history account database.
8. Changes
Material changes to this Policy will be reflected here, with an updated effective date, before the corresponding behavior ships.