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.

Scope

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

Acknowledgement

The team acknowledges reports within the published service window and explains 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

Urgent safety and fraud concerns are reviewed first

If a report suggests immediate safety, impersonation, or payment risk, it is prioritised ahead of routine updates.

First update

You receive an update within the published review window

Customers and Guild members receive a first response and the next evidence step within the stated service window.

Investigation

Disputes stay under review until a documented outcome is reached

Dispute cases are tracked until they are resolved, escalated, or closed with a recorded outcome.

Follow-up

Post-resolution actions move after the review closes

Payment release, standing updates, and follow-up notices move only after the review outcome is recorded.