Aisprx

Aisprx security: controls and boundaries

Aisprx uses product-specific access controls and records for learning, examination, interview-practice and shared-room workflows. Technical mechanisms need deployment and device-level validation before anyone can claim an outcome.

Identity and product access

Shared sign-in does not give a person permission to every Aisprx product or every institution's records. Server routes apply product, role and organization scope to learning and examination administration. Candidates may enter a specific exam through an admission grant; that grant is limited to its assessment flow.

Examination safeguards

Exam server code manages shifts, admission, attempt checkpoints, submission and proctor access. A desktop client contains lockdown policy handling, remote-access detection modules and calls to platform capture-protection APIs. These controls are configurable and depend on the installed release, operating system and device permissions. They do not make an exam cheat-proof or establish a measured detection rate.

Shared-room privacy

BeClose supports host controls, authenticated account features and guest participation in some room flows. Its source uses a room-derived chat key in one messaging path and explicitly does not describe that path as end-to-end encryption. Do not assume room media or messages are end-to-end encrypted. Review your privacy needs before sharing sensitive information.

Assurance and questions

This page describes code-observed mechanisms, not an audit certificate, a production configuration or a guarantee that all controls work on every device. Current certification, data-region, retention, cipher and effectiveness claims require owner and deployment verification. Read the privacy policy, examination guide and security reporting instructions. Contact Aisprx with procurement questions.