Company identity
Verifiable nowRanked Technologies Limited, RC 9522220. Buyers can cross-check through CAC public search: https://icrp.cac.gov.ng/public-search/.
This page is printable and downloadable. It uses redacted/sample evidence to show what buyers receive while avoiding the common trust trap: unpermissioned logos, invented case studies, exposed tester PII, or raw recording URLs.
This table separates what can be verified today from what remains sample-only or permission-gated. It is designed to prevent fake social proof while still giving procurement a concrete audit trail.
Ranked Technologies Limited, RC 9522220. Buyers can cross-check through CAC public search: https://icrp.cac.gov.ng/public-search/.
Public summary is downloadable at /proof/security-dpa-summary and maps to /trust and /trust/data-residency.
Includes DPA coverage, processor list, Identity-verification explainer, incident process, backup/RPO/RTO posture, architecture summary, network-proof status board, and sample audit log.
Synthetic format examples show fields, severity taxonomy, payment rail, and refund terms without implying a customer case study.
Explains verification timing, no tester fee, Flutterwave payout route, and audit trail. Real payout receipts require tester permission before sharing.
Checklist and screenshot fields are public. Real screenshots will be published only after buyer permission.
No logo wall or named case study is shown until permission is granted in writing.
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.
VAT-exclusive; 7.5% FIRS VAT added when applicable. We'll confirm cohort timing when you book. Google approval is not guaranteed.
These are the operational artifacts a buyer can request before a larger or regulated engagement. Current limitations are labelled plainly instead of dressed up as certification.
Standard DPA terms cover controller/processor roles, purpose limitation, sub-processor notice, deletion timelines, breach notice, and data subject request handling.
Supabase, Vercel, Cloudflare, Flutterwave, Google Gemini, Resend, Disify, Country.is, Google Safe Browsing, and Stripe for approved manual international billing only.
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.
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.
Security disclosures go to [email protected]. Confirmed material incidents are logged internally, affected customers are emailed, and NDPA-relevant breach notices target 72 hours after confirmation.
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.
Format example only. Real audit logs are shared under contract or incident process, with personal data minimised.
| Time | Action | Note |
|---|---|---|
| 2026-06-24T08:13:42Z | tester_demo.approvedadmin:sample · demo_session:9JT-SAMPLE-DEMO-014 | Demo approved; verification step unlocked. No payout route exposed. |
| 2026-06-24T08:22:10Z | bank_verification.recordedsystem:flutterwave · tester:anon-7f3a | Bank-account verification succeeded. |
| 2026-06-24T09:02:31Z | submission.approvedadmin:sample · session:9JT-SAMPLE-PLAY-001-08 | Submission approved, anonymised evidence added to buyer pack. |
“We would rather show a smaller, labelled proof pack than borrow logos or pretend a sample is a case study.”
“Payment should come after we know we can route the cohort and stand behind the SLA, not before the buyer understands the fit.”
Evidence: 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.
Evidence: 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.