Collect for a clear reason
Reservation, identity, payment, messaging, and safety data should each have an understandable purpose.
Data stewardship
Privacy
Trust grows when privacy controls are plain-language and practical. Users should be able to tell what data supports booking, safety, fraud prevention, communications, and product improvement.
What to do now
Use the right next step before the issue gets harder to untangle.
Explain retention simply
Users want to know what stays on file for trust, support, tax, and legal needs and what can be changed or deleted.
Controls should be reachable
Communication preferences, saved payments, and privacy requests should not feel buried.
Three actions that keep the case clear.
- Review what account, booking, and payment information is currently saved to your profile.
- Adjust communication or marketing preferences before they become support issues later.
- Use the privacy-request path when you need access, correction, or deletion support.
Guided reading
Practical guidance for this topic.
Types of information a travel marketplace needs
Identity, payments, reservations, messaging, and support history each support different parts of the product.
Why some data is retained longer
Fraud prevention, tax compliance, and dispute resolution can require records beyond the trip itself.
What users should control directly
Marketing preferences, saved payment methods, and profile details should be editable without support friction.
We're here for you
Contact us
Support for reservations, account access, and hosting.
Log in to get help with your reservations, account, and more.