Read-only by default.

• Cashboard never asks for a seed phrase or private key.
• Cashboard itself never builds, signs or sends a transaction. Portfolio, Net worth, Perps positions, Paper trading, alerts and the data widgets only read public data.
• Wallet selection in the Portfolio widget is optional. It asks your wallet for a public address, and for an EVM wallet the current network, and nothing else.
• Checkout for lifetime access does not connect to your wallet or ask for a signature. You enter the public address you will pay from and send the payment yourself.
• Swap forms route through Jupiter on Solana and LI.FI on Base or Robinhood Chain. Your wallet approves every transaction. Board Agent only builds and watches workspaces; it never initiates a trade. Paper trading is a local simulation, and broker or exchange credentials are not accepted.

On the web build, the Jupiter swap widget loads Jupiter's own plugin from plugin.jup.ag. Jupiter builds the swap and your wallet extension asks you to sign it, so a signature prompt on this site can come from that widget. The plugin loads when a Jupiter swap widget is on the board you open, including one added by a Buy button.

Cashboard never sees a private key and never holds funds. Jupiter's form shows its routing and fees before you confirm, and the web build is configured to add a Cashboard referral fee to these swaps, 0.5% as of October 2026. The desktop app does not run the plugin and opens jup.ag in your browser instead. The Limit and DCA links in the widget header also open jup.ag.

The Base and Robinhood Chain swap widgets load LI.FI's form on the web. The desktop app opens the same selection on Jumper in your browser. You choose the route, review fees and slippage, and approve each transaction in your own EVM wallet. An optional Cashboard fee appears in the route when configured; it is absent by default.

The web build's content security policy allows scripts only from cashboard.live and plugin.jup.ag, plus one fixed start-up script. Page analytics run from cashboard.live itself, and the desktop app has none. Token logos and event images load from a fixed list of image hosts.

The server, not the browser, chooses the recipient, token contract, exact amount and expiry of every payment request. A payment is accepted only from the wallet you named, on the route you chose, in the exact amount, after the required confirmations and finality. A download link expires after 5 minutes and works once.

Board layout and manual portfolio amounts stay on the device: in browser storage on the web and in a local database on desktop. Desktop provider connections are encrypted with the operating system's secure storage, are never shown again after saving and never reach widgets. Cashboard refuses to save them when the system offers only basic text storage. The web build cannot store keys. Embedded desktop apps use isolated persistent sessions instead of sharing one global session; deleting a web widget clears its stored session.

Financial values include their source and observation time where available. Cashboard does not replace missing live data with invented values. Market data may still be delayed, incomplete or unavailable.

Cashboard has no separate security address. Write to the support address, contact@cashboard.live, and keep sensitive details out of public channels. Never include seed phrases, private keys or live API secrets in a report.