LockDown Browser Leftover Files in ~/Library on Mac (What to Expect)

A drag-to-Trash uninstall of LDB on Mac leaves 200 MB to 5 GB of leftover files in ~/Library. The largest is the Group Containers directory holding Monitor recording buffers from past exams. Below: every leftover file, where it lives, what it contains, and which actually matter to clean up.

Locations (with typical sizes after a semester)

PathSize after a semesterPrivacy concern?
~/Library/Application Support/LockDown Browser/5-50 MBLow (cached Dashboard config)
~/Library/Caches/com.respondus.lockdownbrowser/10-200 MBLow (WebKit cache)
~/Library/Group Containers/group.com.respondus.lockdownbrowser/1-5 GBHigh (Monitor recording buffers)
~/Library/Preferences/com.respondus.lockdownbrowser.plist<100 KBLow
~/Library/Saved Application State/com.respondus.lockdownbrowser.savedState/<1 MBLow
~/Library/LaunchAgents/com.respondus.lockdownbrowser.plist<10 KBMedium (auto-launch)

What's actually in each leftover

Application Support

Per-course Dashboard configurations LDB pulled from your university's Respondus server. JSON files, log files. Identifies which institution + courses you've used LDB for. Not high-privacy but identifies your university affiliation.

Caches

WebKit cache: HTML, CSS, images from your LMS's exam pages. Effectively a partial copy of your LMS's exam interface (no answers, just the chrome). Macs with large caches typically have weeks of LMS history here.

Group Containers (the privacy concern)

Monitor recording buffer. Per-exam: a file containing the partial pre-upload buffer of:

If your exam uploaded successfully, this directory clears within ~24 hours. If the upload failed (network issues, Monitor server hiccup), the buffer persists.

This is the directory most worth clearing for privacy reasons - it can contain video of you taking exams in your dorm room.

Preferences

UI preferences (window size, last-used LMS, etc.). Trivial.

Saved Application State

Window restoration metadata - where LDB's window was when you last quit. Trivial.

LaunchAgents

Some MDM deployments install a LaunchAgent that helps LDB launch from non-admin accounts. Personal Macs typically don't have this. Removing the LaunchAgent stops auto-launch behaviour.

How to clear ONLY the privacy-sensitive leftovers

If you want to keep LDB installed but clear the recording buffer:

rm -rf ~/Library/Group\ Containers/group.com.respondus.lockdownbrowser/

Safe to run while LDB is installed but not running. Recording buffer gets recreated on next exam.

Why these leftovers exist (Apple's sandboxing model)

Apple's ~/Library structure separates user-scope app data from the application bundle. The intent: when you uninstall an app by dragging its bundle to Trash, your data persists across reinstalls. For LDB, this is mostly inappropriate - the cache and Monitor buffer have no value across reinstalls. But Apple's convention is "preserve user data on uninstall by default", and Respondus follows the convention.

This is why a drag-to-Trash isn't enough - the convention preserves data, not removes it. Manual cleanup is required.

Frequently asked questions

Is the Monitor recording buffer encrypted?

Per Respondus's privacy policy, recordings are encrypted in transit. Local buffer files (~/Library/Group Containers/) - the encryption status of the on-disk buffer is not publicly documented. Treat as potentially readable by anyone with disk access.

How do I know if a Monitor upload failed and the buffer persists?

Check the size of <code>~/Library/Group Containers/group.com.respondus.lockdownbrowser/</code>. If &gt;100 MB after several days, an upload likely failed. Email your instructor if you're concerned about your exam recording not being on Respondus servers.

Are the leftovers in iCloud-synced Library locations?

No - ~/Library/Application Support/ and similar are user-scope, not iCloud-Drive synced. They live on your Mac only.