Digital invigilation that works in any modern browser — no extensions, no apps, no video upload.
Browser-native SDK — no apps or extensions for candidates.
Metadata-only sync, ideal for rural and mobile candidates.
Data minimization designed for European institutions.
Remote invigilation — monitoring candidates during online exams — has traditionally relied on browser extensions, desktop apps, and continuous video upload. These approaches create friction, privacy concerns, and compliance challenges.
ProctorSafe offers a browser-native alternative designed for European universities, certification providers, and testing organizations.
| Aspect | Traditional invigilation | ProctorSafe |
|---|---|---|
| Installation | Browser extension or app required | None — browser-native SDK |
| Video handling | Full upload to vendor cloud | Local processing, no upload |
| Candidate experience | High friction, privacy concerns | Lower friction, privacy-first |
| GDPR alignment | Often challenging | Built-in data minimization |
| Bandwidth | High (video upload) | Low (metadata only) |
ProctorSafe computes an Integrity Budget (0–100) for every session server-side using a deterministic, rule-based algorithm. Violations are deducted by severity (CRITICAL, MAJOR, MINOR) and normalised by session duration, so a brief tab switch in a 3-hour exam weighs differently from the same action in a 15-minute quiz.
Reviewers see the score in the dashboard and drill into the event timeline only for sessions that warrant it. Most sessions can be cleared without watching any footage — because there is no footage to watch.
Visit our interactive demo or contact us for a tailored walkthrough.
Dive deeper with guides from our articles library.
A technical walkthrough of how the ProctorSafe SDK collects, evaluates, and transmits integrity signals — without ever uploading video, audio, or biometric data from the candidate's device.
Read articleTechnical architectureHow WebAssembly enables high-performance in-browser proctoring without invasive downloads or kernel-level software.
Read articleTechnical architectureLatency, reliability, and privacy trade-offs between edge (on-device) and cloud-based proctoring architectures.
Read articleRegulatory & complianceHow privacy-first, on-device proctoring reduces the accessibility friction that makes traditional proctoring tools non-compliant with WCAG 2.1 AA — and what institutions still need to do.
Read articleTechnical architectureWhat no-extension proctoring can and cannot see, how it compares with extensions, desktop apps and lockdown browsers, and 10 questions to ask vendors.
Read articleCommon questions about privacy, compliance, and integration.
Start a free trial and run real sessions against your own application, try the interactive demo in your browser, or contact us for a walkthrough tailored to your program.