Product scope and publishing principles

What is GenDetect—and what does it deliberately not claim to be?

GenDetect is a free browser-based tool and publishing brand for screening AI-content signals. The current public version emphasizes explainability, local processing, and human review. It does not present a heuristic score as a calibrated source verdict or claim model and backend capabilities that have not shipped.

Current scope
Free · Local · Explainable
Last updated

01 · Product scope

Evidence for an initial screen, not a decision made for you.

The site places a working detector, methodology, and verification guidance together so a user can see both a score and what that score can and cannot establish.

An online tool with no account requirement

The current version requires no login, sign-up, or stored history. Text, images, and video are analyzed in the current browser for a quick initial screen. It is not an identity, academic-discipline, hiring, or legal decision system.

Open the GenDetect detector

Three inputs follow three analysis paths

Text screening examines repetition, sentence length, punctuation, and character structure. Image screening samples color, brightness, texture, and edges. Video screening reads duration, resolution, bitrate, and container metadata. The scores are not interchangeable and cannot attribute a specific generator.

A result should lead to verification

The score and factor list flag material worth reviewing. A stronger conclusion also needs the original file, content credentials, version history, an author explanation, publishing provenance, and contextual evidence—not a single detector result treated as a final verdict.

Read the AI content verification guide

02 · Method and limits

Publish the implemented capability and how it can fail.

The current implementation is a front-end heuristic demonstration, not a source classifier trained, calibrated, and continuously monitored on a representative dataset. Product copy and structured data must preserve that boundary.

Explainable rules instead of a mysterious score

Each input receives a score from an explicit combination of observable features, and the interface exposes supporting factors. The rules are inspectable, but language, genre, editing, compression, transcoding, sample length, and device processing can all change them.

Read the methodology and limitations

Expect both false positives and false negatives

Human writing can be repetitive or highly regular, real photos can be heavily processed, and ordinary video can have unusual bitrate. AI content can also be rewritten, edited, or transcoded to weaken signals. A high score is not proof, and a low score does not rule generation out.

Review accuracy and false positives

Detection is not plagiarism checking

GenDetect currently compares features inside the submitted material. It does not search the web, paper repositories, or publishing databases for matching sources. AI detection, plagiarism checking, fact-checking, and provenance verification address different questions and may need to be combined.

Compare AI detection and plagiarism checking

03 · Publishing and upgrade principles

A capability change must first become a verifiable disclosure.

GenDetect uses production code and public pages as the reference. A change to the algorithm, data flow, supplier, or account capability requires corresponding methodology, privacy, and interface updates.

Describe only capabilities that have shipped

Product pages and guides do not present a planned deep model, frame-by-frame video analysis, content-credential verification, or generator attribution as a current feature. A page date identifies the public disclosure version; it is not independent certification or an accuracy endorsement.

Algorithm upgrades require new validation evidence

A future algorithm upgrade should document input scope, feature or model version, threshold rationale, representative test sets, false positives and false negatives, language or media differences, and uncovered cases before methodology and score explanations change.

Disclose the data flow before a backend launches

Detection input is not currently uploaded to a backend. Before a recognition API, account, or cloud task launches, the interface must name submitted fields, purpose, suppliers, retention, deletion, training use, and user controls, with a synchronized privacy notice.

Read the current privacy notice