Read this before interpreting a result
Limitations
This is a hidden-character inspector with selective local cleanup. It is not a universal AI watermark remover, an AI detector, a provenance validator, a document metadata cleaner or a rewriting service.
Mechanisms outside the launch
The processor does not inspect or remove statistical token-selection watermarks such as SynthID Text. It does not score human versus AI authorship, make text “undetectable,” guarantee acceptance by a school or employer, or paraphrase language to influence a detector.
It does not accept DOCX, PDF, RTF, EPUB, images, audio, video, archives, URLs or remote content. It therefore does not remove file properties, XMP, comments, visible overlays or container metadata. Plain-text and Markdown file profiles are limited to strict UTF-8.
Provenance limits
The C2PA check is structural and bounded. It does not verify signatures, trust chains, claims, signer identity or remote resources. A possible, malformed or recognized-but-unverified structure is protected and stops cleanup; that wording must not be read as cryptographic validation.
A “not found” preflight means the covered structural probe completed without finding one of its declared forms. It is not a promise that no provenance mechanism exists anywhere, and it does not authorize removing provenance with another tool.
Character-policy limits
Context can be language-specific. The launch preserves bidi and joining controls, valid emoji sequences, variation selectors, combining marks and unknown format characters rather than claiming a universal safe deletion. There is no normalization or semantic understanding of the prose.
Inspection can reveal a scalar and describe known Unicode properties, but it cannot recover text already lost during an earlier bad decode. A U+FFFD replacement character is evidence of that loss, not an edit that can reconstruct the original bytes.
Privacy and browser limits
The application does not upload or intentionally persist working text, but browsers and operating systems manage memory, swap, clipboard history, crash/session recovery and downloads outside the page’s control. Anyone handling unusually sensitive material should account for the device and browser environment too.
A browser extension, compromised device or modified local build can violate assumptions the delivered page cannot enforce. The utility’s guarantees describe the reviewed production code, response policy and captured network behavior—not every program on the visitor’s computer.