Your test results never leave the device
Every hardware test runs in the browser on the Chromebook in front of you. Nothing about the results is transmitted.
- Camera images are analysed in the page and discarded. Frames are measured for brightness, contrast and motion, then thrown away. No image is stored, uploaded or shown to anyone but the person at the device.
- Microphone audio is analysed in the page and discarded. The speaker test listens for a tone it just played. No recording is kept or sent.
- Keystrokes are used only to light up the key map. Which key was pressed is never recorded as text or transmitted.
- Results are yours. They exist in the browser tab until you close it. They're saved only if you press "Copy results" or "Print".
On managed Chromebooks the tool can read the device's serial number, asset ID and location from the enterprise policy your administrator already set. That information stays on the device — it appears in the report you copy or print, and is never transmitted by this tool.
What is collected: anonymous usage analytics
The site uses Google Analytics 4 to understand which tests are used and where they fail, so the tool can be improved. This is the only thing that leaves the device.
What's sent:
- Page views.
- That a test run started and finished, how long it took, and the build version.
- For each check: its name (for example
keyboard), its verdict (pass, warn, fail, skipped), and whether it was automatic or guided.
- Counts of how many checks passed, warned, failed or were skipped.
- Whether the run was in a kiosk session, and whether the managed agent was present.
- Standard Google Analytics data: approximate location derived from IP address (the IP itself is anonymised), browser and device type, and analytics cookies.
What is never sent:
- Serial numbers, asset tags, hostnames or device locations.
- The detail text of any result — the readings, measurements and device names behind a verdict.
- Camera images, microphone audio, or anything typed.
- Names, email addresses, or anything identifying a student or member of staff. We never ask for them.
The verdict of a check is sent, but not what produced it. Analytics can show that the headphone test failed on 40 devices this week; it cannot show which devices, in which school, or what they reported.
Turning analytics off
- Ask us to exclude your domain. If your district would rather send nothing at all, say so and we'll exclude it.
- Add
?analytics=off to the URL. Verity Bench honours it and sends no events.
- Do Not Track is honoured. If your browser sends the signal, no events are sent.
- Block it at the network. The tool works fully with
googletagmanager.com blocked — analytics simply doesn't load, and no test behaviour changes.
For district privacy reviews
Points that usually come up:
- No accounts, no sign-in, no student data. The tool has no login and no database of people.
- No third-party requests except analytics. Fonts, styles and all test code are served from this domain. Blocking analytics leaves the tool fully functional and entirely self-contained.
- The managed extension reads device identity through
chrome.enterprise.deviceAttributes, which only works for extensions your administrator force-installs. It reports to the page on the same device, not to us.
- Analytics retention follows the retention period configured in Google Analytics.
If something here doesn't match what you observe, that's a bug worth reporting — get in touch.
