> For the complete documentation index, see [llms.txt](https://docs.j.tools/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.j.tools/concepts/privacy-and-responsible-use.md). # Privacy and responsible use The relay tools on J Tools route funds through intermediate wallets so the path from sender to receiver is not a single visible line on-chain. That is the whole feature, and it is useful for ordinary reasons: keeping a treasury address off the radar, separating a public-facing wallet from a working one, or moving funds without broadcasting the link to anyone watching the explorer. This page is about using that feature honestly, and the limits of what it actually gives you. Two tools provide the relay hops. [Relay Transfer](/tools/wallets/relay-transfer.md) routes a single source-to-destination move through a chain of fresh wallets. [Multi to Multi Relay](/tools/wallets/multi-to-multi-relay.md) does the same across many paired sources and destinations at once. Both generate the intermediate wallets in your session and hand you a recovery file of their keys before the run starts. {% hint style="warning" %} **Relays add hops. They are not anonymity, and they are not a way to hide illicit funds.** Routing through intermediate wallets makes the trail longer and harder to read at a glance. It does not erase it. The hops are public Solana transactions, every signature is on-chain forever, and chain-analysis tools can and do follow multi-hop paths. Do not use these tools to launder funds, evade sanctions, or hide the proceeds of anything illegal. That is a misuse of the tool and it is on you. {% endhint %} ## What relays do, and what they do not Be precise here, because "privacy tool" gets read as "untraceable" and the two are not the same.
What they doBreak the direct one-hop link between a source and a destination by routing through wallets you never reuse. Add configurable delays so moves don't all fire at once. Give you per-hop visibility and a recovery file.
What they do not doMake a transfer anonymous, mix your funds with anyone else's, or remove the trail from the chain. Every hop is a public, permanent transaction that analysis can trace end to end.
A relay is one source flowing into one destination through wallets that only ever held your money. There is no shared pool and no other participant, so anyone with the patience to walk the hops can connect the ends. More hops and longer delays raise the effort it takes. They do not change the math. Plan around your own threat model, and assume a determined observer can follow the path. ## Responsible use These tools exist for legitimate privacy and operational reasons. The line is not subtle. * **Acceptable:** protecting wallet addresses you control from casual observation, separating concerns between your own wallets, moving funds you legitimately own without advertising the route. * **Not acceptable:** laundering, hiding stolen or fraudulently obtained funds, evading sanctions or law enforcement, or structuring transfers to defeat reporting obligations you are subject to. You are responsible for following the laws and regulations that apply to you. J Tools is non-custodial software: you sign every transaction in your own wallet, and we never ask for its key. We do not move your funds for you and we cannot reverse a transfer once it is signed. The responsibility for how the tool is used sits entirely with the person running it. If a use case feels like it needs to be hidden from a regulator or a court, that is the signal to stop, not to add more hops. ## The pasted-key caution The relay tools work with private keys you bring to the page, and that is a different risk surface from the rest of the platform. Single-route SPL relays and the entire Multi to Multi Relay flow read raw keys so the hops can sign without prompting your wallet extension on every step. Keys stay in your session and go straight into the recovery file you download. They never reach our servers. Even so, a pasted key is a key out of its vault, so treat the wallets you use here as disposable. {% hint style="danger" %} **Use disposable wallets, and rotate them.** Only paste keys for wallets you can afford to abandon. Once a key has been pasted into any web page, move the funds out and stop using that wallet for anything you care about. Never paste a key back into chat, a form, or a message, and never reuse a relay wallet across unrelated runs. The recovery `.xlsx` that downloads at the start of a run holds live keys, so store it offline and treat it like cash. {% endhint %} This is an architecture rule on our side too. J Tools will never ask you for a private key outside the key-import field on these specific tools, and any message claiming to be from J Tools that requests your seed phrase or key is a scam. For the wider non-custodial model and how signing works everywhere else, see the security overview. ## FAQ
Does a relay make my transfer anonymous? No. It makes the trail longer and less obvious, not invisible. Every hop is a public Solana transaction, and chain-analysis tools can follow multi-hop paths. Use relays for privacy from casual observation, not as a guarantee of anonymity, and plan around your own threat model.
Can I use these tools to hide funds from an investigation? No, and you should not try. Using relays to launder money, hide stolen or illicit funds, or evade sanctions or law enforcement is a misuse of the tool and likely a crime where you live. J Tools is non-custodial software for legitimate privacy work. How it is used is your responsibility.
Why do these tools ask for a private key when the rest of J Tools does not? The relay hops sign with the generated wallet keys and, for SPL and multi-pair runs, with the source keys you provide, so the flow reads raw keys instead of prompting your wallet on every hop. That is why the Phantom risk on these tools is rated low: your extension is not in the signing loop. It is also why you should only ever use disposable wallets here.
What should I do with a wallet after I have pasted its key? Treat it as burned. Move the funds out and retire the wallet from anything sensitive. Pasting a key into any web page widens its exposure, so the safe habit is to use fresh wallets for relay runs and rotate them afterward. Keep the recovery file offline in case funds get stranded mid-run.
Does J Tools store my keys or the relay wallets? No. The relay wallets are generated in your browser session and their keys go straight into the recovery file you download. A private key never reaches our servers in any form. If you lose that file, funds stranded in an intermediate wallet cannot be recovered.
## Related {% content-ref url="/pages/nHTziE15NKeVLAQMnxv5" %} [Relay Transfer](/tools/wallets/relay-transfer.md) {% endcontent-ref %} {% content-ref url="/pages/uVoEslmUoeflpLu9kq7x" %} [Multi to Multi Relay](/tools/wallets/multi-to-multi-relay.md) {% endcontent-ref %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.j.tools/concepts/privacy-and-responsible-use.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.