Is LockDown Browser Safe to Install on Your Mac? (2026 Honest Review)

Last updated 2026-05-02 · LDBypass Editorial

The technical safety answer

From a malware / system-integrity perspective, LockDown Browser is unambiguously safe to install on your Mac:

• Notarised by Apple. Every release of LDB 2.x has passed Apple's notarisation pipeline, which scans the binary for known malware signatures and verifies the codesign chain. You can verify this yourself: spctl -a -vv /Applications/LockDown\ Browser.app reports "Notarized Developer ID".
• Signed with Developer ID. Authority is "Developer ID Application: Respondus, Inc." - a verified, traceable entity. Compare to the unsigned-or-self-signed apps that distribute as "untrusted developer" warnings.
• No kernel extensions. LDB 2.x runs entirely in userspace. Older 1.x had a kext on Big Sur and earlier; the modern version does not. You can verify via kextstat | grep -i respondus - should return empty.
• No LaunchAgents or persistence by default. Some institutional MDM deployments push a LaunchAgent that LDB installs alongside; absent that, LDB is not running between exams.
• Hardened runtime. The .app is signed with hardened runtime + library validation, the same protections Apple requires for App Store apps.

Where the privacy concern actually lives

"Safe" in the privacy sense is a separate question. Respondus Monitor (the optional add-on enabled by your instructor):

• Records your webcam for the duration of the exam.
• Records your microphone for the duration.
• Captures periodic screenshots of your screen.
• Uploads the recording to Respondus's cloud storage (US-based AWS per their privacy policy).
• Retains the recording for the period your institution configures (default 5 years).

Whether this is "safe" depends on your privacy threshold. The recording is associated with your name and student ID via your LMS; it is reviewable by your instructor and Respondus support staff under specific conditions. For some students, that's acceptable; for others, it isn't.

What you can verify yourself before installing

1. Confirm the notarisation: spctl -a -vv /Applications/LockDown\ Browser.app after install.
2. Check the codesign authority: codesign -dvvv /Applications/LockDown\ Browser.app - confirm "Authority=Developer ID Application: Respondus, Inc."
3. Inspect what files it touches: fs_usage -w -f filesys "LockDown Browser" in Terminal during install (some patience required to read the output).
4. Verify network endpoints: nettop -p $(pgrep "LockDown Browser") during exam.

What to do if you're uncomfortable installing it

Legitimate options:

1. Contact your instructor. Most accept that some students will choose alternative arrangements. Common options: in-person exam on a university computer, exam without Monitor enabled, or a different proctoring tool.
2. Use a borrowed Mac. Install LDB on a Mac that doesn't contain your personal data. Limits the privacy surface to that specific session.
3. Document the concern. Most universities have a process where the dean of students mediates between instructor integrity requirements and student privacy preferences.
4. Take the exam in person. Universities almost always offer this as an alternative when remote proctoring is documented as a barrier.

What "safe" doesn't mean

"Safe" does not mean "private". The technical safety bar (no malware, no kernel access, no file system snooping) is met. The privacy bar - what Monitor records and retains - depends on your assessment of Respondus's data handling, their security posture, and your institution's retention policy. See data collection and how long recordings are stored for those specifics.