Is Illuminate Lockdown Browser Invading Student Privacy? What Really Happens During Testing
The software footprint varies depending on whether a student uses a school-owned Chromebook or a personal laptop. The technical architecture dictates how deep the security software reaches into system memory and what telemetry leaves the device.
| Architecture Type | Core System Access Level | Data Recorded & Transmitted | Primary Failure Mode |
|---|---|---|---|
| Chromebook Kiosk Mode (Managed Google for Education) | Sandboxed Single-App Mode; bypasses user login entirely. | Assessment input, session timestamps, and focus-loss logs. No camera feed unless explicitly authorized. | Cached profile sync errors; fails to exit kiosk mode on network drop. |
| Desktop Standalone (Windows / macOS via Respondus) | User-level system hooks; suppresses OS hotkeys, manages process tables. | Running process manifests, peripheral device handshakes, window focus events. | Antivirus false positives; permission collisions with audio/video drivers. |
| Integrated Automated Proctoring (LockDown + Video Monitor) | Continuous peripheral access (AV stream, system audio, input devices). | HD video of student workspace, ambient audio, biometric movement flags. | False cheating accusations caused by lighting, eye ticks, or family interruptions. |
On Chromebooks managed through Google for Education, Kiosk Mode is lightweight. It runs outside any specific student profile, meaning the test application cannot see personal Chrome browser bookmarks, history, or saved passwords from a student's personal account. The session exists in isolation and clears its memory on exit.
The Windows and Mac installers operate differently. They require installation directly onto the host operating system. While they run with standard user privileges rather than administrative rootkits, they actively scan the process list to identify running applications like Discord, Slack, Spotify, or TeamViewer. If an unauthorized app runs in the background, the test refuses to launch until the student closes that specific executable.