Privacy Policy

Last updated: 30 April 2026 · Effective date: 30 April 2026

1. Identity of Responsible Party

The responsible party (as defined in POPIA Section 1) for the processing of your personal information is:

FieldDetail
Legal name[Imbazo (Pty) Ltd / Trading name — to be registered]
Registration number[To be assigned on incorporation]
Registered address[Physical address — to be confirmed]
Contact emailprivacy@imbazoca.com

2. Information Officer

In terms of POPIA Section 55, our designated Information Officer is:

FieldDetail
Name[Information Officer name — to be appointed]
Emailprivacy@imbazoca.com
Phone[To be confirmed]

For Zimbabwean data subjects, enquiries may also be directed to the Postal and Telecommunications Regulatory Authority of Zimbabwe (POTRAZ) at www.potraz.gov.zw.

3. Purpose of Collection (POPIA Section 13)

We collect and process personal information for the following specific, explicitly defined purposes:

3.1 Participant Data

Data categoryPurposeLegal basis (POPIA s11)
Name, phone, emailIdentity verification, communicationConsent (s11(1)(a))
Date of birth, genderTask matching (demographic criteria)Consent (s11(1)(a))
Country, city, provinceGeographic task targetingConsent (s11(1)(a))
Education, employment, incomeSocio-economic task matchingConsent (s11(1)(a))
Languages, ethnicityLinguistic/cultural task matchingConsent (s11(1)(a)); ethnicity is special personal information processed only with explicit consent per s26-s33
Internet access typeTask feasibility assessmentConsent (s11(1)(a))
Payment detailsDisbursing task participation paymentsContract performance (s11(1)(b))
Field of study, technical skillsTask matching (skill-based criteria)Consent (s11(1)(a))
Device typeTask feasibility assessment (mobile vs desktop)Consent (s11(1)(a))
Task responses and outputs (survey answers, image labels, voice recordings, AI ratings)Delivery to commissioning client for their stated purposeConsent (s11(1)(a)) + Contract performance (s11(1)(b))

3.2 Client Data

Data categoryPurposeLegal basis
Name, email, organisationAccount creation, communicationContract performance (s11(1)(b))
Payment informationBilling for task servicesContract performance (s11(1)(b))
Task content/criteriaService deliveryContract performance (s11(1)(b))

3.3 Task Output Data

When you complete tasks on Imbazo — including surveys, image labelling, voice recordings, AI response ratings, and content reviews — your responses and outputs are delivered to the client who commissioned the task. This is the core service that Imbazo provides.

Task outputs may be used by clients for:

By completing a task and receiving payment, you consent to your task output being delivered to and used by the commissioning client for the purpose stated in the task description. Task outputs are considered work product — once delivered and paid for, the intellectual property in the output transfers to the client.

4. How We Share Data with Clients

Imbazo is a marketplace that connects participants with clients who need human input. Sharing your data with clients is fundamental to the service. Here is exactly what we share and when:

4.1 Profile Matching (Pseudonymised)

To match you with relevant tasks, we share your demographic profile with clients in pseudonymised form — using your Imbazo participant ID, not your real name or phone number. Clients may see your age range, gender, country, education level, field of study, technical skills, languages, and device type. They do not see your name, phone number, email, or exact date of birth.

4.2 Task Outputs (Delivered to Client)

When you complete a task, your responses are delivered to the commissioning client. Task outputs may include text responses, voice recordings, image labels, AI ratings, or other work product. Once delivered, the client becomes an independent data controller for that output data and is responsible for their own compliance with applicable data protection laws.

4.3 Identity Data (Only with Explicit Consent)

Your name, phone number, or email are never shared with clients unless: (a) the specific task requires it, and (b) you provide explicit, informed consent for that particular task before participating. You will always be clearly informed before any identity data is shared.

4.4 Aggregated and Anonymised Data

We may use anonymised, aggregated data about our participant panel (e.g., demographic distributions, task completion rates, regional availability) for:

Anonymised, aggregated data is not personal information and may be retained and used indefinitely.

4.5 We Do Not Sell Your Personal Data

Imbazo does not sell, rent, or trade your personal information to third parties for their own marketing or advertising purposes. Data sharing is limited to the purposes described in this policy: task matching, task output delivery, and platform operations.

5. Use of Data for AI and Machine Learning

Some tasks on Imbazo involve creating training data for artificial intelligence systems. This includes but is not limited to:

By completing AI-related tasks, you consent to your task outputs being used to train, evaluate, or improve artificial intelligence systems operated by the commissioning client. Your personal identity data (name, phone number, email) is not included in AI training datasets — only your pseudonymised task outputs.

Your demographic profile may be used in anonymised, aggregated form to ensure AI training data is diverse and representative of different populations, languages, and perspectives.

6. Our Role in Data Processing

Imbazo acts in two distinct roles depending on the type of data:

RoleData typeWhat this means
Data ControllerParticipant profile data (name, demographics, contact details, platform usage)Imbazo decides how this data is collected, stored, and used for platform operations, task matching, and communication. We are directly responsible for protecting this data.
Data ProcessorTask data commissioned by clients (survey questions, labelling instructions, collected responses)The client determines what data is collected through their task. We process and deliver this data on the client's behalf per their instructions. The client is responsible for their own data protection compliance when using data received from Imbazo.

Where Imbazo acts as a data processor, we process task data only in accordance with the client's instructions and applicable law. We do not use client task data for our own purposes except as necessary to operate the platform (e.g., quality assurance, fraud detection, payment processing).

7. Data Minimisation & Adequacy (POPIA Section 10)

We collect only data that is adequate, relevant, and not excessive for the stated purposes. Participants may decline to provide optional fields (education, income, ethnicity) without affecting core panel membership.

8. Consent (POPIA Section 11)

Participant consent is obtained via our WhatsApp onboarding flow. Consent is:

Consent can be withdrawn at any time by messaging "STOP" to our WhatsApp number or emailing privacy@imbazoca.com.

9. Information Quality (POPIA Section 16)

We take reasonable steps to ensure personal information is complete, accurate, and not misleading. Participants can review and correct their information at any time via WhatsApp or by contacting us.

10. Data Retention (POPIA Section 14)

Data typeRetention periodJustification
Active participant profilesWhile participant is active + 2 years after deactivationService delivery + legal compliance
Completed task/study data5 years from task/study completionResearch audit trail, tax records
Task output data delivered to clientsRetained by Imbazo for 2 years from delivery; client retention governed by client's own policyService records, dispute resolution, quality assurance
Consent recordsIndefinite (anonymised after 7 years)Legal compliance proof
Audit logs7 yearsLegal and regulatory compliance
Payment records7 yearsFinancial regulatory requirements
Client accountsWhile active + 2 years after last loginService delivery

On deletion request, personal data is erased from active systems within 30 days. Anonymised aggregates may be retained for platform analytics.

11. Cross-Border Transfers (POPIA Section 72)

Sub-processorLocationPurposeSafeguard
Supabase Inc.United StatesDatabase hosting (Postgres)SOC 2 Type II compliant; contractual data processing terms
Twilio Inc.United StatesWhatsApp messaging via Twilio APISOC 2 Type II compliant; DPA with standard contractual clauses
Clerk Inc.United StatesClient authenticationSOC 2 compliant; contractual safeguards
Vercel Inc.United States / Global edgeWeb application hostingSOC 2 Type II; DPA with standard contractual clauses
Memgraph Ltd.United KingdomGraph database — participant matching and platform operationsContractual data processing terms
Stripe Inc. (future)United StatesPayment processingPCI DSS Level 1; GDPR-compliant DPA

All sub-processors are bound by data processing agreements that require them to process your data only for specified purposes and to implement appropriate security measures.

12. Security Safeguards (POPIA Section 19)

We implement appropriate technical and organisational measures to protect personal information, including:

13. Your Rights (POPIA Section 23–25)

As a data subject, you have the right to:

Limitation on deletion of delivered task outputs: Where your task outputs have already been delivered to a client and payment processed, we may not be able to recall that data from the client. You may contact the client directly to exercise your rights over data they hold. We will provide you with the client's contact details upon request.

To exercise any right, contact us at privacy@imbazoca.com or message "PRIVACY" to our WhatsApp number. We will respond within 30 days.

14. POPIA Section 18 Notification

15. Children's Data

Imbazo does not knowingly collect personal information from persons under the age of 18. Our onboarding flow includes age verification. If we discover we hold data of a minor, it will be deleted immediately.

16. Cookies & Analytics

Our web application uses only essential cookies for session management (authentication). We do not use advertising or tracking cookies. Vercel Analytics may collect anonymised performance metrics (page load times, country-level geographic data).

17. Changes to This Policy

We may update this policy from time to time. Material changes will be communicated via email (clients) or WhatsApp (participants) at least 14 days before taking effect. The "Last updated" date at the top reflects the most recent revision.

18. Contact

For any privacy-related enquiries: