Legal
Cookie and storage policy
How rtp.fun uses browser storage, and why it does not use tracking cookies.
1. The short version
RTP does not use tracking cookies. Functional state — your settings, positions, and preferences — is stored in your browser’s local storage. It stays on your device and is never transmitted to RTP’s servers.
2. What RTP actually uses
| Storage | Where | Contents | Sent to RTP? |
|---|---|---|---|
| Local storage | Your browser | Interface settings, RPC preferences, positions and profit-and-loss records, signal filters, documentation theme | No |
| Session memory | Your browser | Signing results, transaction parameters | Only at signing or submission |
| Server logs | RTP’s servers | IP address, request path, timestamp — for rate limiting and abuse prevention | See Privacy policy |
3. Third parties
- Sign-in and wallet providers may set their own cookies or storage during sign-in, governed by their own policy. RTP neither reads nor copies them.
- Network and market-data providers: public market data you view may be fetched by RTP’s servers or by your browser; their policies apply to that traffic.
- A partner platform you choose to launch or trade through may apply its own storage or hosting rules — see Privacy policy and Launch options.
- RTP embeds no analytics, advertising, or fingerprinting scripts.
4. How to clear
Your browser’s “clear site data” option removes all local storage. A wallet created in your browser lives there too — export it first if you want to keep it.
There is nothing to opt out of, because no tracking exists to opt out of.
5. Changes
This page tracks the product’s actual behavior. If a new storage mechanism or third party is ever introduced, this page is updated first, and the feature ships after.