How it works
One window. Drop, sanitize, review, export.
There is no wizard. The technician drops a zip, a folder, loose files or a SQL Server backup on the window, presses Sanitize and reviews what was found. The visible sanitized copy exists only after the residual scan passes and the review is acknowledged — the work happens in a quarantined job directory the technician cannot pick up off disk and send by mistake.
- Reads everything a support bundle contains — text and log files, JSON, XML, CSV, nested archives, and SQL Server
.bak backups restored through a local SQL Server instance. - The source is never touched —
bundle.zip becomes bundle.sanitized.zip, rebuilt entry by entry, never a mutated copy of the original. - Pre-flight before the job — what was dropped, what no parser recognises, whether a SQL Server instance is available, and a place to add site names, tag prefixes and project words no rule would catch.
- Same replacements next week — keep the job's vault and the next dump from the same site gets the same pseudonyms, so a vendor case can span several uploads.
- Scriptable — the same pipeline runs headless from the command line for scheduled or bulk use.