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 or tracking cookies. No cross-site tracking.

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 Solana 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. What is stored in your browser

A short list of tokens you recently checked, kept in your browser's local storage so the “Recent checks” row works. It never leaves your device and you can clear it by clearing site data.

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.

5. Third parties that see something

• Jupiter — receives token addresses and amounts to quote and build 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 on-chain reads and to broadcast your signed transactions.
• DexScreener — receives token addresses to fetch pool and liquidity data.
• 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.

6. Analytics and monitoring

Pewcake keeps first-party usage counts on its own server: which features are used and how often (a check run, a swap started, a blocked trade). These are counters per event and hour with no IP address, wallet address, cookie or user identifier attached.

Pewcake also uses Google Analytics 4 to understand traffic: pages viewed, approximate country, device type and how visitors arrived. Google sets cookies (such as _ga) to tell returning browsers apart and 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 or by blocking third-party scripts.

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.