Privacy for Jev AI Image Tools

When you select an image in either tool, your browser corrects orientation, resizes without cropping, and converts static JPEG, PNG, or WebP files to PNG copies, with transparent padding for extreme aspect ratios. The local preview shows the prepared copy. Selecting a file alone does not send it to a comparison or image-origin API. Preview references are revoked when you replace or remove the image, or leave the tool page.

This manages the application's preview references; it does not delete the original file from your device. Your selected files remain available to the page while you prepare a comparison or assessment. Only pressing the comparison or image-origin assessment button submits them for processing.

Starting a comparison sends two images and the selected comparison criteria to the Aijev server. A nonblank custom prompt replaces the selected goal’s built-in criteria. Starting an image-origin assessment sends one image with the tool’s fixed assessment question. The server validates the uploads before sending them to Jev at TypeSafe.

Both tools send the browser’s prepared PNG copies. Preparing these copies does not carry over the original file’s embedded metadata; orientation is applied to the image pixels. Information visible within the image remains visible to the model. For a comparison, the server sends both prepared images and your comparison criteria directly to TypeSafe for Jev to evaluate together.

On the AI image detector page, the server sends one prepared image to TypeSafe for Jev. It makes one request to assess visible signs of AI generation or substantive manipulation, including face swaps, composites, and meaningful local edits made with or without AI. Routine edits alone do not count as fake. The result is likely fake, likely real, or inconclusive. An inconclusive result means visible evidence does not support a judgment. The assessment does not certify authenticity or identify the location of an edit.

The application returns the selected outcome, probabilities, and model-reported confidence to your browser. Jev comparisons do not generate separate descriptions or a written rationale. Image-origin assessments also do not include a written rationale. They are visual judgments, not proof of provenance or calibrated accuracy rates; the application does not verify AI watermarks or C2PA credentials. Changing a comparison goal, custom prompt, or image cancels the current comparison and clears its result. Replacing or removing an image also clears an image-origin result. Leaving the tool page discards its in-memory state.

The application does not persist submitted images, prompts, comparison results, or image-origin assessment results. It does not configure a content cache or log submitted image contents, prompts, or credentials. The comparison and image-origin APIs send a no-store response header.

To prevent abuse, comparisons and image-origin assessments share five request attempts per IP address in any rolling 60-minute window, across Jev comparison and the AI image detector. The rate limiter temporarily stores a hashed IP key and request timestamps in Cloudflare Durable Objects. It does not store the original IP address or image contents. These records expire about one hour after the last counted attempt; requests rejected by the limit do not extend that window. Invalid uploads and failed requests still count.

These statements describe the application code. They do not establish a retention period for third-party systems, prove that every infrastructure log is empty, or guarantee deletion from a provider's systems. Images and comparison criteria still pass through the services needed to complete a comparison or image-origin assessment.

Aijev runs on Cloudflare infrastructure and uses TypeSafe for Jev comparisons and image-origin assessments. TypeSafe and Cloudflare operate under their own processing policies. Their handling of requests, technical metadata, logs, retention, and model training is outside the application's storage behavior described above.

This page does not promise that providers keep no logs, never use data for training, or delete submissions within a fixed deadline. Removing a preview or closing the page does not retract data already sent upstream. Before uploading sensitive material, consider both the image and any information included in your custom prompt.

The application does not require an account and currently configures no analytics or tracking cookies. This describes Aijev's code, rather than a guarantee about all hosting or upstream services. You can read the guides and saved example without submitting images.

Upload only images you are comfortable sending through this processing flow. For product context, visit About Aijev; for an explanation of native image comparison, read how AI image comparison works. Review the AI image detector for the scope and limits of image-origin assessments. Return to the image comparison tool →