This page explains the contract controls 9jatesters can put in place for paid scopes: NDPA roles, permitted processing, sub-processor notice, deletion timelines, breach notice, and buyer approval gates.
Human contact: Chat on WhatsApp · [email protected]
For buyer projects, the buyer is normally the controller for its customer/product data and 9jatesters acts as processor. Tester account, payout, anti-fraud, and platform safety records are handled as 9jatesters controller records.
The DPA narrows processing to routing testers, collecting consented sessions, generating summaries, producing evidence packs, paying contributors, and handling support/security obligations.
The live sub-processor list is public. Larger-contract buyers receive notice before material changes involving personal data and can object on reasonable security or compliance grounds.
Confirmed material incidents are triaged, logged, contained, and communicated to affected customers. NDPA-relevant breach notices target 72 hours after confirmation where notification duties apply.
Buyer data deletion follows the engagement terms. Tester account deletion follows the public privacy policy, with fraud-prevention audit records and verification hashes retained where Nigerian legal bases require it.
9jatesters does not currently claim SOC 2 or ISO 27001 certification. The DPA is a contractual control pack for controlled pilots and larger scopes while managed production hardening continues.
A DPA draft, processor list, privacy/security summary, sample audit-log fields, data-residency explanation, and project-specific deletion/retention schedule.
Regulated buyers may require extra clauses, hosted-processing commitments, independent security review, or an NDA-gated architecture walk-through before production volume.
Send the use case and data categories. We will share the current DPA draft and flag anything that needs custom handling before payment.