Privacy

What the workbench does not store or send

The /clean page has no processing POST endpoint, account, result URL, action telemetry, analytics, ad provider, consent-management script, remote font, model API or remote provenance fetch. Its browser policy forbids network connections after the page and its same-origin versioned assets load.

Working text, findings, context, local filename, selections, cleaned output, receipt and content-derived hashes are not written to cookies, localStorage, sessionStorage, IndexedDB, the Cache API or a service-worker cache. They are not placed in a URL, browser history, application log or error-reporting request. Browser/CSP reporting is off on the workbench.

Ordinary page requests and operational logs

Like any website, the host and any delivery network receive request metadata needed to return a page or static asset. That can include time, IP address, requested path, response status, referrer and user-agent information. Security and operational logs may retain that metadata under the host or infrastructure provider’s configured log window.

Public pages, machine-readable routes and the workbench do not start a visitor session or set a session or cross-site-request-forgery cookie. The separate owner-only /ops area uses its own authenticated session when an operator opens it.

The workbench never puts text or result state in its path or query. The site does not intentionally add working text, findings, receipts, filenames or content-derived values to those logs. Aggregate requests to /clean may be counted operationally, but actions inside the workbench are unavailable rather than reported as zero.

Advertising, consent and measurement

Advertising and consent-provider delivery are disabled at launch. No ad, analytics or consent client is loaded on the workbench, legal pages, contact page or machine-readable routes. The current workbench sends no event when you type, inspect, find, select, clean, copy, download or reset.

If advertising is activated later, it may appear only on substantive editorial pages after provider approval, reviewed identifiers, required consent configuration and a notice update. Working text, code points, findings, provenance state, receipt and content-derived audience signals may not be sent to an advertiser. Advertising remains forbidden on /clean and every result or error state.

Reset, navigation and limits of browser control

Start over terminates the worker, clears the application’s references and revokes generated Blob URLs. Leaving the page performs the same cleanup. A back/forward-cache restoration forces an empty workbench instead of restoring prior input.

Those actions cannot control everything on your device. The browser, operating system, clipboard manager, garbage-collected memory, swap, crash/session recovery, extensions or saved downloads may retain copies outside the application’s control. Use a device and browser environment appropriate for the sensitivity of your material.

Contact email

The site provides a mailto: link and no support form. Using it leaves the site and gives your and our email providers your address, message headers and content. Do not email working text, findings, cleaned output or receipts.

The property mailbox deletes routine messages within 90 days. An active support or security matter and a legal hold are exceptions. Those manual exceptions, the mailbox provider and the erasure step are declared in the property’s retention inventory.

Your choices and questions

You can use the editorial pages without opening the workbench, stop a run, reset local state, avoid the email link and delete downloads you created. Because there is no account or server-side workbench history, the site has no saved inspection record to retrieve.

For a privacy or erasure question, use the instructions on the contact page without including working text. This notice will be revised before a material change to workbench egress, telemetry, storage, advertising or consent behavior becomes active.