Draft information about personal information that may be processed when using Travelar.
Draft — legal review required
This policy is draft information, not an approved contract or legal advice. It is not ready for publication as a final policy. Travelar must confirm the applicable legal entity, markets, contact details, effective date, and jurisdiction-specific terms with qualified counsel before relying on or publishing it as final.
1. Who is responsible
This draft identifies HEWOD Destinations Limited as the operator of Travelar. The data controller, any joint controllers, applicable local entities, and verified privacy contact details must be confirmed for each relevant market before this policy is finalised.
2. Information that may be processed
Identity and contact details, passenger or guest details, and information needed for an account or booking.
Booking, itinerary, payment status, transaction reference, refund, and supplier-service information.
Customer-service communications, requests, and relevant records.
Device, browser, log, security, and usage information needed to operate and protect the platform.
Information provided by suppliers or service providers to fulfil, support, or reconcile a booking.
3. How information may be used
Information may be needed to search for and fulfil bookings, process and reconcile payments, communicate itinerary changes, provide support, secure the service, prevent fraud, keep business records, meet legal obligations, and establish or defend legal claims. Optional marketing or analytics processing must be verified and handled under the applicable consent and preference rules.
4. Sharing and international processing
Relevant information may be shared with the carrier, accommodation provider, payment provider, booking or technology partners, service providers, professional advisers, or authorities where necessary and lawful. Actual recipients, purposes, locations, safeguards, and transfer mechanisms must be confirmed before publication; this draft does not establish data-residency or transfer arrangements.
5. Retention and security
Information should be retained only as long as reasonably necessary for bookings, support, financial and operational records, legal requirements, security, and dispute handling. Retention periods and deletion schedules need verification. Appropriate security measures are intended to protect information, but no internet transmission or storage system can be guaranteed completely secure.
6. Rights and requests
Depending on applicable law, a person may have rights to access, correct, erase, restrict, object to, or transfer information, withdraw consent, object to marketing, or complain to a regulator. Rights, exceptions, response timelines, identity checks, and the competent supervisory authority must be confirmed for each market.
A verified privacy contact route has not yet been published. Do not send sensitive identity documents through an unofficial channel.
7. Marketing, cookies, children, and automated processing
Service messages are distinct from optional marketing. Marketing, non-essential cookies, analytics, advertising tools, children's information, and automated decisions must be described only after the actual deployed systems and applicable legal requirements have been verified.
8. Changes and publication status
The final policy must include an approved effective date, last-updated date, controller details, privacy contact, actual service-provider and transfer information, retention details, rights process, and jurisdiction-specific disclosures. This draft is not a substitute for those confirmations or qualified legal review.