Does Mandatory Exam-Proctoring Software Pass the Proportionality Test?

A student refuses to turn on their camera during a remote exam, saying they don't want their home recorded. The institution says exam integrity has to be protected. Two legitimate interests are facing off here, and the real question isn't which one wins — it's whether the method the institution chose is actually necessary.

This question comes up constantly on education-technology projects, and it usually gets framed the wrong way. The debate turns into "camera on or camera off," when the legal question is narrower: can the same aim be achieved by processing less data?

What proportionality actually asks

Article 4 of Law No. 6698 requires personal data to be relevant to, limited to, and proportionate for the purpose for which it is processed. That principle isn't an abstract aspiration — it's a concrete filter.

Exam integrity is a legitimate aim, no argument there. But a legitimate aim doesn't legitimise collecting every piece of data that could possibly be gathered about a candidate. Continuous video recording, screen capture, keystroke and mouse tracking, installing a client with broad device permissions — each of these has to be assessed on its own, against a single question: is this actually necessary to secure exam integrity, or not?

Often it isn't. Randomising the question bank, time limits, shuffling question order, weighting toward open-ended questions, and post-hoc statistical anomaly detection deliver a serious level of integrity without recording anything at all. Reaching straight for camera recording without first trying these is a hard position to defend on proportionality grounds.

Why consent doesn't work here

The first instinct institutions reach for is asking the student for consent. A checkbox appears before the exam starts, and the student can't sit the exam without ticking it.

The problem with that design is this: valid consent has to be freely given. It's difficult to argue that a student who can't enter the exam without ticking the box is agreeing freely. On top of that, the party on the other side sets grades, records attendance and influences graduation decisions. That power imbalance undermines the consent from the outset.

The practical conclusion is this: relying on consent for student data gives the institution a feeling of security without actually providing legal cover. What the institution should do instead is assess whether the processing rests on some other legal basis — and if it doesn't, drop that processing altogether.

Where a child is involved

For students of compulsory school age, the picture is even more sensitive. Capacity to consent, the parent's role, and the child's best interests all need to be assessed separately here.

When designing an education platform, different flows need to be built depending on the user's age. Offering the same interface to a ten-year-old and a twenty-five-year-old postgraduate student is a problem not just for usability but legally too. A field carrying the age group in the data model, with different processing rules tied to it, is the technical counterpart of that distinction.

What a learning record actually proves

The less-discussed side of education technology is what the record it produces is actually good for afterwards.

When a student appeals a grade, what does the institution have? A "exam completed" record that just closes the ticket — or a chain showing which question got which answer, what criterion it was marked against, and who marked it?

With the second, the appeal is resolved in ten minutes. Without it, the appeal turns into a defence that asks the institution to be trusted on its own record — and that defence is weak. That's why an assessment system should be built in this order: define the learning outcome first, tie the pass criterion to that outcome, generate questions against the criterion, keep a record of the assessment, and define the appeals process and review procedure in advance.

Build that chain, and a certificate of achievement has a demonstrable basis behind it. Without it, the certificate is just a statement resting on the institution's good faith.

What I'd suggest to institutions

Before buying proctoring software, measure how much of the integrity problem can be solved through exam design alone. Most institutions never run that measurement and go straight to the most intrusive option available.

Once that measurement is done, if proctoring is still needed, write a separate justification for every single data point collected. "The system collects this" is not a justification. Any data point that can't be justified should be removed from the system. This should also be a point of negotiation with the vendor, because most off-the-shelf products collect more than you need and ship with those defaults switched on.