Your device signals belong in your browser.

Local diagnostic processing

Axes, buttons, pointer events, key events, screen facts and hardware capabilities are processed by JavaScript inside the active tab. Camera and microphone tests request browser permission only after an explicit action. Video is previewed locally, audio is measured as transient level, waveform and spectrum data, and neither stream is uploaded. The optional microphone recorder captures at most five seconds only after another explicit action. Its Blob, camera luminance samples and FFT buffers remain in active page memory.

Controlled SNR, acoustic latency and harmonic checks use a local AudioContext. The webcam bitrate protocol connects two RTCPeerConnection instances inside the page and reads the local sender's byte counters; no camera media is sent to an InputProof server. Temporary decoded receiver tracks are stopped when the eight-second protocol finishes.

The permission verifier may retain the Permission API state, request duration, Track label and readyState, number of visible device labels, classified DOMException name, secure-context state, first-frame latency, and whether every stopped Track reached ended. First-frame evidence is timing and state only. It does not retain a stream, sample, frame or opaque device ID.

Aggregate product analytics

Future production analytics may count low-cardinality events such as diagnostic started, completed, inconclusive or report exported. Allowed events must never include raw device values, keystrokes, images, audio, free text, complete device identifiers or a persistent user ID.

The current MVP does not include a custom event endpoint.

Local reports

JSON, CSV and printable reports are assembled in the browser. They include a protocol ID, schema version, capture time, summary metrics, browser runtime environment, capability state and limitations. Runtime metadata is report-local and is not turned into a stable fingerprint or uploaded. Reports omit raw per-frame input, audio, video, camera stills and opaque device IDs. The keyboard JSON can include the latest 12 transitions entered while its focused test surface is active; it is created only after the user selects Export evidence.

The Local Device Report reads existing low-dimensional history from this browser and groups the latest entry for each protocol. Opening or refreshing that report does not run a device scan or create a new history entry. Its combined JSON export contains saved summaries and report identifiers, never the raw signals that produced them.

Report Diff accepts one exported InputProof Combined Device Report. The file is size-bounded, schema-validated and compared in page memory. It is not uploaded, merged into local history or retained after the page closes. Exporting a Diff writes only the resulting summary comparison to the download location you choose.

Local microphone recordings can be replayed in the tab, but audio bytes are never embedded in Evidence. Re-recording revokes the previous Blob URL and leaving the page releases the remaining in-memory URL. Output-device selection and the 1 kHz return-path probe remain local; the probe exports only its expected and observed frequency summary. Controlled SNR, acoustic round-trip and THD exports contain summary values, not sampled audio. Permission metadata can be included to show that a real browser Track was granted and later released.

A camera still can be downloaded only through the explicit Capture and Download actions. The still remains in page memory, is not embedded in the JSON report and is cleared when the test restarts or the page closes. Fixed-window frame delivery, low-dimensional image signals and local WebRTC encoder bitrate may appear as numeric summaries; no image or video frame is embedded.

Optional local baseline history

Test completion and report export do not save history. A summary is stored only after you enable the per-session opt-in toggle and select Save local baseline. The opt-in state is not remembered.

History uses the `inputproof-history-v1` browser-storage key, keeps at most 20 entries per protocol for 90 days, and contains only low-dimensional summary metrics, protocol version, capture time and coarse browser/platform family. It excludes raw input, key logs, audio, video, images, complete user agents and device identifiers.

Each suite can export or clear its own saved entries. Clearing browser site data removes all InputProof history. The combined Device Report is a read-only view of the same storage key and does not maintain a second hidden history store.

Seven protocol-specific repeatability views are derived locally from compatible saved summaries. Their thresholds, aggregate results and excluded-run counts are included only when you export that protocol history. Compatibility labels are coarse and do not create a stable physical-device identifier.

Advertising and affiliate links

The MVP ships with advertising and affiliate recommendations disabled. If enabled later, the privacy notice and consent behavior must be updated before production release. Commercial links will be labeled and will not alter diagnostic verdicts.

Support feedback submissions

The Feedback page submits only after you press Submit. It sends your selected category, title, description, email address and coarse browser context such as page path, browser family, platform, language, viewport bucket, color theme and timezone. It does not attach raw input events, camera frames, microphone audio, screenshots, local history or exported reports.

Do not include passwords, access tokens, proxy credentials, private logs, customer data, payment data or health information in the feedback text.

Your control

Close or reload the tab to clear the current in-memory diagnostic. Active camera and microphone tracks are stopped when their tests stop or the page closes. Audio recording URLs and media streams are also released on page exit. Downloaded reports remain only where you save them. No account is required.