Your travel preferences should stay under your control.
Prototype privacy page. Production handling of religious preference data requires appropriate UK GDPR design and legal review.
How preference data should be handled
Travel searches can include family details and faith-related preferences. Production systems need clear purpose, limited collection and appropriate UK data protection controls.
Only collect what is needed
Traveller ages, room requirements and preferences should be requested because they improve the search or booking, not simply because they might be useful later.
Explain the purpose
Customers should understand how search choices, saved holidays, enquiries and booking details are used before submitting them.
Control and retention
Production privacy information must explain access, correction, deletion, retention and any supplier or processor involved.
Sensitive preferences
Faith-related preferences require careful design and legal review. They should not be repurposed for unrelated profiling.
What customers need to know.
Clear answers belong on the page, before a customer is asked to contact anyone or continue towards payment.
Is this the final legal privacy notice?
No. This prototype explains the intended principles. A production notice must be completed against the actual systems, suppliers and legal basis.
Are search preferences the same as booking data?
Not necessarily. Production documentation should distinguish anonymous browsing, saved searches, enquiries and information required to make a booking.
Will preferences be sold?
The product direction does not support selling personal preference data. Final production terms must state the actual processing arrangements clearly.