{"id":3902,"date":"2026-05-18T11:36:28","date_gmt":"2026-05-18T09:36:28","guid":{"rendered":"http:\/\/tsholo"},"modified":"2026-05-18T11:36:28","modified_gmt":"2026-05-18T09:36:28","password":"","slug":"working-with-special-personal-information","status":"publish","type":"docs","link":"https:\/\/j-cred.co.za\/zh\/helpcenter\/working-with-special-personal-information\/","title":{"rendered":"Working with Special Personal Information"},"content":{"rendered":"<h2>Overview<\/h2>\n<p>Special personal information is information that requires heightened care. In verification contexts this may include criminal behaviour information, biometric information, health information, children&#8217;s information and other sensitive categories depending on the use case.<\/p>\n<h2>Why it matters<\/h2>\n<p>Special personal information can create significant harm if misused or leaked. It should be requested only when clearly necessary, legally permitted and protected by stronger controls.<\/p>\n<h2>How to think about it<\/h2>\n<ul>\n<li>Confirm that the check is necessary for the role, service, law or risk being managed.<\/li>\n<li>Use explicit workflows and stronger approvals for sensitive checks.<\/li>\n<li>Limit who can view the result and for how long.<\/li>\n<li>Use secure capture methods for biometrics or fingerprints where applicable.<\/li>\n<li>Provide dispute or escalation channels for affected people.<\/li>\n<\/ul>\n<h2>Common examples<\/h2>\n<ul>\n<li>Fingerprint-based police clearance processes.<\/li>\n<li>Biometric liveness checks during high-risk onboarding.<\/li>\n<li>Checks involving children or vulnerable beneficiaries.<\/li>\n<li>Health-related information used only where the programme or service lawfully requires it.<\/li>\n<\/ul>\n<h2>Responsible use reminders<\/h2>\n<ul>\n<li>Do not request sensitive checks simply to appear thorough.<\/li>\n<li>Do not send biometric, criminal or health information through informal channels.<\/li>\n<li>Train users before giving access to sensitive search types.<\/li>\n<\/ul>\n<hr \/>\n<p><strong>Public knowledge note:<\/strong> This article is intended as general education for verification, compliance, fraud prevention and responsible data-use discussions. It is not legal advice and should not replace your organisation&#8217;s own compliance review, regulator guidance, or contractual obligations.<\/p>","protected":false},"excerpt":{"rendered":"<p>Overview Special personal information is information that requires heightened care. In verification contexts this may include criminal behaviour information, biometric information, health information, children&#8217;s information and other sensitive categories depending on the use case. Why it matters Special personal information can create significant harm if misused or leaked. It should be requested only when clearly necessary, legally permitted and protected by stronger controls. How to think about it Confirm that the check is necessary for the role, service, law or risk being managed. Use explicit workflows and stronger approvals for sensitive checks. Limit who can view the result and for how long. Use secure capture methods for biometrics or fingerprints where applicable. Provide dispute or escalation channels for affected people. Common examples Fingerprint-based police clearance processes. Biometric liveness checks during high-risk onboarding. Checks involving children or vulnerable beneficiaries. Health-related information used only where the programme or service lawfully requires it. Responsible use reminders Do not request sensitive checks simply to appear thorough. Do not send biometric, criminal or health information through informal channels. Train users before giving access to sensitive search types. Public knowledge note: This article is intended as general education for verification, compliance, fraud prevention and responsible data-use discussions. It is not legal advice and should not replace your organisation&#8217;s own compliance review, regulator guidance, or contractual obligations.<\/p>","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","template":"","meta":{"_eb_attr":"","footnotes":""},"doc_category":[29],"doc_tag":[],"class_list":["post-3902","docs","type-docs","status-publish","hentry","doc_category-public-compliance-responsible-use"],"blocksy_meta":[],"year_month":"2026-06","word_count":220,"total_views":0,"reactions":{"happy":0,"normal":0,"sad":0},"author_info":{"name":"KTO Digital Admin","author_nicename":"tsholo","author_url":"https:\/\/j-cred.co.za\/zh\/author\/tsholo\/"},"doc_category_info":[{"term_name":"Compliance &amp; Responsible Use","term_url":"https:\/\/j-cred.co.za\/zh\/docs-category\/public-compliance-responsible-use\/"}],"doc_tag_info":[],"_links":{"self":[{"href":"https:\/\/j-cred.co.za\/zh\/wp-json\/wp\/v2\/docs\/3902","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/j-cred.co.za\/zh\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/j-cred.co.za\/zh\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/j-cred.co.za\/zh\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/j-cred.co.za\/zh\/wp-json\/wp\/v2\/comments?post=3902"}],"version-history":[{"count":0,"href":"https:\/\/j-cred.co.za\/zh\/wp-json\/wp\/v2\/docs\/3902\/revisions"}],"wp:attachment":[{"href":"https:\/\/j-cred.co.za\/zh\/wp-json\/wp\/v2\/media?parent=3902"}],"wp:term":[{"taxonomy":"doc_category","embeddable":true,"href":"https:\/\/j-cred.co.za\/zh\/wp-json\/wp\/v2\/doc_category?post=3902"},{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/j-cred.co.za\/zh\/wp-json\/wp\/v2\/doc_tag?post=3902"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}