MEMEFORGE

Privacy policy

Last updated 19 November 2026

Memeforge makes memes from a description: a website, an image API, an MCP server for AI agents, and bots for Microsoft Teams and Slack. This page says what we collect, what we do with it, and how to make us delete it. It is written to be read, not skimmed past.

Who runs it

Memeforge is operated by Memeforge. Questions, deletion requests and anything else go to hello@damemeforge.com.

Using the site without an account

You can browse the template catalog and make memes without signing in. Captions you type are sent to our server to render the image and are not stored. A request typed as a description is also read by an AI model (see "Describing a meme" below). The rendered image is sent back to you and not kept, unless you ask for a shareable link (see "Saved memes" below).

Describing a meme

When you describe a meme in words, on the site or to the Teams or Slack bot, an AI model works out which picture you mean and what it should say. That model is Claude, run by Anthropic. We send it your message, the last few messages of the same conversation, and the pictures it needs to look at: template previews, the meme it has just made, and any picture you attached. We do not send your name, email address or account id.

Our server remembers the last few turns of a conversation for up to two hours, in memory only, so that "not that one" or "shorter" makes sense. That working memory is not written to disk and is gone after that. Separately, if you are signed in, the list of your earlier memes is saved with your account, as described under "Share links and your earlier memes".

Pictures found on the web

If you are signed in, or using a linked Teams or Slack workspace, and you ask for a picture the catalog does not have (a film scene, a match moment), Memeforge can look for it on the web. The search words, which the AI model writes from your request, are sent to an image search service, Serper, which searches Google Images. Our server then fetches a few candidate pictures from the sites they are on; those sites see our server's address, not yours.

The picture you or the model choose is saved as a private template in your account, exactly like one you uploaded: only you can see it, and deleting the template deletes the picture. The other candidates are deleted within two hours. We keep no record of where a picture came from.

Signing in

Accounts use Google sign-in, handled by Supabase Auth. We ask Google only for your basic profile: email address, name and profile picture. Supabase stores that profile as part of your account. Our own server keeps your Supabase user id and your email address, nothing else from your Google profile. We never see your Google password, and we do not get access to anything else in your Google account.

Your profile picture is shown in the site header while you are signed in. It is loaded from Google's servers by your browser, not copied to ours.

API keys

You can create API keys so agents, scripts and bots can use Memeforge as you. We store each key as a SHA-256 hash, together with its name, the first few characters, its scopes, when it was created, when it expires and when it was last used. The full key is shown once, when you create it, and cannot be recovered afterwards. You can revoke or delete a key at any time on the API keys page.

When an AI client connects by signing in through your browser, a key is made in your account, named after that client. The client is not given that key: it gets a token that works for an hour and another it uses to get the next one. We keep a record of the client's registration (its name and redirect URL) and of the sign-in itself (your account id, which key it made, and how many times it has been renewed) so this works. Revoking or deleting the key on the API keys page ends the sign-in at once, and signing in again from the same client replaces its earlier key.

If you link a Microsoft Teams workspace to the bot, a key for your account is kept on our server so the bot can render memes for that workspace. Saying unlink removes it; revoking the key stops it too.

The Slack app keeps no record of your workspace beyond what Slack sends with each command: a hashed user id for analytics and the text of the command, which is rendered and not stored.

Images and templates you upload

Images you upload to caption are sent to our server for rendering. Before a picture is saved as a template, attached in Teams or Slack, or kept from the web, it is shown once to the AI model described under "Describing a meme", which answers only whether it is fit to keep (no nudity, sexual content, gore or hate imagery). A picture that fails that check is not stored. If you save one as a template, the image and its layout are stored on our server under your account. Your templates are visible only to you, through the site or through your own API keys. They are never added to the public catalog and never shown to other users. Deleting a template deletes the image.

Photos you attach to a message

Some memes take photos as well as words, and you can attach photos to a message on the site. Your browser shrinks each one before sending it. On our server it is shown once to the AI model, to check it is fit to keep and so the model can put it in the right place, then re-saved without its metadata (location, device) in a folder that belongs to that one conversation. It never joins the catalog and is not shown to anyone else.

Those photos are deleted 7 days after the last one was attached to the conversation, and at once when you delete the conversation from your list. After that, an earlier meme that used them shows the meme's original pictures instead. If you share a meme that has your photos in it, we keep the finished picture, not the photos, so the link can show it: anyone who has the link can open it, and it is deleted after 30 days. Be sure the people in a photo are happy to be in the meme before you share it.

Saved memes

Memes made through an AI agent, the Teams bot or the Slack app are saved on our server so they can be returned as a link. Those files are deleted after 30 days. Anyone who has the link can open it during that time, so share it with that in mind.

Share links and your earlier memes

When you share a meme from the site, we keep which template it uses and its captions on our server so the short link keeps working. Anyone who has the link can open it. The list of your earlier memes is kept in your browser if you are not signed in. If you are signed in, it is kept with your account on our server so it follows you to other devices; for each meme it holds what you asked for, our one-line reply if there was one, the template and the captions, not the picture. Deleting an entry removes it, and deleting your account removes the whole list.

Feedback you send

If you send feedback through the form on the site, we keep what you wrote, the kind of feedback you chose, a screenshot if you attached one, your email address if you gave one, and, when you send it from under a meme, which template and captions you were looking at. If you are signed in, the message is linked to your account. A screenshot is redrawn before it is kept, which removes anything stored inside the file such as where a photo was taken. We use it to fix and improve Memeforge and to reply to you. It is also filed in our issue tracker.

Product analytics

We use PostHog to understand which features get used. Session replay, autocapture and surveys are turned off: we send only named events, such as "a meme was rendered", with properties like the template id, the output size and which surface made the request (website, API key, MCP, Teams). We do not send the captions on your memes, the messages you type, uploaded images, API keys or email addresses to PostHog. A few events do carry a short piece of text: the name of a meme you asked for that we did not have, the search words an AI tool sends when it looks through the templates on your behalf, a short machine-written note when a caption had to be moved, and a short technical message when the page hits an error.

Visitors who are not signed in are identified by a random id that PostHog stores in your browser. When you sign in, events are tied to your Supabase user id. Teams and Slack users are identified by a hashed id, never by name. As with any request to a third party, PostHog receives your browser's IP address; our server does not send it.

Server logs

Our server keeps ordinary operational logs: request paths, status codes, timings and errors. For a picture search they also record the search words and the addresses of the pictures that were considered, so we can see why a search went wrong. Logs are used to keep the service running and to investigate abuse, and are not combined with analytics to profile you.

Local storage

The site uses your browser's local storage for your theme choice, your sign-in session, your recent templates and the analytics id above. There are no advertising cookies.

Third parties

We do not sell your data, and we do not share it with anyone except the services above, as needed to run Memeforge, or when the law requires it.

Deleting your account

Email hello@damemeforge.com from the address you signed in with and we will delete your account, your API keys, your templates and your list of earlier memes. You can delete keys and templates yourself at any time from the site.

Children

Memeforge is not directed at children under 13, and we do not knowingly keep accounts for them.

Changes

If this policy changes in a way that matters, we will update the date at the top. Keep using Memeforge after that and the new version applies.