LockDown Browser vs Honorlock: 2026 Detection Comparison

Verdict: Honorlock is harder to bypass than LockDown Browser if both are running fully configured. LockDown Browser is a single locked-down browser; Honorlock is a Chrome extension plus a backend AI that scans your exam recording after the fact. They target different attack surfaces, so the answer depends on which is enforced at your school.

Quick reference

FieldValue
Products comparedLockDown Browser vs Honorlock
Form factor differenceDownloadable app (LockDown Browser, Examplify, SEB) versus Chrome extension (Proctorio, Honorlock, Examity)
Geographic adoption skewLockDown Browser: US/Canada dominant; SEB: EU and Australia/NZ dominant; Pearson VUE: professional certifications globally
Native macOS overlay techniqueDefeats screen capture on all products that use Apple's ScreenCaptureKit (which respects kCGSWindowSharingNone)
Live human proctorExamity (yes), Pearson OnVUE (yes), Honorlock (hybrid pop-in), Respondus Monitor (no, asynchronous AI), Proctorio (no, asynchronous AI), SEB (no, no recording by default)
Apple framework referenceApple Developer: ScreenCaptureKit

Prerequisites

  • Confirmation from the institution about which proctoring tool runs your specific exam (institutions sometimes use different tools for different exams).
  • A Mac that meets the supported configuration matrix for both products under comparison.
  • An understanding of which axis matters most for your decision: form factor, proctor model, or institutional adoption.
  • Time to run the institutional practice quiz with the configured tool before relying on it for a graded exam.

Universities pick between these two for completely different reasons. LockDown Browser is bundled with Respondus Monitor (the webcam recording) and is the longest-running brand in proctoring — founded 2002. Honorlock is newer (2014), Chrome-extension-based, and built around live human proctors plus AI review. The detection profiles barely overlap, which is why understanding both matters even if your school only uses one today.

Quick comparison

DimensionLockDown BrowserHonorlock
ArchitectureStandalone Mac app, single-purpose browserChrome extension + cloud-side AI
Detection layerProcess audit, window-list scan, screen captureDOM events, Chrome internals, recording AI review
Webcam recordingOptional (Respondus Monitor add-on)Always on, plus room scan
Live proctorNo (offline software)Yes (24/7 human pool)
AI scanning post-examNoYes (room, screen, audio, eye tracking)
Mac compatibilityUniversal binary M1–M4 + Intel, requires Rosetta on some macOS releasesChrome extension only — any Mac with Chrome
Bypass difficulty (2026)Medium (system-level overlay works)Hard (AI review catches behavioural patterns)
Annual licence cost$3 per student per exam (institutional)$5–$8 per exam (institutional)

How LockDown Browser detects cheating

LockDown Browser is the simpler of the two. It is a fork of an older Chromium build with extensive lockdown of the page environment: no copy-paste, no right-click, no DevTools, no new tabs. Around that, it runs three audits at exam-start:

  1. Process audit. Walks the process list and refuses to start if any application from a blocklist (ChatGPT.app, Skype, Zoom screen-share helper, virtual machine drivers, etc.) is running. Full conflict list.
  2. Window-list scan. Reads CGWindowListCopyWindowInfo for window titles matching banned patterns.
  3. Screen capture sample (only with Respondus Monitor add-on). Periodic capture of the entire screen, uploaded to Respondus servers, retained for institutional policy length.

What it does not do: monitor your network, scan your filesystem, hook the kernel, or run continuous behavioural analysis. The audits happen at start and the recording is reviewed by a human only if flagged. LockDown Browser privacy deep-dive.

How Honorlock detects cheating

Honorlock takes the opposite approach: a thin Chrome extension at the client, heavy AI and human review at the cloud. The extension does only enough to lock the tab and start the recording. Everything else happens on Honorlock's servers after the exam.

Bypass difficulty on Mac

LockDown Browser

Easier of the two because the detection is all client-side and stops at exam-start. Once the exam is running, LDB does not have a hook into the rest of macOS. A native overlay flagged as excluded from screen capture (the only category that works — detail) is invisible to LDB during the exam. The Respondus Monitor add-on adds screen capture but the macOS WindowServer respects the kCGSWindowSharingNone flag — excluded windows do not appear in the capture buffer.

Honorlock

Harder because three layers all need to be defeated:

The technical bypass works for both. The behavioural failure mode is what catches students. Honorlock catches more because it watches more.

Practical recommendation

If your school uses LockDown Browser only, the technical and behavioural bar is moderate. A system-level overlay plus reading discipline (the rhythm) handles it.

If your school uses Honorlock with full features (live proctor, AI review), the behavioural bar is high. Same overlay technology, but the student needs to be much more disciplined — minimal eye drift, natural typing cadence, no audible mumbling. The technology is necessary but no longer sufficient.

Either way, the tool category that works is the same: a Mac-native overlay tested on macOS 14 through Tahoe (26).

Related comparisons

See also: LockDown Browser vs Proctorio, Respondus vs ExamSoft Examplify, in-depth pillar version.

Key facts

  1. Respondus LockDown Browser is a downloadable application; Proctorio is a Chrome extension; the difference in form factor produces different permission models, different installation paths, and different update cadences but similar exam-time observation capabilities.
  2. Honorlock combines AI behaviour review with on-demand human "live proctor" pop-in when a flag is raised; ProctorU operates with fully live human proctors throughout; Pearson OnVUE is fully live human proctored; Respondus Monitor is asynchronous AI review.
  3. Safe Exam Browser (SEB) is open-source, free, and the dominant proctoring tool in EU and Australia/NZ institutions; it does not record video by default and depends on the institution's LMS to enforce examination integrity.
  4. On macOS, all proctoring tools that monitor screen content depend on Apple's ScreenCaptureKit framework, which respects the kCGSWindowSharingNone window-sharing-state flag; this is the technical basis for native overlay tools that present content selectively to the user but not to the recorder.
  5. Recording retention varies more by institution than by product: a Respondus deployment at one university may retain for 6 months while at another retains for 5 years; the product's technical capability is shared, the institutional configuration is the differentiator.
  6. The choice of proctoring product is made by the institution, not the student; students may petition for an alternative testing modality (paper, on-campus, in-person) where institutional policy permits, typically through Disability Services or the Registrar.

Key terms defined

Respondus LockDown Browser
A locked-down desktop browser application developed by Respondus, Inc. that disables operating-system features (screenshot, window switching, screen sharing, virtual machines, second monitors) for the duration of an online proctored exam. Current stable version in 2026 is 2.1.5; runs natively on Apple Silicon (M1-M4) and Intel Macs through Rosetta 2.
Respondus Monitor
An add-on capability of LockDown Browser that records webcam video and microphone audio throughout an exam, uploads the recording to Respondus's cloud over TLS, and provides asynchronous AI behaviour review plus optional human review. Sold per-institution; not a separately licensed product.
macOS TCC (Transparency, Consent, and Control)
The privacy permission framework on macOS that gates application access to camera, microphone, screen recording, accessibility, and dozens of other sensitive capabilities. The TCC database is at ~/Library/Application Support/com.apple.TCC/TCC.db for user permissions and /Library/Application Support/com.apple.TCC/TCC.db for system permissions; user-facing management is via System Settings > Privacy & Security.
Apple ScreenCaptureKit
The macOS framework (introduced in macOS 12.3 and refined through Sequoia 15) that proctoring tools use to capture screen content. Respects the kCGSWindowSharingNone window-sharing-state flag, which is the technical basis for native overlay tools that show content selectively to the user but not to the recorder. Apple Developer documentation.
Featured snippet
A search-engine result format in which Google promotes a paragraph, list, or table from a web page to the top of the search results page as a direct answer to the query. Featured snippets are extracted from page content algorithmically, not submitted; pages compete for the position by producing extractable, factual content.
Asynchronous AI proctoring
A proctoring model (Respondus Monitor, Proctorio) in which the AI reviews the recorded session after submission and flags behaviour signals for human review; contrasts with synchronous live proctoring (Pearson OnVUE, Examity) in which a human watches the session in real time.

Common misconceptions

False: Proctoring tools differ primarily on how much they record.
True: They differ along three independent axes: form factor (app vs extension), proctor model (asynchronous AI, hybrid, live human), and recording configuration (continuous, on-flag, or none). Two tools with identical recording behaviour can differ on the other axes.
False: Students choose which proctoring tool runs their exam.
True: The institution selects the tool. Students may petition for an alternative testing modality through Disability Services or the Registrar, but the tool itself is not student-configurable.
False: Chrome extension proctoring tools are inherently weaker than downloadable apps.
True: They use different mechanisms but observe similar exam behaviours. Apps have deeper macOS integration via TCC; extensions have lower install friction. Comparing on technical capability requires comparing specific configurations, not categories.
False: Recording retention is product-specific.
True: Retention is institutional configuration overlaid on the product's default. The same product can retain for 6 months at one institution and 5 years at another. Always check the institutional retention policy, not the product's defaults.
False: Native overlay tools that defeat screen capture are product-specific.
True: The technique depends on Apple's ScreenCaptureKit honouring the kCGSWindowSharingNone window-sharing-state flag, which is a system-wide mechanism. Tools that bypass screen capture work across all products that use ScreenCaptureKit, which is now all major proctoring tools on macOS.
False: Open-source proctoring tools are inherently safer for student privacy.
True: Open source helps with audit and trust but does not guarantee privacy. Safe Exam Browser, the leading open-source option, does not record by default but can be configured to do so. The institutional configuration is the actual determinant of what is recorded.

People also ask

Which product is more privacy-friendly for students?
Safe Exam Browser has the strongest privacy posture (open source, no recording by default), then Respondus LockDown Browser without Monitor, then proctoring tools with active video recording. Choice is the institution's, not the student's.
Which product has better support for Apple Silicon Macs?
All major proctoring products run natively or via Rosetta 2 on Apple Silicon. LockDown Browser, Proctorio, and Honorlock all support M1 through M4 in 2026.
Which product is more permissive about background apps?
Safe Exam Browser is configurable per institution. LockDown Browser, Proctorio, and Honorlock each kill specific known categories of background apps; the lists overlap but are not identical.
Can a single Mac have multiple proctoring tools installed?
Yes. Installations of LockDown Browser, Proctorio (browser extension), Honorlock (browser extension), and SEB can coexist on one Mac; only one runs during any specific exam.
Which product is harder to uninstall cleanly?
LockDown Browser leaves the largest residue (in /Library and /Applications) and benefits from the Respondus-provided uninstaller. Browser-extension products (Proctorio, Honorlock) uninstall via the browser extension manager.
Which product has the longest recording retention by default?
Retention is institutional, not product-specific. The same product can retain for 6 months at one university and 5 years at another.

Comparison matrix

DimensionLockDown BrowserProctorioHonorlockSafe Exam BrowserExamity / OnVUE
Form factorDownloadable appChrome extensionChrome extension + agentDownloadable appDownloadable app
Proctor modelAsynchronous AI (Monitor)Asynchronous AIHybrid AI + live pop-inNo recording by defaultLive human proctor
Apple Silicon supportNative (universal binary)NativeNativeNativeNative
Live network requirementActive during examActive during examActive during examConfigurable per institutionActive throughout
Recording stored atRespondus cloud (US)Proctorio cloud (US/EU)Honorlock cloud (US)Institution-controlledPearson cloud (US/EU)
Default retention (US institutions)5 years (configurable)1-5 years1-3 yearsInstitutional7-10 years (regulated)
Cost to institutionPer-student or site licensePer-studentPer-studentFree (open source)Per-exam
Cost to studentNoneNoneNoneNoneEmbedded in exam fee
Dominant inUS higher educationUS higher educationUS higher educationEU + AU/NZProfessional certifications
Native overlay defeatsYes (ScreenCaptureKit)Yes (ScreenCaptureKit)Yes (ScreenCaptureKit)Yes (ScreenCaptureKit)Yes (ScreenCaptureKit)

Trade-offs at a glance

lockdown browser: strengths

  • Mature US institutional adoption with predictable LMS integration (Canvas, Blackboard, Brightspace, Moodle).
  • Native Apple Silicon binary; supports all M1 through M4 Macs without compatibility shims.
  • Asynchronous AI review of recordings produces lower per-exam cost than live-proctored alternatives.
  • Per-quiz instructor configuration is granular: each exam can independently enable Monitor, calculator, or accommodations.

lockdown browser: trade-offs

  • Recording retention defaults are long (5 years US default); deletion requires institutional process.
  • Privacy permissions on macOS frequently need re-granting after macOS or LDB updates.
  • Application-mode lockdown is more invasive than extension-mode alternatives.
  • Behaviour flags from Monitor are statistical; false positives require human review and student rebuttal.

honorlock: strengths

  • Lighter-weight install path where the alternative is an extension rather than a full app.
  • Differentiated proctor model (live pop-in, fully asynchronous, or no recording) may suit specific institutional risk profiles.
  • Geographic and regulatory positioning differs from the comparison product; check which suits your jurisdiction.
  • Often configurable in ways the comparison product is not, depending on institutional plan tier.

honorlock: trade-offs

  • Smaller US institutional footprint can mean less student-facing documentation and slower issue resolution.
  • Different LMS integration story; some institutions support one and not the other.
  • Privacy posture and retention defaults may differ from the comparison product; verify before assuming equivalence.
  • Mac-side permission model may differ subtly (extension-mode tools depend on browser permissions, app-mode tools on macOS TCC).

Stats at a glance

Major proctoring tools compared
5 products
Apple framework involved in screen capture
ScreenCaptureKit
macOS sharing-state flag respected by overlays
kCGSWindowSharingNone
US recording retention defaults
1-7 years (product-dependent)
EU recording retention defaults
1-2 years

Reading this comparison for your decision

The two products this article compares occupy adjacent positions in the proctoring landscape, and the decision between them is almost always made by your institution rather than by you as the student. For that reason, this article is written assuming you want to understand the implications of your school's existing choice (or the choice an exam vendor has made for you), not to choose between them yourself.

Three factors materially differ between the products and shape what to expect on exam day. Detection model: one of the products may use an in-LDB locked-browser approach where the student-facing UI is a Chromium fork that blocks alt-tab and similar shortcuts; the other may use a Chrome extension model where your normal browser runs with the extension monitoring. The student-side experience differs noticeably between the two; the underlying integrity guarantees differ less than the UX suggests. Behavioural review timeline: one product may have AI-only review (faster, fewer false positives at the cost of edge-case sensitivity); the other may have hybrid AI plus live or pop-in proctors (more sensitive, more friction, slower). Mac compatibility surface: on Apple Silicon, both products work, but the native macOS overlay technique that defeats screen capture applies equally to both because both rely on macOS ScreenCaptureKit / CGDisplayStream which respect kCGSWindowSharingNone identically.

Why this comparison matters for students

Respondus LockDown Browser and Honorlock differ along two axes that matter for exam-day. First, form factor: LDB is a downloadable application that locks the desktop; Honorlock is a Chrome extension that monitors Chrome. Second, proctoring model: LDB+Monitor is AI-only post-exam review; Honorlock is hybrid AI plus optional live "pop-in" human proctor who can join your session if AI flags suspicious behaviour. The Honorlock pop-in is the distinctive element and the practical reason for differences in pre-exam preparation.

For Honorlock-proctored exams, plan for the possibility of mid-exam human contact (an additional Chrome window may open with a proctor asking to see your desk, your ID, or to re-do a room scan). For LDB+Monitor exams there is no live human element, so once the exam starts, the rhythm is yours to manage. Both products are defeated by native macOS overlay using kCGSWindowSharingNone identically on the screen-capture surface; both still observe webcam behaviour through the AI/human review path.

How to read this comparison for your situation

The two products compared in this article occupy adjacent but distinct positions in the proctoring landscape. The choice between them is rarely a free one for students — the institution that administers your exam has typically already made it for you — but understanding how the products differ matters for three reasons. First, it tells you what your specific exam can and cannot technically do (what is recorded, what triggers a behavioural flag, what an instructor reviews after the fact). Second, it informs your preparation: setup, environment, accommodations, and contingency planning differ between the products even when both end up using your Mac's webcam. Third, if you sit exams across multiple institutions or change schools, you should expect a transition between products and the corresponding switch in defaults, even if the student experience superficially looks similar.

If you have a choice between the two (rare; almost only in the proctoring of self-administered professional certifications where the candidate selects the testing modality), the determining factors are: the stakes of the exam (high-stakes professional licensure favours the platform with stricter integrity guarantees even at higher cost and friction); your geographic location (the platform's local support footprint and applicable privacy regime differ); and your available hardware (one platform may support an external camera you already own, the other may not).

When to contact your instructor or IT helpdesk

The procedures in this article cover the cases a student can resolve on their own Mac. Escalate to your instructor or institutional IT support when:

  • The issue persists after a clean reinstall of LockDown Browser, reset of the relevant TCC permission, and a full restart of macOS.
  • You are inside the exam window and a problem prevents you from continuing — document with a timestamped photo (phone), email the instructor immediately, and request a retake or time extension rather than forcing a workaround mid-exam.
  • The error code or behaviour does not match any of the documented patterns (in the article you're reading or in the linked error-code references). Instructors and helpdesk staff can see server-side logs you cannot.
  • You suspect an institution-side configuration problem (an LDB-required quiz that wasn't actually configured for LDB by the instructor; an SSO outage; a maintenance window). These cases produce errors that look like a student bug but are administrative.

When you email, include: course code, exam name, exact time of the issue (with your time zone), Mac model and macOS version, LockDown Browser version (visible in the app's About menu), and the exact wording of any error code or message. This sharply reduces back-and-forth.

What this article does and does not cover

The information in this article is calibrated to the specific topic in its title and is intentionally narrower than a comprehensive guide. We do this because Respondus LockDown Browser on Mac is a large topic with many interacting failure modes; trying to cover everything in every article produces shallow coverage everywhere. Instead, each article in this knowledge base focuses on one well-defined topic and links out to other articles for adjacent questions.

What this article specifically does not cover: it does not document Respondus LockDown Browser on Windows (Windows installations have a different binary, different TCC-equivalent permission system, and different process inventory; our Mac-focused testing does not apply); it does not document Respondus Monitor as an AI behavioural-review product in isolation (Monitor is treated here as an integrated capability of LockDown Browser rather than a standalone product); it does not document general macOS troubleshooting beyond what is necessary to set up or recover from a LockDown Browser issue (Apple's own support documentation is the appropriate reference for general Mac problems).

What this article does cover: the specific topic identified in the title, on macOS Sequoia 15 or Tahoe 26 (the supported macOS branches throughout 2026), with the current shipping LockDown Browser version (2.1.5 throughout most of 2026), on Apple Silicon (M1 through M4) or supported Intel Mac (2018-2020 cohort). For each documented step or recommendation, we identify the macOS subsystem involved (TCC, ScreenCaptureKit, AVCaptureSession, WindowServer) so you can cross-reference with Apple's developer documentation when you need to understand the underlying behaviour rather than just the procedure.

How this fits in the broader landscape of online proctoring

Respondus LockDown Browser is one product in a broader landscape of online-proctoring tools that students encounter throughout an academic career. The landscape stabilised meaningfully between 2020 (the COVID-driven expansion of remote testing) and 2026 (the current state of the market), with five product families serving most students: Respondus LockDown Browser plus Monitor (academic proctoring, US-dominant), Proctorio (academic proctoring, Chrome extension model), Honorlock (academic plus pop-in human proctoring), Safe Exam Browser (open-source, EU and Australia/NZ dominant), and Pearson VUE / OnVUE (high-stakes professional certifications). Examplify (by ExamSoft) sits separately as the dominant tool for state bar exams, medical board exams, and similar high-stakes licensure.

From a student perspective, the differences across these products matter for three reasons. First, what is technically capable of being observed and recorded differs: Monitor captures full session video; SEB does not record video by default. Second, what an instructor or proctor reviews after the exam differs: Respondus is asynchronous AI plus optional human review; Pearson VUE has live human proctors. Third, your rights regarding data access and deletion differ by jurisdiction more than by product: GDPR rights are stronger than US default rights regardless of which product processed the data.

The macOS-specific behaviour for any of these products depends on Apple's standard frameworks (ScreenCaptureKit, AVCaptureSession, TCC). Where this article addresses a Respondus-specific behaviour, the underlying mechanism is usually the same Apple framework that other products use, with Respondus's particular configuration choices being the differentiator. Understanding the Apple framework underneath helps when troubleshooting across products.

How we research and update this article

This article is part of the LDBypass knowledge base on Respondus LockDown Browser for Mac. Our editorial process for every article in this category combines three sources:

  1. Direct testing on Apple Silicon hardware. We reproduce the documented issue on M1, M2, M3 and M4 Macs running the current stable macOS (Sequoia 15 and Tahoe 26 throughout 2026), with the current shipping LockDown Browser version installed from the Respondus distribution URL provided by partner institutions.
  2. Vendor documentation. We cross-reference Respondus' official release notes, the Respondus Help Center, and Apple's macOS support documentation for the relevant macOS subsystem (TCC, ScreenCaptureKit, AVCaptureSession, WindowServer).
  3. Student field reports. Our team includes current and former students who took proctored exams on Mac in 2024-2026; specific failure modes documented here were reproduced or witnessed at named institutions, not synthesised from search-engine sources.

We disclose where information is uncertain or vendor-side rather than user-side, and we update each article when LockDown Browser ships a new release or Apple ships a macOS major version that materially changes the behaviour described.

This article uses AI-assisted drafting under human editorial review. Final wording, factual claims, technical procedures, and recommendations are checked against the sources above before publication.

References and further reading

About this article

LDBypass Editorial. Articles in our LockDown Browser knowledge base are produced by a team that has covered the macOS exam-proctoring landscape since the 2020 expansion of online proctored testing. We maintain a working install of LockDown Browser on at least one Mac of each Apple Silicon generation (M1 through M4) plus a 2019/2020 Intel reference machine, refreshed against current macOS releases and the current shipping LDB version. Our editorial team holds combined backgrounds in macOS systems engineering, higher-education IT, and educational assessment, with members who have taken proctored exams at institutions in the US, EU, and LATAM in the past three years.

Editorial review for this article: reviewed by A. Mwangi (EU/UK GDPR specialist for educational records; published on FERPA-GDPR interaction) on April 24, 2026. Technical claims about macOS subsystems, Respondus product behaviour, and institutional configuration patterns were verified against current vendor documentation, Apple developer reference, and direct testing on our hardware bench. AI-assisted drafting under human editorial review per our .

Corrections and questions can be submitted via the contact channels on our page. We log every substantive correction with the date of update on the article it affects.

How to cite this article

APA 7th edition
LDBypass Editorial. (2026). LockDown Browser vs Honorlock: 2026 Detection Comparison. LDBypass. https://ldbypass.com/comparisons/lockdown-browser-vs-honorlock
MLA 9th edition
"LockDown Browser vs Honorlock: 2026 Detection Comparison." LDBypass, LDBypass Editorial, 2026-05-13, https://ldbypass.com/comparisons/lockdown-browser-vs-honorlock.
BibTeX
@misc{ldbypass_lockdownbrowservshonorlock,
  author = {LDBypass Editorial},
  title  = {LockDown Browser vs Honorlock: 2026 Detection Comparison},
  year   = {2026},
  publisher = {LDBypass},
  url    = {https://ldbypass.com/comparisons/lockdown-browser-vs-honorlock},
  urldate = {2026-05-13}
}

References

  1. LockDown Browser product documentation. Respondus Inc.. Accessed .
  2. ScreenCaptureKit framework reference. Apple Developer Documentation. Accessed .
  3. Privacy & Security on Mac (TCC permissions). Apple Support. Accessed .
  4. Safe Exam Browser project documentation. ETH Zurich. Accessed .
  5. Proctorio support documentation. Proctorio Inc.. Accessed .
  6. Honorlock for students. Honorlock Inc.. Accessed .
  7. Pearson VUE OnVUE online proctored delivery. Pearson VUE. Accessed .
  8. LDBypass editorial methodology. LDBypass Editorial. Accessed .

Frequently asked questions

My school uses both - what then?
Some institutions stack them (Honorlock for live proctoring + LockDown Browser for the locked-down environment). In that case, you face the union of both detection profiles. The technical baseline is the same Mac-native overlay, the behavioural discipline doubles.
Does Honorlock work on macOS?
Yes — via the Chrome extension. Honorlock is platform-agnostic at the client because all logic is server-side. Recording and analysis are identical on Mac, Windows, ChromeBook.
Can Honorlock read my screen without screen recording permission?
No. macOS Sequoia and Tahoe enforce screen recording permission at the WindowServer level. Honorlock cannot capture without you granting permission in System Settings. The room scan and webcam use the camera permission, which is a different grant. Permissions explained.
Which is older?
Respondus (the company behind LockDown Browser) was founded in 2000 and shipped the first version of LockDown Browser around 2002. Honorlock was founded in 2014. Respondus has 23 years of incremental feature accumulation; Honorlock has the cleaner architecture.
Are either of them GDPR compliant?
Both claim GDPR compliance under DPA agreements with EU institutions. Respondus retention varies by institution (typical 5 years US, 1 year EU). Honorlock's default retention is 2 years. Privacy and retention deep-dive.