Proctoring Without Student ID Storage | MyProof
Schools and certification programs can verify a registered test-taker at exam check-in without making a retained student ID photo part of the exam record. MyProof returns the configured identity result and receipt reference, while the institution keeps responsibility for privacy notices, retention rules, academic-integrity policy, and review procedures.
Never sent during verification
- Student ID photo
- Biometric template
- Room scan
- Screen recording
Best for
- Schools and certification programs reviewing how student ID images are retained.
- Privacy and procurement teams separating identity proofing from exam surveillance.
- Institutions documenting what the exam vendor receives and what becomes part of the exam record.
Not for
- Exam surveillance, room scans, screen recording, or keystroke monitoring.
- Replacing institutional privacy notices, retention schedules, or academic-integrity policy.
- Building a retained biometric template database.
Legacy IDV vs MyProof
| Legacy IDV |
MyProof |
| Store the student ID photo with the exam record and increase breach exposure. |
Verify the student on device and send only the check-in proof result. |
| Let identity artifacts flow into the same record as monitoring footage and exam events. |
Keep the identity result narrow and document the boundary between check-in and exam monitoring. |
| Ask students to trust another platform with their full identity artifacts. |
Show students a proof flow where the ID photo is never sent to the platform. |
Treat student identity retention as a governance decision
The institution should define what the exam vendor receives, how long each record is retained, who can review failures, and how students are informed. MyProof can keep the student ID photo out of its result, but it does not write the institution's retention schedule or privacy notice.
Separate the identity record from the exam record
A check-in result and receipt reference can support an access decision without placing a student ID image, reusable biometric template, room scan, or screen recording into the MyProof payload. Exam-monitoring records remain a separate institutional and vendor responsibility.
What institutions should require
Institutions should map student-privacy responsibilities to concrete vendor behavior: data flow, retention, access, accessibility, incident response, and the product's exact boundary.
A proof result can reduce data collection, but it does not decide academic integrity, replace institutional policy, or eliminate human review when a student cannot complete the automated path.
Frequently asked questions
Can proctoring platforms verify identity without storing student ID photos?
Yes. MyProof is designed to verify the test-taker at check-in and return a proof result instead of sending the ID photo into the proctoring platform.
What should an institution document before using MyProof for exam check-in?
Document the identity facts required, what the platform receives, retention and access rules, the failure-review path, accessibility options, and how the check is described to students.
Does MyProof replace the institution's privacy or academic-integrity policy?
No. MyProof handles the identity check-in layer. The institution remains responsible for privacy notices, retention policy, accommodations, academic-integrity rules, and human review.
What becomes part of the exam platform's identity payload?
The intended MyProof flow returns the configured check-in result and receipt reference. The student ID photo and reusable biometric template are not sent as part of that result.
Does MyProof monitor the exam?
No. MyProof does not record the room, screen, audio, keystrokes, or exam session. It is an identity check-in layer used before access.
Canonical page: https://myproof.ai/proctoring-without-student-id-storage