AI Image Evidence Checker
← Back to Evidence Checker

Privacy, image handling, and upload retention

Privacy Policy

This policy explains how this deployment of AI Image Evidence Checker handles image uploads and evidence reports. The service is operated by Img2det Project. For privacy requests, contact [email protected]. This is a product privacy notice, not legal advice.

Last updated: August 23, 2026

Short version

Uploads are processed only for your requested evidence report, deleted after analysis by the application path where temporary storage is used, and not used for training or persistent report history.

What we collect

  • When you run an evidence check, the service receives the uploaded image file plus basic file metadata such as filename, MIME type, extension, and file size.
  • The service may also process technical request metadata such as request time, IP-derived routing information, user agent, and API status codes through normal infrastructure logs.
  • The current product flow does not create user accounts, saved galleries, persistent report history, or marketing profiles.

How we use uploads

  • Uploaded images are used only to run the evidence check requested by the user.
  • The analysis inspects provenance metadata, raw byte markers, camera-like evidence, and frequency-domain signals to generate an evidence report.
  • The evidence report is not legal attribution, not a copyright determination, and not a definitive AI-versus-real detector.

Upload retention commitment

  • Current deployment behavior depends on the active backend path: the Cloudflare Worker path reads the image during the request and does not write it to R2, KV, D1, or an application database.
  • The FastAPI backend path may write the upload to temporary backend storage while the request is analyzed, then removes the temporary directory after analysis, including error and timeout paths.
  • The application code does not intentionally persist uploaded images after analysis, and uploads are not written into samples, runs, saved galleries, or persistent report history by the current product flow.

No training or model improvement use

  • Uploaded images are not used to train models, retrain models, improve AI systems, or build facial recognition datasets.
  • The current checker runs local evidence modules for the requested report and does not use uploads for unrelated product development.
  • If a future deployment adds a third-party AI or storage processor, the privacy notice should be updated before that behavior is enabled.

What not to upload

  • Do not upload images that you are not authorized to process or share with this deployment.
  • Avoid uploading highly sensitive, illegal, confidential, medical, biometric-identification, or third-party private images unless you have the required rights and consent.
  • This product is designed for lightweight evidence review, not for identity verification, medical advice, legal advice, or law-enforcement decisions.

Limits and user controls

  • Because the current product flow does not store uploaded files or persistent report history, there is no in-product archive to download or delete later.
  • Infrastructure providers may retain request metadata or operational logs according to the deployment environment's logging configuration.
  • For privacy questions, contact the site operator for this deployment.

Cookie and consent controls

  • Strictly necessary storage may be used to remember consent choices and support the requested product flow.
  • This site uses Google Privacy & messaging / Funding Choices, a Google-certified CMP, to collect consent from EEA, UK, and Switzerland visitors.
  • Non-essential analytics stays off unless measurement consent is recorded through the CMP. Current pages do not display AdSense ad units or Auto ads.

Advertising and third-party vendors

  • This site has a Google AdSense publisher account and an ads.txt authorization record for Google.
  • Current pages do not display AdSense ad units or Auto ads. The AdSense advertising script is not enabled by the production switch.
  • Google and third-party vendors may still use cookies or similar technologies through the CMP for consent storage, fraud and abuse prevention, and future ad serving, measurement, and protection.
  • If AppLixir rewarded or video ad placements are enabled in a future deployment, AppLixir may serve, measure, limit, and protect those ads as an advertising technology provider.

Personalized advertising controls

  • When ads are later enabled, Google may use information from visits to this site and other sites to help show more relevant ads, subject to the CMP choice.
  • You can manage personalized advertising in Google ad settings at https://www.google.com/settings/ads and may opt out of some third-party vendors' personalized advertising through https://www.aboutads.info/ where available.
  • You can review how Google uses data on partner sites at https://policies.google.com/technologies/ads.
  • You can also manage cookies or similar technologies through your browser settings, subject to the limits of your browser and device.

EEA, UK, and Switzerland consent

  • EEA, UK, and Switzerland visitors receive Google's certified CMP (Privacy & messaging / Funding Choices) where Google shows a consent message.
  • Advertising consent is read from the IAB TCF signal. Device storage (purpose 1) and Google's advertising vendor (755) must be granted before any future AdSense ad script can load.
  • You can reopen Privacy options from the Cookie Policy page when Google's revocation message is available.

Google advertising links