History stays in the browser.
The server processes submitted URLs to run a live analysis, but saved history and shareable snapshots remain client-side.
What stays local
Completed scans are stored in IndexedDB on your device only. Clearing history removes the browser-side archive, with an immediate undo in the same session.
What the server does
Submitted URLs are processed on the server to query providers, compute the verdict, and stream results back. That processing is necessary for the product to function; nothing about your history is stored server-side.
Logging
Operational logs keep scan identifiers, timings, cache state, and hashed URL context rather than the original raw URL string.
Shared links
Share links embed a browser-generated snapshot in the URL itself — there is no server-side share database. A snapshot is a point-in-time record; run a fresh scan to verify against current provider responses.