This page explains how public content, applicant records, enrolled-student Academic Workspace and Institutional Control Center are separated. Role selection is not authentication. Student Login and Institutional Login use the Hostinger API. A remembered role or local device code is not access.
Install ≠ Access
Installing this application installs the application shell and permitted public content only. Installation does not grant access to candidate records, institutional records, confidential documents, fee information, assessment information, screening information or attendance records. Installation ≠ Access.
Public App ≠ Candidate Workspace
Public App ≠ Candidate Workspace. Public pages do not display candidate-specific personal, financial, screening, attendance or assessment records.
Candidate Verification
Candidate Verification for controlled access to the candidate's institutional workspace.
Candidate Verification is not a login, sign-up, username/password account, or user-registration system.
Candidate Verification provides controlled access to the candidate's institutional workspace. It does not constitute Government, HSSC, Aadhaar, or other third-party identity authentication.
Institutional Workspace
Institutional access is granted only after server-side staff authentication on the Hostinger API. Role selection is not access. A local device code, generated PIN, or remembered role is not institutional authentication.
Ordinary candidate verification does not unlock the administrator register, all-candidate database, or other candidates' records.
Security limitation
Without conventional authentication, Candidate Verification provides controlled application-level access but should not be treated as a substitute for a full identity-management or server-side authentication system.
Local-first storage on this device is not tamper-proof, not cloud authentication, and not a substitute for institutional identity management.