Privacy Policy
Effective date: September 10, 2026
This Privacy Policy describes what rtp.fun (“we”, the “Service”) collects, where it lives, and what we never touch.
1. Design Principle
Section titled “1. Design Principle”The Service is non-custodial and minimizes data collection by architecture, not by promise: most of what you do never reaches our servers because transactions are constructed and signed locally in your browser.
2. What We Do Not Collect
Section titled “2. What We Do Not Collect”- Private keys, seed phrases, or signing credentials — these never leave your device.
- Analytics or behavioral tracking — we embed no analytics, advertising, or fingerprinting scripts.
- Trading history as an account record — your positions and PnL live in your browser’s local storage, not in our database.
3. What Is Stored on Your Device
Section titled “3. What Is Stored on Your Device”| Storage | Contents | Sent to us? |
|---|---|---|
| Browser local storage | Interface settings, RPC preferences, positions/PnL records, signal filters, documentation theme | No |
| Session memory | Wallet signing results, transaction parameters | Used at signing/submission only |
Clearing your browser’s site data removes all of it. Warning: locally created hot wallets are also stored there — export any wallet you intend to keep before clearing.
4. What Our Servers Process
Section titled “4. What Our 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 invoke, when they are enabled: token metadata and images you upload for a launch (hosted to produce an on-chain metadata URI, which is permanent); fee event reports carrying a transaction hash; access checks involving your public wallet address and a proof of control.
Launch upload, fee reports, and access checks are not enabled in the current production build. They will not run until the corresponding product path is on.
5. Third Parties
Section titled “5. Third Parties”- Sign-in and embedded-wallet providers, when sign-in is configured: subject to that provider’s own privacy policy. We do not copy their cookies.
- Network and market-data providers: public market data you view may be fetched by our servers or by your browser; their policies apply to that traffic. We do not publish the list of providers.
- We do not sell, rent, or share personal data with data brokers.
6. Retention
Section titled “6. Retention”Server logs rotate automatically. Launch metadata, if you ever upload it, must remain reachable because its URI is written on-chain and cannot be changed; do not upload anything you are not prepared to make permanent and public.
7. Your Controls
Section titled “7. Your Controls”Clear site data to delete local storage. Contact us through the channels at Contact for log-related requests — those channels are currently unpublished. There is no account to delete because there is no account database.
8. Changes
Section titled “8. Changes”Material changes to this Policy will be reflected here with an updated effective date before the corresponding behavior ships.