Trust
This product doesn't use biometrics, not even as an option
Most school access products offer fingerprints as a feature. We designed biometrics out of the product entirely: the data schema has no such field, the API rejects this data and the adapter strips it out.
Three layers of protection against biometrics
The standard event format defines no field for a fingerprint, face vector or template; a field that doesn't exist can't be filled.
Any request containing biometric data is rejected and returned with the reason.
If the panel produces biometric events, the connector strips those fields out before they ever reach us and logs this in its ledger.
The reasons
Because of the power imbalance in school-parent and employer-employee relationships, the Board does not consider consent given in them to be freely given.
Converting biometric data into a mathematical code does not stop it being special category personal data.
If the data can still be accessed, processing is considered ongoing; switching the system off isn't enough.
Card numbers are never sent in plain form
Card numbers are transmitted as an institution-specific salted hash. The same card produces different values at two institutions, and the card number can't be recovered from the records.
Who owns the data?
If the institution chooses the cloud, the data is kept on infrastructure we operate and the institution can export it at any time. The data still belongs to the institution; we act as the processor.
If the institution chooses its own local network, the data never leaves the building; updates and support happen only in time windows the institution allows.
Retention and destruction
The institution sets the retention period, and the record is destroyed when it ends. Destruction means the data is actually deleted; deactivation doesn't count.
Audit trail
Who changed what and when is recorded, and that record can't be altered retroactively. When an attendance record is corrected, the old value is kept.
Anonymity in internal reports
Density, occupancy and absence reports are built from totals, not from individual records.
Parents see only their own child
When another student's record is requested, the system replies “record not found”. Even saying “you are not authorised” would reveal that the record exists, so we don't use messages that leak information.