Privacy

What Editmamei does with your data.

Editmamei runs on your own computer and edits inside the Photoshop you already have. The honest version is short: your photos aren't uploaded to us, and the only thing Editmamei sends to its own servers is content-free usage you can audit and turn off. When your AI assistant needs to see an edit, a downscaled preview goes to that assistant, covered below. A formal legal policy lands with the v1.0 launch; this page describes how the product behaves today.

What Editmamei never sends to us

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

  • Your image and document content. No photos, previews, thumbnails, layer renders, or Photoshop document data are ever sent to Editmamei.
  • Your file paths. Full paths stay local; nothing identifies where your work lives on disk.
  • Your metadata. Camera info, GPS, and author fields are never part of what the product transmits.

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. The earlier "no telemetry at all" promise is retired: a licensed product that phones home should say so plainly rather than claim a purity it can't keep. Everything below is anonymous, modelled on how editors like VS Code handle telemetry, and documented field by field.

  • Usage and reliability (on by default). Per edit: which tool ran, whether it succeeded, an error category if it didn't, and how long it took. Per session: the Editmamei version, your Photoshop version, your operating system, and a random install ID that counts installs without identifying you. No prompts, no arguments, no content.
  • 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.

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.

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 downscaled JPEG goes to that AI provider, exactly as if you'd dropped the file into a chat with it. That's a property of using a cloud AI, and a function of which assistant you choose, not a hop Editmamei adds.

This website

Everything above is about the Editmamei software. This marketing site is a separate system with its own, ordinary analytics.

It uses Microsoft Clarity for analytics: session recordings and heatmaps that help us understand how visitors use the site. Clarity operates in two modes depending on your consent:

  • No cookies (default). If you decline or haven't yet made a choice, Clarity runs without setting any cookies. No cookies are persisted to your device; Clarity may use session storage to correlate page views within a single tab, which is cleared when the tab closes.
  • With cookies (if you accept). Clarity sets two first-party cookies: _clck (persists a user ID across sessions, expires in 1 year) and _clsk (ties page views within a session, expires in 30 minutes). Both are set by editmamei.com and processed by Microsoft per their privacy statement.

You can change your choice at any time using the link in the site footer.