What FounderZA verifies and what remains self-declared. Effective date: 18 November 2026.
FounderZA requires account verification before a user can use protected marketplace functions. We collect the user's full legal name, email address, mobile number, South African identity number or passport details, and the identity-document information needed for the check. The verification process may collect a live facial image or short capture, liveness result, face-match result, verification reference, date and outcome. We do not ask users to place identity documents in a public profile or ordinary marketplace message.
Where a user acts for a company or organisation, we collect its legal name, registration number, registration status and available office-bearer or director information. We may also collect a mandate, board authority, professional registration or other evidence needed for the particular role or action. Professional qualifications, languages, experience and services remain self-reported unless FounderZA expressly states that a specific item was checked.
The information comes from the user, the user's device during the verification process, the appointed verification provider, CIPC or another lawful authoritative source, and authority documents supplied by the relevant organisation or representative.
We use verification information to confirm that an account is linked to the person using it, reduce impersonation and fraud, compare company information with registration records, assess authority for protected actions, investigate mismatches and keep evidence of the completed check. We do not use identity, liveness or CIPC checks to assess creditworthiness, financial capacity, investment suitability, business quality or honesty.
The required fields are mandatory for the protected function concerned. If the user does not provide them, or the check cannot be completed, FounderZA may keep the account at a limited-access stage and offer an appropriate review or lawful alternative where available. A failed or inconclusive automated check is not treated as proof of misconduct.
FounderZA sends the minimum information needed for the selected check to its appointed verification provider through a protected server connection. The provider compares the information with the applicable identity or company source and returns a status, reference and limited result. FounderZA keeps the minimum result and evidence needed to administer the account, respond to disputes and meet legal duties. Raw biometric material is not retained by FounderZA unless it is technically necessary, lawful and disclosed before collection.
Only authorised FounderZA personnel and service providers may access verification records for verification review, security, support, incident handling or legal compliance. The relevant user may be asked for additional information where a mismatch requires review. Another marketplace user does not receive the user's raw identity document, facial capture or biometric result merely because they are deciding a confidential-access request.
Verification is a point-in-time check and may depend on user-supplied information and external records. It does not replace due diligence, source-of-funds checks, regulatory checks, professional advice or an assessment of a counterparty. It does not prove a broker's mandate or a signatory's authority for a particular agreement; those matters are checked separately where required.
The Privacy Notice explains the lawful grounds, recipients, cross-border safeguards, retention and rights that apply. A user may request access to or correction of their verification information, object where POPIA permits it and ask for review of an unresolved result through Complaints and Rights Requests. FounderZA may use de-identified or aggregated verification and interaction information to research technical reliability and improve the platform. That research does not create a public trust score or make an access decision by itself.