Data Processing Addendum
This Data Processing Addendum (“DPA”) supplements the agreement between Makronexus (Pvt) Ltd (“Processor”, “Makronexus”) and the subscribing school or institution (“Controller”, “School”). It sets out the terms under which Makronexus processes personal data on behalf of the School when providing the Makronexus Education Services.
Controller / Processor
The School controls data collection and purposes. Makronexus processes data strictly under the School's instructions.
Security Measures
Comprehensive technical and organisational measures (TOMs) aligned with enterprise education standards.
Breach Notification
72-hour breach notification commitment with structured incident response and remediation.
Data Portability
Full data export in standard formats with certified deletion upon contract termination.
Contents
1Definitions & 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 (Pvt) Ltd, 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. |
2Scope & Application
- This DPA applies to all processing of personal data by Makronexus on behalf of the School in connection with the provision of the Services.
- This DPA is incorporated into and forms part of the Agreement. In the event of a conflict between this DPA and the Agreement, this DPA prevails with respect to data protection matters.
- This DPA applies to both cloud-hosted (SaaS) and self-hosted deployments, though specific security measures may vary based on deployment model.
- The School acknowledges that it is the Controller for all personal data processed through the Services and remains responsible for the lawfulness of its processing instructions.
3Roles & Responsibilities
3.1 Controller (School)
- Determines the purposes and means of processing personal data.
- Ensures a lawful basis exists for all processing (e.g. contractual necessity, legitimate interest, consent).
- Provides appropriate privacy notices to Data Subjects (learners, parents, staff).
- Obtains any consents required under applicable law.
- Manages user access, roles, and permissions within the platform.
- Ensures its processing instructions to Makronexus comply with applicable data protection law.
- Implements appropriate internal data governance policies.
3.2 Processor (Makronexus)
- Processes personal data only on documented instructions from the Controller, unless required by law.
- Implements appropriate technical and organisational measures to protect personal data.
- Assists the Controller in fulfilling its obligations under the Act (data subject requests, breach notification, impact assessments).
- Ensures that personnel authorised to process personal data are bound by confidentiality obligations.
- Engages sub-processors only with prior notice to the Controller and under data protection agreements.
4Details 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.
5Processor Obligations
Makronexus undertakes to:
- Process personal data only on the documented instructions of the School, including with regard to transfers of personal data to a third country, unless required to do so by law—in which case Makronexus will inform the School of that legal requirement before processing (unless prohibited by law).
- Ensure that persons authorised to process personal data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality.
- Take all measures required pursuant to Section 7 (Security Measures).
- Respect the conditions for engaging sub-processors as set out in Section 8.
- Taking into account the nature of the processing, assist the School by appropriate technical and organisational measures in fulfilling the School's obligation to respond to requests for exercising Data Subject rights.
- Assist the School in ensuring compliance with its obligations related to security, breach notification, data protection impact assessments, and prior consultation, taking into account the nature of processing and the information available to Makronexus.
- At the choice of the School, delete or return all personal data after the end of the provision of Services, and delete existing copies unless applicable law requires storage.
- Make available to the School all information necessary to demonstrate compliance with the obligations laid down in this DPA and the Act, and allow for and contribute to audits and inspections.
- Immediately inform the School if, in Makronexus's opinion, an instruction from the School infringes the Act or other applicable data protection provisions.
6Confidentiality
- Makronexus ensures that all personnel involved in processing personal data are bound by written confidentiality agreements or are under appropriate statutory obligations of confidentiality.
- Confidentiality obligations extend to all employees, contractors, and agents who have access to personal data in connection with the Services.
- Confidentiality obligations survive the termination of employment or engagement.
- Access to personal data is provided on a strict need-to- know basis, consistent with the principle of least privilege.
7Technical & Organisational Measures (TOMs)
Makronexus implements and maintains the following security measures, which are reviewed and updated regularly:
7.1 Access Control
- Role-based access control (RBAC) with granular, configurable permissions.
- Multi-factor authentication (MFA) support for administrator accounts.
- Automatic session expiry and re-authentication for sensitive operations.
- Principle of least privilege enforced across all system roles.
- Centralised identity and access management.
7.2 Encryption
- TLS 1.2 or higher for all data in transit.
- AES-256 encryption for sensitive data at rest.
- Passwords hashed using industry-standard algorithms with unique salts.
- Encryption key management following security best practices.
7.3 Network & Infrastructure Security
- Firewall protection and network segmentation.
- DDoS protection and rate limiting.
- Intrusion detection and prevention systems.
- Regular vulnerability scanning and penetration testing.
- Hardened server configurations with automated patching.
- Secure software development lifecycle (SSDLC) practices.
7.4 Monitoring & Audit Logging
- Comprehensive audit trails for data access, creation, modification, and deletion.
- Real-time security event monitoring and alerting.
- Log retention for security analysis and compliance (up to 3 years).
- Tamper-evident log storage with restricted access.
7.5 Business Continuity & Disaster Recovery
- Automated encrypted backups with defined frequency (minimum daily for cloud deployments).
- Geographically separated backup storage where applicable.
- Documented disaster recovery plans with defined Recovery Time Objectives (RTO) and Recovery Point Objectives (RPO).
- Regular testing of backup restoration and recovery procedures.
7.6 Personnel Security
- Background checks for personnel with access to personal data.
- Security awareness training for all employees.
- Documented incident response roles and responsibilities.
- Prompt access revocation upon employment termination.
7.7 Physical Security
- Data centres used by Makronexus (cloud infrastructure providers) maintain industry-standard physical security controls including access controls, surveillance, and environmental protections.
- For self-hosted deployments, the School is responsible for physical security of on-premises infrastructure.
8Sub-Processor Management
- Prior notification: Makronexus will notify the School of any intended changes concerning the addition or replacement of sub-processors at least 30 days in advance (or such other period as agreed in the Agreement).
- Right to object: The School may object to a new sub-processor on reasonable data protection grounds within the notice period. If the School objects and Makronexus cannot reasonably accommodate the objection, either party may terminate the affected Services.
- Contractual obligations: Makronexus imposes data protection obligations on each sub-processor by way of a written contract that provides at least the same level of protection as this DPA.
- Liability: Makronexus remains fully liable to the School for the performance of each sub-processor's obligations.
- Current list: A current list of sub-processors is available upon request. Contact us for the latest sub-processor register.
8.1 Sub-Processor Categories
| Category | Purpose | Data Processed |
|---|---|---|
| Cloud infrastructure | Hosting, compute, database, and object storage | All platform data (encrypted at rest and in transit) |
| Email delivery | Transactional and notification emails | Recipient email, name, message content |
| SMS / messaging | SMS notifications to parents and staff | Phone number, message content |
| Error monitoring | Application error tracking and alerting | Error context (may include user ID, request metadata; no academic data) |
| Payment processing | Fee collection and subscription billing | Billing contact, payment transaction data (PCI-DSS compliant) |
| Analytics | Anonymous product usage analytics | Anonymised usage events (no PII) |
9International Data Transfers
- Where personal data is transferred to a country outside Zimbabwe, Makronexus ensures that appropriate safeguards are in place as required by the Act.
- Safeguards include: contractual data protection clauses with sub-processors; assessment of the destination country's data protection framework; encryption and access controls; and pseudonymisation where feasible.
- The School may request information about the countries where personal data is processed and the safeguards in place.
- Where the School requires data residency within Zimbabwe, Makronexus will discuss feasible deployment options (including self-hosted or Zimbabwe-hosted infrastructure).
10Data Subject Rights Assistance
- Makronexus will assist the School in responding to Data Subject requests (access, rectification, erasure, restriction, portability, objection) by providing appropriate technical and organisational measures.
- If Makronexus receives a Data Subject request directly, it will promptly redirect the request to the School (unless legally prohibited) and will not respond independently unless instructed by the School.
- The platform provides built-in tools for Schools to manage Data Subject requests, including data export, record amendment, and record deletion capabilities.
- Makronexus will respond to School requests for assistance within 5 business days.
11Data Breach Notification
- Notification timeline: Makronexus will notify the School of a Data Breach without undue delay and in no event later than 72 hours after becoming aware of the breach.
- Initial notification content: The nature of the breach, categories and approximate number of Data Subjects affected, categories of data affected, likely consequences, and measures taken or proposed to address and mitigate the breach.
- Supplementary information: Where full details are not available at the time of initial notification, Makronexus will provide supplementary information as it becomes available.
- Documentation: Makronexus will document all Data Breaches, including facts, effects, and remedial action taken, and make this documentation available to the School.
- Regulatory notification: Makronexus will cooperate with the School in notifying POTRAZ or any other competent authority as required by the Act.
- Individual notification: The School remains responsible for notifying affected individuals where required. Makronexus will provide reasonable assistance in preparing such notifications.
12Data Protection Impact Assessments
- Where a type of processing is likely to result in a high risk to the rights and freedoms of Data Subjects, the School shall carry out a Data Protection Impact Assessment (DPIA) prior to the processing.
- Makronexus will provide the School with all information reasonably necessary to conduct a DPIA, including details about the nature of processing, security measures, and sub-processors.
- Makronexus will cooperate with the School and any supervisory authority in connection with prior consultation as required by the Act.
13Audit & Compliance
- Information access: Makronexus will make available to the School all information reasonably necessary to demonstrate compliance with this DPA and the Act.
- Audits: The School (or a mandated independent auditor) may conduct audits, including inspections, to verify Makronexus's compliance with this DPA. Audits will be conducted with reasonable notice (minimum 30 days), during business hours, and in a manner that does not unreasonably disrupt Makronexus's operations.
- Audit frequency: The School may conduct audits no more than once per 12-month period, unless required by a Data Breach or regulatory investigation.
- Costs: Each party bears its own costs in connection with audits, unless otherwise agreed.
- Third-party certifications: Where available, Makronexus may provide third-party audit reports or certifications (e.g. SOC 2, ISO 27001) as evidence of compliance, which the School may accept in lieu of an on-site audit.
14Data Return & Deletion
- During the term: The School may export its data at any time using the platform's built-in export tools (CSV, PDF, and other supported formats).
- Post-termination export: Upon termination or expiry of the Agreement, Makronexus will make the School's personal data available for export for a period of 90 days (the “Export Period”), unless otherwise agreed in the Agreement.
- Deletion: After the Export Period, Makronexus will securely delete all personal data from production systems within 30 days. Encrypted backup copies will be purged within 180 days following the end of the Export Period.
- Certification: Upon request, Makronexus will provide written certification confirming that personal data has been deleted in accordance with this section.
- Exceptions: Makronexus may retain personal data beyond the deletion timeline only where required by applicable law (e.g. tax records, audit logs required for compliance). Retained data will be isolated and protected.
15Records of Processing Activities
Makronexus maintains records of processing activities carried out on behalf of each School, as required by the Act. These records include:
- Name and contact details of the Processor (Makronexus) and each Controller (School).
- Categories of processing carried out on behalf of the School.
- Where applicable, details of transfers to third countries and the safeguards in place.
- A general description of technical and organisational security measures.
These records are maintained in electronic form and are available to the School and any supervisory authority upon request.
16Liability
- Each party is liable for damage caused by processing that infringes the Act or this DPA.
- Makronexus is liable for damage caused by processing only where it has not complied with obligations of the Act specifically directed to processors, or where it has acted outside or contrary to the lawful instructions of the School.
- Liability limitations and exclusions agreed in the Agreement also apply to this DPA, except where prohibited by applicable law.
- Neither party excludes liability for: death or personal injury caused by negligence; fraud or fraudulent misrepresentation; or any other liability that cannot be excluded under applicable law.
17Term & Termination
- This DPA becomes effective on the date the Agreement takes effect and remains in force for as long as Makronexus processes personal data on behalf of the School.
- This DPA automatically terminates upon the expiry or termination of the Agreement, subject to the data return and deletion obligations in Section 14.
- Provisions of this DPA that by their nature should survive termination will continue to apply, including: confidentiality, data return and deletion obligations, liability, and audit rights (for a reasonable period post-termination).
18Contact
For questions about this DPA, to request the current sub-processor register, or to initiate the formal DPA signing process, contact us:
For procurement: request the “DPA pack” and include your school name, deployment model, and any specific compliance requirements.