Client-side processing and execution model
All binary parsing of EXIF tags, GPS coordinates, sensor hardware signatures and capture timestamps executes on the client device, through native web APIs and the compiled exifr parser.
The application does not stream, transmit or cache full-resolution photograph binaries to external servers, AI models, or third-party analysis services.
What is transmitted, and what is kept
So that lecturers and laboratory supervisors can audit practical coursework, only the derived verification record is persisted to the institutional ledger:
- SHA-256 digest
- A one-way fingerprint of the file's bytes, used solely to detect duplicate submissions across students.
- Telemetry summary
- Capture timestamp, resolved latitude and longitude, camera make and model, and the pass or fail of each check.
- Thumbnail, 96px or smaller
- A heavily downscaled visual reference, kept strictly so a reviewer can confirm the specimen's subject.
- Submission metadata
- Student name, registration number, course code and the time the record was filed.
Geospatial telemetry and location privacy
Where an image carries embedded GPS coordinates, those coordinates are resolved to a human-readable place name through OpenStreetMap Nominatim — for example, “UNIZIK Faculty of Physical Sciences, Awka”. This happens once, for one photograph, at the moment it is checked.
There is no continuous or background location tracking of the user or their device at any point.
Academic integrity and record retention
Verification records are retained through the active academic session for grading, moderation and accreditation review.
Under the Nigeria Data Protection Regulation, students may request review of a flagged entry through their departmental head or course lecturer.