Incident reporting

Report the issue safely

Submit a service, payment, Guild member, fraud, safety, or platform concern for review. Keep the report factual and limited to the information needed.

Start report

Report details

Tell us what happened

Submit a factual summary and only the information needed for review. The team may request supporting evidence after the report is received.

What are you reporting?

Service or job disputeQuality, completion, materials, timing, or an unsafe handoff.Payment concernAn incorrect amount, changed payment instruction, receipt, hold, or release concern.Guild member concernA profile, conduct, verification, availability, or representation concern.Fraud or impersonationSuspected impersonation, payment diversion, false identity, or deceptive contact.Safety concernA situation that may put a customer, Guild member, or another person at risk.Platform or account issueA technical, account, navigation, or general Qubictry issue.

Contact emailRelated reference (optional)

Short summaryWhat happened?Do not include passwords, OTPs, card details, CVVs, bank tokens, or unrelated identity documents.I confirm that this report is factual and contains only the information needed for review.

Reporting a security weakness?

Active fraud or impersonation

Report impersonation, changed payment instructions, false identities, or attempts to move work away from its protected record.

Service, payment, or safety concern

Report contested quality, completion, materials, payment, receipt, conduct, or unsafe handoff concerns.

Security weakness

Use responsible disclosure for credentials, account takeover risks, or technical weaknesses that should not be shared in an ordinary report.

Open responsible disclosure

What to include

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.

Need another route?

Security and general support stay separate

Use responsible disclosure for sensitive technical findings. Use support email for a question that does not require an incident record.

Responsible disclosure Email support

Service 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.