Skip to the policy
rtp.fun

Legal

Cookie and storage policy

How rtp.fun uses browser storage, and why it does not use tracking cookies.

Effective date: September 10, 2026

1. The short version

The RTP app uses essential browser storage for sign-in, encrypted wallet data, interface settings, and your storage preference. Optional app statistics are off; no optional statistics integration is configured. Your cookie choice does not delete your wallet or sign you out. Some account and transaction information is sent when the feature you use requires it; see the Privacy policy.

2. What RTP actually uses

StorageWhereContentsSent to RTP?
Local storageYour browserSign-in session, interface settings, positions and profit-and-loss records, signal filters, documentation theme, and your cookie preferenceSign-in or enabled features may send the information they need; the cookie preference itself stays on your device.
Encrypted wallet storageWallet browser storageYour encrypted wallet and recovery dataPrivate keys are not sent to RTP; an explicitly created encrypted backup may be stored for recovery.
Session memoryYour browserSigning results, transaction parametersOnly at signing or submission
Server logsRTP’s serversIP address, request path, timestamp — for rate limiting and abuse preventionSee Privacy policy

3. Third parties

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.

Choose Accept necessary, Reject optional, or Customize in the app. Both initial choices retain essential storage and leave optional app statistics off. You can revisit Cookie preferences at any time. If your browser blocks saving this preference, the choice lasts for the current page only.

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.