A local check should stay local.

Image checks

The checker reads one image in the browser as its primary path. The current build has no server fallback. It does not upload, persist, mutate, or include image bytes, filenames, or metadata values in analytics.

If a future fallback is introduced, this notice will name it before use, state its size cap and deletion semantics, and be tested for non-retention.

Pilot forms and events

When you choose to submit the pilot form, we collect the form fields you provide: email, role, AI-image use, approximate image volume and store count, workflow, concern, desired outcome, pilot intent, consent choices, and source/UTM attribution. The server issues and authenticates a random journey identifier in a 30-day HttpOnly cookie; request bodies cannot choose the stored identifier. With analytics consent, event records use only that identifier, event name, time, result or intent dimension where applicable, and source attribution. They do not contain image content or filenames.

Retention

Lead and event records are kept for no more than 30 days during this validation. Expired records are deleted from the private database; expired rate-limit hashes are deleted after their short abuse-control window. Aggregated, de-identified validation totals may remain in the final evidence report. Image bytes never enter these records.

Your choices

Optional analytics is off until you choose it, and you can turn it off from the checker or pilot form to stop future events. Do not submit the pilot form if you do not want us to hold the contact details and answers above. You can ask for access or earlier deletion by emailing matze.schedel@gmail.com; replying to a delivered confirmation works too.

Scope

This tool inspects declared metadata. It does not detect whether an image is AI-generated, certify legal or Google Merchant Center compliance, or predict an enforcement outcome. Read the terms and return to the checker.