Privacy

What the Ponspree extension sends, and what never leaves your browser.

Ponspree has no accounts, no analytics and no trackers. Nothing you do is tied to an identity, because there is no identity to tie it to. We never ask for an email address, we set no cookie of our own, and there is no advertising of any kind.

One exception, and it is on this website rather than in the extension. The front page of ponspree.com plays a short video, and that video is hosted by YouTube. It is embedded through youtube-nocookie.com, which is Google's own version of the player that does not build an advertising profile from it - but it is still Google's player, and loading it tells Google someone visited the page. Nothing else on either the site or the extension does that. If you would rather it did not, a content blocker stops it and the rest of the page works exactly as before.

What never leaves your browser

The extension makes a wallet for you and holds its private key locally, encrypted with the password you set. That key is the whole product, and it is the thing we are most careful about.

Your private keys. Encrypted with your password and stored in your own browser profile. They are never transmitted anywhere, to us or to anyone else, under any circumstance. We could not read them if we wanted to.
Your password. Never stored and never sent. It is used to derive an encryption key and then discarded.
Your settings. Kept in your browser.
Your launch history. Kept in your browser.
Your optional API keys for Pinata and Anthropic, if you add them. Neither is needed - both services work without one - and if you do add them they are encrypted alongside your wallet keys and used only to call those services directly from your browser.

What is sent, and when

Four things leave your browser, each for a stated reason and only when you act.

The post you are launching from, to name the token. When you press Insta Launch or Suggest with AI, the post's text, the author's handle and the post's image are sent to our naming service at api.ponspree.com, which passes them to Anthropic's API to generate a name and ticker. They are used for that one request and not stored. If you fill the name in yourself, none of this is sent at all.
A landed launch, for the public gallery. After a token is created, its contract address, name, ticker, image URL and pairing are sent to api.ponspree.com so it can appear on the Launches page. All of that is already written into the token on-chain and public to everyone. Your wallet address is not sent, and neither is the post it came from.
Transactions, to the blockchain. Launching, collecting fees and withdrawing are transactions on Robinhood Chain, sent through its public RPC at rpc.mainnet.chain.robinhood.com. That node sees your wallet address and what you signed, as any blockchain node does. Everything on a public chain is public by design.
The token's picture, so it outlives the post. A token's logo is a link written on-chain at launch, and that field can never be edited afterwards - so pointing it at the post's own image means the picture dies the day the post does. Every launch therefore sends its picture, whether that is the post's own image or one you uploaded, to api.ponspree.com, which stores a permanent copy on IPFS through Pinata and returns the address it now lives at. Only the picture is sent. If you have added a Pinata key of your own in settings, your browser uses that instead and the copy lands in your account rather than ours.

Two things we read, and nothing is sent with them

The price of ETH, from CoinGecko, so costs can be shown in dollars.
Logos for the assets you can pair with, from Parqet, looked up by ticker.

Both are plain requests for public information. Nothing about you or your wallet goes with them, and both are made by the extension's background worker rather than by the page you are looking at.

What we do not do

We do not sell or share data with anyone. There is nothing to sell.
We do not track you across the web. The extension only runs on x.com and twitter.com, and only to put two buttons on posts.
We do not read your posts, your timeline or your messages. The extension reads a post only at the moment you press a button on it, and only that post.
We do not use your data to train anything.

The permissions it asks for

storage to keep your encrypted wallet, your settings and your launch history on your own machine.
x.com and twitter.com to add the launch buttons and read the post you launch from.
pbs.twimg.com to fetch the post's image so it can become the token's picture.
rpc.mainnet.chain.robinhood.com to read balances and send your transactions.
api.ponspree.com for naming and the public launches gallery.
api.coingecko.com for the price of ETH.
assets.parqet.com for the pair logos.
api.pinata.cloud only if you add a Pinata key of your own; otherwise the picture is stored through our service instead.

Deleting everything

Removing the extension deletes your wallet, your settings and your history with it, so export your key first if the wallet holds anything. Settings has a Back up my key button for exactly that. Tokens already launched stay on the blockchain and in the public gallery, because neither is ours to erase.

Getting in touch

Questions about any of this go to driz0x0@gmail.com. If this policy changes, the date below changes with it.

Last updated 15 September 2026.