Local product data stays local.

Product-operation data

Released Emulyn tools are designed for local operation without an Emulyn account, activation service, telemetry, analytics, crash upload, advertising identifier, remote collaboration, or product network request. The exact product-specific notice identifies what the selected tool reads and whether it creates a user-requested local file or folder.

No Emulyn plug-in for Adobe Photoshop Lightroom Classic opens a `.lrcat` database directly. Catalog access uses documented Lightroom Classic SDK surfaces only. Scope differs by product: some observe an explicit selection, some observe aggregates returned by Lightroom, and desktop companions read only the declared local inputs described on their product page.

Manual copying

A user-initiated copy, text download, report, or new output folder is stored only where the customer chooses. Clipboard and filesystem destinations are controlled by the customer and are not an Emulyn upload. Product-specific notices identify every implemented write.

Purchase, delivery, and website data

At launch, the merchant of record and delivery provider process the minimum transaction data needed for checkout, fraud screening, taxes, receipts, delivery, redelivery, and refunds. The checkout identifies the live provider, and its notice explains its role, retention, and data-request process.

The launch site does not include an Emulyn product account or an upload for photographs, catalogs, filenames, or pasted lists. Hosting logs are limited to the service needed to deliver and protect the site; the site includes no Emulyn analytics, advertising tracker, or customer-data form.

Support privacy

A support request should contain only the order reference, exact product, version and checksum, relevant host or runtime versions, an exact on-screen error, and a synthetic description. Customers should not send catalogs, photographs, previews, production lists, private filenames or paths, credentials, payment details, or unreviewed logs.