Custody model
Rudra.exchange is non-custodial. You sign every transaction with your own wallet or key, and Rudra never holds your funds, your keys or your recovery phrase. Nobody at Rudra can move, freeze or recover your assets.
How you sign in
Wallet apps such as Freighter and LOBSTR, Ledger hardware wallets and WalletConnect sign inside the wallet. The Rudra page only sees your public address and the signed transaction.
A secret key entered on the login page stays in the page memory and signs in your browser. It is never sent to Rudra and never saved in your browser storage.
After a refresh Rudra restores only your public address in view mode, and asks for the key again before anything can be signed.
Protect your keys
Never share your secret key or recovery phrase. Rudra will never ask for them by email, chat or social media.
Prefer a wallet app or a hardware wallet over typing a secret key into any website.
Check that the address bar shows https://rudra.exchange before you sign in.
Set an anti-phishing Secret Phrase on the login page. Rudra shows it only on the genuine site on your device, so a look-alike page cannot.
Transaction and market risk controls
On-chain transactions are generally irreversible after confirmation.
Always verify destination, asset code, issuer, amount and network in your wallet before signing.
Dollar values and price impact are estimates; the minimum you receive in a swap is set by your slippage tolerance.
Anyone can issue a token with any name. Check the issuer account and its home domain, not just the code.
How the site is protected
HTTPS is enforced for rudra.exchange and its subdomains (HSTS for one year).
A strict Content Security Policy limits scripts to Rudra and its named analytics providers, and blocks the site from being embedded in other pages.
Browser access to location, microphone and motion sensors is switched off for the site.
Analytics and error reports never receive secret keys, and product analytics removes addresses and transaction hashes.
Every release passes automated tests and a protected-file check before it goes live.
Responsible disclosure
To report a security issue, send details to support@rudra.exchange with reproduction steps, impact, affected URL(s), and supporting evidence.
IncludeReproduction steps
IncludeImpact
IncludeAffected URL(s)
IncludeSupporting evidence
@RudraExchange