Home / Verification & Consent Language

Verification & Consent Language

Draft consent blocks for KYC, credit checks & marketing · For attorney review · POPIA & NCA compliant
Attorney review required — not yet legally binding
This is a thorough, SA-specific draft for your lawyer to review and finalise. Items in red italics require your specific details or a legal decision before publication.

This page sets out the consent language shown to users during sign-up and before a credit check is requested. Each consent block is a separate, granular consent as required by POPIA.

How to use this document

Each block below represents a distinct consent moment in the user journey. Implement these as separate, tappable checkboxes — never pre-ticked, never bundled into one "I agree to everything" checkbox. Required consents gate the action they enable. Optional consents (Gold, marketing) must never gate core functionality.

Block 1 — Identity verification consent (required at sign-up)

Shown on the sign-up KYC screen before the user uploads their ID document and takes the liveness selfie. This consent is required to create a verified account.

Block 2 — Landlord ownership consent (required for landlords at sign-up)

Shown in addition to Block 1 when the user selects "landlord" during registration. Required before a property can be listed.

Block 3 — Credit & affordability check consent (optional, per application)

Shown when a tenant chooses to add a credit check to their application (the R250 vetting option). Must be a separate, explicit consent — this is a requirement of both POPIA and the National Credit Act. Never pre-selected.

Attorney action — NCA section 70

Confirm the exact wording of the credit bureau's own consent language under the NCA and align Block 3 with it. The bureau may have a prescribed consent form that must be incorporated verbatim. Also confirm that [credit bureau name] is correctly registered with the NCR.

Block 4 — Marketing consent (optional, at sign-up)

Must be a separate optional checkbox — never bundled with the identity or service consent. The user can use the full platform without ticking this.

5. Implementation notes for developers

Good practice — record of consent

Store for each consent: user ID, consent version ID, timestamp (UTC), IP address, and the checkbox state. This is the evidence you will need if a data subject or regulator ever asks whether consent was properly obtained.

RentBid (Pty) Ltd · Pretoria, South Africa · info@rentbid.co.za

Prepared by Nuvora on behalf of RentBid. This is a draft only and does not constitute legal advice.