Your watchlist and wallet
Browser watchlists and scenario drafts stay on your device. Signing in lets you keep a separate synced watchlist; importing browser entries is your choice. Private labels are not included in public wallet pages or usage events.
Paperdash does not store wallet private keys. Connecting or signing in does not authorize trades or withdrawals. You can remove saved entries in Watchlist.
External-wallet connections use your wallet provider and services such as WalletConnect, which may process connection and network metadata under their own privacy policies. You approve signature requests in your wallet; Paperdash does not import or take custody of your wallet’s private key. See the WalletConnect privacy notice and Reown privacy policy. Google Analytics consent is separate from these functional wallet connection requests.
Public wallet research
Paperdash archives public Papertrade account and event reports, including wallet addresses, amounts and source transactions, for the Traders and wallet pages. This product data is separate from measurement of visits to Paperdash.
Arcade rounds
When you play in the arcade, Paperdash keeps each round with your account: the game, its fairness seeds, the Papertrade orders and positions it opened, and the result copied from Papertrade. The arcade board shows only players who turn it on, with their wallet, Papertrade username, rounds and return; turning it off removes you. Table limits you set are kept with your account.
Trading keys
When you enable trading, Paperdash creates a trading key for your account at Privy, a key custody provider, and your wallet registers it on Papertrade with one signature. Privy holds the key; Paperdash stores its address, your wallet, its expiry and when it was last used, and asks Privy to sign only the orders you confirm on the website, in the arcade or in Telegram. Disabling trading stops Paperdash signing at once; the key's registration on Papertrade lasts until it expires or your wallet revokes it.
Live market charts
Tick charts connect directly to Hyperliquid’s public price stream. Hyperliquid receives the selected market and normal connection information, such as your IP address. Paperdash sends no wallet address, private labels or account details through this connection. The stream pauses when the page is hidden; tick history stays in memory.
Basic usage counts
We count page categories, successful watchlist saves, sharing, wallet searches, scenario comparisons, example loads and Telegram opens. Events contain only a fixed event name and category. They do not contain wallet addresses, search text, private labels, URLs, referrers, scenario inputs or financial amounts.
These counts have no persistent anonymous tracking ID and do not measure unique anonymous visitors. If you are signed in, we keep your verified account ID and UTC attendance date for eight calendar dates to measure seven-day return visits. Aggregate counts are retained for ninety days. We respect Do Not Track and Global Privacy Control for usage measurement.
Optional Google Analytics
Google Analytics is optional and requires your permission.
When enabled, Google’s tag loads only after you allow it, on a limited set of public pages. It uses analytics cookies to measure public-page visits and basic actions. Google receives technical information such as your IP address and browser information.
Our Google events use fixed page names and canonical public URLs without query strings. Wallet profiles, trade receipts, account pages and Telegram ownership-proof pages are excluded. We do not send account IDs, wallet addresses, labels, linking tokens or financial values. Advertising storage, advertising personalization and Google Signals are disabled.
Your Google Analytics choice is saved on this device for 180 days. When Google Analytics is configured, the footer’s Analytics settings lets you change it. Declining removes the Google Analytics cookies managed by Paperdash and stops new Google measurement. Public-page events already collected with your permission may finish transmitting after you decline or move to an excluded page. Browser privacy signals override an allowance. Basic usage counts remain separate and also respect those browser signals.
Hosting and security logs
Hosting, database and security providers may process technical request logs separately. Our usage-count tables do not store IP addresses or user agents. Rate limiting uses short-lived, in-memory identifiers rather than persistent visitor profiles.