Legal
Privacy Policy
Version 1.1 · Effective 22 September 2026
1. Who we are
Wazora provides managed human intelligence services for organizations developing artificial intelligence systems. This policy describes how we handle personal information collected through wazora.ai.
OFFERPOINT LLC, doing business as Wazora, is the controller of personal information used for contributor identity verification. Didit provides the verification service and acts as Wazora's processor or service provider for that processing. Didit's Data Processing Agreement also states that Didit may act as an independent controller for limited processing of anonymized, aggregated, or pseudonymized data derived from client data, for model training and improvement, fraud and abuse prevention, and service security and integrity. Didit states that pseudonymized data remains personal data where it can still be linked to an individual. That limited processing is carried out by Didit for Didit's own purposes and is separate from Didit's processing as Wazora's processor.
2. Information we collect
Enterprise enquiries: name, work email, company, job title, and the project details you choose to share.
Contributor applications: name, email, country and city or region, age confirmation, education level, languages, area of expertise, equipment and connectivity information, availability, optional LinkedIn URL, optional CV, and your reasons for applying.
We do not request government identification, banking details, or other highly sensitive information during initial registration.
Later identity verification
Identity verification is a later contracting-readiness step. It is separate from initial application and registration.
If Wazora later invites a contributor to verify their identity, Didit may ask the contributor to present a government-issued identity document and use their device's camera. Wazora's configured workflow uses:
- Government identity-document verification: checking whether the document appears authentic and valid.
- Passive Liveness: using camera information to help establish that a real person is present.
- Face Match: comparing the live facial image with the photograph on the identity document.
- Device & IP Analysis: examining device and network information for fraud-prevention and security signals.
Didit must process the identity-document, facial, liveness, device, and network information needed to carry out those checks. Wazora does not claim that Didit avoids processing those data.
Wazora's ordinary identity-verification and consent records are configured not to store identity-document, passport, or national identification numbers; date of birth; identity-document images; selfie or liveness media; biometric templates; raw IP addresses; or device fingerprints.
Wazora may receive and keep limited information needed to establish and audit the result. This may include verification status, provider and session references, workflow and version information, timestamps, notice and consent evidence, and configured returned verification fields or results.
Before a verification begins, the contributor must give separate, explicit consent. For more detail, see the Identity Verification Privacy Notice, Version 1.0, approved and effective 22 September 2026.
3. How we use information
To respond to enquiries, evaluate applications, match contributors to suitable projects, operate quality assurance, and communicate about opportunities and services.
Where identity verification is introduced, Wazora will use it for identity verification, fraud prevention and security, and contributor contracting readiness.
Identity verification does not determine qualifications, assessment scores, jurisdiction eligibility, or project assignments. It does not guarantee project work. Kenya jurisdiction eligibility remains Under review and is a separate control; successful identity verification must not be treated as a finding that a contributor is eligible to work on projects from Kenya.
4. Legal bases
Depending on your location, we rely on your consent, our legitimate interests in operating and improving our services, and the steps necessary to enter into a contract.
Separate, explicit consent is required before Didit identity verification starts.
If you do not consent to face-processing verification, do not continue. Contact Wazora Operations at ops@wazora.ai to ask whether an appropriate alternative verification method is available. Wazora does not promise that an alternative will be available.
5. Sharing
We may share limited information with service providers who support our operations and, where a project requires it, with customers under confidentiality obligations. We do not sell personal information.
For contributor identity verification, Didit is Wazora's processor or service provider and processes information needed to perform the configured checks. The Didit Business Terms and Annex 2 Data Processing Agreement are the provider-published version shown as updated on 2026-09-04. Wazora holds an account-specific executed copy of the Business Terms and Data Processing Agreement, together with the associated DocuSeal audit log, dated 19 September 2026.
On 19 September 2026, Didit's legal team confirmed in writing that Didit currently uses two subprocessors and no others:
- AWS EMEA SARL — cloud infrastructure. Didit states that its verification platform runs on this infrastructure and that the features enabled for Wazora's verification workflow are processed and stored in the European Union, Ireland region (eu-west-1).
- Google Cloud EMEA — geolocation through the Maps API only. Didit states that this processing remains within the European Economic Area.
These are statements made by Didit in its contractual documentation and written response. Wazora has not independently certified or audited them.
6. Retention
We keep application and enquiry information for as long as needed for the purposes above and to meet legal obligations.
For the Didit application named Wazora Identity Verification, provider retention is configured to one month. The biometric-template setting is Delete with session. Retain until scheduled expiry or earlier deletion is not selected. Didit's console states that verification data is automatically and permanently deleted after the configured retention period and that, with Delete with session, the face biometric template is deleted together with the session.
Wazora retains its limited identity-verification result, consent, and audit records while the contributor remains active in the Wazora network and for up to 24 months after the contributor's last engagement or meaningful contact, after which those records are deleted or irreversibly anonymised. For this purpose, last engagement or meaningful contact means the effective date on which the contributor's independent-contractor engagement with Wazora ends, whether voluntarily by the contributor or terminated by Wazora; routine communications, assessments, logins, automated messages, internal administrative activity, or later non-engagement contact do not restart or extend the period. A shorter destruction period required by applicable law controls. A longer period applies only where a documented legal, contractual, fraud-investigation, dispute, or legal-hold requirement justifies preserving a particular non-biometric record.
7. Your rights
Subject to applicable law, you may request access, correction, deletion, or withdrawal of consent by contacting us.
Withdrawing consent does not affect processing that was lawful before withdrawal. The effect of withdrawal on records that Wazora or Didit must retain for legal, security, fraud-prevention, or audit purposes depends on applicable law and must be confirmed for the contributor's circumstances.
8. International transfers
Wazora operates across markets, and information may be processed in countries other than your own with appropriate safeguards.
Didit's published materials state that its primary processing infrastructure is in the European Economic Area. Didit's legal team confirmed in writing on 19 September 2026 that, in Didit's standard operation, there is no transfer of personal data outside the European Economic Area, and that Clause 8 of the Data Processing Agreement provides for Standard Contractual Clauses and a transfer impact assessment should that arrangement change. These are provider statements and contractual findings, not independent verification, certification, or legal conclusions by Wazora.
Didit's Data Processing Agreement also provides contractual transfer mechanisms where relevant, including recognized European Union, United Kingdom, and Swiss mechanisms and adequacy frameworks, with transfer-impact safeguards where required. This is a contractual finding, not independent legal certification by Wazora.
Wazora has opted out of allowing its organization's verification data to be used for Didit's future model training, fine-tuning, evaluation, validation, and dataset curation. Didit's console states that historical and new verification data are excluded from those future uses after opt-out. Models trained before the opt-out are not retroactively untrained.
9. Contact
Questions about this policy, identity verification, or privacy rights can be sent to ops@wazora.ai.