One local browser session
How the inspector works
The utility is an anonymous browser-local workflow. The server delivers versioned code and page copy; the admitted text, findings, selections, output and receipt stay in browser memory for the current page session.
From input to inspection
You can paste or type text, or choose one local UTF-8 .txt, .md or .markdown file. The page enforces byte, UTF-16 and scalar ceilings before processing. File input is decoded strictly: malformed UTF-8 is refused instead of being silently replaced with U+FFFD.
A dedicated Web Worker receives one immutable run. It first performs the bounded C2PA structural preflight. If provenance is clear, it inventories Unicode scalars, creates bounded findings and returns a closed result envelope. Progress reports phases rather than an invented percentage.
- Choose typed text or one supported local file.
- Inspect text after the version and asset handshake completes.
- Read provenance and coverage before considering a change.
- Review visible tokens, explanations and proposed edits.
- Select only the occurrences you intend to remove.
- Clean selected items through a separately validated child run.
- Compare output and read the exact change receipt.
- Copy/download locally, then use Start over to clear application references.
What crosses the network
Loading the page and its same-origin static assets creates ordinary web requests. The workbench’s response policy permits no browser connection after load: connect-src is none, and the page includes no analytics, advertising, CMP, remote font, model API or provenance fetch.
There is no processing POST endpoint or result URL. The input does not appear in a query string, browser history, server log, cookie, localStorage, sessionStorage, IndexedDB or service-worker cache. Downloads and clipboard writes occur only after a user gesture.
Reset and browser boundaries
Start over terminates the active worker, clears the application’s references and revokes generated Blob URLs. Navigating away triggers the same destruction path. If the browser restores the page from its back/forward cache, the workbench mounts from an empty state rather than reviving prior content.
Those controls cannot erase copies already made by the operating system, clipboard manager, saved downloads, crash/session recovery, swap or browser memory management. The privacy page separates what the application controls from those platform limits.