Private by design

A hardware test should collect the minimum evidence needed to answer the question.

DeviceOK separates sensitive live test input from ordinary site requests. Camera, microphone, keyboard and controller data should remain local whenever the browser can produce the result without uploading the raw input.

Camera
Frames are used in the browser test.

DeviceOK does not request camera permission until you start a camera test. Core previews, resolution/frame-rate checks and visual inspection happen in the page rather than requiring camera-frame uploads.

Microphone
Audio analysis and local recordings stay in the browser.

Permission is requested only for a microphone test. Level, channel and recorder tools use the selected browser media stream locally.

Keyboard / mouse / controller
Input events drive the live result.

Raw key sequences, pointer traces and controller state are not needed as server-side content to diagnose whether the browser receives the expected event.

Advanced hardware APIs
The browser controls device selection and permission.

WebHID, WebUSB, Web Serial, Web Bluetooth and Web MIDI availability varies by browser, OS and hardware. DeviceOK explains the requested capability before invoking a browser chooser where the API requires one.

Search
Your search text is sent to DeviceOK's search endpoint.

Search is server-backed so the knowledge base can grow without downloading tens of thousands of records into the browser. Do not paste passwords, private serial numbers, account tokens or other secrets into search.

Result sharing

Inspection reports are user-controlled

Guided checks can create a compact result summary for printing, copying or sharing. The share workflow should contain the diagnostic state you deliberately recorded—not raw camera footage, microphone audio or keystroke history.

Repair-shop summaryIncludes pass/attention outcomes and manual inspection notes you selected.
Print / Save PDFUses the browser's print flow so you choose the destination.
Share stateUses the report state needed to reproduce the checklist result; review it before sending it to another person.
Analytics principle

Measure product use, not sensitive test content

If analytics are enabled, the appropriate event is something like “webcam test completed” or “permission denied,” not captured frames, microphone recordings, raw keys or full controller traces.

Important boundary

The browser and hosting platform still make network requests

Loading DeviceOK, calling server-backed search and normal web delivery necessarily involve network requests and standard server/CDN logs. The local-processing statement applies to the sensitive device-test payload described above, not to every HTTP request made by the website.