Scope
Use this route for security flaws, credential exposure, impersonation vectors, or technical weaknesses that could affect customers, Guild members, or ecosystem operators.
Responsible disclosure
Coordinated reporting for sensitive technical issues
Use this route when the issue is technical, confidential, or dangerous to publish openly. This includes credential exposure, impersonation vectors, account takeover risk, and flaws in trust or payout flows.
Acknowledgement
TrustOps should acknowledge responsible disclosures within 24 hours and move severe cases into immediate triage.
Coordination
We coordinate remediation with the affected product owner, confirm the safe fix path, and publish an anonymised note when the issue closes.
What to send
- Do not send card PANs, CVVs, bank tokens, or login passwords.
- Redact unrelated identity records before uploading screenshots or PDFs.
- Share only the booking, dispute, or device context needed to verify the issue.
- Use the disclosure route for sensitive technical weaknesses and the incident route for active customer harm.
Primary channels
TrustOps hotline
+234 800 400 1122
Escalations, fraud sync, disputes
Security email
security@qubictry.com
Coordinated disclosure, vulnerability reports
Response windows
T+30 min
Initial triage
TrustOps reviews active service risk, fraud, or handoff reports and confirms the first routing path.
T+24h
Acknowledgement
Reporters receive a first response, evidence checklist, and the next action expected from the operations desk.
14 working days
Investigation window
Disputes, referral incidents, and service-risk reviews should reach a documented outcome within the published review window.
T+48h
Post-resolution action
Once a case closes, restitution routing, trust-note publication, or follow-up action should move within the next 48 hours.