Privacy

What USN Parser collects, what it does not, and how forensic data you submit to it is handled. Short answer — it never leaves your machine.

File handling

When you drop a $UsnJrnl:$J or $MFT file onto this site, the file does not leave your device. The parser is a WebAssembly module running in a Web Worker on your browser. There is no upload endpoint, no server-side parsing, no cloud storage.

You can verify this in two ways:

  • Network tab. Open your browser's developer tools, drop a file in, click Parse. The Network tab will not show a single request to usnparser.com after the page itself is loaded. The records come back from the worker.
  • Source code. The repository at github.com/Cyber-Experts/usn-parser is the same code that runs in your browser. The worker and the wasm artefact are static files served from /wasm/ and /workers/.

Analytics

The site uses Vercel Web Analytics and Vercel Speed Insights for aggregate, anonymised usage and performance data. These services record page views and Core Web Vitals — no cookies, no IP storage beyond aggregation, no cross-site tracking. They do not see the content of files you analyse.

Logs

Vercel, our hosting provider, keeps server-side request logs for ~24 hours by default for operational reasons. Requests are recorded as HTTP method, path, status code, and a coarse client IP. The static asset and the wasm binary are the only resources fetched after the initial page load — your file content is not visible to Vercel because it is never transmitted.

Cookies

We do not set any cookies.

Contact

If you have a privacy question, open an issue at github.com/Cyber-Experts/usn-parser/issues.