Separate file processing from page delivery
A local tool performs its image operation on the device instead of sending photo pixels to an image-processing server. The website still needs to load its code, styles and assets. Hosting can receive normal request information even when the selected photograph is processed locally.
This distinction is why a blanket promise that nothing ever leaves the device is unsuitable for the entire website. Describe the actual operation and any connected services. A privacy decision should be based on the page’s processing notes, not just a lock icon.
Understand large local assets
Background removal and colour prediction can use bundled model or runtime files. Loading them can use bandwidth and take time, especially on first use. That download is separate from uploading the selected photograph, but it still affects performance and device storage or cache.
If processing appears slow, read the status message and try a smaller input after the assets are available. Repeatedly restarting a large first download can make the problem harder to diagnose. On an 8 GB computer, avoid several large simultaneous editing sessions.
Know the exception for connected checks
Image Investigation can combine local signals with configured external detection. Activated connected checks can send the selected image to a service. Read the analysis acknowledgment and the published privacy information before using sensitive material.
Unavailable detectors should remain unavailable rather than being replaced by invented evidence. If you want an entirely local inspection, use an appropriate local workflow and understand which forensic questions it cannot answer.
Review the output as well as the input handling
Local processing does not automatically make the exported image safe to publish. A result can still contain faces, location clues, names in a filename or embedded information depending on the operation. Use Metadata Viewer and a careful scene review when those details matter.
An exported report can also contain sensitive case context or a thumbnail. Treat it as a separate file requiring review. Keeping pixels local during one operation does not remove the need to decide who should receive the final output.
Keep the live-site policy aligned with enabled services
Advertisement spaces remain placeholders. Google Analytics is available after an explicit analytics acceptance, while connected forensic operations have their own processing notices. Use Cookie preferences to change optional analytics, and read the current legal pages for the active data flows.
Use a verified support mailbox for questions and reports, and keep private API credentials out of the source package. The practical goal is accurate information about each data flow, supported by the real configuration, rather than an absolute promise that does not describe the deployed website.
Optional analytics is separate from image processing
The current website offers an explicit analytics choice. Rejecting analytics keeps the core local image operations available; accepting permits the Google Analytics tag to load. The preference is specific to the browser origin, so localhost and the live website have separate choices.
Advertising is not installed in this release. Connected Image Investigation remains a different data flow: configured services can receive selected images after acknowledgment. Review the Privacy Policy and the specific tool notice rather than assuming one cookie choice controls every requested processing operation.