Privacy posture
Scrutinix keeps history in the browser and avoids storing raw URLs in server logs.
The server still has to process submitted URLs to query providers and complete a live analysis, but the application is designed so your saved history and shareable snapshots remain client-side wherever possible.
History
IndexedDB only
Completed scans are stored locally on your device, and clearing that archive removes the client-side copy unless you use the immediate undo.
Logs
Hash-oriented
Operational logs keep scan IDs, timings, cache state, and hashed URL context rather than the original raw URL string.
Sharing
URL snapshot
Share links embed a browser-generated snapshot in the URL itself. They are not persisted to a server-side share database.
What stays local
History and shared snapshots are client-managed.
Completed scans are stored in IndexedDB on your device only. Shareable links are generated in the browser by encoding a small snapshot into the URL itself, so there is no server-side share store to manage or breach.
What the server still does
Submitted URLs must still be processed on the server to query providers, compute the verdict, and stream the results back to the browser. That processing is necessary for the product to function.
Logging boundary
Operational logs capture scan identifiers, cache behavior, timing, and hashed URL context rather than the original raw URL string.
Local clearing
Clearing history removes the browser-side archive. The UI exposes an immediate undo so accidental wipes can be reversed in the same session.
Shared links
Shared links are convenient, but they represent a snapshot taken in the browser at a point in time. Running a fresh scan verifies the target against current provider responses.