Corrected . See the revision log.
Back to all articlesOnline proctoring asks students to accept a webcam, monitoring software, and behavioural analysis in exchange for the convenience of taking exams anywhere. That trade only works if institutions handle the privacy side responsibly. This article examines what data proctoring systems actually need, what they should never collect, and how regulations like the GDPR shape the answer.
What Proctoring Systems Actually Need to Know
Strip away the technology and a proctor needs to answer four questions: Is the right person taking the exam? Are they alone? Are they using forbidden materials or devices? Did they attempt to extract exam content? Every piece of data collected should trace back to one of those four questions. Identity requires a name and enrolment record. Presence requires knowing whether a face is in frame. Device misuse requires knowing whether a phone appeared. None of these questions requires storing hours of bedroom video on a company server — and that distinction is where good and bad proctoring architectures part ways.
The Two Architectures: Cloud Recording vs Local Processing
First-generation proctoring platforms adopted a surveillance model: stream the student's webcam to the cloud, record everything, and let humans or algorithms review the footage afterwards. This maximises evidence but also maximises risk. Recorded footage of students in their homes is sensitive personal data; every recording is a liability if the vendor is breached, and several high-profile incidents have shown exactly how badly that can go.
Local inference processes media on the student’s device. ZYNQO’s current browser exam uses this approach for camera frames and sound-level checks, while sending session events and answers to Firebase. The source does not include an audio/video recording-upload flow. This reduces stored media, but identifiers and event logs still need access control and a retention policy. Check the current privacy policy and the institution’s own arrangements.
What the GDPR and Similar Laws Require
Data-protection regulations converge on a handful of principles that apply directly to proctoring. Lawful basis and transparency: students must be told, before the exam, exactly what is monitored, what is stored, and for how long. Data minimisation: collect the least data sufficient for the purpose — a principle that strongly favours metadata-only architectures over video recording. Purpose limitation: proctoring data may be used to assess exam integrity, not repurposed for anything else. Retention limits: violation logs should be kept only as long as an academic appeal could reasonably require, then deleted. Access rights: a student accused of a violation is entitled to see the evidence against them.
Institutions outside Europe are not off the hook. Similar obligations appear in laws from California's CCPA to India's DPDP Act, and universities frequently enrol students across borders, which pulls multiple regimes into scope at once. Designing to the strictest common denominator — minimal collection, local processing, short retention — is both the safest legal posture and the right ethical one.
Proportionality: Matching Monitoring to Stakes
Not every assessment justifies the same level of scrutiny. A weekly practice quiz does not warrant face tracking; a professional licensing exam might justify every layer available. A proportionate proctoring policy defines tiers — for example, browser-only monitoring for low-stakes quizzes, camera-based AI monitoring for graded exams, and full multi-layer proctoring for terminal or certification assessments — and applies the minimum tier the stakes require. This is not just good ethics; regulators explicitly weigh proportionality when assessing whether data processing is justified.
Communicating with Students: The Trust Dividend
Explain monitoring before the exam so students can plan and raise concerns. Publish a plain-language notice, provide a practice run, describe any automatic submission rule, and explain the review process. Do not promise that these steps produce a particular improvement in grades or anxiety; ask students what remained unclear and use that feedback to improve the next sitting.
Questions to Ask Any Proctoring Vendor
Institutions evaluating proctoring platforms can cut through marketing language with a short list of direct questions. Is video recorded or processed locally? Precisely what data leaves the student's device? Where is it stored, and under which jurisdiction's laws? How long is it retained and who can access it? Are automated flags decisions, or inputs to human decisions? Can a student obtain the evidence log for their own session? A vendor with a privacy-respecting architecture answers these in one sentence each. Evasive answers are themselves an answer.
The Bottom Line
Exam integrity and student privacy are frequently framed as opposites, but the trade-off is largely an artefact of outdated architecture. Modern browser-based AI makes it possible to detect the behaviours that matter while collecting a fraction of the data older systems hoarded. Institutions that choose privacy-preserving proctoring get both halves of the bargain: credible exam results and students who trust the process that produced them.