Service trust

Service trust, clearly handled

Public guidance for verification, payment protection, service evidence, and support.

Request a serviceOpen the directoryReport a service issue

Directory trust state

60

Listed Guild members

29

Active trust badges

21

Covered locations

3

Capability tracks

How trust works

How Qubictry keeps service work clearer

Trust centres on visible verification, a clear brief, and support that stays attached to the job.

Verification

How Guild member verification works

Read what evidence is reviewed before a Guild member can receive public requests.

Trust Badge

How to read Trust Badge status

Read badge status, public evidence, and warning guidance before hiring.

Protected payment

How protected payment works

See how service milestones and customer confirmation support completion and release decisions.

Support

How to report a service issue

Open a guided support path when a job, Guild member, payment, or safety issue needs attention.

Rules

Policies

Review the rules for service requests, evidence, privacy, and disputes.

Verification layer

Trust Badge and Trust Passport live inside the Trust Centre

Use these routes to review evidence, trust context, and reporting guidance.

Trust Badge

Read badge status before hiring

Check verification status, public evidence, and warning guidance before a service request moves forward.

Trust Passport

Open portable trust context

Use the public trust layer of the Qubicbox unified profile when a person or business needs wider ecosystem context.

Report misuse

Flag impersonation or fraud

Send the minimum evidence needed when a badge, profile, Guild member, or service claim appears suspicious.

Verification

How Guild members are verified

Review who you are dealing with before work starts.

  • Identity and contact details are reviewed before a Guild member is shown as verified.
  • Service evidence, trade information, and location details help determine readiness.
  • Confirmed Curator references can appear as “Reference-backed” without exposing sponsor identity or private notes.
  • Reference-backed, identity checked, service evidence checked, and operational approval are shown as separate trust states.
  • Verification status can change over time if evidence expires, disputes increase, or reviews remain unresolved.

Protected payment

How jobs, payment, and evidence stay linked

Where supported, payment steps stay attached to the service record.

  • The agreed service scope should be clear before payment moves.
  • Job notes, proof of progress, and completion evidence can support the release decision.
  • If a concern is raised, the case can stay on hold while the support review completes.

Service windows

How review windows are explained

Service windows set clear expectations for customers and Guild members.

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.

Disputes

What happens if there is a dispute

Disputes are tracked until there is a documented outcome, escalation, or closure.

Clear job scope

Start with the service, location, timing, and budget where possible.

Protected payment where supported

Where supported, keep payment on the service record rather than in private side deals.

Evidence-led completion

Use service notes, photos, and customer confirmation where needed.

Dispute review

Keep the job record and supporting evidence together for review.

Privacy and minimisation

Share only the minimum evidence needed. Never include bank or login details.

Reporting concerns

How to report a concern safely

Use the guided support routes and share only the information needed to understand the case.

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.

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

Published guidance

Recent trust guidance

Only published trust guidance backed by live records is shown here.

24/07/2026

Production Trust Notes smoke draft

AI disabled, TrustOps completion required.

21/07/2026

Trust Notes Production Smoke Draft

This is a review-only Trust Note draft intended to verify the production drafting path after a deploy transport repair. The submitted pattern references a possible payment diversion risk category affecting Qlutterbox, but the available basis is a single manual-review signal with no independent corroboration provided. This draft should not be treated as a public advisory or evidence of an active threat without further validation.

21/07/2026

Production Trust Notes smoke draft

AI disabled, TrustOps completion required.

Contact and escalation

Where to go next

Use the route that best fits the issue you are trying to resolve.

Support

support@qubictry.com

General service and account issues

Report a concern

/report

Guided service, payment, and safety issue reporting

Policy centre

/policies

Marketplace rules, privacy, and payment guidance

Responsible disclosure

/responsible-disclosure

Sensitive security reports