Cookie Chat — Privacy Policy
What Cookie Chat stores, why, and for how long
Last updated: 5 October 2026
1. Who we are
This policy covers cookiechat.net and its chat terminal (the "Service"). Cookie Chat is an official Cookie Chain ecosystem app operated by the Cookie Chat team ("we", "us"), and we decide how the data described here is used — in the language of the EU General Data Protection Regulation (GDPR), we are its controller.
Contact for anything in this policy: cookiechat.info@yahoo.com.
2. The short version
- No accounts. No sign-up, no names, no email addresses, no passwords.
- No keys. We never receive your seed phrase or private key and cannot sign anything for you.
- No analytics, no ads, no tracking cookies. We do not sell or rent data to anyone.
- A random identifier in one cookie ties your conversations to your browser.
- Your questions and the answers are stored so your history works, until you delete them.
- Questions are sent to an AI model provider to write the answer — without your identifier or IP address attached.
- Anything that happens on a blockchain is public and permanent, and is not ours to erase.
3. What we collect
A device identifier. The first time you send a question, the Service sets a
cookie named sid holding a random identifier. It is not derived from you or your
device; it only lets the Service know that a later visit comes from the same
browser.
Your conversations. The questions you type and the answers the Service gives,
including any wallet address, token or other detail you put in a question, stored
against your sid.
Ratings. If you rate an answer up or down, that vote, stored against your
sid.
Visits. One record per browser per day (the sid and the date), so we can
count how many people use the Service.
Wallet addresses. If you connect a wallet, its public address is sent to the Service to read your balance and the tier it opens; on higher tiers the daily allowance is counted against that address. We never receive a key, and connecting requires no signature.
Transaction records. When you sign an action prepared by a card, the Service records the transaction's signature, type, outcome, chain and an approximate value in US dollars, to count what the Service is used for. The transaction itself is already public on its blockchain.
Promotion records. If you take part in an airdrop or a matching promotion, we keep what that promotion needs to pay you once and only once: your wallet address, the X handle you took part with, the purchases or posts that made you eligible, the payout and its transaction, and a one-way hash of your IP address (not the address itself) to spot duplicate claims.
Network data. Your IP address is used to apply rate limits, inside short-lived counters that are deleted automatically once their time window has passed. Our hosting provider processes IP addresses and basic request data to deliver and protect the Service (see section 6).
Messages you send us. If you email us, we keep the email and your address to reply.
4. Why we use it, and our legal basis
We do not use your data for automated decisions that have legal or similarly significant effects on you, and we do not build profiles for advertising.
5. The AI model
To write an answer, the Service sends the model your question, the recent turns
of the same conversation, and the data it fetched for the answer. It does not
attach your sid, your IP address or your connected wallet; a wallet address
reaches the model only when it is part of your question (as with "View my
holdings") or of the data the answer is about. The model runs through
OpenRouter, which routes the request to Groq; both process it under their
own terms. Please do not put sensitive personal information into a question.
6. Who else processes data
We use a small number of service providers, each only for what the Service needs:
- Cloudflare — hosting, the database and storage that hold the data above, and network protection. Cloudflare processes IP addresses and request data to serve the site.
- OpenRouter and Groq — the AI model that writes answers (section 5).
- Data providers — to build cards the Service queries public sources such as
the Cookie Chain RPC and CookieScan explorer, CoinGecko, DexScreener, DefiLlama
and Solana RPC providers (for example Helius). Those queries can contain a
wallet address or token you asked about, but not your
sidor IP address. - Image hosts — token logos and NFT images are loaded by your browser through wsrv.nl and IPFS gateways (Lighthouse, Pinata), which see your IP address the way any website you load an image from does.
- Your wallet — wallet software such as Nightly is a separate product with its own privacy policy. When you sign a transaction it is broadcast to the public network.
We may disclose data if the law requires it, to protect the Service or its users from fraud or abuse, or as part of a transfer of the Service to a new operator, who would remain bound by this policy.
Some of these providers are based outside the European Economic Area, including in the United States. Where data leaves the EEA, it does so under the safeguards the GDPR provides for, such as the European Commission's standard contractual clauses or an adequacy decision.
7. Blockchain data is public
Wallet addresses, balances and transactions on Cookie Chain and Solana are public by design and can be read by anyone. Anything you sign is recorded permanently by the network. We cannot change or delete it, and the rights in section 10 do not reach it.
8. How long we keep it
If you clear the sid cookie, conversations stored against it can no longer be
opened from your browser.
9. Cookies and local storage
The Service uses one cookie and a few local storage entries, all needed for it to work. None is used for tracking or advertising, so there is no consent banner.
Local storage stays in your browser and is never sent to us.
10. Your rights
Depending on where you live — and in any case under the GDPR if you are in the EU or EEA — you have the right to access the data we hold about you, to have it corrected or deleted, to restrict or object to its processing, and to receive it in a portable form. You can delete any conversation yourself from the sidebar at any time.
For everything else, email cookiechat.info@yahoo.com. Because there are no
accounts, we can only find data linked to a browser or a wallet: tell us your
wallet address, or the sid value from your browser's cookies, and we may ask you
to prove control of a wallet by signing a message (never a transaction). We will
answer within one month.
You also have the right to complain to a data protection authority, in particular in the country where you live or work.
11. Security
Data is stored with our hosting provider, encrypted in transit, and access is
limited to what running the Service requires. The sid cookie cannot be read by
scripts on the page. No system is perfectly secure; if a breach affecting your data
happens, we will deal with it as the law requires.
12. Children
The Service is not intended for anyone under 18, and we do not knowingly collect data from children. If you believe a child has used it, contact us and we will delete what we can find.
13. Changes to this policy
We may update this policy as the Service changes. The date at the top shows when it last changed, and significant changes will be made visible on the Service.
14. Contact
cookiechat.info@yahoo.com — for privacy requests, questions about this policy, or anything else in it. See also the Terms of Service and the Risk Disclosure.