What we keep, and what we don't.

What you type. The scenario you enter is stored along with the meme it produced. That's how a meme keeps working when you share its link, and how we can tell later whether a style is producing anything good. Don't type anything into it you would mind being stored — it is a joke machine, not a diary.

Your reactions. When you mark a meme funny, or scroll past one, we record that against the meme. It is the only signal we have about whether any of this is landing.

A device identifier. A random UUID in the signed, HTTP-only _king_kongra_device cookie brings back “Your memes” on this browser. It lasts one year from your last visit. The same ID is carried in the short-lived session cookie for generation limits and ratings, and stored with new memes to identify their collection. It isn't tied to a name, email or account.

Text duels store both moderated outputs, backend names and this anonymous device ID. A winner vote stays separate from meme ratings and is counted only once for that device's duel. Public scoreboards show aggregate wins, never device IDs. Duel records have the same indefinite retention as memes; clearing cookies loses access to an unvoted duel.

Clearing the device cookie or site data starts an empty collection. Previous collection access cannot be recovered. Memes made before this feature have no recorded owner and cannot be added retrospectively. Shared meme links remain public; collection ownership does not make individual memes private. Clearing cookies does not reset anti-abuse fingerprint limits, generation budget or moderation.

Usage events. Which buttons get pressed, which styles get used, whether generation succeeded. These are deliberately stripped of prompts, meme text, image URLs, and IP addresses before they leave the server.

Generating a meme costs us real money, so we need some way to tell one visitor from another beyond a cookie you can clear. Your IP address and browser type are combined and put through a one-way hash. We store only the resulting scramble, which cannot be turned back into your address.

Your raw IP is handled in memory to serve the request and by our hosting provider in the ordinary course of routing traffic, as it is for every site you visit.

Building this without other companies' infrastructure isn't realistic, so here is exactly who is involved and what reaches them:

• xAI receives your prompt in order to generate the meme. It cannot be otherwise — that is the generation step.
• PostHog receives the stripped usage events described above.
• Sentry receives error reports when something breaks, which can include technical details of the failing request.
• Cloudflare stores and serves generated images.
• Fly.io runs the servers and the database.

We don't sell data, and we don't run advertising trackers.

Memes, their prompts and their collection identifiers are kept indefinitely, because shared links should not rot. Clearing cookies removes collection access rather than deleting server records. Rate-limit counters expire within about a day. Usage events are kept according to our analytics provider's retention settings.

Want a meme taken down, or a prompt deleted? Ask, and we'll do it. There is no form and no ticket queue — just an email, below.

Privacy questions, deletion requests, or anything else about your data: srm@metabureau.com.au.

To report a specific meme rather than a privacy matter, see the terms .