Voyanta
Information

Privacy Policy

A plain-language template describing how a travel platform may collect, use, secure and retain personal information.

1. SCOPE This privacy template applies to use of the Voyanta website, account area, enquiry forms and booking interfaces. Replace company placeholders and obtain qualified legal review before production launch. 2. INFORMATION WE MAY PROCESS Account details such as name, email, mobile number and password hash; traveller details entered for booking; booking and payment-status records; support enquiries; saved preferences; recent searches; technical logs and security information; and optional marketing subscription details. 3. PAYMENT DATA The static release uses a mock payment gateway and is not designed to store genuine card numbers. In production, payment credentials should be handled by an approved payment provider using hosted or tokenised methods. 4. WHY INFORMATION IS USED To operate accounts, create and manage bookings, provide support, prevent abuse, improve product experience, send transactional updates, honour deletion or privacy requests and meet legal or accounting obligations. 5. SHARING A production travel platform may need to share necessary booking information with airlines, hotels, ground transport providers, insurers, payment processors, technology vendors and authorities where legally required. Document actual recipients before launch. 6. RETENTION Keep personal information only as long as necessary for the purpose collected, except where tax, accounting, fraud prevention, dispute or other legal requirements require longer retention. 7. SECURITY Use access controls, encrypted transport, secure password hashing, restricted secrets, validated uploads, audit practices and vendor due diligence appropriate to the production system. 8. USER REQUESTS Users may use the dedicated Delete Account flow or configured support channels for access, correction or deletion requests, subject to applicable law. 9. CONTACT Privacy and grievance contact details are controlled through Admin Settings and should be replaced with the actual responsible person/entity before launch.