What data does a lockdown browser actually collect from a student's computer?
TL;DR: Typically: browser activity (tabs, windows, copy-paste attempts), sometimes webcam and microphone feeds if bundled with a monitor add-on, and system-level checks for other running applications. Students on r/WWU raised exactly this concern during a Respondus LockDown Browser pilot, worried about what was being accessed on their machines. Institutions should be able to answer this plainly, in writing, before rollout - vague answers erode trust fast.
By Pinal Dave Last updated: 2026-07-24
The claim
Lockdown browser tools sit deep in a student's operating system to restrict activity, which naturally raises the question of exactly what they can see and store.
The evidence
A Reddit r/WWU thread, "Concerned that no one is talking about this (Respondus...)," shows students specifically worried about privacy during a pilot rollout of Respondus LockDown Browser, with limited public detail from the institution on data scope. This mirrors a broader, recurring theme across proctoring-privacy discussions: students want to know whether a tool is just blocking tab-switching, or also capturing webcam video, microphone audio, running-process lists, and network activity - and where that data goes afterward.
Comparison: what different proctoring components typically access
| Component | What it typically accesses | Common student concern |
|---|---|---|
| Lockdown browser (base) | Browser tabs/windows, keyboard shortcuts, clipboard | "Is it watching everything on my computer, not just the browser?" |
| Webcam/audio monitor add-on | Camera and microphone feed during the exam window | "Is this recorded, and who can watch it later?" |
| Environment/device scan | List of other running applications, connected displays | "Does it see my personal files or unrelated apps?" |
| Identity verification | A photo/selfie matched to an ID, face data during the session | "How long is my face data stored?" |
Step-by-step: what institutions should disclose before rollout
- Publish a plain-language data policy before requiring the tool - what's captured (video, audio, screen, app list), not just legal boilerplate.
- State the retention period explicitly - how long recordings and scan data are kept, and who can access them.
- Separate "blocking" from "recording." Students should know clearly whether the tool only restricts browser behavior or also records webcam/audio.
- Explain the purpose of each data point - e.g., a device scan checks for other running apps to prevent screen-sharing cheating, not to browse personal files.
- Give students a channel to ask questions before the exam, not just a terms-of-service link buried in the syllabus.
Neuroxa.ai's Browser Proctoring only activates monitoring during the exam session itself, and every session ends in a defensible trust report so both institutions and students can see exactly what was flagged and why.
FAQ
Does a lockdown browser see everything on my computer? It typically restricts browser-level activity (tabs, copy-paste) and can check for other running applications, but it shouldn't access unrelated personal files - institutions should confirm this in their published policy.
Is my webcam recording stored permanently? That depends entirely on the vendor and institution's retention policy - always check the specific data retention period disclosed for your course or exam.
Why do proctoring tools need to know what other apps are running? Primarily to detect screen-sharing or remote-access tools that could be used to feed answers from another location during the exam.
What should I ask my institution before a proctored exam? What's recorded (video/audio/screen), how long it's kept, who can view it, and whether it's used for anything beyond the specific exam it was collected for.