Teachly

POPIA protection framework

Next Step Educational Services Pty Ltd · 2025/173080/07 · Version 31 October 2026

Prepared using South African statutory and regulator guidance. Company adoption and the operational items identified below remain to be confirmed; publication does not certify compliance.

Contact Information Officer

1. Accountability and officer responsibilities

Next Step Educational Services Pty Ltd Registration: 2025/173080/07 Information Officer: Rudi Jansen van Rensburg Business contact address: Sweetwater Road, Firlands, Gordons Bay, 7130 Telephone: 0655110483 Email: nxtservices_2020@outlook.com This framework sets out the controls the company must implement under POPIA; it is not an attestation that each control is operational. The Information Officer must encourage and ensure compliance, handle requests, cooperate with investigations and discharge section 55 and Regulation 4 duties. Maintain written appointment/delegation and registration evidence, a compliance framework, personal-information impact assessment, staff awareness and request-handling procedures. The company states that its officer is registered; verify the evidence in the company’s governance records.

2. Eight conditions for lawful processing

Accountability: assign ownership and retain compliance evidence. Processing limitation: identify a section 11 basis, minimise collection, collect directly where required and justify exceptions. Purpose specification: define specific lawful purposes and section 14 retention/disposal rules. Further-processing limitation: assess compatibility before secondary use; do not repurpose educator content for marketing or other purposes without a valid basis. Information quality: provide correction channels and take reasonably practicable steps to keep information complete, accurate and not misleading. Openness: maintain the section 51 manual and deliver section 18 notices before collection or as soon as reasonably practicable where permitted. Security safeguards: assess foreseeable risks, apply appropriate safeguards, bind operators and manage compromises. Data-subject participation: enable lawful confirmation, access, correction, deletion, objection and complaints.

3. Rights-request handling procedure

The officer’s operational procedure must log requests received at nxtservices_2020@outlook.com; acknowledge receipt; verify identity/authority proportionately; identify affected records/operators; distinguish PAIA access from POPIA correction, deletion or objection; preserve evidence; assess lawful fees, retention and third-party rights; and communicate the outcome and remedies. Restrict intake records to authorised staff. A suspended or expired service account must not lose statutory information rights. Do not demand passwords or excessive identity documents. Record reasons for refused actions and statutory retention. Where required, notify relevant recipients of corrected information. Keep a register of requests, actions, deadlines and outcomes. Email is the public intake channel; an automated deletion/export service is not being claimed. Official POPIA Forms 1, 2 and 5 support objections, corrections/deletions and complaints respectively.

4. Operator and transfer controls

Maintain an operator register covering each service, contracting entity, role, data categories, purpose, subprocessors, processing locations, retention and section 72 transfer basis. Execute written section 21 agreements requiring appropriate safeguards and confidentiality; operators must immediately notify the responsible party of reasonable grounds for unauthorised access/acquisition. Confirm instructions, access limitation, deletion/return, incident cooperation and audit evidence. Cloud services and AI generation are part of Teachly’s processing chain. Their contracts, countries and retention settings remain to be verified, not inferred from source code. Check section 57 prior-authorisation requirements where relevant, including certain processing of unique identifiers, criminal conduct or transfers of children’s/special personal information to inadequately protected foreign recipients. Do not introduce a covered activity before the required authorisation process is satisfied.

5. Security baseline and incident-response procedure

Verify least-privilege accounts, owner isolation, administrator controls, credential protection, private file access, safe exports, dependency updates, secure communications, backups/restores, log minimisation and review of access. Record risk assessments, remedies, staff training and operator assurance. Existing application access controls do not substitute for these operational checks. Incident steps: receive reports and escalate immediately to the Information Officer; contain access without destroying evidence; establish affected records and people; preserve an incident chronology; assess the section 22 trigger; notify the Regulator and affected people as soon as reasonably possible; communicate protective steps and updates; remediate and record lessons learned. A low-risk assessment is not a general exemption from reporting a qualifying compromise. Notifications to affected people should describe possible consequences, mitigation taken/intended, recommended protective action and the unauthorised person’s identity if known, subject to lawful exceptions. Lawful delay provisions must be assessed, not assumed. Operators notify the company immediately under section 21. The officer uses the Regulator’s security-compromise reporting service and current SCN1 procedure. Do not substitute a GDPR-style 72-hour deadline for POPIA’s requirement.

6. Learner data, sensitive information and impact assessment

Assess Teachly’s educator inputs, AI processing, resource exports, dossiers, proofs and access administration in a personal-information impact assessment. Identify foreseeable harms, minimisation controls, operator dependencies and residual risk. Prefer anonymised class examples; identifiable learner and special personal information must not be introduced without a lawful statutory basis and approved safeguards. Before any future learner-data feature, determine sections 26–35 conditions and any prior-authorisation requirement. Account-holder consent cannot simply replace competent-person authorisation or another necessary statutory basis. Assess section 71 before any solely automated decision with legal or substantial effects. AI assessment materials are educator aids; payment/access administration must not be described as an unreviewable automated legal decision.

7. Retention, marketing and tracking controls

Adopt a record-by-record retention schedule stating purpose, lawful basis, exact period/trigger, responsible person, legal holds, restricted access and disposal method. Include live data, proofs, moderation snapshots, logs, exports, backups and operator copies. Do not invent a universal retention period or claim automatic erasure is implemented. Keep marketing permissions separate from service terms, record the lawful section 69 basis, provide a free opt-out and honour objections. Complete a browser-storage, telemetry and tracking inventory and give appropriate choices before non-essential processing. Do not add a decorative consent banner and treat it as proof that all underlying tracking is controlled.

8. Company adoption checklist and evidence

Required company actions not completed by publishing these pages: □ Retain officer appointment and registration evidence; confirm deputy and postal/inspection arrangements. □ Approve the company-wide record inventory, processing purposes and lawful-basis assessments. □ Complete the operator/subprocessor/country register and signed agreements; verify section 72 safeguards and AI settings. □ Complete the impact assessment and security risk review, including incident-response and backup tests. □ Adopt exact retention/disposal schedules and implement the approved processes. □ Train staff, designate monitored request/incident channels and test the request procedure. □ Confirm marketing/tracking practice and consent/objection records if applicable. □ Complete PAIA record/legislation schedules and approve this manual and notice. These are unresolved governance requirements, not a declaration that the company is non-compliant in every respect or that a regulator has assessed it. Legal and operational review must establish the actual position. No DBE, SACE or Information Regulator certification is claimed.

9. Assistance and complaints

Information Regulator (South Africa) Woodmead North Office Park, 54 Maxwell Drive, Woodmead, Johannesburg, 2191 Telephone: 010 023 5200 / 0800 017 160 General enquiries: enquiries@inforegulator.org.za POPIA complaints: POPIAComplaints@inforegulator.org.za PAIA complaints: PAIAComplaints@inforegulator.org.za