Security

Security and custody

Understand where your keys are held, how transaction approvals work, and how to check what your Wallet signs.

Rtp.Fun is self-custodial by design. Your Wallet signs on your device. A password-protected wallet keeps an encrypted local copy. Sign-in-wallet recovery can store a separately encrypted backup on RTP servers; the server does not receive the plaintext keys or the local decryption material required to sign.

Who holds what

	Holds	Can move your funds?
You	Your recovery material and access to the chosen protection method	Yes — by authorizing actions in your Wallet
Your Wallet, in your browser	Your keys, encrypted on your device	After your approval, or within the presets and automation limits you authorize
Rtp.Fun servers	Market data, settings, unsigned transactions and, when saved, an encrypted recovery backup	No

How a transaction is made

You ask. Pick the token, the amount and the settings.
Rtp.Fun prepares it. Our servers build the transaction and send it back unsigned, with the amounts and fees spelled out.
You authorize. Review the selected route and settings. One-tap trades use your presets; enable Confirm each trade if you want a separate review for each order. Automation uses the limits you authorize.
Your Wallet signs. Signing happens on your device. Plaintext signing keys do not leave it. A recovery backup, if saved, is encrypted before it is uploaded.
It is sent. The signed transaction goes to the network, and the status updates until it settles.

A signed transaction cannot be altered on the way: any change would break the signature.

Built for the bad day

Server storage is not a signer. A stored encrypted backup alone is not enough to sign. Protect your device, recovery material and linked wallet too; compromised application code or a compromised device remains a risk.
Check each type of charge. The Rtp.Fun platform fee is included in the transaction for routes that collect it there. Network fees can still be charged for failed on-chain attempts; approval, account creation and multi-step routes may incur separate costs. See Fees.
“Checking” is never shown as “failed”. If the network has not answered, Rtp.Fun keeps checking instead of letting you send twice. See Transaction status.
Sign-in and signing are separate. The wallet or account you sign in with is never asked to sign a trade.

Self-custody versus custodial tools

	Custodial tools	Rtp.Fun
Private key	Decryptable on the provider’s server	Used for signing on your device; optional encrypted recovery backup
Who signs	The provider’s server	Your browser-held Wallet under your authorization
Server backup access	The provider may hold signing access	Encrypted backup alone does not provide signing access
Automation	Runs on their server with your key	Runs in your browser, inside the limits you set

Check it yourself

The order settings. Turn on Confirm each trade for a separate order review. For quick buys and automation, check the preset, spend limits and permissions before enabling them.
The signing address. Confirm that execution uses your RTP Wallet, not the external wallet used only to sign in. Never send signing secrets or a browser network capture to support; a capture can contain private account information.
The explorer. Open any confirmed transaction: it is signed by your Wallet’s address.
The addresses. Compare what your Wallet shows with Contracts and addresses.

Recovery and new devices

Account sign-in does not transfer trading keys. Restore the original wallet and compare its addresses before using it on a new device. A recovery option being visible does not confirm that a backup exists. If all device copies and recovery methods are lost, RTP cannot reconstruct the keys. Follow the backup and mobile recovery guide.

Your part

Keep recovery material offline. Support will never ask for it. Only enter it into the secure wallet restore window that you deliberately open.
Start at https://rtp.fun; enter trading passwords and recovery secrets only at https://wallet.rtp.fun. Check the address bar first.
Read what you sign, and lock the Wallet on a shared computer.
A confirmed transfer cannot be reversed by Rtp.Fun. A pending or uncertain transaction still needs to resolve; closing the page does not cancel it.

Automation and session limits

Automation requires an open browser session, an unlocked Wallet and current execution authorization. Closing the browser stops authorization renewal; locking the Wallet or an expired authorization prevents new signing and sends. The server does not take over as an unattended signer. A transaction already sent while authorization was valid may still confirm after you close the page.