Legal
This page explains what personal data MoonTechLife collects, why it is collected, how it is used, and the choices available to users. This draft reflects the current platform features in the repository and should be reviewed with local counsel before production use.
MoonTechLife Edu Portal is a cybersecurity learning platform that provides account registration, authentication, course access, student progress tracking, support communications, instructor workflows, exam delivery, and platform security monitoring.
For privacy questions or rights requests, contact support@moontechlife.com. If you are already signed in, you can also use the internal support desk.
We may collect the following categories of data:
We use personal data to:
Depending on the processing activity, MoonTechLife may rely on contract, legal obligation, legitimate interests, and consent. Consent is especially relevant where optional communications or non-essential cookies are used.
If you rely on consent-based processing, you should be able to withdraw that consent without losing access to strictly necessary platform functions.
Based on the current codebase, personal data may be processed by service providers such as:
You should keep written vendor agreements in place and document any international transfers where providers host or access data outside Nigeria.
Data should be kept only for as long as needed for the original purpose, legal obligations, platform security, dispute handling, or academic record management.
MoonTechLife should maintain a formal retention schedule covering profiles, submissions, support tickets, exam records, security logs, backups, and inactive accounts.
Subject to applicable law, users may request to:
To make a request, contact support@moontechlife.com or use the support page. Signed-in students can use the student support desk and choose the privacy category once enabled in the product.
If the platform is used by minors, MoonTechLife should define the relevant age threshold, parental or guardian consent process where required, and the school or institutional basis for processing student records.
If the service targets adults only, that should be stated clearly in the registration and terms flow.
The repository already shows controls such as secure session handling, security event logging, rate limiting, MFA setup, and protected routes. These controls reduce risk but do not remove the need for regular review, vendor hardening, backup controls, and documented incident response.