Privacy.

1. What we do not collect

No names, emails, passwords, or payment details. No accounts exist. We never receive your private keys or seed phrase; signing happens inside your wallet.

No advertising cookies. No cross-site tracking. No fingerprinting.

2. What the site processes to work

• Your wallet's public address, when you connect it, to show balances, run the portfolio scan, offer rent reclaim, and build transactions. Public addresses are public information on the blockchain.
• Token addresses you check, so the report can be built. Reports are cached on the server for 45 seconds and are not tied to you.
• Your IP address, transiently, for rate limiting. Limits are counted in server memory per minute and are not written to disk or kept.
• Standard server request logs (path, status, timing), retained briefly for operations and debugging.

3. Cookies and what is stored in your browser

Pewcake itself sets no cookies. A few things are kept in your browser's local storage so the site works between page loads: the tokens you recently checked (the “Recent checks” row), your recent Robinhood Chain swaps (the activity list in the swap card), your cookie choice, and, if you connect a phone wallet through WalletConnect, that session so you do not have to scan again. None of it leaves your device, none of it identifies you to us, and clearing site data removes all of it.

Google Analytics is the one non-essential thing on the site. It does not load until you choose “Allow analytics” in the banner, and you can change your mind at any time with “Cookie settings” in the footer. When allowed, Google sets its own cookies (such as _ga) to tell returning browsers apart. Choosing “Essential only” keeps every feature working.

Your wallet extension may remember that you connected to this site; that is controlled by the wallet, not by Pewcake.

4. What is stored on our server

Snapshots of tokens as they graduate from launchpads — the token's address, our verdict and findings at first sight, and liquidity over time — to power the public Caught wall. These are about tokens, not people, and contain no wallet addresses of visitors.

First-party usage counts: which features are used and how often (a check run, a swap quoted, a blocked trade). These are daily counters per event with no IP address, wallet address, cookie or user identifier attached.

5. Third parties that see something

• Jupiter — receives token addresses and amounts to quote and build Solana swaps; receives your public address in the swap-build request because the transaction is built for it.
• Helius (RPC) — receives token and public addresses for Solana on-chain reads and to broadcast your signed transactions.
• DexScreener and GeckoTerminal — receive token addresses to fetch pool, price and liquidity data, on both chains.
• PumpPortal — your browser opens a direct WebSocket to receive the migration feed; PumpPortal sees your IP like any site you connect to.
• IPFS gateways and image hosts — reached from our server, not your browser, to fetch token icons.
• Robinhood Chain — the chain's public RPC endpoints, GoPlus (token security data) and the Blockscout explorer receive token addresses for checks; your wallet address is read for balances and allowances. Uniswap contracts and launchpad curves execute the swaps you sign, with your address in the transaction, as on any chain.
• WalletConnect — if you connect a phone wallet, the WalletConnect relay (run by Reown) carries the encrypted session between this site and your wallet app and sees your IP like any relay. Nothing about your trades is readable by it.
• Google Analytics — only after you allow it: pages viewed, approximate country, device type and how you arrived. Google receives your IP address to derive a coarse location; Google Analytics 4 does not log or store that IP. Wallet addresses, token addresses you check and swap amounts are never sent to Google. You can opt out with Google's browser add-on, by blocking third-party scripts, or with “Cookie settings” in the footer.

6. Your choices

• Cookie settings, in the footer of every page, turns analytics on or off.
• Clearing this site's data in your browser removes everything listed in section 3.
• Disconnecting your wallet forgets the connection immediately; a WalletConnect session is closed on the relay as well.
• Nothing on our server is tied to you, so there is nothing to request or delete there; if you believe otherwise, write to the contact at the top of this page.

7. Children

Pewcake is not directed at anyone under 18.

8. Changes and contact

Changes to this page update the effective date at the top. Questions go to the contact listed there.