Data Processing Addendum
This page summarises proposed data-processing terms for Makronexus Education. A school-specific DPA takes legal effect only when executed or expressly incorporated into an authorised school agreement. The signed pack must identify both parties, their processing roles, their deployment and the applicable schedules.
Last updated 13 November 2026 · Version 3.1 · Applies in Zimbabwe
Contents (18 sections)
1. Definitions & Interpretation
Unless otherwise defined, capitalised terms in this DPA have the same meaning as in the main agreement (the “Agreement”) between the School and Makronexus.
| Term | Definition |
|---|---|
| Controller | The School, which determines the purposes and means of processing personal data. |
| Processor | Makronexus, which processes personal data on behalf of the Controller. |
| Data Subject | An identified or identifiable natural person whose personal data is processed (e.g. learner, parent, staff member). |
| Personal Data | Any information relating to a Data Subject as defined under the Cyber and Data Protection Act [Chapter 12:07]. |
| Processing | Any operation or set of operations performed on personal data, whether automated or manual. |
| Sub-Processor | A third party engaged by the Processor to process personal data on behalf of the Controller. |
| Data Breach | A breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to personal data. |
| TOMs | Technical and organisational measures implemented to ensure a level of security appropriate to the risk. |
| Services | The Makronexus Education platform and related services provided under the Agreement. |
| The Act | The Cyber and Data Protection Act [Chapter 12:07] of Zimbabwe. |
2. Scope & Application
This page sets out the proposed data-processing provisions for Makronexus Education. It becomes a binding DPA for a particular school only when an authorised school agreement expressly incorporates it, or the parties execute the applicable DPA pack. A public web page is not a substitute for the written contract or legal instrument required by section 18(5) of the Cyber and Data Protection Act and regulation 10(4)(f) of SI 155 of 2024.
Before processing begins, the executed arrangement must identify the legal supplier, school controller, authorised signatories, instructions, purposes, deployment, categories of personal information, technical safeguards, subprocessors, recipients and data locations, and agreed schedules for retention, incidents and exit.
For ordinary learner, parent and staff records, the school is the controller and Makronexus the processor. For Makronexus's own business records, it may be a separate controller; those records are covered by the Privacy Policy rather than a school's processing instructions. Different roles must be expressly documented where they arise.
3. Roles & Responsibilities
The school controls the purposes of processing, determines lawful grounds and school policies, gives appropriate notices, manages access, ensures required guardian consent and its verification, and makes statutory decisions about its learners and employees. The school must identify its breach contact and comply with applicable licensing, DPO and regulator-notification requirements.
Makronexus processes school information on documented lawful instructions, protects it through appropriate technical and organisational measures, binds authorised personnel to confidentiality, supports rights requests and lawful regulator engagement, and alerts the school promptly when an incident or unlawful instruction is identified.
Both parties must document who operates and secures local equipment, cloud services, synchronisation, backups, communications, user accounts and exports. The allocation of operational duties does not exclude either party's mandatory duties under Zimbabwean law.
4. Details of Processing
4.1 Categories of Data Subjects
| Category | Description |
|---|---|
| Learners | Students enrolled at the School, including current and former. |
| Parents / Guardians | Parents, legal guardians, and emergency contacts of learners. |
| Teaching staff | Teachers, lecturers, tutors, and teaching assistants. |
| Administrative staff | School administrators, IT staff, finance staff, and support personnel. |
| Applicants | Prospective learners and their families applying through admissions. |
| External contacts | Vendors, contractors, and other third parties whose data may be stored by the School. |
4.2 Categories of Personal Data
| Category | Examples |
|---|---|
| Identity data | Full name, date of birth, gender, nationality, national ID numbers, student IDs, photographs. |
| Contact data | Email addresses, phone numbers, physical addresses, emergency contacts. |
| Academic data | Grades, assessments, attendance, report cards, class enrolments, disciplinary records, academic history. |
| Financial data | Fee structures, invoices, payment records, balances, bursary/scholarship information. |
| Employment data | Employee ID, qualifications, employment dates, department, timetable, leave records, professional development. |
| Communications data | Messages, announcements, notification logs, delivery status. |
| Technical data | IP addresses, device identifiers, browser information, login timestamps, audit logs. |
| Application data | Admissions forms, uploaded documents, interview notes, application status. |
| Sensitive data | Health information, special educational needs, welfare notes (only where the School chooses to record this). |
4.3 Purposes of Processing
| Purpose | Description |
|---|---|
| Service provision | Hosting the platform, managing tenants, processing data as instructed by the School. |
| Authentication & security | User authentication, session management, RBAC enforcement, fraud prevention. |
| Admissions management | Processing applications, document management, communications with applicant families. |
| Academic management | Maintaining student records, assessments, report generation, attendance tracking. |
| Financial management | Fee invoicing, payment processing, financial reporting, receipting. |
| Communications | Sending notifications, announcements, and transactional messages on behalf of the School. |
| Support | Providing technical support and troubleshooting. |
| Backup & recovery | Automated encrypted backups for disaster recovery and business continuity. |
| Compliance & audit | Maintaining audit logs, supporting regulatory compliance, and record-keeping. |
4.4 Duration of Processing
Processing continues for the duration of the Agreement and for the post-termination period specified in Section 14 (Data Return & Deletion), unless extended with the School's written consent or required by law.
5. Processor Obligations
Makronexus must process School Data only for the documented service purposes and lawful instructions, unless a binding legal obligation requires otherwise. Where legally allowed, we will notify the school before processing that departs from its instructions.
- Limit access to authorised persons who are subject to confidentiality duties and remove access when it is no longer needed.
- Apply and maintain appropriate security measures, assist with privacy requests, incident investigations, breach reports and regular child-data impact assessments.
- Ensure that authorised subprocessors are subject to enforceable written obligations and permitted transfer safeguards.
- Provide information reasonably needed for contractual verification and lawful regulator review, subject to protecting other schools' information.
- After termination, assist with data export and delete or retain information only in accordance with the agreed exit schedule and applicable law.
- Promptly inform the school where an instruction appears to conflict with the Act or other applicable data-protection law.
Nothing in this DPA permits independent exploitation, sale, behavioural advertising or unrelated profiling of identifiable School Data.
6. Confidentiality
Makronexus must restrict school-controlled information to authorised personnel who need it to perform their work and who are bound by suitable confidentiality obligations. We must ensure appropriate safeguards apply to contractors and authorised subprocessors.
Access to learner information, financial records, disciplinary information, medical or special-needs records and other sensitive categories must be proportionate to role and purpose. Each party must promptly revoke unnecessary access under its control.
Confidentiality and security duties continue for as long as School Data remains stored, accessible, exported, held in backup or otherwise processed under this DPA or applicable law.
7. Technical & Organisational Measures (TOMs)
A signed technical-and-organisational-measures schedule must define the security controls for the actual deployment before production use. It should cover user authentication and permissions, secure transmission, appropriate protection of stored information, privileged access, audit records, vulnerability management, incident handling, personnel access, backups, disaster recovery and change control.
Makronexus must maintain measures appropriate to the risks and provide reasonable evidence of their operation. Specific algorithms, encryption coverage, monitoring tools, daily backup frequency, restoration targets, testing cycles, supplier certifications and retention periods must be confirmed in the versioned schedule; this public template does not assert that every listed measure is presently implemented in every deployment.
The school and Makronexus must separately identify physical, operating-system, network, patching, power, user administration, offline synchronisation and local backup responsibilities for any school-hosted server. Controls must be reassessed when a material change is made or a serious risk is identified.
No ISO 27001, SOC 2 or independent security certification is represented by the existence of this DPA.
8. Sub-Processor Management
A school must receive a named, dated list of all approved subprocessors applicable to its deployment, identifying each provider, the service supplied, categories of information, processing country and applicable transfer safeguards. The list forms a controlled annex to the executed DPA, not a generic promise that a list may be requested after onboarding.
Makronexus must obtain appropriate written commitments from authorised subprocessors and remain responsible for its own obligations under this DPA and applicable law. Planned material additions or replacements must be communicated in the manner and notice period agreed with the school, with a reasonable opportunity to object on documented data-protection grounds.
The parties must determine whether an objection can be addressed through alternatives, additional safeguards or termination of the affected service without unlawful loss of access to essential school information.
9. International Data Transfers
Transfers, foreign support access, overseas storage, global messaging services and offsite backups involving School Data must be recorded before activation in the signed transfer schedule. Each entry should identify destination, recipient, data categories, purpose and safeguard.
The school and Makronexus must assess the transfer in light of sections 28 and 29 of the Cyber and Data Protection Act, applicable exceptions, and any notification to POTRAZ required under regulation 10(2)(c) of SI 155 of 2024. A subprocessor contract or encryption is not, by itself, proof that every transfer is lawful.
A school operating an onsite server should agree separately on any remote-access, diagnostic, sync or backup routes. Makronexus must not activate a materially different cross-border processing route for School Data without the authorisation and legal steps required by the executed DPA and law.
10. Data Subject Rights Assistance
The school ordinarily determines and responds to requests regarding learner, guardian and staff information. Makronexus will assist with retrieval, authorised correction, deletion of false or misleading data, objections and other rights applicable under Zimbabwean law or an agreed contractual service.
When a request reaches Makronexus directly, we will reasonably determine whether we are the controller or processor for the information in question and refer or handle it accordingly. Reasonable identity and authority verification must precede any disclosure, especially for children's information.
The school's DPA schedule should identify points of contact, escalation and feasible assistance periods so that the controller can meet applicable legal deadlines. No platform functionality is an unconditional promise of instant deletion from every audit record or backup.
11. Data Breach Notification
Zimbabwe's Cyber and Data Protection Act section 19 and SI 155 of 2024 regulation 17 require the controller to report a personal-data breach to POTRAZ within 24 hours after awareness. The Regulations also require notification of affected individuals within 72 hours in high-risk circumstances.
Makronexus will alert the school without undue delay after identifying an actual or reasonably suspected breach affecting School Data. Initial notification will not be postponed solely until an investigation is complete or the precise number of affected persons is known. Updates will provide the facts available, affected systems or data, containment steps, known risks and contact details.
Each party will maintain an operational incident contact and escalate incidents promptly enough to support statutory reporting. The school has its own controller reporting duty; Makronexus must assist with investigation and required notices and fulfil any separate duties for information it independently controls.
The executed support and incident schedule must specify the emergency communication channels, escalation responsibility, notification method, evidence preservation and post-incident review. The initial processor notice must not be deferred for 72 hours where this would prevent a school from meeting its own 24-hour reporting duty.
12. Data Protection Impact Assessments
For children's personal information, regulation 10(5)(d) of SI 155 of 2024 calls for regular data-protection impact assessments. Schools must address the nature and risks of admissions, SEN or medical records, discipline, analytics and automated decisions before adopting material high-risk processing.
Makronexus will provide the school with reasonably necessary information about the service, data flows, configured measures and approved subprocessors, and cooperate in proportionate mitigation and lawful consultation with POTRAZ.
The parties must give particular attention to remote support, foreign hosting, biometric data, profiling, guardian-consent mechanisms and locally stored data. High-risk changes should not proceed without the necessary assessment and controls.
13. Audit & Compliance
The school may request reasonable evidence that Makronexus meets its DPA and applicable statutory obligations. Routine evidence reviews should protect the security and confidentiality of other school tenants and third-party systems.
Audit scope, security conditions, notice, frequency and costs should be agreed in the school's DPA. An ordinary contractual frequency limit does not prevent urgent investigation after a serious breach, regulatory request or substantiated material security failure, or remove lawful inspection powers of POTRAZ.
Independent reports and certifications may be provided only where they actually exist and are current. A reference to ISO or SOC standards is not a representation of achieved certification.
14. Data Return & Deletion
The signed school data-exit schedule must establish when exports can be requested, available formats, transition access, production deletion, backup expiry, any agreed certification and exceptions required by law. It should include a process for restoring access to essential records during a disputed termination.
Makronexus must return or delete school-controlled information in its custody in accordance with the lawful controller instruction and that schedule, unless applicable law requires continued retention. Necessary retained copies must remain protected, access-limited and purpose-restricted.
No universal 90-day export window, 30-day production deletion or 180-day backup purge is promised by this template for all hosting models. Each agreed timeline must be technically feasible and consistent across the school order, Privacy Policy and Terms. School-hosted databases, local backups and exports remain within the school's allocated responsibility, without absolving Makronexus for copies it operates.
15. Records of Processing Activities
Makronexus will maintain processing records appropriate to its role and the legal requirements, including the school controller, processing categories, authorised recipients, overseas transfers, retention decisions and technical safeguards.
The school must maintain its own controller records and any required notices to POTRAZ. Each party will cooperate reasonably with lawful regulatory enquiries and keep records accurate when processing arrangements materially change.
16. Liability
Each party is responsible for damage and legal consequences attributable to its own breach of the applicable data-protection law, this DPA or documented lawful instructions, subject to causation, applicable defences and mandatory law.
The executed customer agreement should allocate ordinary commercial liability separately from privacy, confidentiality, security and children's information risks, and may provide negotiated caps only to the extent legally enforceable. A blanket cap calculated from the previous 12 months' fees does not automatically extinguish statutory rights or non-excludable liabilities.
Neither party may exclude its own fraud, wilful misconduct or another liability that the law does not allow it to limit. The parties will cooperate in responding to affected individuals and regulators and allocate joint losses according to legally established responsibility.
17. Term & Termination
This DPA takes effect for a school when it is validly executed or expressly incorporated into that school's accepted agreement and continues for as long as Makronexus or its authorised subprocessors process or retain School Data.
End of the commercial subscription does not end confidentiality, incident cooperation, audit access where legally required, data export, retention or deletion obligations until those duties are discharged. A change of service provider or local hosting arrangement must follow the school's approved exit schedule.
18. Contact
To obtain an executable DPA pack, contact support@makronexus.com and provide the school's authorised representative, deployment type, service order and any relevant regulator or data-residency requirements.
Before signing, the pack must state the actual legal entities and service addresses, the school's authorised controller and incident contacts, responsible privacy or DPO contacts where appointed, the scope and duration of processing, technical controls, named subprocessors and transfer countries, and the return-and-deletion schedule.
The website version provides general information and proposed contractual provisions; it does not itself attest to the current licence, external certification or regulatory status of either party.