One of the main design constraints behind BenchReport was keeping Touchstone measurement contents off an application server. The browser reads selected S1P/S2P files with the File API, then parsing, complex-value conversion, plotting, limit evaluation and report generation happen client-side.
The privacy claim is deliberately narrow: the site itself is hosted normally and aggregate analytics can record a page visit, but the contents of selected measurement files are not uploaded to BenchReport. The built-in filter demo is synthetic, so the complete workflow can be evaluated without supplying any data.
The current parser supports common Touchstone 1.0-style S1P/S2P files in DB/angle, magnitude/angle and real/imaginary representations. It rejects malformed rows and evaluates limits only at samples actually present in the file there is no hidden interpolation at band boundaries.
If you work with RF measurement data, I would value feedback on what evidence a generated report needs to be genuinely reviewable. Guided demo: https://edwarddeakin06-maker.git...
