Use the private account with care

A shield moves SOL, USDC, or USDT out of the connected wallet and into a private balance. A private send later pays any Solana address from that balance. The deposit and the withdrawal are separate events. Someone watching the chain can see that money went in and that money came out. They cannot read a direct pointer from the depositing wallet inside the withdrawal.

You can shield, read a private balance after signing in, send to a recipient, and review receipts saved on this device.

What stays visible is the deposit from your wallet, the withdrawal that pays the recipient, and the amounts and times of both. Those last two are enough to guess a link when they match too closely.

One wallet is one private account. The same wallet has to be used every time you want to see or spend what it shielded. Connecting a different wallet opens a different account, even on the same browser.

Use Connect in the header. A browser wallet works. If you sign in without one, a wallet can be created for you. After it connects, confirm it is on Solana mainnet and that it holds a little SOL. Network fees on deposits are paid from that wallet.

Disconnecting does not delete private notes. It only ends the connection. The notes remain available the next time that same wallet signs in.

Opening the account asks the wallet to sign a fixed message: “Privacy Money account sign in”. That signature derives the key for your private notes. SOLCLOAK saves it in this browser for that wallet address. It is not sent anywhere, and it does not spend funds.

Wallets that sign this message the same way each time can reopen the account. A wallet that returns a different signature cannot read notes created with the first one. Those funds stay where they are. Do not experiment with a second wallet if you already have a balance.

End this session from the balance header when you want the signature removed from this browser. Sign again with the same wallet to reopen the account. Clearing site data has the same effect. Do not switch wallets while a signature or a shield is in progress.

A shield moves an amount from the connected wallet into the private balance for that asset. Your wallet signs the deposit and pays the network fee. There is no separate deposit charge.

Keep a small SOL balance in the wallet. Choosing the available amount for SOL leaves 0.01 SOL behind for the network fee. A USDC or USDT shield still needs a little SOL in the wallet for that fee.

A deposit can be declined if the source wallet is flagged. The funds stay in the wallet, and the app shows the failure. The first shield in a session can take longer while this browser prepares. Leave the tab open until the receipt appears.

The private balance is what this wallet can read. The wallet balance is what the chain reports for the connected address. They are different numbers. Shielding reduces the wallet balance and increases the private balance. Sending does the reverse for the recipient, not for this wallet.

Each asset is separate. Shielding SOL does not create a USDC balance. If a successful shield is missing from the private figure, refresh. A new note can take a moment to appear.

Balances are available only after the signature step. Before that, SOLCLOAK can show the wallet but not the private notes.

A private send spends the private balance and pays a recipient. Enter the gross amount. The fee is taken from that amount, and the recipient receives the remainder. The form shows both numbers before you confirm.

You do not sign the outgoing transfer. A proof is built in this browser, then the withdrawal is submitted for you. That is why the withdrawal is not signed by the wallet that deposited.

If the private balance cannot cover the full request, a partial amount may be sent. The receipt says so. Amounts under the live minimum are blocked. Recent floors are about 0.01 SOL, 2 USDC, and 2 USDT. Trust the minimum on the form, which follows the current schedule.

Keep the tab open. Building the proof can take up to a minute. Closing the tab interrupts it.

This breaks the direct on-chain pointer. It does not make a transfer impossible to guess.

• Wait before sending. A withdrawal minutes after a matching deposit is easier to pair.
• Prefer ordinary amounts over a figure that appears only once.
• Send to a fresh address, then move funds onward if you need to use them in public.
• Do not announce the amount, the time, or the recipient alongside the deposit.

Activity in the app is stored locally for this wallet. Anyone with this browser profile can read those receipts. The private balance itself still requires the wallet signature. Clearing activity does not affect the funds.

• Signature cancelled. Nothing was spent. Sign again when you are ready.
• The wallet changed mid-flow. Refresh and continue with one wallet.
• A deposit was declined. Funds remain in the wallet. A flagged source can be refused.
• The tab was closed while a proof was building. Start again. Wait for a receipt or a balance change before assuming the result.
• A successful shield is missing from the private balance. Refresh. It can take a moment to appear.
• An older balance will not open. You are likely on a different wallet, or this wallet is signing the message differently than it did before.