# 9jatesters Procurement Proof Pack Updated: 2026-09-12 This is a public synthetic/sample pack. It shows the structure of buyer evidence without implying a redacted customer case study, exposing client data, tester PII, raw media URLs, or unpermissioned client logos. ## Company - Legal supplier: Ranked Technologies Limited - CAC/RC reference: RC 9522220 - Support: support@9jatesters.com - Evidence status: public assets are sample/redacted unless a customer has granted written permission. ## Sample Report - Order: 9JT-SAMPLE-PLAY-001 - Pack: Managed Play launch - Client: Synthetic demo fintech app - Scope: Synthetic Google Play closed-test support scenario with 15 staffed testers for a rule that requires 12, showing the structure of a buyer deliverable, including seat refill support and proof screenshot fields. - Status: Synthetic sample only - not a redacted customer case study ### Evidence Included - Tester roster uses anonymised IDs only; no raw names, phone numbers, or bank details. - Engagement proof includes timestamped Play Console screenshots and enrolment checklist. - Failed or duplicate tester attempts are manually reviewed; the 3 spare seats in the 15-tester roster cover them, and every swap is documented before the 14-day window is marked complete. ### Sample Findings - P1 Onboarding copy unclear after OTP retry: Synthetic example: 3/15 demo testers paused on the retry screen for more than 45 seconds. Recommendation: Add a resend timer, clarify whether WhatsApp or SMS receives the OTP, and preserve the typed phone number after retry. - P2 Low-end Android load time risk: Synthetic example: Tecno Spark 10 and Infinix Hot 30 sessions showed first dashboard paint above 7 seconds on throttled 3G. Recommendation: Lazy-load promotions and defer non-critical analytics until after account balance appears. ## Sample Invoice - Invoice: 9JT-SAMPLE-INV-0007 - Item: Managed Play launch - 15 testers / 14 days - Subtotal: NGN 103,500 - VAT: VAT-exclusive; 7.5% FIRS VAT added when applicable - Payment rail: Flutterwave NGN checkout or invoice link for approved custom scopes - Refund: We'll confirm cohort timing when you book. Google approval is not guaranteed. ## Security Summary - Bank-account verification is handled through Flutterwave; 9jatesters stores only a one-way hash for uniqueness. - Buyer-facing media playback is routed through authenticated API proxies rather than exposing storage URLs in client JSON. - Contributor-data exports require approved submissions, live ai_data_reuse consent, and provenance rows linked to the exact job. - Exports omit raw PII: no names, phone numbers, bank details, exact addresses, or raw internal object URLs. - Admin reviews, consent events, payouts, and material state changes write audit-log records for incident reconstruction. ## Procurement Artifacts - DPA coverage: Available for scoped paid work. Standard DPA terms cover controller/processor roles, purpose limitation, sub-processor notice, deletion timelines, breach notice, and data subject request handling. - Processor list: Published. Supabase, Vercel, Cloudflare, Flutterwave, Google Gemini, Resend, Disify, Country.is, Google Safe Browsing, and Stripe for approved manual international billing only. - Identity-verification explainer: Published. Bank-account verification happens only after demo approval and before paid work unlocks; it is handled by Flutterwave, and only a one-way hash is stored. - Backup / RPO / RTO: Operator-managed. Backups and incident playbooks are operator-managed and not yet replicated off-site. Larger engagements receive the hosted-production upgrade plan, target PITR posture, RPO/RTO assumptions, and vendor questionnaire responses before launch. - Incident process: Published summary. Security disclosures go to support@9jatesters.com. Confirmed material incidents are logged internally, affected customers are emailed, and NDPA-relevant breach notices target 72 hours after confirmation. - Architecture diagram: Public summary. Browser clients talk to the Next.js app; authenticated server routes broker database, storage, email, payment, AI summarisation, and safety checks. Raw private media URLs are not exposed in buyer/tester JSON. ## Sample Audit Log - 2026-06-24T08:13:42Z | admin:sample | tester_demo.approved | demo_session:9JT-SAMPLE-DEMO-014: Demo approved; verification step unlocked. No payout route exposed. - 2026-06-24T08:22:10Z | system:flutterwave | bank_verification.recorded | tester:anon-7f3a: Bank-account verification succeeded. - 2026-06-24T09:02:31Z | admin:sample | submission.approved | session:9JT-SAMPLE-PLAY-001-08: Submission approved, anonymised evidence added to buyer pack. ## Procurement Checklist - Company identity: Ranked Technologies Limited, RC 9522220. - Sample report: report structure, evidence fields, severity taxonomy, and recommendation format. - Sample invoice: pack name, NGN price, VAT treatment, refund policy, and payment rail. - Security/DPA summary: identity verification, processor list, media access, consent, export privacy, audit logs. - Tester proof: payout-control summary, verification timing, no tester fee, verification requirement, and support path. - Play Console proof: 15-tester roster against Google's 12-tester/14-day rule, seat-refill policy, screenshot requirements, and no-approval-guarantee note. - Operational proof: incident process, backup/RPO/RTO posture, architecture summary, and sample audit log. ## Play Console Checklist - 15 qualified Nigerian Gmail testers staffed into the closed-test track. Google requires 12 for 14 consecutive days, so 3 seats are spare cover. - 14 consecutive days are tracked manually before the buyer is told to submit Play Console evidence. - Testers are paid for each day they check in, credited the moment they open the app, plus a completion bonus they keep only by never missing a day. That is what holds the roster together for the full window. - Drop-outs or invalid accounts trigger manual seat refill during the active window. - Final buyer pack includes anonymised roster, date range, and screenshot checklist. ### Screenshot Fields - Closed-test track name and package name, with sensitive app identifiers redacted when requested. - Tester count and opt-in date range covering the 14-day window. - Anonymised Gmail roster or evidence table showing accepted/replaced testers. - Replacement log for invalid/drop-out testers, including reason and date. - Final submission checklist reminding buyers that Google approval is not guaranteed. ## Founder Notes - Proof philosophy: "We would rather show a smaller, labelled proof pack than borrow logos or pretend a sample is a case study." - Buyer promise: "Payment should come after we know we can route the cohort and stand behind the SLA, not before the buyer understands the fit." ## Evidence Status - Company identity: Verifiable now. Ranked Technologies Limited, RC 9522220. Buyers can cross-check through CAC public search: https://icrp.cac.gov.ng/public-search/. - Security/DPA summary: Verifiable now. Public summary is downloadable at /proof/security-dpa-summary and maps to /trust and /trust/data-residency. - Procurement bundle: Verifiable now. Includes DPA coverage, processor list, Identity-verification explainer, incident process, backup/RPO/RTO posture, architecture summary, network-proof status board, and sample audit log. - Sample report and invoice: Sample now. Synthetic format examples show fields, severity taxonomy, payment rail, and refund terms without implying a customer case study. - Payout controls: Control summary now. Explains verification timing, no tester fee, Flutterwave payout route, and audit trail. Real payout receipts require tester permission before sharing. - Play Console proof gallery: Not claimed yet. Checklist and screenshot fields are public. Real screenshots will be published only after buyer permission. - Customer logos and case studies: Not claimed yet. No logo wall or named case study is shown until permission is granted in writing.