Privacy, in plain language.
What this image workflow stores and sends.
Images and metadata stay on this device
The application reads selected image files in the browser. Image contents, thumbnails, filenames, extracted metadata and content hashes are not uploaded for processing or sent as analytics parameters. Unsupported processing never falls back to a server upload.
Website and Google Analytics requests
Loading the website uses network requests. We use Google Analytics (G-DVC0BNGRG6) for site-usage measurement, including public page paths. Those requests go to Google and may use browser identifiers. The app does not include image contents, filenames or metadata values in page paths or analytics events. This page does not claim that the website is entirely offline or makes zero external requests.
Your session and optional browser storage
Switching between Remove, Check and Learn clears selected files, outputs and saved recovery data. The logo resets image-session choices and data, even on Remove; your selected language is retained. The language preference is stored separately and contains no images or session data. We ask once per new session whether to enable local browser recovery. With consent, a local database stores the actual original and output file bytes and your choices for up to 24 hours. Expired records are cleared the next time the app opens; the browser may evict records sooner. Deletion while the browser is closed is not guaranteed.
Decline, clear or reload
Declining keeps the session memory-only, so reload or closing may lose it. Clear session stops work, releases app-held references and removes the local recovery record. It does not change original files or downloaded copies and is not a forensic memory-erasure guarantee.
Sensitive information and outside links
Metadata values are visible by default. Settings can mask values across all metadata views. Extracted values are rendered as text, not HTML. The application does not automatically visit metadata links, credential records or maps.