Privacy

What Editmamei does with your data.

Editmamei runs on your own computer and edits inside desktop Photoshop. 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 fuller, formal privacy policy is in progress; 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 content-free, 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, 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.
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.

See how this fits together in How It Works →

Your rights, and the legal basis

Who is responsible for this data, the basis for collecting each kind, how long it is kept, and what you can require us to do. This applies to everyone, not only to people in the EU or UK.

Controller: EMBD Artifacts LLC, doing business as Editmamei. Contact us at editmamei.com/contact.
The install ID: A random value generated on your machine. It is not derived from your name, account, email, hardware, or anything else about you, and on its own it identifies nobody. It is stable across sessions, and stable identifiers can be correlated with other information, so data protection law classifies it as pseudonymous rather than anonymous: personal data, and subject to the rights below.
Lawful basis: Usage and reliability data (on by default) rests on legitimate interests: identifying defects, and establishing which features are used and on which Photoshop versions. You have the right to object, and the setting is the mechanism. Diagnostic detail (off by default) rests on consent, given by enabling it and withdrawn by disabling it. The two settings are independent — switching usage off does not switch diagnostics off.
Retention: Per-install daily counts: 24 months from the day they cover. The install record: 24 months after the install was last seen. Opt-in diagnostic records: 90 days. All deleted automatically. Aggregate daily totals carry no install ID and are not subject to these windows.
Your rights: Access, rectification, erasure, and objection. Your install ID is the reference for all of them; print it with editmamei config get telemetry.install_id and send it to us with your request. Two limits apply: erasure removes the stored records but does not stop collection, because the same ID remains in your settings file — disable telemetry first if you want both; and aggregate daily totals were summed on arrival with no ID attached, so they cannot be recalculated to exclude a single install. Without an install ID we cannot locate your records, because no email address, account, or IP address is stored alongside it.
Processing: Editmamei's own infrastructure, on Cloudflare and on equipment we operate. No third-party analytics processor. Telemetry is not sold, shared, or used for advertising. Your IP address reaches that infrastructure with the request, as it does with any web request. It is used to rate-limit abuse and is not written to the telemetry store. Three values the network edge derives from the connection are recorded with your install ID: country, time zone, and the datacenter that served the request.

Every field Editmamei sends is documented one by one in the privacy reference.

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.

The email list

If you sign up for updates, we store the address you gave us and nothing else. No name, no company, and nothing about how you use Editmamei.

Signing up stores your address right away, marked unconfirmed, and sends you a confirmation link that expires after 48 hours. Until you click it, nothing is ever sent to that address again. Addresses are held by Resend, who send the mail on our behalf. Every message has an unsubscribe link, and using it takes you off the list immediately.

The list is never joined to product telemetry. Telemetry carries a random install identifier and never an email address or a name, so there is nothing to connect an address to, and we do not try. They are separate systems with separate consent, and we intend to keep it that way.