Privacy Notice
v1.2 · updated 2026-09-30
1. What this notice covers
POO.MEME has no accounts. It doesn't ask for a name or an email, and it uses no analytics or tracking cookies. Pictures you choose to upload are optional, and once uploaded they are public.
POO.MEME is a non-custodial website for smart contracts on Robinhood Chain. Most of what the Interface does — creating a token, buying or selling, collecting a token's own fees — happens through your own wallet signing a transaction directly with a smart contract; POO.MEME's server is not part of that transaction and does not see your private keys.
This notice covers the two places personal data does reach us: our server, and your browser's own local storage.
2. What our server processes
| Data | Why | Source |
|---|---|---|
| Wallet addresses | To show who created a token, and who trades and holds it; to check who may bind an uploaded picture to a token | Read from the blockchain itself, or supplied by you (e.g., signing an upload) |
| Module handles (short public names) | To resolve /@handle to the module family that declares it | Read from the blockchain |
| Uploaded images (token pictures and banners) | To display a token's chosen picture and banner | Uploaded by you, stored content-addressed (keyed by the file's own hash); image metadata (EXIF and similar) is stripped before storage |
| A hashed, truncated client identifier, kept in memory only | To rate-limit picture uploads and reduce abuse | Derived from the request's forwarded-IP header (SHA-256, truncated to 16 hex characters); not written to disk or to the database, and cleared as it ages out of the rate-limit window |
We do not collect your name, email address, physical address, or any government ID. We do not require an account or a sign-up to use the Interface.
3. What your browser stores, and does not send us
Your browser keeps a few small, functional items in local storage, which stay on your device and are never transmitted to our server:
- That you've accepted the Terms of Use, so you are not asked again;
- An in-progress token or launch creation draft, so you do not lose it if you navigate away;
- Your slippage setting;
- Your wallet connection state (which wallet you last connected, so it can reconnect).
We do not run analytics, advertising or tracking scripts of any kind, and the Interface sets no tracking or advertising cookies. If this changes in the future, this notice and, where the law requires it, a consent mechanism will be updated first.
4. Third parties who see your data
Because the Interface is non-custodial and runs largely in your browser, several parties you interact with directly see data we do not control:
- The blockchain itself. Every transaction you sign — creating a token, buying or selling, collecting a token's own fees — is public, permanent, and visible to anyone, on Robinhood Chain.
- RPC providers. Your browser sends read and write requests directly to public blockchain RPC endpoints to read chain state and submit your transactions. Those providers see your IP address and the requests you make; POO.MEME does not route this traffic through our own server.
- Your wallet and WalletConnect. Connecting a wallet may involve a relay operated by WalletConnect (Reown), which can see connection metadata.
- Cloudflare. The Interface sits behind Cloudflare, our edge and CDN provider. Cloudflare sees the IP address of every request to our site as part of operating that network, under its own privacy terms.
- Our storage provider. Uploaded images are stored on IPFS, a public peer-to-peer network, and pinned there through QuickNode; in local development only, uploads fall back to a developer's own disk. Anyone who knows an image's content identifier can fetch it, and an IPFS node that has fetched it may keep a copy of its own.
We do not sell personal data, and we do not share it with anyone for their own marketing purposes.
5. Retention
- Wallet addresses, handles and uploaded-image bindings are kept for as long as the underlying token, module or picture is in active use, and cleaned up when no longer referenced (an unreferenced uploaded image is unpinned on a periodic sweep). An image a launch wrote into its token on the blockchain stays pinned for as long as the token names it, which is permanently. Unpinning removes our copy; it cannot recall a copy another IPFS node already keeps.
- The hashed client identifier used for upload rate-limiting is kept in memory only, for at most 24 hours, and is never persisted to disk or database.
6. Your rights and contact
Because most data we hold is either public blockchain data or minimal operational data with no account system, a request to access, correct or delete data is answered by pointing to what is, and is not, held under §2. Send that request, or any other question about this notice, to [email protected].
7. Changes
We may update this notice. Each version carries a version number and date at the top.