Skip to content
checkaifree
Back to detector

Privacy and image handling

Last substantively updated: 2026-10-15.

Check AI Free is maintained by the Check AI Free team. Contact [email protected] about processing, stored extension results or corrections.

Images you choose to check

  • Local clues: The website initially inspects up to the first 64 KB in your browser. These may contain source declarations, camera metadata or generation text. Signatures are not verified.
  • Header fallback: If needed, a fragment of up to 64 KB, the original filename, size and MIME type can be sent to the Cloudflare edge function. The fragment may include embedded metadata and pixels. The function processes it in memory and does not save the input as an image file.
  • Pixel model: When needed and available, the browser redraws a JPEG with a longest edge of at most 1,536 pixels. This copy omits embedded EXIF/GPS metadata and is sent to our backend and the configured Hive or Sightengine provider. The provider may apply its own processing and retention policy. We do not promise that third parties never retain submissions; review Hive's policy and Sightengine's policy before checking sensitive material.
  • Score cache: The edge classifier may cache a provider score keyed by a hash of the reduced copy for up to 30 days. This cache does not contain the original uploaded file.
  • Image URLs: Our server retrieves a supplied direct image URL to obtain supported file bytes. This exposes the address and image to our backend and the hosting network. The application does not cache the image-fetch response.
  • Limits: The current tool checks still JPEG, PNG and WebP images, not video, audio, identity or account history. Model availability and request limits apply.

We do not sell checked images or use them to train our own models. Avoid submitting confidential material unless you are comfortable with the applicable processing paths.

Browser extension history

The extension checks only images you select. Up to ten recent results and reduced previews are saved on your device. Clear history removes completed local records; an already running check may finish afterward. Full source addresses are held in extension session storage for tasks and retries. Original uploaded files are not saved in durable history. Provider credentials remain on the server.

Optional usage analytics

Google Analytics 4 loads only after you allow analytics. Browser Do Not Track or Global Privacy Control preferences keep it off. You can change the choice through Analytics settings. Consent choice is stored locally; consenting may allow Google Analytics identifiers.

We measure accepted checks, completed results and fixed error states, separating demo activity. Analytics event parameters do not include image bytes, supplied image URLs, filenames, EXIF/GPS or raw exceptions. Page addresses are reduced to known paths and approved campaign parameters. Counts may omit users who decline, use blockers or activate privacy controls.

A team QA setting suppresses analytics in marked browsers. We do not treat internal tests or controlled examples as external users or demand.

Infrastructure and support

Cloudflare provides hosting, delivery and edge processing. Network providers necessarily handle request information such as IP addresses and security logs under their own policies. We do not claim the whole network is log-free. If you email support, your message is processed to answer it. This site currently requires no user account and offers no paid subscription checkout.

Requests and changes

For access, correction or deletion questions, contact support with enough context to identify the relevant record. Image inputs are not saved by our application as a retrievable upload archive; extension history is controlled on your device. We may be unable to retrieve a previously processed image. Material changes will be described on this page.