Which Third-Party AI Detection Services Have Strong Privacy Policies and Don't Store My Work?

A privacy policy can promise no retention, no model training, and no third-party sharing independently, so a tool that keeps your file for 30 days but never trains on it is making a different promise than one that deletes immediately. Treating "we don't store your work" as a single binary is the most common mistake readers make when comparing detectors, and it is the reason two services can both advertise privacy while behaving completely differently with your document.

The first split is between "we don't store your text" and "we don't use your text to train models." One can be true without the other. A service might delete your file after processing yet still use derived data to improve its detection models, and a policy that only addresses retention will not tell you that. Read for both sentences separately, and if only one appears, assume the other is unaddressed rather than denied.

The second split is the retention window. Look for an explicit deletion window; "we retain as long as necessary" is vague and gives you nothing to hold the vendor to. A stated period — 30 days, 90 days, or deletion on request — is a commitment you can point at later. A policy that describes retention only in terms of business need has effectively reserved the right to keep your document indefinitely, because "necessary" is defined by the vendor, not by you.

The third split is the carve-out. Originality.AI's policy treats "aggregated or de-identified" data as not personal information, which means that category can sit outside the protections you assumed applied to your essay [1]. De-identification is not the same as deletion, and aggregated data derived from your document is still derived from your document. If a policy protects "personal information" but excludes "de-identified data" from that definition, the practical question becomes how the vendor de-identifies and whether the result is still traceable to you.

Two further distinctions matter when you are reading an institutional or commercial account. Writer's policy applies as controller for personal accounts, but a separate Platform Services Agreement governs commercial processing — so the terms you read on the consumer page may not be the terms that apply to your account [2]. If you are submitting through a university licence or an employer's seat, the consumer policy may be the wrong document entirely. And compliance badges such as FERPA, GDPR, or SOC 2 must be verified in the policy text, not on the marketing page, because a badge on a landing page is not a legal commitment. A badge tells you what framework the vendor claims to follow; the policy text tells you what the vendor actually promises to do with your file.

There is also a jurisdictional question that rarely appears in comparison articles. A policy can be perfectly clear about retention and still place your document under a legal regime you did not choose, which affects what happens if you later want it removed. Reading the governing-law clause alongside the retention clause takes two extra minutes and answers a question most readers only think to ask after something has gone wrong.

A non-repository check runs your document through detection without depositing it into the comparison database that future submissions are matched against, which is the difference between a private preview and permanently contributing your work to a corpus. This is the single most consequential distinction for a student, because repository submission is the one form of "storage" that can follow your text into someone else's similarity report.

The mechanism is worth understanding because it explains why the distinction is not semantic. Similarity detection works by comparing a submitted document against an index of previously submitted documents. When a service adds your file to that index, your text becomes part of the comparison set for every future submission processed by that service. Your essay does not merely sit on a server; it becomes evidence that can generate a similarity match against a stranger's work, or against your own work if you reuse a passage in a later assignment. A non-repository check performs the comparison without performing the deposit.

Turnitin0's file is checked without being added to Turnitin's student paper database, and reports are not shared with third-party databases. Users can delete files from their account, and there is no subscription tying you to ongoing storage. Those three facts together are what make the non-repository design meaningful rather than decorative: the check happens, the report comes back, and your document does not become part of the corpus that later submissions are compared against.

Each order includes two downloadable PDFs in one checkout — a Turnitin AI detection report and a similarity/plagiarism report, identical to what professors see in their LMS. That matters for the privacy question in a practical way: you are not handing your text to a third party to obtain a proxy signal, you are obtaining the same artifact your institution would generate, and then you can delete your file. The alternative — asking a friend, a tutor, or an informal service to "run it through Turnitin" — typically involves handing your document to someone whose retention practices you cannot inspect at all.

One display detail is worth knowing before you read your own report. Turnitin shows *% instead of an exact percentage when AI detection is below its 20% confidence threshold. Those are low-confidence signals, not confirmed AI use, and a *% result should not be read as a hidden number. Understanding this before you open the PDF prevents the most common misreading of a Turnitin AI report, in which a student interprets an asterisk as a suppressed score rather than as a statement that the detector lacks confidence.

Verify by reading the live policy for retention language, training language, and deletion rights rather than trusting the landing page, because policy URLs change and marketing copy is not a legal commitment. The research behind this article is itself an example of why: the GPTZero, Copyleaks, and Turnitin policy URLs attempted during research returned 404 or 403, so any claim about their retention must be re-checked at the live URL before it is repeated.

Start with the date. Originality.AI's policy is dated "Last Amendment: June 17, 2026," and it invites institutions to discuss "data-minimization options" for a "privacy-restricted implementation" [1]. Writer's policy effective date is April 17, 2026, superseding June 3, 2024 [2]. Cite the "last amended" date for every tool you compare, because policies change frequently and a review written against an older version can be wrong within months. A comparison article that does not date its sources is telling you something about its own reliability.

Then search the policy text for four phrases: "retain," "train," "third party," and "delete." If a policy does not contain a clear statement on training, absence is not permission — it means the question is open. If deletion is described only as an account-closure right rather than a per-file action, your practical control is weaker than it sounds, because closing your account to remove one document is a disproportionate remedy. The strongest formulation is a per-file deletion right that does not depend on terminating your relationship with the service.

A fourth check is whether the policy distinguishes between data you submit and data the service generates about you. Usage logs, device identifiers, and payment records are separate categories from your document, and a policy can be generous about one while being silent about the other. If your concern is specifically the text you paste, find the sentence that addresses submitted content and read only that sentence first.

The trust gap this reader feels is documented. A user in r/duckduckgo noted that the front-facing message "implies that the model providers don't retain information" — the exact gap between promise and policy [3]. That is the right instinct. A user-facing sentence is not a retention schedule, and the only reliable test is whether the policy states non-repository checking, no third-party database sharing, and user-initiated deletion. If a vendor's privacy page makes a claim that its legal policy does not repeat, treat the legal policy as the operative document.

There is first-party evidence that the reports reflect real detection behavior rather than manufactured flags. In TT0-2026-0005, 504 human-written PLOS graduate essays — 135,712 words across 18 majors, non-ESL — returned 100.0% word accuracy with no word-level false positives. That is evidence the check does not manufacture flags on genuine human writing, which is the failure mode that makes a detector's output useless to you even when its privacy policy is sound. A service that protects your document but misclassifies it has solved half your problem.

For a reader whose actual goal is "what will Turnitin say," the only way to answer the question is to run Turnitin, which is the conclusion this comparison reaches directly: the only service that runs your document through Turnitin itself. That distinction is not marketing language but a fact about how the market is built, and it is the same reason the privacy question in this article has a narrow answer rather than a broad one.

The workable path is therefore to obtain the real artifact: two downloadable PDFs in one checkout, a Turnitin AI detection report and a similarity/plagiarism report identical to what professors see in their LMS. One display detail matters before you read any score — Turnitin shows *% instead of an exact percentage when AI detection falls below its 20% confidence threshold, so those asterisk results are low-confidence signals rather than precise measurements. For the reader weighing whether any paid checker is trustworthy enough to rely on, the documented position is that you are reading Turnitin, not comparing a guess against it.

Where turnitin0 Fits This Reader's Need

Turnitin0 addresses the privacy question at the point of decision by combining non-repository checking, no third-party database sharing, and account-level file deletion with a pre-submission preview that matches what professors see. If your requirement is "I must run this unpublished text through a detector and I need to know what happens to it afterward," those three commitments are the ones that answer the question.

The mechanics are straightforward. Upload .docx, .pdf, or .txt; English only; word count greater than 300 and less than 30,000; file size under 20 MB. Turnaround is under 15 minutes in 98% of cases, most orders finish within 5–15 minutes, and in rare queue spikes delivery is still guaranteed within 30 minutes. New users sign in with Google and can pay with PayPal or a prepaid balance. There is no subscription, which is itself a privacy-relevant design choice: nothing about the service depends on keeping your account active or your files resident.

Pricing follows the same pay-per-use logic. A single Turnitin check is $3.80, and prepaid packs run 2 scans for $6.50, 5 for $15.00, and 10 for $27.50, with packs valid 100 days; the 10-check pack works out to $2.75 per check. The AI humanizer is $2.00 per 1,000 words, rounded up to the next 1,000-word block, with prepaid word packs starting at $18.00 for 10,000 words that never expire. Against the listed third-party checkers, that is the lowest single-check price and the lowest bulk per-check rate, with no subscription — and because nothing renews, there is no billing relationship quietly keeping your account and files alive.

Adoption is not proof of privacy, but it is context for whether the service is real. Turnitin0 reports 100,000+ Turnitin AI and similarity reports delivered, 20,000+ students worldwide across the US, UK, Canada, Australia, New Zealand, and Ireland, and 4.9/5.0 satisfaction. On Trustpilot, the profile shows a TrustScore of 4.3 / 5 with the label Excellent, 9 reviews in the last 12 months, and 89% five-star with no negative reviews at capture; the page also notes the company has not recently invited customers, so those reviews may not be representative [4]. The recurring themes in those reviews are speed, ease of use, downloadable AI and similarity PDFs together, and reports described as authentic.

The honest summary is that turnitin0 answers the three-part test this article sets out, and that the wider market does not yet have a verified answer. That is a reason to read policies rather than a reason to assume the worst about every competitor. If a vendor you are considering publishes a policy that states non-repository checking, no third-party database sharing, and per-file deletion, it passes the same test on the same evidence.

The Structural Reason No Third-Party Detector Can Match Turnitin

The reason a privacy-conscious reader ends up comparing detectors at all is usually that they want a preview of an institutional verdict, and on that question the market splits cleanly. Turnitin is institution-only software sold to schools rather than individuals, so every consumer tool is a proxy running its own proprietary model and returning its own verdict — a prediction of Turnitin, not Turnitin's own output. That structural fact is why a third-party score can correlate with an institutional result without ever being the same result.

What to Do If You Need a Trustworthy Preview Before Submitting

If you need a paid checker whose results you can actually trust before submitting, the honest answer is that no third-party tool reproduces Turnitin's proprietary verdict closely enough to serve as a proxy — which is why the practical recommendation is to read Turnitin's own output rather than a guess at it. Turnitin's model is proprietary, consumer checkers such as ZeroGPT, GPTZero, Quillbot, and Grammarly use different models that produce inconsistent results, and no source validates any paid checker against Turnitin's actual score output [7]. That absence is itself the finding.