Last reviewed: September 24, 2026
This Privacy Policy explains what AI Detector Checker processes when you use the public AI detector. The detector currently works without account registration. Using it without an account does not make the request anonymous.
What is sent for analysis
- Pasted text: the text is sent to our servers and analysis backend when you run a check.
- PDF, DOCX, and RTF files: the file is processed from PHP’s request-scoped temporary upload so readable text can be extracted. The application does not move it into the WordPress Media Library or public uploads directory. In the normal flow, it explicitly deletes the temporary file before returning extracted text; PHP request cleanup provides a second cleanup path.
- TXT files: the file is read in your browser, then its text is submitted for analysis.
Do not submit passwords, private keys, medical or financial records, government identifiers, confidential business material, unpublished research, or other sensitive content.
Submitted text is not retained. Limited operational metadata may be logged for reliability and aggregate product monitoring. The metadata written for each analysis is: time, engine, word count, length band, result band, language code, latency, the displayed score, and a hashed network identifier that is re-salted every day, plus internal bookkeeping such as a marker for our own test checks; never the text. For a request that is not analysed (for example, text that is too short or too long, or a request that was rate-limited), we keep only an hourly count by reason.
Free access and current limits
- The public detector is currently free to use and does not require sign-up.
- Text must contain at least 50 meaningful characters and may contain up to 50,000 characters.
- Supported uploads are PDF, DOCX, TXT, and RTF files up to 5 MB.
- For anonymous visitors, the current application limit is 30 analysis requests per IP address in a one-minute fixed window. A rejected request includes a retry time. Limits may be adjusted to protect availability and prevent abuse.
Technical and result data
We may process limited technical request data, such as an IP address, timestamp, browser or request details, to deliver and protect the service, apply rate limits, and troubleshoot errors.
The metadata of each analysis — the fields listed above, never the text — is stored in the site’s WordPress database and is deleted automatically after 90 days, like the request logs. Separately, historical non-content records created before the deployment of WordPress plugin version 1.1.1 on August 30, 2026 remain in the WordPress database until a separate retention decision is implemented. Those historical records may include a random analysis identifier, result values, analysis settings, a timestamp, and a numeric WordPress user ID; public requests used user ID 0.
The reviewed WordPress application code does not write raw submitted text, extracted text, file contents, a text hash, or an IP address into those historical records or into the per-analysis metadata. Submitted content still passes through the analysis backend and hosting or security infrastructure, where technical logs may be created. We have not verified fixed deletion periods for hosting, Cloudflare edge, or security logs, and this policy does not claim that those systems never store content or use it for model training.
Retention
Request logs are deleted automatically after 90 days. After that we keep only daily totals that cannot be linked to any person. Our server backups also contain these logs and are replaced on a rolling basis, so a deleted log can remain in a backup copy for up to about two weeks.
- In the normal upload flow, PDF, DOCX, and RTF files are read from PHP’s request-scoped temporary location and explicitly deleted before extracted text is returned. PHP also removes request upload files at shutdown. An abnormal process or infrastructure failure may delay physical cleanup beyond the normal response path.
- Temporary progress state contains status and timing data, not submitted text or results. It expires 10 minutes after creation. Expired files are removed on an authenticated later poll, when a later valid analysis starts, or by a WordPress cleanup task scheduled every 15 minutes. WordPress Cron is traffic-dependent, so physical deletion can occur after the 10-minute expiry and is not guaranteed at an exact minute.
- The application rate-limit identifier is a one-way site-specific token and its counter is short-lived for the active one-minute window.
- Historical non-content WordPress analysis records created before version 1.1.1 remain until a separate retention or deletion decision is implemented. The per-analysis metadata stored in the WordPress database is deleted automatically after 90 days.
- We have not published a verified fixed deletion period for hosting, Cloudflare edge, or security logs. Until those operational schedules are verified, do not submit sensitive content.
Analytics and cookies
Google Analytics is not currently active. Cloudflare Web Analytics and network security services may process cookieless, aggregated usage, performance, and security signals. Hosting and security providers may also set strictly necessary cookies in limited circumstances, such as bot or security checks. Advertising, including Google AdSense and the cookies it uses, is covered in the Advertising section below. See the Cookie Policy.
Advertising
Status: advertising served by Google AdSense has been shown on this site since September 17, 2026, the first date our records show ads being displayed. Google’s advertising code and its consent tool set cookies in your browser; the ones we have observed are listed in the Cookie Policy.
- This site may display advertising served by Google AdSense and, through it, by other third-party vendors and ad networks.
- Third-party vendors, including Google, use cookies to serve ads based on a user’s prior visits to this website or other websites.
- Google’s use of advertising cookies enables it and its partners to serve ads to users based on their visits to this site and/or other sites on the internet.
- Users may opt out of personalised advertising through Google Ads Settings, and may review vendor opt-outs at aboutads.info/choices and youronlinechoices.eu.
- Where required — the European Economic Area, the United Kingdom and Switzerland — consent for advertising cookies is collected through a consent management platform before personalised ads are served.
- Advertising never receives the text you submit for analysis. Ad vendors receive only the ordinary page-request signals described above.
Advertising is not allowed to influence what the detector reports. Scores, bands and thresholds are produced by a frozen engine that has no connection to any ad system, and no advertiser can change, buy or suppress a result. See the Cookie Policy for the cookie inventory and the Terms for the advertising clause.
Contact and updates
For privacy questions or requests, use our Contact page or email [email protected]. We will update this page when data flows, providers, retention periods, analytics, advertising, or service limits materially change.