← 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. It is intended as a clear product privacy notice, not as legal advice.

Last updated: June 13, 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 cookie choices and support the requested product flow.
  • The current consent baseline keeps non-essential analytics only after consent, with EU, UK, and Swiss visitors in mind.
  • Marketing cookies, advertising pixels, and remarketing tags are not enabled by default in the current deployment.

Advertising and third-party vendors

  • If Google AdSense or other ad partners are enabled, Google and third-party vendors may serve ads on this site.
  • 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.
  • If advertising is enabled, Google and third-party vendors may use cookies or similar technologies to serve, measure, limit, and protect ads, including fraud and abuse prevention.
  • The current source code does not enable marketing cookies, advertising pixels, remarketing tags, an AppLixir script, or an AdSense script by default.

Personalized advertising controls

  • If personalized advertising is enabled, Google may use information from visits to this site and other sites to help show more relevant ads.
  • You can manage personalized advertising in Google ad settings and may opt out of some third-party vendors' personalized advertising through aboutads.info where available.
  • 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

  • Before serving ads to EEA, UK, and Switzerland users, a Google-certified CMP should be enabled where required.
  • The current local cookie banner is a lightweight product consent control and should not be described as a Google-certified CMP, IAB TCF implementation, or complete regional advertising consent system.
  • If AdSense or other ad partners are added later, this policy and the consent flow should be reviewed before those scripts are enabled.

Cookie and consent notice

EU_UK_CH_READY

EU, UK, and Swiss visitors can reject non-essential storage.

We use strictly necessary storage to remember this choice. Optional analytics stays off unless you accept it. Marketing cookies are not enabled by default in this deployment.

Current choice: not set · Cookie Policy · Privacy Policy