Privacy boundary
AI Detector privacy note
This page describes how the current AI Detector version handles detection text, imported files, local history, and website resources. Last reviewed: 2026-08-27.
Where is detection text processed?
Text that you paste or import is processed in the current browser. It is not posted as a detection request to a detection server. The website and browser still need network access to load the page, scripts, and resources required for the analysis; “no detection-server upload” does not mean the entire website is offline.
Imported files and local history
TXT, Markdown, DOCX, and text-based PDF files are read and extracted on the current device. Recent analysis summaries are stored in this browser’s local storage so you can revisit them; the product interface lets you clear that history. On a shared device, follow your own device and account security practices.
Boundary for normal website requests
Loading a website and static resources creates ordinary web requests. A CDN, hosting provider, browser, network operator, or organization network may handle request metadata under its own policies. The product boundary described here is that source text used for detection is not placed in a detection request or used as input to a detection server.
Your responsibility
Local processing does not replace device encryption, browser security, malware protection, access controls, or an organization’s data-handling policy. Before processing confidential material, confirm that this workflow is permitted by your policy.