The short version (plain language)
- Q2GO is an intermediary technology platform, not a party to your stay. The Host is the Merchant of Record and seller of the stay; the stay contract is between Guest and Host.
- A payment dispute or chargeback freezes the Host's payout for that booking and is logged; transfers already made to the Host can be reversed (clawed back).
- Refunds and admin/goodwill refunds run through one controlled, audited path. The payment provider debits a refund to Q2GO first; Q2GO recovers the Host's share from the Host (Payment Terms §12).
- You can report content you believe is illegal through our DSA notice-and-action channel — no account needed (see doc 18).
- Reviews are moderated for spam/contact-sharing patterns and may be held for manual review.
- We may suspend or restrict accounts and listings for trust-and-safety, compliance, or non-payment reasons, with a stated reason where applicable.
- We do not make automated risk decisions about you today. No risk score is used to restrict any user.
1. Q2GO's role and scope
1.1 This Policy applies to Q2GO LTD ("Q2GO"), a company incorporated in England and Wales, with company number 17332954 and registered office 128 City Road, London, United Kingdom, EC1V 2NX, operating the Q2GO platform across the United Kingdom and the EU/EEA.
1.2 Q2GO is an intermediary technology platform. The Host is the Merchant of Record and seller of the stay; Q2GO is not the seller of the stay, not the issuer of the stay invoice, and not the tax collector on the stay. Every booking records the Host as seller, invoicing party and party responsible for taxes on the stay.
1.3 Q2GO is not a party to the contract for the stay. The stay is a contract between the Guest and the Host. Q2GO facilitates discovery, booking, payment routing, messaging, and the trust-and-safety and dispute processes described here. Nothing in this Policy makes Q2GO a party to, guarantor of, or insurer of the stay.
1.4 This Policy is read together with, and does not override, the Terms of Service (the "ToS"), the Payment Terms (doc 04), the Cancellation & Refund Policy (doc 05), the Host Payout Policy (doc 06), the Content / Listing / Reviews Policy (doc 10), the Acceptable Use and Community Standards Policy (doc 11), the Compliance / Registration Policy (doc 13), and the Notice-and-Action and Copyright Policy (doc 18).
2. Definitions
2.1 Capitalised terms (Guest, Host, Booking, Payout, etc.) have the meaning given in the ToS dictionary (ToS §2). In addition, in this Policy:
2.2 "Dispute" means a complaint or contested matter between a Guest and a Host, or a payment dispute/chargeback raised through the payment provider.
2.3 "Chargeback" means a payment dispute initiated by a cardholder with their bank or card scheme and notified to Q2GO by the payment provider.
2.4 "Payout hold" means a state in which the Host's payout for a booking is frozen and will not be released until the underlying condition is resolved.
2.5 "Transfer reversal" means the clawing-back of funds previously transferred to a Host's connected balance.
3. How a Guest–Host dispute is handled
3.1 Q2GO is not an arbiter of the underlying stay contract. Because the stay contract is between Guest and Host (§1.3), a dispute about the stay itself (e.g., property condition, services, conduct) is, as a matter of substantive contract, between Guest and Host, subject to applicable consumer-protection and other law.
3.2 What Q2GO does provide. Q2GO provides: (a) support channels through which either party may raise a complaint (see doc 16); (b) the cancellation and refund mechanics defined by the booking's locked cancellation-policy snapshot (doc 05); (c) the controlled refund path (§6); (d) payout holds where warranted (§5); and (e) the records and audit trail that document what occurred.
3.3 No guarantee of outcome. Q2GO facilitates resolution but does not guarantee any particular outcome, refund, or payout beyond what the applicable policies, the booking's locked snapshot, and law provide.
3.4 Cooperation and evidence. Guests and Hosts agree to cooperate reasonably and to provide relevant evidence (e.g., messages, photos, receipts) to support the review of a complaint, dispute, or chargeback. Evidence due-dates set by the payment provider are recorded where applicable (§4.4).
4. Payment disputes and chargebacks
4.1 Trigger. When the payment provider notifies Q2GO that a payment dispute has been opened, Q2GO records the dispute and freezes the related Host payout.
4.2 Payout freeze. On a dispute the Host payout for that booking is frozen and the hold is recorded. A payout is not released while a refund, hold, or dispute is open against the booking.
4.3 Dispute record. Q2GO keeps a record of each dispute, its status, the deadlines, the evidence and every action taken (Host / Supplier Terms §8.5).
4.4 Evidence window. The dispute record stores the evidence due-date supplied by the payment provider; the outcome of the dispute follows the payment provider's and card scheme's process, which Q2GO does not control and whose result Q2GO does not guarantee.
4.5 Transfer reversal. The Host's share was transferred to the Host at the moment of payment. To recover it, Q2GO may reverse that transfer — temporarily while the dispute is open, or finally when it is lost (Host / Supplier Terms §8.5A–8.5B). A reversal after payout can leave the Host with a negative balance (§6.5).
4.6 Who pays a dispute. The payment provider debits the disputed amount and its dispute fee from Q2GO's platform account when the dispute is opened. The Host bears its share and the dispute fee on a lost or accepted dispute, unless Q2GO caused the loss (Host / Supplier Terms §8.5B); Q2GO recovers them from the Host's balance and future payouts. Where an amount cannot be recovered from the Host, Q2GO may bear it towards the payment provider.
5. Payout holds during trust-and-safety review
5.1 Grounds for a hold. A Host payout for a booking may be held where the booking is not yet eligible for release or where a blocking condition exists. Payout releases only when, among other conditions, the payout has not already been released, the payment status is payable, there is no open refund, hold, or dispute, a connected account is present, the scheduled release time has passed, and check-in has started.
5.2 Examples of blocking conditions. These include an open payment dispute/chargeback (§4), a pending or executed refund (§6), or a Host payment account that is not ready (payments or payouts disabled, or information overdue).
5.3 Stated reason. Where Q2GO applies an administrative hold beyond the automatic conditions above, a stated reason is recorded.
5.4 Relationship to payout timing. General payout timing (no escrow; payout from 15:00 property time on the day after check-in) is governed by the Host Payout Policy (doc 06) and the Stripe Connect / No-Escrow Policy (doc 15); this Policy addresses only holds arising from trust-and-safety and dispute conditions.
6. Refunds, admin refunds, and the single refund path
6.1 One controlled path. All refunds run through a single, audited refund process.
6.2 Who pays a refund. The payment provider debits the refund to Q2GO's platform account; Q2GO recovers the Host's share by reversing the transfer from the Host's connected balance, and returns the corresponding part of its own Service Fee (Service Fee Policy §4). Each refund is made once, even if a request is repeated.
6.3 Before the charge. Where the amount is only held on the card (not yet charged), cancelling releases the hold and no money moves.
6.4 Admin / goodwill refunds. An administrator may issue a refund only with a classified reason (guest support, host fault, duplicate charge, fraud, legal, goodwill, or technical error); it uses the same refund process and is recorded in an immutable audit trail.
6.5 Refund after payout (negative balance). If a Host payout has already been released, a refund is still issued via transfer reversal, which may put the Host into a negative balance; such cases are flagged for administrator attention. Hosts acknowledge that a late refund or reversal can result in them owing funds.
6.6 No manual money movement outside these processes. Q2GO does not move booking money manually outside the refund, payout, and dispute mechanisms described in this Policy and in docs 04–06.
7. Damage, security deposits, and property protection
7.1 No security deposit. Q2GO does not take or hold security deposits (Payment Rail Disclosure, doc 15).
7.2 Damage matters. Q2GO does not currently offer a damage or security-deposit claim process. Damage matters are between Guest and Host, subject to applicable law.
8. Content moderation, reviews, and illegal-content reporting
8.1 Reviews — eligibility and moderation. Reviews are Guest-only, require a completed booking whose review window is open, are limited to one per booking, carry a 1–5 rating and a 10–1,500-character comment, and are held in a double-blind window (~14 days) before publication.
8.2 Spam / contact-sharing flagging. A review matching a spam pattern (e.g., phone number, WhatsApp reference, or URL) is flagged, kept hidden and sent for human review. Review content and publication rules are detailed in the Content / Listing / Reviews Policy (doc 10).
8.3 Illegal-content notice-and-action (DSA). Anyone — with or without an account — may report content they believe is illegal through Q2GO's DSA Article 16 notice-and-action channel, which issues a case number and returns an administrator decision (removed, kept or restricted) with a written Statement of Reasons. The full process, copyright/DMCA route, and appeal information are set out in the Notice-and-Action and Copyright Policy (doc 18), which this Policy cross-references and does not duplicate.
8.4 Q2GO-initiated moderation. Independently of the notice channel, Q2GO may on its own initiative moderate, label, restrict, unpublish, or remove content and listings, and may set a compliance status on a listing. See docs 10, 11, and 18.
9. Account suspension, restriction, and termination
9.1 Grounds. Q2GO may suspend, restrict, downgrade, or terminate an account or listing for, among other grounds: breach of the ToS or any incorporated policy; fraud, abuse, or trust-and-safety concerns; compliance or legal requirements (doc 13); or failure to complete identity/KYC verification.
9.2 *(Deleted — Q2GO's Service Fee is withheld from booking payments and cannot be unpaid.)*
9.3 *(Deleted — there is no Host subscription that can lapse.)*
9.4 Effect on open bookings. Q2GO will not, solely on a compliance or trust-and-safety restriction, delete listings or auto-cancel existing confirmed bookings, except where required by law or by the safety of users; existing bookings are handled under the cancellation and refund mechanics (doc 05).
9.5 Stated reason and record. Where Q2GO takes an enforcement action, a reason is recorded in the relevant log/audit trail.
10. Automated decision-making and risk scoring — current status
10.1 No automated risk decisions today. Q2GO does not make solely-automated trust-and-safety decisions with legal or similarly significant effects. If that changes, this Policy will be updated first.
10.2 Recommendations only. If an automated risk tool is introduced, it will make no irreversible decision: it will only recommend an action (allow, hold for compliance, admin review, or block), a person will decide, and AI systems will not be used to approve or reject hosts or listings. No such tool is live today.
10.3 If activated. Before any automated decision producing legal or similarly significant effects is made live, Q2GO will provide the disclosures and human-review rights required by applicable law (e.g., UK GDPR / GDPR Art. 22) and update this Policy and the Privacy Policy (doc 08 §6).
10.4 AI-assisted support and search. Some support, search, and concierge features are AI-assisted (OpenAI); these assist rather than make binding trust-and-safety decisions, and human escalation is available (docs 08 §6, 16).
11. Support escalation for money and safety issues
11.1 Money-related and safety issues — payment failure, refund, dispute/chargeback, and urgent safety concerns — can be escalated to human support through the channels in the Support & Communications Policy (doc 16). Q2GO does not move money outside the controlled processes in §6 and docs 04–06.
12. Records, audit, and retention
12.1 Disputes, refunds, admin actions, and enforcement decisions are recorded in immutable ledgers/audit trails. Retention periods and legal bases are governed by the Privacy Policy (doc 08 §12) and the retention schedule, including support threads (~6 years) and audit logs (~5 years).
13. Changes to this Policy
13.1 Q2GO may update this Policy. Material changes will be reflected in the version note and effective date above and in the "what changed" note at the version archive in the Q2GO Legal Centre at q2go.net/legal, and surfaced as required by law.
14. Governing law and disputes
14.1 This Policy is governed by the laws of England and Wales, and is read together with the ToS. Governing law and venue for disputes are as stated in the ToS (§20), including the courts of England and Wales; the limitation of liability is in ToS §15. Out-of-court dispute-settlement and judicial remedies available under the DSA and local law are not limited by this Policy.
15. Contact
15.1 Trust-and-safety contact: support@q2go.net. To report illegal content, use the in-product "Report illegal content" channel (doc 18). General support: support@q2go.net. Q2GO LTD, with company number 17332954 and registered office 128 City Road, London, United Kingdom, EC1V 2NX

