Privacy policy
This Privacy Policy explains how Makronexus (“Makronexus”, “we”, “us”, “our”) collects, uses, shares, and protects personal information when schools and their users access Makronexus Education—including the platform, admissions workflows, and public website.
Last updated 13 November 2026 · Version 3.1 · Applies in Zimbabwe
Contents (20 sections)
1. About Makronexus
Makronexus Education is the school-management service supplied under the Makronexus brand. The legal supplier and its service address are identified in the relevant school order or customer agreement; schools may request those registered particulars from our contact address before contracting.
For information a school controls in its tenant, that school ordinarily determines why the information is collected and how it may be used. Makronexus ordinarily acts as its data processor under documented instructions. For our own website enquiries, account administration, supplier billing, customer support, service security and direct marketing, Makronexus may act as an independent controller.
The precise allocation of responsibilities for admissions, multi-school groups, locally hosted servers and authorised integrations is set out in the applicable school agreement and data-processing schedule. Neither a school nor Makronexus is relieved of duties imposed on it by law.
2. Scope & Application
This notice covers the public website, admission application interfaces, customer support, and personal information processed through Makronexus Education when deployed as a hosted service or on an authorised school server. A school may provide its own privacy notice and consent forms for activities it controls.
In an offline or self-hosted deployment, student records may remain on school-controlled equipment while authorised synchronisation, support, updates or backups may involve separate systems. What data leaves the local environment depends on the deployment configuration and the written agreement, and must be confirmed with the school before activation.
This notice is principally written for Zimbabwean school operations. Other jurisdictions may impose additional requirements; an applicable signed school agreement must identify them where relevant.
3. Key Definitions
We use the meanings of personal information, data subject, controller, processor, consent and processing in the Zimbabwe Cyber and Data Protection Act [Chapter 12:07]. A controller decides the purpose and means of processing; a processor handles information on documented controller instructions.
Sensitive data has a wider statutory meaning than medical information alone. Depending on context it can include health, genetic, biometric, financial, educational, employment, criminal, family and other information identified by the Act or presenting significant risk to an individual. Learners' information requires particular safeguards.
A sub-processor is a supplier engaged to process school-controlled personal information for the services. A personal-data breach includes unauthorised access, loss, destruction, alteration or disclosure affecting personal information.
4. Data We Collect
The categories and scope of personal data processed depend on the school's configuration, the modules enabled, and how end users interact with the Services. We categorise data as follows:
4.1 Account & Identity Data
- Full name, username, email address, phone number, role (e.g. administrator, teacher, parent, learner), profile photograph, and school/organisation affiliation.
- Authentication credentials (hashed passwords, session tokens, multi-factor authentication records).
4.2 Learner Data
- Student identifiers (internal IDs, national registration where provided by the school), date of birth, gender, nationality, home language, and residential address.
- Academic records: class/grade enrolment, subjects, assessment marks, report cards, examination results, promotion history, and curricular comments.
- Attendance records, disciplinary records, and extracurricular participation (as configured by the school).
- Special educational needs or welfare notes (only where the school chooses to record this; treated as sensitive data with restricted access).
- Photographs or document scans uploaded by the school (e.g. birth certificate copies, transfer letters).
4.3 Parent & Guardian Data
- Full name, relationship to learner, contact details (email, phone, address), employer information (if collected by the school).
- Communications preferences (SMS, email, push), language preferences, and interaction history within the parent portal.
- Admissions application data: application forms, uploaded documents, application status, and interview/assessment notes.
4.4 Staff & HR Data
- Employee identifiers, employment dates, department, qualifications, teaching subjects, and timetable assignments.
- Leave records, performance review data, and professional development logs (where enabled by the school).
4.5 Financial & Billing Data
- Fee structures, invoices, payment records, outstanding balances, receipts, and scholarship/bursary information.
- Payments made through an enabled payment provider are subject to that provider's own processing and security arrangements. Do not enter full card details in school free-text fields.
4.6 Communications Data
- Messages, announcements, notice templates, delivery status logs, and parent-school correspondence within the platform.
4.7 Technical & Usage Data
- Device identifiers, IP address, browser/OS type and version, screen resolution, timezone, and language setting.
- Pages/screens visited, feature usage metrics, click events, timestamps, session duration, and referral source.
- Error and performance logs, API request metadata (method, endpoint, status code, response time).
4.8 Support & Correspondence
- Support tickets, screenshots, attachments, troubleshooting logs, and feedback survey responses.
4.9 Admissions & Application Data
- Online application form submissions, uploaded supporting documents, application timeline, reviewer notes, and acceptance/rejection decisions.
- Waitlist positions, communications with applicant families, and related workflow data.
5. How We Collect Data
Schools and their authorised staff supply learner, guardian and staff information through enrolment, admissions, imports, day-to-day administration and connected systems. Parents and applicants may supply information directly through an application form operated for a school.
Makronexus collects separate website enquiries, support correspondence, billing contacts and technical information needed to deliver and protect its service. The categories of technical identifiers and browser storage used are described in the Cookie Policy.
We do not represent that optional analytics pixels, third-party session recording or identity-verification suppliers operate on every site or deployment. Where any such processing is enabled, it must be assessed and disclosed in the relevant collection notice.
6. Purposes of Processing
For school-controlled information we perform the administration and educational workflows the school configures: admissions, enrolment, attendance, assessments, discipline, fee administration, staff management, communications, reporting, access control and related support. The school is responsible for ensuring that each use has an appropriate lawful purpose.
For information we control independently we use it to respond to enquiries, manage contracts and payments, protect accounts, investigate faults, maintain security logs and send marketing messages only where lawful and with the required ability to object or withdraw consent.
School records must not be repurposed for advertising, sale, unrelated profiling or identifiable external research. Any proposed secondary use must first be separately assessed, lawfully authorised, documented and, where applicable, approved by the school and the affected individuals.
7. Legal Basis for Processing
The applicable grounds depend on the data and purpose. Sections 10 and 11 of the Cyber and Data Protection Act address consent, permitted grounds for processing non-sensitive information, and special rules for sensitive data. A subscription contract between Makronexus and a school does not itself replace a required parent or guardian consent or justify unrelated processing.
- For school-controlled learner and staff records, the school must identify and document the lawful ground, any statutory duty and the notices or consents required before using a module.
- For children's information, obtain and reasonably verify parental or legal-guardian consent where required by the Cyber and Data Protection Regulations, 2024 (SI 155 of 2024).
- Sensitive information requires the protections and consent or applicable lawful exceptions provided by the Act; do not rely on ordinary adult implied consent as a universal substitute.
- For our own business information we document the lawful ground appropriate to each activity, including consent where required, applicable legal duties and permitted legitimate interests.
Schools must not instruct Makronexus to process data unlawfully. Makronexus may seek clarification, suspend an unlawful instruction or cooperate with a lawful regulatory request.
8. Children & Minors
The platform is designed for schools, including children under 18. Under section 26 of the Act, a child's statutory rights may be exercised through a parent or legal guardian. Regulation 10(5) of SI 155 of 2024 requires controllers to address guardian consent, reasonable verification, privacy by design and default, regular child-data impact assessments and protection from prohibited automated decisions.
- The school ordinarily collects, verifies and records the necessary guardian permissions and provides an understandable learner or guardian notice before processing.
- Only authorised school personnel should access sensitive learner information, subject to the school's configured roles and the measures actually available in its deployment.
- A school must not use the platform to subject a child to automated decision-making that affects the child's rights; admission and disciplinary determinations require meaningful human responsibility.
- When Makronexus independently collects data from a child, its own controller obligations apply and must not be delegated to the school by this notice.
To question a child's record, contact the school controller or support@makronexus.com. We will route school-controlled matters to the authorised school contact and support lawful correction, restriction or deletion as applicable.
9. Data Sharing & Disclosure
Personal information is made available only to recipients who have an authorised purpose: the relevant school and its permitted users, contracted hosting and communications suppliers where configured, payment providers, professional advisers bound by appropriate duties, and authorities when disclosure is legally required.
Access is governed by the configured roles and deployment arrangements. We do not sell school-controlled records to advertising buyers or use identifiable learner records to target Makronexus marketing.
A school can request the current recipient and sub-processor schedule for its actual deployment. Disclosure to an overseas recipient requires a separate transfer assessment under Zimbabwean law. We assess lawful disclosure requests and notify the school where permitted.
10. Sub-Processors
A named and deployment-specific sub-processor and destination-country schedule must form part of the executed school agreement or its controlled annex. Generic categories on a public website do not identify every recipient. The schedule should state the supplier's legal name, service, categories of information, processing location, applicable safeguards and change process.
Makronexus will only engage sub-processors for school-controlled information under the authorisation and contractual safeguards agreed with the school and required by law. The school must be notified of material additions or replacements under its agreement and given an appropriate opportunity to raise data-protection objections.
To obtain the current schedule for an existing or proposed school deployment, contact support@makronexus.com. The presence of a vendor in an illustrative product description does not establish that it receives a particular school's data.
11. International Data Transfers
Hosting, remote support, messaging, storage, backup and synchronisation can involve processing or access from outside Zimbabwe. We do not claim all school information remains in Zimbabwe or that every deployment uses the same destination countries.
Before a school enables an overseas transfer, the controller and processor must document the destination, recipient, purpose, applicable safeguards and whether the transfer meets sections 28 and 29 of the Cyber and Data Protection Act. The controller must also address any POTRAZ notification required by SI 155 of 2024, including regulation 10(2)(c).
A local server does not automatically eliminate cross-border transfers: remote diagnostics, optional cloud sync, offsite backup and foreign support access must be assessed separately. Specific data-residency restrictions and approved transfer routes belong in the signed school order and DPA schedule.
12. Data Retention
We limit retention to what is necessary for the documented purpose and applicable legal duties. Schools set the retention rules for the learner, staff and educational records they control, subject to law and the capabilities of the selected deployment.
The school's executed agreement and retention schedule must specify the export window, production deletion trigger, backup expiry, legal holds, audit records and any self-hosted copies. We do not apply one universal 90-day or 180-day period to every deployment without an agreed, technically supported schedule.
Account administration, financial records, incident evidence, correspondence and other information controlled by Makronexus may be retained for separate justified periods. We restrict retained records and do not retain them merely because a contractual relationship has ended. Schools remain responsible for locally held records, their backups and statutory educational record-keeping.
13. Your Rights
Section 14 of the Cyber and Data Protection Act provides rights to be informed about use of personal information, access it, object to processing, correct false or misleading information and delete false or misleading information. These rights are subject to the Act and any applicable lawful exceptions.
Depending on the circumstances, individuals may also request withdrawal of consent, assistance with a broader deletion or export request, or other protections available under a specific agreement or other applicable law. Such additional services should not be mistaken for an unconditional statutory portability or erasure right in every case.
A parent or legal guardian may exercise a child's rights as permitted by section 26. A concern about unlawful processing may be raised with the school, Makronexus for its independently controlled activities, or the competent authority.
14. How to Exercise Your Rights
For school-controlled records, ordinarily contact the school that enrolled the learner or collected the information. We will assist the school with properly authorised access, correction or deletion instructions. If the request is sent to Makronexus first, we will identify the appropriate controller where we can do so lawfully.
For our independently controlled information, or to report a privacy concern, contact support@makronexus.com. We will verify authority before disclosing a learner's record, log the request, and respond within applicable legal requirements. A request is not refused merely because it was initially directed to the wrong organisation.
Where a request cannot be fulfilled because of a statutory exception, an unresolved identity issue or another legitimate limitation, the responsible controller should explain the basis and the available complaint route. Individuals may contact POTRAZ as Zimbabwe's Data Protection Authority.
15. Security Measures
Protecting education records requires layered technical and organisational measures appropriate to the information, the deployment and the assessed risks. Controls include authenticated access, role permissions, monitored administrative activity, secure data transmission, vulnerability remediation, incident handling and suitable backup and recovery arrangements.
The exact controls, supported encryption methods, log retention, restore testing, staff vetting and recovery targets vary by hosting model and must be recorded in a versioned technical-and-organisational-measures schedule supplied to the school. This notice is not a claim of ISO 27001 or SOC 2 certification, uninterrupted protection or implementation of an unverified feature.
For school-hosted systems, the school must secure its devices, local network, physical server, user onboarding and offboarding, power arrangements and locally managed backups to the extent allocated in the service agreement. Both parties must promptly report suspected compromises through their defined incident contacts.
16. Cookies & Tracking Technologies
Our public website uses cookies and similar technologies for security, basic analytics, and improving content. The platform uses session storage and local storage for operational and security purposes.
For a complete breakdown of cookie types, third-party cookies, and how to manage preferences, see our dedicated Cookie Policy.
17. Automated Decision-Making & Profiling
Automated reports, flags and scoring features may assist authorised school personnel, but should not replace the school's independent judgement in admissions, welfare, discipline or another decision affecting a child's rights.
Under regulation 10(5)(f) of SI 155 of 2024, controllers must not subject children's data to automated decision-making that has the effect of affecting children's rights. A school must review proposed automations and conduct child-data impact assessments before enabling high-risk workflows.
Requests to contest, explain or correct an outcome should be directed to the school, with Makronexus providing appropriate technical assistance. Any new AI-driven or automated feature requires separate legal and operational review before activation.
18. Data Breach Notification
Section 19 of the Cyber and Data Protection Act and regulation 17 of SI 155 of 2024 require a data controller to notify POTRAZ of a personal-data breach within 24 hours of becoming aware. Where the breach is likely to present a high risk to individuals, the Regulations additionally address notification of those individuals within 72 hours.
Makronexus will escalate actual or reasonably suspected incidents affecting school-controlled personal information to the school without undue delay, using the agreed incident contact. An initial warning may be incomplete and must not be held back merely to establish final cause or severity. We will supply available facts, mitigation steps and further updates to help the school meet its legal duties.
Each school remains responsible for controller notifications where required. Makronexus is independently responsible for incidents affecting data it controls itself. The parties must maintain current incident contacts and a practical escalation procedure in their DPA and support schedule.
19. Changes to This Policy
We may update this notice where laws, services, recipients or processing activities change. We will show the revised date and version and communicate material changes to affected schools in accordance with their agreements and applicable law.
A material new purpose of processing, foreign transfer or optional tracking activity is not authorised solely by posting revised text. Where new consent, school instruction, regulator notification or another lawful step is needed, it must be completed before the relevant processing begins.
20. Contact Us
If you have questions about this Privacy Policy, wish to exercise your rights, or need to report a privacy concern, please contact us:
If you are not satisfied with our response, you may escalate your complaint to the Postal and Telecommunications Regulatory Authority of Zimbabwe (POTRAZ) or the relevant data protection supervisory authority.