Data & privacy.

Your wallet signs. Your keys stay with it.

Connecting shares your selected public wallet address and network. Sign-in sends a signed message to StonksApp so the server can verify wallet control. That message identifies the app, network and request deadline; it does not authorize a transaction.

The app keeps its login token in this tab’s memory. The server stores a hash of that token, your wallet address and a short session expiry. Login and recovery message signatures are checked, not saved as account records. Transactions require separate wallet signatures.

Requests leave an app record.

StonksApp stores your wallet account, transaction requests, parsed amounts and destinations, quotes, statuses and timestamps. For an accepted approval, it stores the signed transaction and its signature to submit and check that same transaction. Account and transaction actions also create audit records.

Saved contacts contain the nickname and full wallet address you enter. They are stored under your account; saving one does not publish it on Solana or notify the recipient. A request keeps its own destination and saved-label snapshot even if you remove the contact later.

Chat commands are processed by the server. The visible conversation stays in this tab’s memory, while transaction requests and the responses needed to recognize repeated requests remain on the server.

A small reference helps recover an interrupted approval.

Before submitting a signed transaction, the app saves its request reference and a timestamp in browser local storage. A hashed scope ties these records to the app, account, wallet and network. The records contain no login token, signed transaction, amount, recipient or private keys.

These references survive reloads and sign-out. They are removed when the app observes a confirmed, failed or cancelled result. Keep this browser’s site data while a request is pending or uncertain. Reconnecting checks the original request; it never automatically resubmits an approval.

The current wallet connection keeps WalletConnect session data in memory too. StonksApp does not add advertising trackers or an analytics SDK. This does not control data handled by your wallet, hosting services or other providers.

Some requests go to connected services.

Solana RPC providers receive the public addresses and transaction data needed to read balances, simulate transactions, broadcast approvals and check results. Jupiter receives token, amount and route details, including the wallet address when building a swap. StonkFun discovery reads its public token catalog.

If you choose WalletConnect, pairing and signing requests use Reown’s connection infrastructure and your chosen wallet. The mobile wallet picker also requests a supported-wallet directory. These services, and the infrastructure serving this website, receive connection information such as IP addresses. Their data handling is separate from StonksApp’s application storage.

Standard commands use the app’s parser. If an optional AI parser is configured, unrecognized command text is sent to that provider. Do not put confidential information in a command. A parser cannot approve a transaction for you.

Solana transactions are public.

Submitted on-chain transactions can expose wallet addresses, token movements, amounts and signatures to anyone inspecting the blockchain. Explorer links open an external service. A saved nickname is an app label, not something the transfer needs to put on-chain.

StonksApp cannot erase blockchain records or reverse a confirmed transfer. Removing app data does not remove public transaction history.

Signing out is different from deleting records.

Sign out clears the local login and asks the server and wallet to end the connection. If the server cannot be reached, its session expires within 15 minutes. Sign-out does not cancel an accepted transaction, delete app history or clear pending recovery references.

You can remove saved contacts in the app. Existing transaction snapshots, audit records and backup copies are separate. There is currently no self-service account or transaction-history deletion, and transaction and audit records are not automatically purged.

For an approval that needs checking, follow the steps in wallet help before clearing browser data.