{"clause": "POPIA children's information", "premise": "Our gaming-platform onboarding for the under-16 tier requires a parent or guardian to complete an OTP-verified mobile-number check and explicitly accept a child-data notice before the account is provisioned.", "hypothesis": "The responsible party has obtained consent from a competent person before processing the child's personal information.", "label": "entailment", "scenario": "gaming-platform-otp"}
{"clause": "POPIA children's information", "premise": "Our after-school robotics club records each minor's full name, school, contact details and medical conditions in a Google Sheet that we never share, with explicit signed authorisation from each parent at enrolment.", "hypothesis": "The responsible party has obtained consent from a competent person before processing the child's personal information.", "label": "entailment", "scenario": "robotics-club-enrolment"}
{"clause": "POPIA children's information", "premise": "We allow learners as young as 9 to register with their own email address for our music-practice tracking app, with no parental verification step at any point.", "hypothesis": "The responsible party has obtained consent from a competent person before processing the child's personal information.", "label": "contradiction", "scenario": "music-app-no-parent"}
{"clause": "POPIA children's information", "premise": "Our coding-bootcamp marketing team buys mobile-number lists of Grade 9 learners from a third-party data broker and sends them WhatsApp messages promoting our holiday camps.", "hypothesis": "The responsible party has a lawful basis to process the children's personal information for direct marketing.", "label": "contradiction", "scenario": "coding-bootcamp-marketing"}
{"clause": "POPIA children's information", "premise": "Our paediatric dental practice processes minors' clinical history only with the written consent of their parent or legal guardian.", "hypothesis": "The responsible party has obtained consent from a competent person before processing the child's personal information.", "label": "entailment", "scenario": "paediatric-dental"}
{"clause": "POPIA children's information", "premise": "Our church's youth-group register contains photos, contact numbers and dates of birth of every minor in the programme, all collected without any parental-consent process or notice.", "hypothesis": "The responsible party has obtained consent from a competent person before processing the child's personal information.", "label": "contradiction", "scenario": "church-youth-register"}
{"clause": "POPIA children's information", "premise": "Our public hospital sends every paediatric in-patient's parent a written summary explaining what clinical data is being captured before treatment begins.", "hypothesis": "The processing of children's personal information is justified by a lawful basis and parents are informed.", "label": "entailment", "scenario": "public-hospital-paediatric"}
{"clause": "POPIA children's information", "premise": "Standard Bank reviews a 35-year-old client's monthly statements to authorise a home-loan application.", "hypothesis": "The responsible party is processing children's personal information.", "label": "neutral", "scenario": "adult-home-loan"}
{"clause": "POPIA children's information", "premise": "Our online retailer's analytics dashboard receives only aggregated session counts with no per-user identifiers.", "hypothesis": "The responsible party is processing identifiable personal information of children.", "label": "neutral", "scenario": "retailer-anon-analytics"}
{"clause": "POPIA children's information", "premise": "A News24 reporter writes a feature on Matric exam pass rates using only aggregated district-level statistics.", "hypothesis": "The responsible party is engaged in systematic processing of identified minors' personal information for commercial purposes.", "label": "neutral", "scenario": "matric-aggregate-reporting"}
{"clause": "POPIA children's information", "premise": "A creche operator hands over each enrolled child's name, allergies and parent contact to its catering subcontractor without ever consulting the parents.", "hypothesis": "The responsible party has obtained consent from a competent person before sharing the child's personal information with the third party.", "label": "contradiction", "scenario": "creche-unauthorised-share"}
{"clause": "POPIA children's information", "premise": "Our prep school's IT helpdesk processes parent-reported password resets for learner accounts strictly on the basis of the signed parental authorisation captured at enrolment.", "hypothesis": "The responsible party has obtained consent from a competent person before processing the child's personal information.", "label": "entailment", "scenario": "prep-school-helpdesk"}
{"clause": "POPIA children's information", "premise": "A children's hospital ICU records minors' clinical data under its statutory obligation to deliver care, and notifies the legal guardian in writing on admission.", "hypothesis": "The processing of children's personal information is justified by a lawful basis and parents are informed.", "label": "entailment", "scenario": "icu-paediatric-statutory"}
{"clause": "POPIA children's information", "premise": "An adult opens a Capitec savings account; the bank processes their salary deposits and transaction history.", "hypothesis": "The responsible party is processing children's personal information.", "label": "neutral", "scenario": "adult-savings-account"}
{"clause": "POPIA children's information", "premise": "Cape Town traffic-camera data captures vehicle speeds at intersections, anonymised at source.", "hypothesis": "The responsible party is processing identifiable minors' personal information.", "label": "neutral", "scenario": "traffic-cam"}
{"clause": "POPIA children's information", "premise": "A wedding-photography studio shoots adult guests at a corporate event and the gallery contains no identifiable minors.", "hypothesis": "The responsible party is processing children's personal information.", "label": "neutral", "scenario": "corporate-event-photo"}
{"clause": "POPIA special personal information", "premise": "A health-tech startup ingests members' chronic-condition history from their medical-aid feed only after each member completes an in-app consent flow specific to that processing.", "hypothesis": "The responsible party has a lawful basis under §32 for processing health information.", "label": "entailment", "scenario": "healthtech-explicit-consent"}
{"clause": "POPIA special personal information", "premise": "A police-investigator queries a national database for an arrest record for purposes of an open criminal docket, under the §29 exception for processing criminal-behaviour data by competent authorities.", "hypothesis": "The responsible party has a lawful basis under POPIA to process criminal-behaviour information as special personal information.", "label": "entailment", "scenario": "police-investigation"}
{"clause": "POPIA special personal information", "premise": "A retail-staff scheduling tool quietly tags each employee's apparent religion based on names, then assigns shifts that avoid certain religious dates without any consent flow or legal-duty basis.", "hypothesis": "The responsible party is processing religious belief as special personal information on a lawful basis.", "label": "contradiction", "scenario": "scheduling-religion-inference"}
{"clause": "POPIA special personal information", "premise": "A mobile-network operator runs a biometric voiceprint-matching pipeline on every inbound call from its USSD line for anti-fraud, without disclosing biometric processing in its terms or seeking explicit consent.", "hypothesis": "The responsible party has a lawful basis under §27/§32 to process biometric special personal information.", "label": "contradiction", "scenario": "mno-voiceprint-no-consent"}
{"clause": "POPIA special personal information", "premise": "A hospital system uses minors' medical-record data for clinical-decision support solely with explicit parental consent and within the §32 medical-treatment exception.", "hypothesis": "The responsible party has a lawful basis to process special personal information.", "label": "entailment", "scenario": "hospital-cds-consent"}
{"clause": "POPIA special personal information", "premise": "A jewellery store sets up its CCTV system to identify the apparent race of every customer entering, then routes the feed to a regional 'risk' dashboard with no consent or legal basis.", "hypothesis": "The responsible party has a lawful basis to process race as special personal information.", "label": "contradiction", "scenario": "jewellery-cctv-race"}
{"clause": "POPIA special personal information", "premise": "Standard Bank checks a customer's payslip and statements for a personal-loan affordability assessment under the NCA.", "hypothesis": "The responsible party is processing special personal information under §26.", "label": "neutral", "scenario": "loan-affordability"}
{"clause": "POPIA special personal information", "premise": "An e-commerce site stores delivery addresses and order history for shipping fulfilment, with no special-category data involved.", "hypothesis": "The responsible party is processing special personal information under §26.", "label": "neutral", "scenario": "delivery-shipping"}
{"clause": "POPIA special personal information", "premise": "StatsSA publishes aggregated provincial unemployment data based on its labour-force survey.", "hypothesis": "The responsible party is processing identifiable special personal information of individual data subjects.", "label": "neutral", "scenario": "statssa-unemployment"}
{"clause": "POPIA special personal information", "premise": "A medical practice publishes only aggregated anonymised consultation-pattern statistics in its annual community-health report.", "hypothesis": "The responsible party is processing identifiable special personal information of individual data subjects.", "label": "neutral", "scenario": "practice-aggregate-stats"}
{"clause": "POPIA special personal information", "premise": "A pharma research project processes participant health data only after each participant has signed a §32(2) compliant informed-consent document approved by an ethics committee.", "hypothesis": "The responsible party has a lawful basis under §32 for processing health information.", "label": "entailment", "scenario": "pharma-research-consent"}
{"clause": "POPIA special personal information", "premise": "A national criminal-records check on a candidate for a security-cleared role is processed under §29 by an authorised body for the legally-required vetting.", "hypothesis": "The responsible party has a lawful basis under POPIA to process criminal-behaviour information as special personal information.", "label": "entailment", "scenario": "security-vetting"}
{"clause": "POPIA special personal information", "premise": "A fitness app silently uploads heart-rate and ECG samples to a third-party analytics vendor for population studies, without informing or obtaining consent from users.", "hypothesis": "The responsible party has a lawful basis under §32 for processing health information.", "label": "contradiction", "scenario": "fitness-app-shadow-health"}
{"clause": "POPIA special personal information", "premise": "A school photo gallery captures wide-angle images of sports day without identifying or focusing on any individual learner.", "hypothesis": "The responsible party is processing identifiable special personal information of individual data subjects.", "label": "neutral", "scenario": "school-sports-photo"}
{"clause": "POPIA special personal information", "premise": "An MNO processes monthly call-detail records for routine network capacity planning with no special-category data involved.", "hypothesis": "The responsible party is processing special personal information under §26.", "label": "neutral", "scenario": "mno-cdr-capacity"}
{"clause": "POPIA special personal information", "premise": "An insurance underwriter prices a life-cover policy based on the applicant's voluntarily disclosed health questionnaire and the applicant's signed consent for the insurer to access medical records.", "hypothesis": "The responsible party has a lawful basis under §32 for processing health information.", "label": "entailment", "scenario": "life-cover-underwriting"}
{"clause": "POPIA automated decision-making", "premise": "Our travel-insurance platform's pricing model is registered as part of a Regulator-approved §60 code of conduct, and each applicant can submit additional context before the final premium is fixed.", "hypothesis": "The responsible party is processing automated decisions in compliance with §71.", "label": "entailment", "scenario": "travel-insurance-code"}
{"clause": "POPIA automated decision-making", "premise": "A municipal-services tariff platform auto-classifies indigent applicants under predefined rules, but every applicant flagged 'borderline' is reviewed and finalised by a human officer who can override the system.", "hypothesis": "The responsible party is using automated processing as decision support, not as a solely automated decision with legal effect within §71.", "label": "entailment", "scenario": "municipal-indigent"}
{"clause": "POPIA automated decision-making", "premise": "Our buy-now-pay-later platform rejects applicants based on a black-box vendor score; rejected users get a single sentence and there is no human-review path.", "hypothesis": "The responsible party is complying with §71 by offering data subjects the opportunity to make representations or by providing the underlying logic of the automated decision.", "label": "contradiction", "scenario": "bnpl-blackbox"}
{"clause": "POPIA automated decision-making", "premise": "Our gig-platform deactivates drivers whose acceptance rate falls below 80% via a fully automated rule, with no notice, no logic disclosed, and no avenue for the driver to challenge the deactivation.", "hypothesis": "The responsible party complies with §71's requirement to inform the data subject of the underlying logic of an automated decision.", "label": "contradiction", "scenario": "gig-platform-deactivation"}
{"clause": "POPIA automated decision-making", "premise": "Our funeral-cover application form is processed by a rule-based engine that confirms eligibility within minutes; declined applicants receive a structured letter explaining the precise rule that failed and a clearly-marked human-review address.", "hypothesis": "The responsible party is meeting §71's requirements on automated decision-making with legal or substantial effect.", "label": "entailment", "scenario": "funeral-cover-rules"}
{"clause": "POPIA automated decision-making", "premise": "Our home-loan affordability decisioning is automated up to a documented threshold, beyond which a human credit officer makes the final call; applicants are told this in writing.", "hypothesis": "The responsible party is using automated processing as decision support, not as a solely automated decision with legal effect within §71.", "label": "entailment", "scenario": "home-loan-human-override"}
{"clause": "POPIA automated decision-making", "premise": "A factory's barcode scanner-to-product-ID lookup runs as an automated pipeline.", "hypothesis": "The responsible party is making an automated decision with legal or substantial effect on a data subject within the scope of §71.", "label": "neutral", "scenario": "factory-barcode"}
{"clause": "POPIA automated decision-making", "premise": "A company's email server runs an automated phishing detector that quarantines suspect messages with a one-click release option.", "hypothesis": "The phishing filter is the kind of automated decision §71 was designed to regulate.", "label": "neutral", "scenario": "phishing-filter"}
{"clause": "POPIA automated decision-making", "premise": "An open-data portal runs an anonymous national budget survey, aggregating respondent opinions without making any decision about any individual.", "hypothesis": "The site is engaged in §71 automated decision-making about individual data subjects.", "label": "neutral", "scenario": "open-data-survey"}
{"clause": "POPIA automated decision-making", "premise": "A bursary-screening platform uses fully automated ranking to drop candidates below a cutoff, with no human review and no notice to rejected applicants about what data was used.", "hypothesis": "The responsible party is complying with §71 by offering data subjects the opportunity to make representations or by providing the underlying logic of the automated decision.", "label": "contradiction", "scenario": "bursary-blackbox"}
{"clause": "POPIA automated decision-making", "premise": "A car-rental fraud-detection model auto-blocks bookings based on an opaque risk score without notice or appeal channel for the blocked customer.", "hypothesis": "The responsible party complies with §71's requirement to inform the data subject of the underlying logic of an automated decision.", "label": "contradiction", "scenario": "car-rental-fraud"}
{"clause": "POPIA automated decision-making", "premise": "A health-insurance platform offers a transparent claim-decision flow: claims are scored automatically against published rules, claimants receive a structured explanation, and disputed claims route to a human assessor within five business days.", "hypothesis": "The responsible party is meeting §71's requirements on automated decision-making with legal or substantial effect.", "label": "entailment", "scenario": "health-claim-transparent"}
{"clause": "POPIA automated decision-making", "premise": "A university applications portal auto-shortlists candidates against admission criteria, but every shortlisted candidate is finally interviewed by a human admissions panel.", "hypothesis": "The responsible party is using automated processing as decision support, not as a solely automated decision with legal effect within §71.", "label": "entailment", "scenario": "university-shortlist"}
{"clause": "POPIA automated decision-making", "premise": "A logistics company's route-optimisation engine assigns delivery sequences to drivers based on geofencing rules, with no individual customer decision being made.", "hypothesis": "The responsible party is making an automated decision with legal or substantial effect on a data subject within the scope of §71.", "label": "neutral", "scenario": "logistics-route"}
{"clause": "POPIA automated decision-making", "premise": "A national lottery's automated draw selects winning numbers each Wednesday and Saturday with no decision being made about any individual applicant.", "hypothesis": "The lottery draw is the kind of automated decision §71 was designed to regulate.", "label": "neutral", "scenario": "lottery-draw"}