Purpose
The system collects attendance evidence only to verify participation in a faculty-created classroom session. It must not be reused for advertising, profiling or unrelated monitoring.
Clear handling. Limited purpose.
This policy explains what the live-attendance workflow collects, why it is used, where it is stored and how students can request review.
POLICY OWNER
Electrical Engineering Department
Government Polytechnic Bhuj · Effective 17 August 2026
Information collected
Depending on the student route, this includes enrollment and attendance PIN or provisional name, session code, server timestamp, a newly captured photo, basic browser information and optional location evidence when enabled by faculty.
Where it is stored
Voltbook holds the captured photo temporarily in browser memory while the form is open. After submission, the attendance backend stores the private image in the department-controlled Google Drive and the attendance record in Google Sheets.
Who may access it
Access should be limited to authorized Electrical Engineering Department faculty or institutional administrators who need the information for attendance verification and correction.
Retention
Attendance records and private images remain under the department's institutional record schedule. Authorized faculty should review and delete material when it is no longer required for attendance, audit or grievance handling.
Correction or deletion
A student may ask the faculty member who created the session or the Electrical Engineering Department office to review, correct or delete an attendance record where institutional rules permit.
Camera and location
The gallery-upload route is disabled. Camera access begins only after the student presses Start camera and grants browser permission. Location is optional unless the active session requires it, and can be discarded with the photo before submission.
Important limitation
A live camera capture is attendance evidence; it is not biometric identification and does not guarantee liveness. Faculty supervision and the session-code, duplicate and server-time checks remain necessary.