1. What Student E-page provides
Student E-page organises student-support services, requests, documents, messages, status tracking and sourced admission information. Some services involve assistance with external portals or processes controlled by third parties.
A Student E-page request does not by itself guarantee admission, examination results, acceptance, clearance, a portal outcome or successful completion of a third-party process.
2. Accounts and access
Use accurate account information and keep your password private. Do not share another person’s account or attempt to access requests, files or admin functions you are not authorised to use.
New student accounts must verify their email before signing in. Password-reset links are one-time use and invalidate existing signed-in sessions after a successful reset. Real email delivery depends on the deployment email provider.
3. Service requests
Review the service page, requirements, availability and current pricing information before submission. You are responsible for checking the information you enter before creating a request.
The team may ask for more information or documents. A request can be cancelled when work should not continue. Completed and cancelled requests are closed to new student messages and uploads under the current workflow.
4. Information and documents you provide
Provide only information needed for the selected service. Do not place passwords, OTPs, bank-card details, verification codes or examination PINs in normal request messages.
You must not intentionally upload unlawful, malicious or unrelated files. Uploads have format and size checks. Production deployments are expected to use the configured malware scanner before a new file is stored; local development may allow unscanned sample files.
5. Fees, quotes and payments
Where a fixed fee is configured, the interface may separate provider charges from the Student E-page service fee. Quote-required services can receive an itemised quote that the student can accept or decline.
Where Paystack is enabled, checkout is started from the request and payment is applied only after server-side verification of the provider reference, amount and currency. TEST payment records remain workflow-only and are not proof of money received. See the Refund Policy.
6. Admission information
Published school pages, admission updates and deadlines are managed content. Publishing requires source information and a last-checked date, but admission details can still change after they are published.
When a deadline, cut-off mark, eligibility rule or school requirement matters, follow the linked official source and confirm with the institution.
7. Service availability and changes
Services can be paused when they are not currently available. Existing saved requests keep their recorded service and fee snapshot. Public content and service details can be updated when new verified information becomes available.
Do not rely on a previously opened browser tab after a visible change warning; refresh and review the latest saved information.
8. Current development limits
This version is designed for local testing. It does not by itself provide production hosting, SMS/WhatsApp delivery or direct automatic submission to education portals. A ClamAV file-scanning integration is available but still requires deployment configuration and acceptance testing. Email verification and password recovery require a configured email provider. Paystack checkout is available only on deployments that explicitly configure it.
Before public launch, the final operational details and these terms must be reviewed again. For current support, use the Help Centre or Contact page.