Sensitive reporting

Report sensitive issues safely

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.

Scope

Use the report path for impersonation, payment abuse, safety issues, or service disputes that need support review.

Acknowledgement

The team works to acknowledge reports within the published service window and explain the next step.

Resolution

Resolved cases may lead to standing updates, payment actions, or support follow-up depending on the outcome.

What to send

  • Do not send card details, CVVs, bank tokens, or login passwords.
  • Share only the booking, evidence, or contact details needed to review the case.
  • Redact unrelated personal data before uploading screenshots or PDFs.
  • Use the support path for active customer harm and the policy pages for general guidance.

Primary channels

Support

support@qubictry.com

General service and account issues

Report a concern

/report

Guided service, payment, and safety issue reporting

Response windows

Urgent concerns

Safety and fraud concerns come first

Reports suggesting immediate safety, impersonation, or payment risk are prioritised.

First update

First updates follow the published target

The first response and next evidence step follow the stated service window.

Investigation

Disputes stay under review until an outcome

Cases remain tracked until resolved, escalated, or closed with a recorded outcome.

Follow-up

Follow-up starts after review closes

Payment, standing, and follow-up actions move after the outcome is recorded.