The short version
This summary is for convenience only and does not replace the full Policy below.
- Who we are. Q2GO LTD, a company incorporated in England and Wales, is the controller of your personal data. You can reach our privacy team at privacy@q2go.net.
- What we collect and why. We collect the data we need to run the marketplace — your account and contact details, your bookings and messages, Guest and Host identity information when verification is required, Host tax information, and basic device and usage data — to operate Bookings, take and route payments, provide support, keep the marketplace safe, and meet our legal obligations.
- We do not store your card. Booking payments are handled by our payment providers. Q2GO does not store full card numbers or security codes.
- We share data with named partners. We use a short list of sub-processors — including our card payment provider, Twilio, Resend, Google/Firebase, and OpenAI — each named in Section 10, each for a stated purpose. PayPal is not used today (Section 4.3).
- We report host earnings to tax authorities. Where the law requires it, we report Host earnings to EU tax authorities under the DAC7 rules, and we keep tax and financial records for several years.
- You have rights. You can access and export your data, ask us to correct or delete it, and exercise the other rights in Section 14. Deletion starts a 30-day window but is held while you have open bookings, funds, or disputes; some records survive in anonymised form because the law requires it.
- Automated verification and human review. Qualifying low-risk cases may be approved automatically; other cases are escalated to human review (Section 6).
1. Who we are and what this Policy covers
1.1 This Privacy Policy ("Policy") explains how Q2GO LTD ("Q2GO", "we", "us", or "our") collects, uses, shares, and protects personal data when you use the Q2GO website, mobile applications, and related services (together, the "Platform"). Q2GO LTD is a private limited company incorporated in England and Wales; our company number is 17332954 and our registered office is 128 City Road, London, United Kingdom, EC1V 2NX.
1.2 Q2GO is the data controller for the personal data described in this Policy. This Policy applies to Guests, Hosts/Suppliers, and visitors to the Platform.
1.3 The Platform is offered to users in the United Kingdom and the European Economic Area (EU/EEA). This Policy forms part of, and is incorporated by reference into, the Terms of Service, and it works together with the Cookie Policy.
1.4 Capitalised terms used but not defined in this Policy — such as Guest, Host, Supplier, Booking, Listing, and Service Fee — have the meaning given to them in the Terms of Service (Section 2). In addition, in this Policy:
- "Personal data" means any information relating to an identified or identifiable individual.
- "Processing" means any operation performed on personal data, such as collecting, storing, using, sharing, or deleting it.
- "Sub-processor" means a third party that processes personal data on Q2GO's behalf and under our instructions (see Section 10).
2. The categories of personal data we collect
2.1 We collect the following categories of personal data, depending on how you use the Platform.
| Category | Examples | Mainly relates to |
|---|---|---|
| Account and contact data | Name, email address, phone number, profile photo, short bio, country, language preference, and login credentials | Guests and Hosts |
| Booking data | Bookings you make or receive, dates, guest details, prices, the cancellation policy recorded with the Booking, and the status of each Booking | Guests and Hosts |
| Messages and support data | Pre-booking inquiries, in-app messages between Guests and Hosts, support conversations and tickets, and the content of those communications | Guests and Hosts |
| Host identity and verification data | Identity documents (such as a passport, ID card, driving licence, a selfie, or proof of address) submitted during host onboarding, stored under access control and reviewed by authorised staff | Hosts/Suppliers |
| Guest identity and verification data | Legal name, date of birth, identity-document images and extracted document fields, a selfie, document-validity and name/date-of-birth matching results, verification status, and fraud or risk indicators when verification is required before a Booking can proceed | Guests |
| Host tax and business data | Legal type, tax residence country, tax identification number (TIN), VAT registration and number, date of birth, billing address, and any short-term-rental or hotel registration numbers | Hosts/Suppliers |
| Payout and payment-account data | Identifiers for the payout/connected account a Host holds with our payment provider, and limited payment metadata such as status, amounts, and transaction identifiers | Hosts and Guests |
| Listing and calendar data | Listing content you publish, availability, and external calendar (iCal) and property-management-system data you choose to connect | Hosts/Suppliers |
| Reviews and content | Reviews, ratings, and other Content you submit | Guests and Hosts |
| Device and usage data | Device information, log data, and cookie and similar-technology data as described in the Cookie Policy | All users |
2.2 What we do not store. Q2GO does not store full payment card numbers or card security codes (CVV). Card data is handled by our payment provider's secure infrastructure (see Section 4).
2.3 Children. The Platform is not directed to children, and you must be at least 18 years old to use it (see Section 13). We do not knowingly collect personal data from anyone under 18.
3. The purposes and legal bases for which we process your data
3.1 We process personal data only where we have a lawful basis to do so. The table below sets out, for each main purpose, the legal basis we rely on under the UK GDPR and the EU GDPR.
| Purpose | Examples | Legal basis |
|---|---|---|
| Provide your account and the Platform | Creating and maintaining your account, authenticating you, and making the Platform's features available | Performance of a contract |
| Operate Bookings | Creating, confirming, advancing, and cancelling Bookings, and recording the cancellation policy with each Booking | Performance of a contract |
| Take and route payments | Processing booking payments through our payment providers to the Host, processing refunds, and billing the Host's Service Fee | Performance of a contract; legal obligation (accounting) |
| Transactional communications | Booking confirmations, payment and billing notices, phone verification, data-export and account-deletion notices, review invitations, and a post-payment support/welcome message | Performance of a contract; legal obligation |
| Marketing communications | Optional newsletters and promotional messages where you have chosen to receive them | Consent |
| Support and concierge | Answering your questions and providing in-app, email, SMS, and WhatsApp support, including AI-assisted support (see Section 6) | Performance of a contract; legitimate interests in providing efficient support |
| Host identity verification and onboarding | Reviewing identity documents and "know your customer" data, and verifying registrations | Legal obligation; performance of a contract |
| Guest identity verification | Requiring and reviewing identity evidence before a Booking in risk-based or otherwise configured cases; checking document structure and validity signals; comparing extracted name and date-of-birth information; and preventing impersonation and fraud | Legitimate interests in marketplace safety and fraud prevention; performance of a contract |
| Trust, safety, and fraud prevention | Protecting the marketplace and our users, preventing fraud and abuse, and keeping audit and security records | Legitimate interests in a safe marketplace; legal obligation |
| Tax, accounting, and regulatory reporting | DAC7 reporting of Host earnings, VAT handling, short-term-rental activity reporting, and financial record-keeping | Legal obligation |
| Improve the Platform | Understanding how the Platform is used and improving its features and reliability | Legitimate interests in maintaining and improving our service |
| Cookies and similar technologies | Strictly necessary technologies to run and secure the Platform; optional analytics, functional, and advertising technologies | Legitimate interests (strictly necessary); consent (optional categories) |
| Comply with legal requests and protect rights | Responding to lawful requests, enforcing our Terms, and establishing, exercising, or defending legal claims | Legal obligation; legitimate interests |
3.2 Where we rely on legitimate interests, we have balanced those interests against your rights and freedoms; you can ask us for more information about that balancing, and you can object as described in Section 14.
3.3 Where we rely on consent (for example, for marketing or for optional cookies), you can withdraw it at any time without affecting processing that took place before you withdrew it.
4. Payments and payment-provider roles
4.1 Booking payments are processed by our third-party payment providers under their own terms. Q2GO is a marketplace intermediary: the Host is the seller and Merchant of Record for the stay, and card payments are processed as destination charges in which the Host's share is transferred to the Host at the moment of payment (Payment Rail Disclosure). Q2GO does not store full card numbers or security codes.
4.2 Card payment provider. Our card payment provider processes card payments and, for Hosts, runs the connected-account and identity/"know your customer" checks that allow a Host to receive booking funds. In doing so, that provider acts as an independent controller of the payment and verification data it handles under its own terms, and also processes certain data on our behalf. Q2GO receives only limited payment metadata (such as status, amounts, and identifiers).
4.3 PayPal — possible future payment method. PayPal is not a payment method on the Platform today, and Q2GO does not share data with PayPal. Q2GO may offer PayPal in the future; before it does, Q2GO will update this Policy to describe the data PayPal processes and its role.
4.4 In all cases, the payment provider's own privacy notice governs how it processes data as a controller. We name our payment providers in the sub-processor table in Section 10.
5. Communications: transactional versus marketing
5.1 Transactional messages. We send transactional messages — for example, booking confirmations, payment and billing notices, phone verification, data-export and account-deletion notices, review invitations, and a post-payment support/welcome message — by email, SMS, or WhatsApp (WhatsApp and SMS are delivered through Twilio). These messages are necessary to operate your Booking and account; we send them on the basis of performance of our contract with you and, where applicable, our legal obligations. They are not marketing.
5.2 Marketing messages. Marketing communications are separate and preference-based. We send them only where you have chosen to receive them, on the basis of your consent, and you can opt out at any time through your preferences or by using the unsubscribe option in the message.
5.3 In-app and support messaging. We process the messages you exchange through the Platform — including pre-booking inquiries, Guest–Host messages, and support conversations — to deliver the service, keep records, and resolve disputes.
6. AI-assisted support, search, and concierge
6.1 Some features use AI to help us serve you — for example, AI-assisted support and concierge, and turning a free-text search into structured search filters. Where these features are used, the relevant inputs and outputs are processed by our AI provider (OpenAI) acting as our sub-processor, solely to provide the feature.
6.2 AI-assisted features do not remove access to human support or escalation. Generative query and content assistance is distinct from the deterministic guest-verification approval policy described in Sections 6.3–6.4 and from listing-readiness workflows.
6.3 Automated verification and review. Qualifying low-risk guest identity submissions may be approved automatically when the required deterministic checks pass. Uncertain, incomplete, conflicting or higher-risk cases are referred to authorised human review. This guest verification flow does not automatically reject a person. Depending on the applicable law, jurisdiction and the nature and effect of a decision, you may have rights concerning automated decisions. Contact us to request human review, explain your position or challenge an outcome; the applicable legal safeguards are subject to jurisdiction-specific review.
6.4 Identity-document tools. Automated tools may extract document text and machine-readable-zone (MRZ) fields and check identity-name consistency, document expiry, technical integrity and risk indicators. Google Cloud Document AI may process the submitted document for this purpose. These tools may make or support approval decisions in qualifying cases; other cases are escalated to authorised reviewers. You may contact support to provide corrected evidence. This disclosure and the applicable legal safeguards remain subject to legal review.
7. Cookies and similar technologies
7.1 We use cookies and similar technologies as described in the Cookie Policy. Strictly necessary technologies, which are needed to run and secure the Platform and its payment flows, may operate without consent. Optional categories — functional, analytics/performance, and advertising/marketing technologies — are off by default and load only after you opt in. We honour the Global Privacy Control (GPC) signal, and no marketing or advertising cookies are active at launch unless they are deliberately added, inventoried, and consent-gated. You can change your choices at any time.
8. Listings, calendars, and connected integrations
8.1 If you are a Host, you can connect external calendars (by iCal URL) and supported property-management systems so that availability and reservations stay in sync. When you do, we fetch availability and reservation data from those sources and store the credentials you provide securely. The integrations we support, and the data involved, are limited to what is needed to keep your Listings and Bookings in sync.
9. Who we share data with
9.1 We share personal data only as needed to run the Platform, namely:
- with Hosts and Guests — as needed to make and complete a Booking (for example, a Host receives the booking details needed to host the Guest, and a Guest receives the information needed to complete the stay). A Host's phone number is not shared with Guests: Guests and Hosts communicate through the Platform's messaging;
- with our sub-processors — the third parties listed in Section 10, each acting under our instructions for the stated purpose;
- with payment providers — as described in Section 4;
- with authorities and regulators — where the law requires it, including tax reporting (Section 12) and responses to lawful requests; and
- in connection with a corporate transaction — such as a reorganisation, merger, or sale, subject to appropriate safeguards.
9.2 We do not sell your personal data.
10. Sub-processors and partners
10.1 We use the following sub-processors and partners, each for the stated purpose. We keep this list current and require each to protect personal data under a written data-processing agreement.
| Sub-processor / partner | Purpose | Role |
|---|---|---|
| Card payment provider | Card payments, connected accounts for Hosts, host identity/"know your customer" checks, tax calculation on our Service Fee, and payouts to Hosts | Processor for us, and independent controller for the payment/verification data it handles |
| PayPal | Not used today. Possible future payment method (Section 4.3); no data is shared with PayPal | — |
| Twilio | SMS and WhatsApp messaging, and phone verification | Processor |
| Resend | Sending Q2GO's e-mails (booking, payment and account messages) and reporting delivery and bounce events | Processor |
| Google Cloud / Firebase, including Document AI where identity verification is used | Hosting, database, file storage, authentication infrastructure, and extraction of identity-document fields and technical signals for qualifying automated approval or authorised human review | Processor |
| OpenAI | AI-assisted support, search, and concierge features | Processor |
10.2 Where a sub-processor acts as an independent controller for some of the data it handles (for example, a payment provider for its own payment and fraud-prevention purposes), that provider's own privacy notice governs that processing.
11. International transfers
11.1 Most of our processing takes place within the EU/EEA. Some processing — for example, certain identity-document handling and some sub-processor services — may involve transferring personal data outside the UK or the EU/EEA.
11.2 Where we transfer personal data internationally, we use appropriate safeguards required by UK and EU data-protection law, such as transfers to countries with an adequacy decision, or the use of Standard Contractual Clauses (and the UK International Data Transfer Addendum) together with any additional measures needed to protect your data. You can ask us for more information about the safeguards we use.
12. How long we keep your data (retention)
12.1 We keep personal data only as long as we need it for the purposes in this Policy and to meet our legal obligations. The main retention periods in our systems are set out below.
| Record type | Retention period | Primary legal basis |
|---|---|---|
| Bookings, financial ledger, financial documents, and Host tax profile | Approximately 7 years | Tax and accounting law; audit and compliance |
| DAC7 tax reports | Approximately 10 years | Tax-reporting legal obligation |
| Support conversations and tickets | Approximately 6 years | Dispute resolution; service records |
| Audit logs | Approximately 5 years | Audit and compliance; fraud prevention |
| Webhook deduplication records | Approximately 30 days | System integrity |
12.2 The legal bases we record for keeping data beyond an account deletion are tax and accounting, fraud prevention, dispute resolution, and audit and compliance.
12.3 We may also preserve data for longer under a legal hold where it is needed to comply with the law or to establish, exercise, or defend legal claims. When a retention period ends and no legal hold applies, we delete or anonymise the data.
13. Children
13.1 The Platform is intended for adults. You must be at least 18 years old to create an account or use the Platform, and it is not directed to children. If we learn that we have collected personal data from someone under 18, we will delete it.
14. Your rights and how to exercise them
14.1 Subject to applicable law, you have the right to:
- access the personal data we hold about you, and obtain a copy;
- rectify inaccurate or incomplete data;
- erase your data ("right to be forgotten"), subject to the retention exceptions in Section 12;
- restrict our processing in certain circumstances;
- port the data you provided to us, in a structured, commonly used, machine-readable format;
- object to processing based on our legitimate interests, and to object to direct marketing at any time; and
- withdraw consent at any time where we rely on it.
14.2 Data export (access and portability). On request, we generate a full export of your data as a machine-readable file together with a readable snapshot, stored securely and made available to you through a time-limited (7-day) download link sent to you by email. You can also use the in-product data tools where available.
14.3 Account deletion (erasure). When you request deletion, a 30-day window begins. Your public profile is hidden immediately, your name is anonymised to a "deleted user" label, and your phone number, photo, and marketing preferences are removed; your Listings are archived and your sessions are revoked.
14.4 Deletion is held while certain matters are open. We cannot complete a hard deletion while you have active bookings, open disputes, pending funds, or failed or unpaid invoices, and any payment-provider cleanup is also held while there is an open balance, dispute, or pending payout. Once those matters close, deletion proceeds.
14.5 What survives deletion, and why. Even after deletion, we keep — in minimised or anonymised form — the financial ledger, minimised booking records, tax records, and audit trail, under the legal bases in Section 12. Other personal fields are cleared, stored files are deleted, and the authentication account is removed. Historical content you contributed (such as reviews, messages, and booking history) persists in anonymised form: your name is replaced with a "deleted user" label and your email and phone are cleared, so other users can still see the history without your personal identifiers.
14.6 How to exercise your rights. Use the in-product data tools where available, or contact us at privacy@q2go.net. We will respond within the time the law allows (generally one month, which can be extended for complex requests, in which case we will tell you). We may need to verify your identity before acting on a request.
14.7 Right to complain. If you have a concern, please contact us first so we can try to resolve it. You also have the right to lodge a complaint with a supervisory authority. In the UK, that is the Information Commissioner's Office (ICO) (ico.org.uk). In the EU/EEA, you can complain to the data protection authority in your country of residence or work.
15. How we protect your data
15.1 We use technical and organisational measures to protect personal data against loss, misuse, and unauthorised access. Payment-card security is provided through our payment provider's infrastructure, and sensitive identity documents are stored under access control and reviewed only by authorised staff. Access to personal data is limited on a need-to-know basis, and we keep audit and security records.
15.2 Personal data breaches. No measures are perfect. If a personal data breach occurs that is likely to result in a risk to your rights and freedoms, we will notify the relevant supervisory authority and, where the law requires, affected individuals, in line with our legal obligations.
16. Our privacy contact, DPO, and representatives
16.1 You can contact us about this Policy or about your personal data at privacy@q2go.net, or in writing to our registered office (published in the Legal Centre). For legal notices, you may also use legal@q2go.net.
16.2 Where we are required to appoint, or have appointed, a Data Protection Officer or a UK or EU/EEA representative, their contact details are published in the Legal Centre alongside this Policy. You can always reach our privacy team using the contact above.
17. Changes to this Policy
17.1 We may update this Policy from time to time. Where we make a material change, we will give notice as required by law. The version number and effective date show the current version, and we keep prior versions and a short note of what changed in the version archive in the Legal Centre at q2go.net/legal.
18. Language
18.1 This Policy is published in English and in Hebrew. The English version is the controlling version; the Hebrew version is provided so that Hebrew-speaking users can understand the Policy, and in the event of any conflict the English version prevails.

