POPIA Compliance for Schools: What Every Principal Must Know

South African schools hold large amounts of learner and parent data—ID numbers, medical details, academic records, fee information—yet many principals and SGBs are unsure what POPIA requires or how to avoid fines of up to R10 million. The Protection of Personal Information Act (POPIA) has been in full effect since 1 July 2021, and the Information Regulator can enforce strict penalties for non-compliance. Getting POPIA compliance for schools right protects your community and your school.

This guide explains what constitutes personal information in a school context, the eight conditions for lawful processing, consent requirements, data storage and retention rules, access requests and breach notification, and how to choose POPIA-compliant school management software. Whether you are building your school’s POPIA framework or reviewing existing policies, the following sections give practical steps aligned with the Information Regulator’s guidance.

What Is POPIA and Why It Matters for Schools

The Protection of Personal Information Act (Act 4 of 2013) is South Africa’s primary data protection legislation, designed to protect individuals’ personal information while enabling responsible data processing. POPIA applies to all organisations—including schools—that process personal information, establishing eight conditions for lawful processing and granting individuals rights over their personal data.

Why POPIA matters for schools:

Schools process vast amounts of personal information daily: learner names, addresses, ID numbers, medical information, academic records, parent contact details, financial information, and more. Under POPIA, schools are “responsible parties” with legal obligations to protect this information. Non-compliance can result in:

• Administrative fines: Up to R10 million or imprisonment for up to 10 years
• Reputational damage: Loss of parent and community trust
• Legal liability: Civil claims for damages from data subjects
• Regulatory action: Enforcement by the Information Regulator
• Operational disruption: Mandatory remediation and compliance measures

POPIA’s eight conditions for lawful processing:

Condition	What it means for schools
Accountability	Ensure compliance with POPIA; appoint an Information Officer and register with the Information Regulator.
Processing limitation	Only collect and process personal information that is necessary for a specific purpose.
Purpose specification	Collect for specific, lawful purposes and inform data subjects what you collect and why.
Further processing limitation	Use information only for the original purpose or compatible purposes; otherwise obtain consent or rely on law.
Information quality	Keep information accurate, complete and up to date; allow correction.
Openness	Be transparent about how you process data; provide notices and respond to access requests.
Security safeguards	Implement technical and organisational measures to protect data from loss, unauthorised access or alteration.
Data subject participation	Allow individuals to access, correct and, where lawful, delete their personal information.

Understanding these conditions is the foundation of POPIA compliance for schools.

What Constitutes Personal Information in Schools?

POPIA defines “personal information” broadly as any information relating to an identifiable, living, natural person or juristic person. In a school context, this includes a wide range of data about learners, parents, guardians, staff, and other individuals.

Learner Personal Information

Schools collect extensive personal information about learners:

Identity information:

• Full names and surnames
• Identity numbers (ID numbers or passport numbers)
• Date of birth
• Gender
• Race (if collected for reporting purposes)
• Nationality
• Home language

Contact information:

• Residential address
• Postal address
• Email addresses
• Telephone numbers (home, mobile, emergency contacts)
• Parent/guardian contact details

Academic information:

• Learner numbers (LURITS numbers)
• Admission dates
• Grade and class assignments
• Academic records (marks, assessments, report cards)
• Attendance records
• Disciplinary records
• Extramural activity participation

Medical and health information:

• Medical conditions
• Allergies
• Medication requirements
• Medical aid details
• Doctor contact information
• Immunisation records
• Disability information

Financial information:

• School fee payment records
• Fee exemption status
• Payment methods and banking details
• Financial aid or bursary information

Biometric information:

• Fingerprints (if used for access control or attendance)
• Photographs (for ID cards, yearbooks, school records)

Special personal information: POPIA provides additional protection for “special personal information,” including:

• Information about children (learners under 18)
• Health information (medical conditions, disabilities)
• Biometric information (fingerprints, photographs used for identification)

Processing special personal information requires stricter compliance measures and, in some cases, explicit consent.

Parent and Guardian Personal Information

Schools also process personal information about parents and guardians:

• Full names and ID numbers
• Contact details (addresses, phone numbers, email addresses)
• Employment information (if relevant for fee exemption applications)
• Financial information (income, payment records)
• Relationship to learner (parent, guardian, legal custodian)

Staff Personal Information

While this guide focuses on learner and parent data, schools also process staff personal information (subject to POPIA and employment legislation).

Key principle: If information can identify a specific person, it’s personal information under POPIA and must be protected accordingly.

Lawful Processing and Consent for Schools

POPIA establishes eight conditions that schools must meet to process personal information lawfully (summarised in the table above). The following outlines practical steps for the main conditions, plus when and how to obtain consent.

Accountability and processing limitation

Schools must take responsibility for POPIA compliance, ensuring that all personal information processing complies with POPIA conditions. This requires:

• Appointing an Information Officer: Designate a staff member (typically the principal or deputy principal) responsible for POPIA compliance
• Developing policies: Create comprehensive POPIA policies and procedures
• Training staff: Ensure all staff understand POPIA requirements
• Regular audits: Conduct periodic compliance reviews
• Documentation: Maintain records of data processing activities

Practical steps:

• Appoint an Information Officer and register with the Information Regulator
• Develop a POPIA compliance policy document
• Train all staff on POPIA requirements annually
• Conduct annual compliance audits
• Maintain a register of data processing activities

Condition 2: Processing Limitation

Schools may only process personal information that is necessary for a specific purpose. This means:

• Minimal collection: Only collect information that is necessary
• No excessive data: Don’t collect more information than needed
• Purpose-driven: Each piece of information must serve a clear purpose

Examples:

• Correct: Collecting learner ID numbers for LURITS registration (required by law); collecting medical information for emergency care (necessary for learner safety).
• Incorrect: Collecting parent employment details unless needed for fee exemption applications; collecting learner photographs for non-essential purposes without consent.

Practical steps:

• Review all forms and data collection points
• Remove unnecessary fields from forms
• Document the purpose for each piece of information collected
• Regularly audit data collection practices

Condition 3: Purpose Specification

Schools must inform data subjects (learners and parents) about:

• What information is being collected
• Why it’s being collected (the purpose)
• Who will have access to it
• How it will be used

Information notices: Schools should provide clear information notices when collecting personal information, explaining:

• The purpose of collection
• Whether collection is mandatory or voluntary
• Consequences of not providing information
• Who will have access to the information
• How long information will be retained
• Data subject rights (access, correction, deletion)

Practical steps:

• Include POPIA notices on all forms (admission forms, consent forms, etc.)
• Display privacy notices on school websites
• Provide information notices during parent meetings
• Ensure notices are in languages parents understand

Condition 4: Further Processing Limitation

Schools may only use personal information for the purpose it was collected, unless:

• The further processing is compatible with the original purpose
• The data subject consents to further processing
• Further processing is required by law

Examples:

• Correct: Using learner contact details to send report cards (compatible with original purpose); sharing learner information with provincial education department (required by law).
• Incorrect: Using parent email addresses for marketing without consent; sharing learner information with third parties for commercial purposes without consent.

Practical steps:

• Document all uses of personal information
• Obtain consent for any uses beyond the original purpose
• Review data sharing agreements with third parties
• Ensure all processing is compatible with original purposes

Condition 5: Information Quality

Schools must ensure personal information is:

• Accurate: Correct and up-to-date
• Complete: Contains all necessary information
• Not misleading: Reflects the true situation

Practical steps:

• Regularly update learner and parent contact details
• Verify information accuracy during annual registration
• Allow data subjects to correct their information
• Remove or correct outdated information promptly
• Implement data validation in school management systems

Condition 6: Openness

Schools must be transparent about how personal information is processed, providing data subjects with access to:

• What information is held about them
• How it’s being used
• Who has access to it
• How to exercise their rights

Practical steps:

• Publish a privacy policy on the school website
• Provide information notices when collecting data
• Respond promptly to access requests
• Maintain transparency in all data processing activities

Condition 7: Security Safeguards

Schools must implement appropriate technical and organisational measures to protect personal information from:

• Loss
• Damage
• Unauthorised access
• Unauthorised destruction
• Unauthorised alteration

Technical safeguards:

• Access controls: Limit access to authorised staff only
• Encryption: Encrypt sensitive data (especially when stored or transmitted)
• Password protection: Require strong passwords and regular changes
• Firewalls and antivirus: Protect systems from cyber threats
• Secure backups: Regularly back up data securely
• System updates: Keep software and systems updated

Organisational safeguards:

• Staff training: Train staff on data protection and security
• Access policies: Define who can access what information
• Incident response: Develop procedures for security breaches
• Physical security: Secure physical records (locked filing cabinets, restricted access)
• Visitor management: Control access to school premises and systems

Practical steps:

• Conduct a security risk assessment
• Implement access controls (role-based access in school management systems)
• Encrypt sensitive data (especially learner ID numbers, medical information)
• Train staff on password security and phishing awareness
• Develop a data breach response plan
• Regularly review and update security measures

Condition 8: Data Subject Participation

Data subjects (learners and parents) have rights under POPIA:

Right of access:

• Request access to personal information held by the school
• Schools must provide access within reasonable timeframes

Right to correction:

• Request correction of inaccurate or incomplete information
• Schools must correct information promptly

Right to deletion:

• Request deletion of personal information (subject to legal retention requirements)
• Schools must delete information when no longer needed (unless retention is required by law)

Right to object:

• Object to processing of personal information
• Schools must consider objections and respond appropriately

Practical steps:

• Develop procedures for handling access requests
• Respond to requests within POPIA timeframes (typically 30 days)
• Maintain records of all access requests
• Allow data subjects to correct their information easily
• Document decisions regarding deletion requests

Consent Requirements for Schools

Consent is one way schools can lawfully process personal information, but it is not always required. Understanding when consent is needed and how to obtain it properly is essential for POPIA compliance.

When Is Consent Required?

Consent is required when:

• Processing special personal information (children’s information, health information, biometric information) for purposes beyond what’s necessary for education
• Using personal information for marketing or commercial purposes
• Sharing information with third parties for non-essential purposes
• Processing information for purposes beyond the original collection purpose

Consent is NOT required when:

• Processing is necessary for performing a contract (e.g., school admission contract)
• Processing is required by law (e.g., reporting to provincial education department)
• Processing is necessary to protect a legitimate interest (e.g., learner safety)
• Processing is in the public interest (e.g., public health requirements)

Important: For learners under 18, consent must be obtained from parents or guardians, not from the learners themselves.

How to Obtain Valid Consent

Valid consent under POPIA must be:

• Voluntary: Given freely without coercion
• Specific: Relates to a specific purpose
• Informed: Data subject understands what they’re consenting to
• Unambiguous: Clear and explicit (not implied)
• Revocable: Can be withdrawn at any time

Consent forms should include:

• Clear explanation of what information is being collected
• Specific purpose for which consent is given
• Who will have access to the information
• How long the information will be retained
• Right to withdraw consent
• Consequences of not providing consent (if applicable)

Practical steps:

• Use clear, simple language in consent forms
• Provide consent forms in languages parents understand
• Explain consent requirements during parent meetings
• Allow parents to withdraw consent easily
• Keep records of all consent given and withdrawn
• Regularly review consent to ensure it’s still valid

Common Consent Scenarios in Schools

Photographs and media:

• Consent required for using learner photographs in marketing materials, social media, or public displays
• Consent NOT required for official school records or ID cards
• Best practice: Obtain annual consent for media use, allowing parents to specify restrictions

Medical information:

• Consent required for sharing medical information beyond what’s necessary for emergency care
• Consent NOT required for collecting medical information necessary for learner safety
• Best practice: Obtain consent for sharing medical information with external parties (e.g., sports coaches, excursion organisers)

Third-party sharing:

• Consent required for sharing information with commercial third parties
• Consent NOT required for sharing with provincial education department (required by law)
• Best practice: Obtain specific consent for each third-party sharing arrangement

Marketing communications:

• Consent required for sending marketing emails or SMS messages
• Consent NOT required for essential school communications (report cards, fee statements, emergency notifications)
• Best practice: Provide opt-in for marketing communications separately from essential communications

Data Storage, Retention and Breach Notification

Schools must store personal information securely and retain it only for as long as necessary. Understanding retention requirements helps schools comply with POPIA while meeting legal obligations.

Secure Storage Requirements

Digital storage:

• Store data on secure servers with access controls
• Encrypt sensitive data (especially ID numbers, medical information, financial information)
• Implement regular backups with encryption
• Use secure cloud services with POPIA-compliant providers
• Restrict access to authorised staff only
• Monitor access logs regularly

Physical storage:

• Store physical records in locked filing cabinets
• Restrict access to storage areas
• Implement document destruction procedures for expired records
• Secure areas where records are stored
• Control visitor access to record storage areas

School management systems:

• Choose POPIA-compliant software providers
• Ensure data is stored in South Africa (or with adequate safeguards for cross-border transfers)
• Verify that providers have appropriate security measures
• Review data processing agreements with software providers

Retention Periods

Schools must retain personal information only for as long as necessary, but various laws require minimum retention periods:

Record type	Retention period
Academic records	Permanently (required by provincial education departments)
Admission forms	Duration of enrolment plus 5 years
Attendance records	5 years after learner leaves
Disciplinary records	5 years after learner leaves (or as per provincial policy)
Medical records	Duration of enrolment plus 7 years
Fee payment records	5 years (tax and audit requirements)
Fee exemption applications	5 years after exemption period ends
Financial statements	Permanently (SASA requirement)
Parent contact details	While learner is enrolled, plus 2 years
Parent employment information	Only while needed for fee exemption purposes
Staff employment records	3 years after employment ends (Basic Conditions of Employment Act)
Payroll records	5 years (tax requirements)

Retention requirements may vary by province. Check your provincial education department’s policies for specific requirements.

Data Destruction Procedures

When retention periods expire, schools must securely destroy personal information:

Digital data:

• Permanently delete from systems (not just mark as deleted)
• Ensure backups are also deleted
• Verify deletion is complete
• Document destruction activities

Physical records:

• Shred or incinerate paper records
• Ensure destruction is complete and irreversible
• Document destruction activities
• Maintain records of what was destroyed and when

Practical steps:

• Develop a data retention and destruction policy
• Schedule regular reviews of stored data
• Securely destroy expired records
• Document all destruction activities
• Ensure software providers can delete data when requested

Access Requests and Data Subject Rights

Under POPIA, data subjects (learners and parents) have rights to access, correct, and delete their personal information. Schools must have procedures to handle these requests promptly and compliantly.

Right of Access

Data subjects can request:

• Confirmation that the school holds their personal information
• Access to their personal information
• Information about how their data is being used
• Details of third parties who have access to their information

How to handle access requests:

1. Acknowledge receipt: Confirm receipt of the request within 5 days
2. Verify identity: Ensure the requester is authorised to access the information
3. Gather information: Collect all relevant personal information
4. Review for exemptions: Check if any information is exempt from disclosure (e.g., third-party information)
5. Provide access: Supply the information within 30 days (can be extended to 60 days with justification)
6. Document: Keep records of all access requests

Format for providing access:

• Provide information in a clear, understandable format
• Explain any technical terms
• Provide copies of documents if requested
• Allow inspection of original records if preferred

Fees:

• Schools may charge a reasonable fee for providing access (e.g., photocopying costs)
• Fee must not be excessive
• Provide a fee estimate before processing the request

Right to Correction

Data subjects can request correction of inaccurate, incomplete, or outdated information.

How to handle correction requests:

1. Verify the correction: Check if the correction is accurate
2. Update records: Correct information in all systems and records
3. Notify third parties: If information was shared, notify third parties of corrections
4. Confirm completion: Inform the data subject that correction is complete
5. Document: Keep records of correction requests

Practical steps:

• Allow easy correction of contact details (online portals, forms)
• Verify corrections for critical information (ID numbers, medical information)
• Update all systems simultaneously
• Notify relevant staff of corrections
• Maintain audit trail of corrections

Right to Deletion

Data subjects can request deletion of their personal information, but schools may refuse if:

• Retention is required by law (e.g., academic records)
• Retention is necessary for legitimate purposes (e.g., ongoing legal proceedings)
• Deletion would harm the data subject or others

How to handle deletion requests:

1. Review retention requirements: Check if information must be retained by law
2. Assess impact: Consider impact of deletion on school operations and data subject
3. Make decision: Approve or refuse deletion with clear reasons
4. Execute deletion: If approved, securely delete information
5. Notify third parties: If information was shared, request deletion from third parties
6. Confirm completion: Inform the data subject of the outcome
7. Document: Keep records of deletion requests and decisions

Practical steps:

• Develop clear procedures for handling deletion requests
• Document reasons for refusing deletion requests
• Securely delete information when deletion is approved
• Maintain records of deletion activities
• Ensure software providers can delete data when requested

Data Breach Notification Requirements

POPIA requires schools to notify the Information Regulator and affected data subjects when personal information is compromised. Understanding breach notification requirements helps schools respond quickly and compliantly.

What Constitutes a Data Breach?

A data breach occurs when personal information is:

• Lost or destroyed
• Altered without authorisation
• Accessed or disclosed without authorisation
• Processed without authorisation

Examples of data breaches:

• Unauthorised access to school management system
• Loss or theft of devices containing personal information
• Accidental email sent to wrong recipient containing personal information
• Ransomware attack encrypting school systems
• Physical theft of files or records
• Accidental disclosure during presentations or meetings

Breach Notification Requirements

Notify the Information Regulator:

• When: As soon as reasonably possible after becoming aware of the breach
• Timeline: Within 72 hours if feasible, or as soon as possible thereafter
• Method: Submit breach notification form to the Information Regulator
• Information required: Description of breach, categories of data affected, number of data subjects affected, likely consequences, measures taken to address breach

Notify affected data subjects:

• When: As soon as reasonably possible after becoming aware of the breach
• Timeline: Without undue delay
• Method: Direct communication (email, letter, SMS) or public notice if direct communication not feasible
• Information required: Description of breach, likely consequences, measures taken to address breach, recommendations for data subjects

Exceptions: Schools don’t need to notify data subjects if:

• The Information Regulator determines notification is unnecessary
• Appropriate security measures were in place (e.g., encryption) and breach is unlikely to result in harm
• Notification would involve disproportionate effort (in which case public notice may be used)

Breach Response Plan

Schools should develop a data breach response plan:

Step 1: Contain the breach

• Immediately stop the breach if possible
• Isolate affected systems
• Prevent further unauthorised access
• Secure physical areas if applicable

Step 2: Assess the breach

• Determine what information was compromised
• Identify how many data subjects are affected
• Assess the severity and likely consequences
• Determine if breach is notifiable

Step 3: Notify

• Notify the Information Regulator within 72 hours
• Notify affected data subjects without undue delay
• Notify relevant authorities if required (e.g., SAPS for theft)

Step 4: Investigate

• Conduct thorough investigation of the breach
• Identify root causes
• Document findings
• Implement measures to prevent recurrence

Step 5: Remediate

• Address security vulnerabilities
• Implement additional safeguards
• Provide support to affected data subjects
• Monitor for further incidents

Step 6: Review and improve

• Review breach response effectiveness
• Update security measures
• Revise policies and procedures
• Provide additional staff training

Practical steps:

• Develop a data breach response plan
• Designate a breach response team
• Train staff on breach identification and reporting
• Maintain contact details for the Information Regulator
• Prepare breach notification templates
• Conduct regular breach response drills
• Review and update the plan annually

Choosing POPIA-Compliant School Management Software

School management software processes vast amounts of personal information, making POPIA compliance a critical consideration when selecting software. Choosing POPIA-compliant software helps schools meet their obligations while protecting learner and parent data.

Key POPIA Compliance Features

Data security:

• Encryption of data in transit and at rest
• Access controls and role-based permissions
• Regular security updates and patches
• Secure authentication (multi-factor authentication preferred)
• Audit logs of all data access and modifications

Data storage:

• Data stored in South Africa (or adequate safeguards for cross-border transfers)
• Regular secure backups
• Data recovery capabilities
• Secure data deletion when requested

Access controls:

• Role-based access (principals, educators, admin staff have different access levels)
• User authentication and authorisation
• Session management and timeout
• Activity logging and monitoring

Data subject rights:

• Ability to export personal information (for access requests)
• Ability to correct information easily
• Ability to delete information (subject to retention requirements)
• Audit trail of all changes

Privacy by design:

• Minimal data collection (only necessary fields)
• Purpose limitation built into system design
• Data minimisation features
• Privacy settings and controls

Questions to Ask Software Providers

Security:

• What security measures are in place to protect data?
• Is data encrypted? (in transit and at rest)
• Where is data stored? (South Africa or elsewhere?)
• What access controls are available?
• Are there audit logs of data access?

Compliance:

• Is the software POPIA compliant?
• Do you have a POPIA compliance certificate or assessment?
• What data processing agreements do you have in place?
• How do you handle data subject access requests?
• Can you delete data when requested (subject to retention requirements)?

Data management:

• Can we export our data?
• Can we correct information easily?
• How long do you retain our data?
• What happens to data if we cancel the service?
• Do you share our data with third parties?

Support:

• What training do you provide on POPIA compliance?
• Do you have documentation on POPIA compliance features?
• What support is available if we have POPIA-related questions?
• Do you provide breach notification assistance?

Data Processing Agreements

When using school management software, schools should have data processing agreements (DPAs) with software providers. DPAs should specify:

• Purpose of processing: What data will be processed and why
• Security measures: What security measures the provider will implement
• Data location: Where data will be stored
• Third-party sharing: Whether data will be shared with third parties
• Data subject rights: How the provider will assist with access requests
• Breach notification: How the provider will notify schools of breaches
• Data deletion: How data will be deleted when no longer needed
• Compliance: Provider’s commitment to POPIA compliance

Practical steps:

• Review software providers’ privacy policies and terms of service
• Request data processing agreements from providers
• Ensure agreements comply with POPIA requirements
• Keep copies of all agreements on file
• Review agreements annually

For more on school governance and compliance, see our SGB financial management guide and LURITS number guide.

POPIA Compliance Checklist for Schools

Use this checklist to assess your school’s POPIA compliance:

Governance and Accountability

• Information Officer appointed and registered with Information Regulator
• POPIA compliance policy developed and approved by SGB
• Staff trained on POPIA requirements (annual training)
• POPIA compliance responsibilities assigned to specific staff members
• Regular compliance audits conducted (annually)
• Register of data processing activities maintained

Data Collection and Processing

• All data collection forms include POPIA information notices
• Only necessary personal information is collected
• Purpose for each piece of information is documented
• Consent obtained where required (photographs, marketing, third-party sharing)
• Consent forms are clear, specific, and revocable
• Records of consent are maintained

Data Storage and Security

• Personal information stored securely (encrypted where appropriate)
• Access controls implemented (role-based access in systems)
• Physical records stored in locked, secure areas
• Regular backups conducted with encryption
• Security measures reviewed and updated regularly
• Staff trained on password security and phishing awareness
• Incident response plan developed for data breaches

Data Retention and Destruction

• Data retention policy developed (aligned with legal requirements)
• Retention periods documented for each type of information
• Regular reviews conducted to identify expired records
• Secure destruction procedures implemented for expired records
• Destruction activities documented

Data Subject Rights

• Procedures developed for handling access requests
• Procedures developed for handling correction requests
• Procedures developed for handling deletion requests
• Requests responded to within POPIA timeframes
• Records maintained of all requests and responses
• Easy methods provided for data subjects to correct their information

Third-Party Sharing

• All third-party sharing arrangements documented
• Data processing agreements in place with software providers
• Third parties assessed for POPIA compliance
• Consent obtained for non-essential third-party sharing
• Regular reviews of third-party arrangements conducted

Breach Notification

• Data breach response plan developed
• Breach response team designated
• Staff trained on breach identification and reporting
• Contact details for Information Regulator maintained
• Breach notification templates prepared
• Procedures tested through drills

Documentation and Transparency

• Privacy policy published on school website
• Information notices provided when collecting data
• POPIA information included in admission packs
• Parents informed about data processing during meetings
• All policies and procedures documented
• Compliance activities documented and filed

Software and Technology

• School management software assessed for POPIA compliance
• Data processing agreements in place with software providers
• Software security features reviewed and enabled
• Access controls configured appropriately
• Audit logs enabled and monitored
• Data export capabilities tested

Scoring:

• 0–10 items checked: Critical compliance gaps—immediate action required
• 11–20 items checked: Significant compliance gaps—priority action needed
• 21–30 items checked: Good compliance—continue improvement
• 31+ items checked: Strong compliance—maintain and review regularly

Best Practices

Treat POPIA compliance as a core responsibility and allocate time and staff to it. Provide annual POPIA training for all staff and include it in induction. Maintain records of data processing activities, consent, and access requests. Conduct annual compliance audits and review policies and procedures each year. Choose POPIA-compliant software, implement encryption and access controls, and respond promptly to data subject requests. Consult legal advisors or POPIA consultants for complex questions.

POPIA compliance for schools is a legal requirement with significant consequences for non-compliance. Principals, school administrators, and SGB members must ensure their school processes personal information lawfully and securely. Compliance demands ongoing effort—policies, staff training, security measures, and handling access requests—but it protects learner and parent data, builds trust, and avoids penalties.

For a single platform that helps South African schools stay DBE compliant, manage learner data securely, and handle report cards and fee collection in one place, see Fundisa.

---

Frequently Asked Questions

Do schools need to register with the Information Regulator?

Yes. Schools must appoint an Information Officer (typically the principal) and register the Information Officer with the Information Regulator. Registration is free and can be done online through the Information Regulator’s website. The Information Officer is responsible for ensuring POPIA compliance and serves as the point of contact for POPIA-related matters.

Can schools share learner information with other schools or organisations?

Schools can share learner information in specific circumstances:

• Required by law: Sharing with provincial education departments, SAPS (for safety concerns), or other authorities when required by law
• With consent: Sharing with third parties when parents have given explicit consent
• For legitimate purposes: Sharing information necessary for learner safety, educational purposes, or other legitimate interests

Schools should always verify the legal basis for sharing and obtain consent when required. Any sharing should be documented, and data processing agreements should be in place with third parties.

What happens if a school experiences a data breach?

If a school experiences a data breach:

1. Contain the breach immediately to prevent further unauthorised access
2. Assess the breach to determine what information was compromised and how many data subjects are affected
3. Notify the Information Regulator within 72 hours (or as soon as possible)
4. Notify affected data subjects without undue delay, explaining what happened and what they should do
5. Investigate the breach to identify root causes
6. Remediate by addressing security vulnerabilities and implementing additional safeguards
7. Review and improve security measures to prevent future breaches

Schools should have a data breach response plan in place to ensure they can respond quickly and compliantly.

How long must schools retain learner records?

Retention requirements vary by type of record:

• Academic records: Retain permanently (required by provincial education departments)
• Admission forms: Retain for duration of enrolment plus 5 years
• Attendance records: Retain for 5 years after learner leaves
• Disciplinary records: Retain for 5 years after learner leaves (or as per provincial policy)
• Medical records: Retain for duration of enrolment plus 7 years

Specific retention requirements may vary by province—check your provincial education department’s policies for exact requirements. Schools must securely destroy records when retention periods expire.

Can parents request deletion of their child’s academic records?

Generally, no. Academic records must be retained permanently as required by provincial education departments and SASA. However, parents can request deletion of other types of information (e.g., photographs used for marketing, contact details after the learner leaves) subject to retention requirements. Schools should explain retention requirements to parents and work with them to address concerns while maintaining compliance with legal obligations.