Local processing and controlled transmission
Where designed, capture and biometric comparison are performed locally. External transmission occurs only when required for a configured function, such as the OASIS query.
Security & privacy
EOAS separates verification, the personnel decision and technical release. Errors or missing confirmations are handled safely.
Transparent before the check
A biometric match does not directly release a device. Document capture, identity match, OASIS query, StaffPad confirmation, device selection and a confirmed release signal must all be complete and unambiguous.
Where designed, capture and biometric comparison are performed locally. External transmission occurs only when required for a configured function, such as the OASIS query.
Security-relevant events may be logged. General system logs should not contain clear-text identity data, document images or biometric features unless this is demonstrably necessary.
Sees only the information and functions required to run the current check.
May confirm or reject the current process on StaffPad.
Configuration, maintenance and diagnostics require separate protection.
Only data required for the intended process is processed.
To clearly match the person to the process.
For the technical comparison of ID and person.
For traceability of the verification and release process.
The measures actually used must be specified and documented for the deployed configuration.
For every data category, define the purpose, legal basis, storage location, retention period, deletion process, access rights and statutory retention obligations.
Before production use, the site-specific privacy and operating concept must undergo professional and legal review.
With active registration, the ID does not need to be scanned again. A current OASIS check and staff confirmation remain required for every process.
Voluntary registration at the player's request.
Biometric reference stored locally in the EOAS system; no facial photo.
Recognition plus a current OASIS check and staff confirmation on every process.
Automatically after three months, or at any time on request via staff.
After expiry or deletion, the ID must be scanned again; a new registration is then possible. Access is limited to EOAS system administration.