Same device. Classroom-proctored.

Browser-level lockdown, seven layers deep.

No webcams, no invasive spyware — just a fullscreen, keystroke-locked exam surface built for a college lab, with every violation timestamped to the session and surfaced live to the invigilator.

Start free trial →
  • 01Fullscreen exit → flagged
  • 02Tab switch → 3 strikes, auto-submit
  • 03Right-click → disabled
  • 04Copy / paste / view-source → blocked
  • 05DevTools open → detected
  • 06Duplicate login → refused

Layer by layer.

Fullscreen enforcement

Trigger

Test starts in fullscreen. Exiting it — Esc, Alt-Tab, minimizing — is caught immediately.

Response

First exit logs a warning banner to the student. It's recorded against their session either way.

Tab / window switching

Trigger

Detected via the browser's Page Visibility API — fires the instant a tab loses focus.

Response

Three switches and the company can configure auto-submit, ending the attempt on the spot.

Right-click & text selection

Trigger

Context menu is disabled outright; text selection is blocked via CSS everywhere except the code editor.

Response

No warning needed — the action simply doesn't fire, so there's nothing to circumvent mid-test.

Copy / paste / view-source

Trigger

Ctrl+C, Ctrl+V, Ctrl+A, Ctrl+U, and their browser equivalents are intercepted at the key-event level.

Response

Blocked silently for MCQ screens; the code editor is the one deliberate exception for coding rounds.

DevTools detection

Trigger

A window-size heuristic flags when the browser's DevTools panel is opened.

Response

Logged as a violation the same way a tab switch is — visible to the invigilator in real time.

Duplicate login

Trigger

One active session per student, enforced server-side against the access code + roll number pair.

Response

A second login attempt on another device is refused outright, not silently allowed to run in parallel.

What happens when something's flagged?

01

Logged instantly

Every violation is timestamped against the student's session — nothing is silent.

02

Live to the invigilator

The roster updates in real time — no refresh needed to see who's been flagged.

03

On the final report

Suspected-cheating counts roll up into the exam report and PDF, per student.

What this isn’t.

No webcam proctoring

Built for a college lab with an invigilator physically present — not a remote, camera-watched exam. Nothing records video or audio.

No installed software

Everything runs in the browser. Students don’t install a lockdown app or browser extension — just the test link and an access code.

No biometric data

No face ID, no fingerprint, no data collection beyond what's needed to run and score the exam itself.