What Editmamei Desktop does with your data.

Editmamei Desktop runs on your own computer and drives Photoshop or GIMP. Your photos aren't uploaded to us. The only usage data Editmamei sends us is content-free, and you can audit it and turn it off. The few other requests it makes, listed below, check for updates and handle a Pro license, and none of them carries your images. When your AI assistant needs to see an edit, a preview goes to that assistant, along with tool results, covered below. The legal basis, retention periods and your rights are further down this page.

What Editmamei never sends to us

There is one line we don't cross, on any setting:

• Your images. No photos, previews, thumbnails, layer renders, or other pixel data are ever sent to Editmamei. (If you opt in to diagnostics, an error message can name a layer or repeat a value you gave a tool; see below.)
• Your file paths. Full paths are never sent to Editmamei. Tool results can show them to your AI assistant.
• Your metadata. Camera info, GPS, and author fields are never sent to Editmamei. When your AI assistant inspects a document, the camera details it reads, GPS included, go to that assistant with the rest of the conversation.

What Editmamei does send

Editmamei is built by a small team, so it sends a thin stream of content-free signals that show what's working and what's breaking. It follows the way editors like VS Code handle telemetry, and every field is documented one by one.

• Usage and reliability (on by default). Per edit: which tool ran (a Photoshop or a GIMP tool), whether it succeeded, an error category if it didn't, and how long it took. Per session: the Editmamei version, your Photoshop version (no GIMP version is recorded), your operating system, which AI client connected, which install route you used (npx, a global or project-local npm install, the one-click Claude Desktop extension, or a source checkout), and a random install ID that is not derived from anything about you. On Pro installs, one extra startup signal records whether your Pro add-on actually loaded, so a purchase that failed to install is distinguishable from one that's working. No prompts, no arguments, no content.
• Feature names (on by default for new installs). Daily counts of which editing features were used: which filter, blend mode or effect a tool was asked for, and which operations a script used. A tool's option is counted only when its value is one of the fixed values that tool declares, and a script operation only when it is on a published list; any other name in a script is counted as unknown. A file path, layer name, text or the script itself is never sent. These counts carry no install ID. An install from before this setting existed is asked once, in your AI client, before anything is sent, and an unanswered question means off. Your answer is recorded with your install ID, so we know who was asked. Turn it off with editmamei config set telemetry.features false or the Share feature names toggle in Claude Desktop. Switching usage data off stops it too.
• Diagnostics (off until you turn it on). When you opt in, a sanitized error message and the name of the step that failed, so a bug can be traced without you mailing a log by hand. File paths are reduced to bare names; still no image content. The message is the error's own text, so it can name a layer, group or channel, or repeat a value you gave a tool; those names are sent as written.

This data goes to our own infrastructure, not a third-party analytics company. You can see the current settings, and switch usage data off entirely, by editing ~/.editmamei/settings.json or running editmamei config. The file is plain text and yours to inspect at any time.

Other requests Editmamei makes

Besides usage data, Editmamei makes four other kinds of request. None of them carries images, documents or file paths.

• Update check (on by default). At startup, Editmamei asks the public npm registry for the latest version number. The request carries no identifiers and no usage data, and it is skipped when you're offline. Switch it off with editmamei config set update_check false, or with the Check for updates toggle in the Claude Desktop extension settings.
• Pro activation. Activating Pro sends your license key and a hashed device identifier to the licensing service, a third-party licensing provider, which assigns an activation ID to that device. The identifier is a salted hash, with no raw hostname or username in it.
• Pro license check. About once a day, a Pro install sends your license key and activation ID to the licensing service to confirm the license is still valid. This request does not carry the hashed device identifier.
• Pro module update. Each time Pro starts, Editmamei asks its own delivery service whether a newer Pro module exists, and downloads it if so. The request carries your license key, your activation ID and a fixed user-agent that is the same for every install. It is separate from the update check above, and the update check setting does not switch it off.

Your AI assistant is a cloud service

The AI assistant you drive Editmamei with is a cloud service. When you ask it to look at an image (for example, the visual-verification preview), a preview JPEG goes to that AI provider, exactly as if you'd dropped the file into a chat with it. Previews are 1024 pixels on the long edge by default, and your AI assistant can ask for up to 8192, so a smaller photo can go at full size. Tool results go to the same provider, and they can include file paths, layer names, measurements and document metadata. That's a property of using a cloud AI, and a function of which assistant you choose, not a hop Editmamei adds.

Turning off previews in Editmamei's settings stops preview images going to the AI provider, in both Photoshop and GIMP: editmamei config set privacy.send_previews_to_llm false.