Data use
What passes through, and what we do with it.
A connectivity service owned by two marketplaces sees operators' availability and bookings. That is a conflict of interest worth naming rather than managing quietly, so this page sets out what flows through RezRoute, whose instructions it acts on, and what it commits to in place of a claim of independence it is not entitled to make.
Last updated 2026-08-28
Consent
Nothing is distributed unless you ask for it.
Being listed on a marketplace is not permission to sell your tours somewhere else. Connecting a sales channel is a separate decision, it belongs to you, and it is made per tour rather than once for your whole catalogue.
An operator who wants to keep selling only through the marketplace, or who already has a GetYourGuide account they run themselves, or who simply does not want their availability leaving the platform, keeps all of that unchanged by doing nothing. There is no default that opts you in, and no setting that quietly turns itself on when a new channel is added.
This is worth stating on a site that also owns the marketplaces, because the temptation runs the other way. The distribution right is yours to grant, one tour at a time, and to withdraw.
What flows through
What the connection needs, and nothing beyond it.
- Product and option identifiers
- So that a request from a sales channel can be matched to the right departure on the right calendar.
- Dates, times, seat counts and availability
- Carried in both directions: a channel asks what is free, and the marketplace that owns the product answers.
- Reservation, booking and cancellation references
- Including the identifiers a channel needs in order to cancel or amend what it has already sold.
- Prices and currency
- As held by the marketplace that owns the product. Prices are carried, not set.
- Traveller details sent with a booking
- A sales channel sends what its own specification requires in order to complete a booking, which typically includes the lead traveller's name, contact details and the composition of the party.
- Technical records of each call
- Which channel called, about which product, when, and whether the call succeeded. These records exist so that a failure can be explained to the operator it affected.
Nothing else passes through the connection. The service does not ask an operator for anything a call does not need, and it does not read anything else in the marketplace it routes to. Operator contact details, correspondence and billing records are held separately, for the reasons and for the periods set out in the privacy notice.
The exact field list differs between one channel and the next, because each channel specifies its own payloads.
Instructions
The service carries out other people's instructions.
Every call RezRoute handles begins somewhere else. A sales channel asks whether a seat is free, or asks to hold one, or asks to book it. The marketplace that owns the product answers from its own live calendar. RezRoute decides where the question goes, and nothing about the answer.
It does not decide what is sold, at what price, to whom, or on what terms. It does not create products, does not change availability of its own accord, and does not contact travellers.
In the language of the GDPR, RezRoute holds two roles at once, and collapsing them into one would misdescribe the service.
- A processor for traveller data. Personal data that passes through the router in the course of a booking is processed on documented instructions, for the purpose of operating the connection, and for no purpose the controller has not set. The instructions come from the marketplace that holds the product.
- A controller for operator data. Operator contact details, correspondence with us, and billing records where a fee applies are ours to decide about. For those we are the controller, and the privacy notice sets out the purpose, the legal basis and the retention period for each one.
The processor terms are on the data processing page. The providers involved are named on the sub-processors page.
Separation
One operator's data is never combined with another's.
Each request is answered for the product it names. There is no pooled view of what operators are selling, no ranking of who fills faster, and no report assembled out of many operators' numbers. Aggregates of that kind are not built, so they cannot be shared, sold, or quietly consulted before a commercial decision.
Data is not sold. It is not shared outside the sales channel that made the request and the marketplace that owns the product, except where the law requires it, or where a named infrastructure sub-processor necessarily handles it in order to run the service.
Traveller details are used to complete the booking they belong to. RezRoute does not market to travellers, does not build audiences out of booking data, and does not pass traveller details to anyone the booking does not require.
An operator can ask what has been recorded about their products, and can ask for it to be deleted when they disconnect.
The conflict of interest
We do not call this service independent, because it is not.
RezRoute routes for The Greek Local in Greece and Cyprus Bucket List in Cyprus, and it is owned by the company behind Cyprus Bucket List. A connectivity service in that position that described itself as independent or neutral would be making the easiest claim on this site to disprove.
So the word is not used. What replaces it is a set of commitments that are specific enough to be broken, which is the only kind worth publishing.
- 01
Availability and booking data is used to serve the connection. It is not used to inform commercial decisions on either marketplace, including pricing, product selection, promotion, or the creation of a competing product.
- 02
Routing is decided by which marketplace holds the product, and by nothing else. The same code path answers both, and neither marketplace is given priority in a response.
- 03
The service levels published on the reliability page apply to every product, whichever marketplace owns it. There is no faster tier for products the owning company earns more from.
- 04
One operator's data is never combined with another operator's data for a commercial purpose. No benchmarks, no league tables, no demand reports built out of what passes through.
- 05
The ownership relationship is disclosed wherever the question could arise, including in applications to sales channels and in the terms an operator signs.
If a commitment is broken
Where to take it.
An operator who believes their availability or booking data has been used for anything other than serving their connection is entitled to a direct answer about what was accessed, by whom, and why. The technical records described at the top of this page exist partly so that such a question can be answered rather than deflected.
If the answer is that a commitment on this page was broken, the honest course is to say so, fix it, and tell the operators it affected. That is the standard this page is written to.
For technical and partnership reviewers
The related pages.
Ask the awkward question before you connect, not after.
If something on this page is not specific enough to hold us to, say so, and we will make it specific or withdraw it.