What the extension stores, and where
Your paper wallet, settings, trade journal, session replays, verification chain, X-Ray ledger, and (if you enable them) capture frames and screen recordings are kept in chrome.storage.local — local storage inside your Chrome profile. Nothing is uploaded by the extension, ever. Using the extension requires no account and no sign-up.
If you add an AI API key for the optional coaching feature, it is stored locally and sent only to the endpoint you yourself configured.
Network requests the extension makes
Every network call the extension can make, exhaustively:
- Public price APIs (Dexscreener, Jupiter) — to price the coins you trade.
- Public Solana RPC — for on-chain price anchoring, or a private RPC if you configure one.
- An AI endpoint you configure (optional) — coaching prompts go only to the OpenAI-compatible endpoint you typed in, with your own key.
- X's public oEmbed endpoint (optional, only when hover preview cards are enabled) — called with
dnt=1, no cookies and no login, only for post links you hover on a trading site.
These requests carry only what the feature needs. None of them carry your journal, your trades, or anything identifying you to us. The extension never contacts the leaderboard server — see the next section for the one way your record can reach it, and it is not the extension sending it.
The leaderboard (optional, website-only)
papertrench.com offers an optional leaderboard operated on our own server. Nothing about it is automatic:
- It only receives what you submit. Your record reaches the server in exactly two ways: you upload the file you exported from the dashboard, or you click Sync on the leaderboard page. Sync asks the extension for your record; the extension answers only if you enabled Site sync in the dashboard (off by default), only for papertrench.com, and it never initiates anything on its own.
- What a submission contains: your committed fill chain (token mints, sides, quantities, prices, timestamps, hashes), your declared starting bankroll, and your claimed summary stats. That is the whole payload — no journal text, no theses, no replays, no recordings, no browsing data.
- Signing in uses X (Twitter) OAuth. We store your X account id, handle, display name, and avatar URL — nothing else from your X account, and no posting rights are requested.
- What becomes public: your handle, avatar, verification status, and the statistics derived from your submitted chain appear on public standings and your public profile page.
- Deletion is self-serve: "delete my data" on the leaderboard page removes your account, record, submissions, and sprint history from the server immediately. Your local extension data is never touched by this — it was never on the server's side to begin with.
The X-Ray and Instant X features
Both are opt-in and off by default. X-Ray builds its account-intel card from data the X page itself already loaded in your browser session; what it keeps is a local digest (account field snapshots, post ids and dates, contract addresses), stored on your machine. Raw post text never leaves the page context, and nothing is sent anywhere. Instant X links keep a muted background viewer tab and route your own clicks into it; they read nothing from your X session and send nothing anywhere. The full technical description is in the public permissions audit.
What we collect about you
From the extension: nothing — no telemetry, no analytics, no way to receive it. From the website: only what the leaderboard section above describes, only if you choose to use it. We do not sell or share any of it, and there is no advertising or third-party analytics on either.
Deleting your data
Local data is yours and stays local: removing the extension deletes everything it stored, and you can export or reset from the dashboard at any time. Leaderboard data (if you ever submitted) is removed with the "delete my data" control on the leaderboard page.
Changes to this policy
If a future version ever changes any of the above, this page will say so before that version ships, and the change will be visible in the open-source history like everything else.
Contact
Questions: open an issue on GitHub.