COOK is built to know as little about you as it can. This policy covers the COOK app (the Solana dApp Store and Google Play versions), COOK's server (the service that runs COOK's AI and hosts coin files) and the cookkitchen.fun website. Where something applies only to COOK 2.0 or later, it says so.
| What | Why, and how long it is kept |
|---|---|
| Your prompts, characters, captions and photos you check | Sent to Cloudflare Workers AI to make your art and check photos. In COOK 2.0 and later, your words and the character's name, lore and captions may also go through OpenRouter to Google and OpenAI models that write ideas, captions and posts, with no device ID, IP address or wallet (section 3). Not stored by COOK unless you report something or launch the coin. Logos from the older logo service are the exception (section 10). |
| Pictures COOK draws (COOK 2.0 and later) | Scenes and icons may go through OpenRouter to a Google model that checks them for logos, lettering and drawing mistakes (section 3). Your own photos and stickers are not sent there. |
| Names, tickers and links you type | Checked by COOK's server against the Kitchen rules; a coin name is also looked up on Wikidata to spot real people's names (COOK 2.0 and later). In COOK 2.0 and later, a name and ticker that pass the rules may also go through OpenRouter to a Google model that checks them for slurs and for crude, sexual or hateful words and price promises, with no device ID, IP address or wallet (section 3). COOK keeps only the answer, under a one-way hash, for up to 7 days. Not stored unless you report something or launch the coin. |
| A random device ID (COOK 2.0 and later) | Counts daily AI use and launches on this phone. Those daily counts are deleted after 7 days. |
| Your IP address | Used briefly for rate limits. Only a one-way hash that changes daily is kept, in daily counters deleted after 7 days. |
| Reports you send | Reviewed against the rules. The report image is deleted after 180 days; the rest is kept as a moderation record, with no device ID, wallet address or IP address. |
| Teaser links, if your version has them | The device ID is removed when the link expires; the link and its teaser image are deleted 7 days after that. |
| A coin you launch: name, ticker, logo, description, X handle and links | Published so wallets and explorers can show the coin. Public on Solana and at a fixed public address. |
| A coin's character kit (COOK 2.0 and later) | Saved with the coin when you serve it: the character sheet, lore and stickers, and the icon for Jupiter Studio and Bags coins. Public, like the coin. A one-way hash of the saving phone's device ID is kept with it for 7 days (section 7). |
| Views of a coin's web page | Counted with the share channel and a one-way code made from your IP address and browser. The key that makes the code is deleted about an hour after the day ends (section 9). |
| Your wallet address | Used to build the transactions you approve and to read your coins and fees. Public on Solana; COOK keeps no account for it. |
| Daily totals and launch outcome records | Tell us whether COOK works. No device ID, wallet address or coin text. |
COOK has no sign-up and no user accounts. It doesn't ask for your name, email address, phone number or any government ID. The app has no ads and no analytics or advertising SDKs, and COOK doesn't sell personal data or share it for advertising.
Memes, characters and stickers you keep in My Kitchen are saved in the app's own storage on your phone. The app's secure storage holds the wallets you connected (public addresses and the wallet names your wallet app reports; no keys), the device ID, the date you agreed to the terms, the creators whose coins you hid, and a launch that is still confirming. Nothing you make is public until you share it or launch it. Deleting a meme, or uninstalling the app, removes these from your phone.
When you cook, the app sends your words, your chaos and style picks, and the character COOK made to COOK's server, which asks Cloudflare Workers AI to draw the art. In COOK 2.0 and later, the character, captions and post drafts are written through OpenRouter first (below). Names, tickers and links you type are sent to COOK's server to check them against the Kitchen rules. In COOK 2.0 and later, when a name and ticker pass those rules, COOK's server may also send them (and the ticker as you typed it, if it was longer than the saved one) through OpenRouter to a Google model that checks them for slurs and for crude, sexual or hateful words and price promises. The request carries no device ID, IP address or wallet address. COOK keeps only the answer (whether it was flagged, and why), under a one-way hash of the name and ticker, for up to 7 days, so the same name is not checked twice. To spot real people's names, COOK's server also looks up the coin's name on Wikidata, run by the Wikimedia Foundation (COOK 2.0 and later). Only the name goes to Wikidata, from COOK's server, so Wikidata doesn't receive your IP address, device ID or wallet address.
In COOK 2.0 and later, when COOK checks a photo you picked, the photo is sent to Cloudflare Workers AI too. The app re-encodes the photo on your phone first, which removes location and camera data. Your photo is not sent to the image model in any version.
In COOK 2.0 and later, COOK's server may also send your words, your chaos pick and the character COOK made (its name, lore and captions) through OpenRouter to text models made by Google and OpenAI, which write the character, captions and post drafts. When they can't answer, or COOK's daily OpenRouter budget is used up, COOK uses Cloudflare Workers AI or the app's own templates instead. The scenes and icons COOK draws may also go through OpenRouter to a Google model that checks them for logos, lettering and drawing mistakes such as an extra eye; when it finds one, COOK draws the picture again. Your own photos and the stickers are not sent to OpenRouter. These requests come from COOK's server and carry no device ID, IP address or wallet address.
COOK's server keeps none of this unless you report something, share a teaser link or launch the coin (sections 6 to 8; logos from the older logo service are the exception, section 10). Cloudflare processes these requests under its own terms and privacy policy. OpenRouter, and the companies that run these models for it, process what they receive and keep it under their own terms and privacy policies. The Workers AI models in use are listed under credits in the app's Kitchen rules.
The first time you use COOK 2.0, COOK's server gives the app a random ID and a token that proves COOK issued it. Nothing about your phone, your wallet or you goes into the ID. The app sends it with AI, name check, teaser link, upload and character kit requests so COOK can apply daily limits per phone and tell which phone saved a coin's kit.
Uninstalling COOK or clearing its data removes the ID from your phone; the app then gets a new one. Versions before 2.0 don't use a device ID.
Like every web server, COOK's server sees the IP address a request comes from. COOK uses it briefly for rate limits: per-minute limits run inside Cloudflare's rate limiting, and daily limits (images per day, new device IDs per day) keep only a salted one-way hash of the address that changes every day. For IPv6 addresses the hash covers the network prefix. Those daily counters are deleted after 7 days.
Cloudflare hosts COOK's server and this website and processes IP addresses and request data to deliver and protect them, under its own privacy policy.
"Report" on an AI result, a coin or a page sends: the reason you picked, what you reported (for example a coin address or a page), its name and ticker if it has them, the reported caption or text if there is one, your optional note, the character sheet with its seed and model, and, when there is one, a downscaled copy of the image. COOK stores no device ID, wallet address or IP address with a report.
Report images are deleted after 180 days. The rest of a report is kept as a moderation record, with no fixed deletion date. Reports from versions before 2.0 carry the reason, the name, ticker and description of what you reported, a link to its image and your note.
Launching is optional. When you serve a coin on COOK Kitchen or Pump.fun, the app uploads its name, ticker, description, logo, X handle and links to COOK's server just before you sign. COOK hosts them at a fixed public address so wallets and explorers can show the coin. If the launch doesn't complete, the uploaded files stay at an unlisted address; COOK doesn't list or publish them.
Your launch transaction, your wallet address as the coin's creator, and every trade are recorded on the public Solana blockchain. Nobody, COOK included, can delete data from Solana. COOK's launch checker reads public chain data about coins made on COOK's configs (for example the creator wallet, early buys and the largest holders) to show launch facts, and keeps those facts with the coin.
In COOK 2.0 and later, after a coin made in the COOK app launches, COOK's server also sends its public name and ticker, as read from Solana, through OpenRouter to a Google model that checks them the same way as above. COOK keeps the result with the coin's address: whether it was flagged, the kind of word and what COOK did, and no name or ticker. If the check flags a coin, COOK may hide it from COOK's pages, and you can ask COOK to look again (section 17). The coin itself stays on Solana.
Your X handle and links are published with the coin. COOK doesn't verify accounts. Don't put personal or sensitive information in a coin's name, description, logo or links.
If you launch on Jupiter Studio or Bags, the coin's details, its logo and your wallet address go to that service, which builds the launch and hosts the coin's files under its own privacy policy. For a Bags coin without a picture, the app first uploads the coin's name, ticker and description to COOK's server, which makes an emoji logo and hosts both at a public address.
In COOK 2.0 and later, serving a coin can also save its character kit on COOK's server: the character sheet (with its lore, catchphrases and rival), up to four stickers and, for Jupiter Studio and Bags coins, the icon. It is saved with public facts about the coin: its address, launchpad, name and ticker, the launch transaction and your wallet address as its creator. Each sticker and icon goes through the photo check on Cloudflare Workers AI first, and one the check blocks or can't read is not stored. The kit is public, like the coin: its pictures are at public addresses, and COOK may show the kit to anyone who opens the coin, so the character can be loaded again later. A salted one-way hash of the saving phone's device ID is kept with the kit for 7 days after the first save, so only that phone can change it; then the hash is deleted. Kits have no fixed deletion date. When COOK hides a coin, it deletes the coin's kit and the pictures the kit stored.
If your version of COOK has them: a teaser link stores the teaser image, a one-way hash of the link's key and an optional planned time, and no name, ticker or coin address until the coin is served. The device ID is removed from it when the coin is revealed or the link expires. A link that doesn't become a coin is deleted with its image 7 days after it expires. A link that becomes a coin's page stays, with its teaser image, as that coin's public page.
COOK counts, per day, how many memes were started, how much art was drawn and how many coins were served. These totals carry no device ID or wallet address. The app also sends a short record when a launch ends: the launchpad, the step it reached, how long it took, an error code if any, how much SOL the wallet was short when it didn't hold enough, which store the app came from and the Solana network. It carries no wallet address, device ID or coin text.
COOK's server counts views of its own web pages (coin pages, teaser pages, the Kitchen rules page and its home page). Each view records the page, the share channel named in the link's tag (a word for where the link was shared, not a person) and whether the visit came from a browser, a bot or a prefetch. Your browser's details are not kept. When a person opens a coin's page, the view also records the coin and a one-way code made from the visitor's IP address and browser with a key that changes every day, so COOK can count people rather than page loads. Each day's key is deleted about an hour after that day ends (UTC); after that, nobody, COOK included, can tell which address or browser a code came from. These view records are kept in Cloudflare's analytics storage, not in COOK's database.
None of the totals, view records or launch outcome records have a fixed deletion date.
To warn about copies, COOK's server samples the names of new public Solana pools. Those counts are deleted after 8 days.
COOK versions before 2.0 draw AI logos through an older service that saves each logo on COOK's server at an unlisted address so it can be launched. COOK 2.0 uses that service only as a fallback when its newer art service is unavailable. Those logo files have no fixed deletion date. The IP address rules in section 5 apply to those requests too.
COOK's server also reads Google Trends, Wikipedia and CoinGecko for What's Cooking ideas and new-pool counts. It sends them no data about you.
The app talks to COOK's server over HTTPS. Access to COOK's server data is limited to COOK's operator. COOK's server writes log lines with counts and error codes, not your prompts, names or tickers.
COOK runs on Cloudflare's global network, so requests may be handled in a country other than yours.
COOK is not meant for children. You must be at least 18 and of legal age where you live to use it.
This policy can change. Changes are posted on this page with a new date.
Privacy questions: hello@cookkitchen.fun
See also the Terms of Service.