The quote form collects only what a specialist needs to price a route with an airline or consolidator: airports, dates, passenger count, cabin, postal code, phone and email. We do not collect payment card numbers on this website.
Who is responsible
Controller: Travelobuds, 999 Lawrence Street, Suite 6, Brentwood, NY 11717, USA. Privacy contact: support@travelobuds.com. Phone: +1 (888) 764-9585.
Data we collect
- Quote data: departure and arrival airports, dates, trip type, passenger count, cabin preference, postal/ZIP code, phone, email, and later details you send (legal names, dates of birth, frequent-flyer numbers, special-service requests, meal codes).
- Chat and call-back messages: name, email or phone, destination if provided, the message, time, and IP used for spam control.
- Technical data: IP address, time of submission, browser user-agent if our host logs it, and a cookie that records you accepted this notice.
- Ticketing data (only if you accept a quote): passport-style names and whatever the validating airline requires to issue, stored as part of the PNR with that airline.
We do not require an account. We do not scrape your contacts. We do not run credit checks from the website form.
Why we use it
- To send fare options and to talk to you about the itinerary (steps toward a contract).
- To pass required passenger data to the validating airline, GDS, or consolidator so they can price or issue under that airline’s rules (necessary to perform the ticketing you requested).
- To prevent spam and abuse of the form (legitimate interests).
- To meet bookkeeping, chargeback, and airline ADM records if you ticket through us (legal obligation where it applies, including tax retention).
Who we share it with
- Email hosting and the Hostinger account that receives site mail.
- The validating airline, operating carrier, GDS, and licensed consolidators — only the fields those systems require to quote or ticket the itinerary you asked us to pursue. Their privacy notices and the airline’s contract of carriage then also apply to data inside the PNR.
- Regulators, insurers, or courts if required by law (including U.S. Secure Flight / similar government watchlist programmes when a ticket is issued).
We do not sell personal data. We do not send your route to unrelated call centres. If that model ever changes, this policy will change first.
How long we keep it
Unquoted or abandoned requests are typically deleted or anonymised within 24 months unless a longer period is required for a complaint or law. Ticketed bookings follow airline and tax record periods — often up to seven years. PNRs also live on the airline’s system for the retention the carrier sets. Hostinger server logs follow that host’s cycle.
International transfers
International itineraries require passenger data to move to the airline’s country of operation. Where GDPR or UK GDPR applies, we rely on an adequacy decision, standard contractual clauses with the processor, or the transfer being necessary to quote or ticket the international trip you requested.
Your rights
Subject to local law you may ask for access, correction, deletion, restriction, objection, or portability, and you may withdraw consent for future marketing (we do not run a separate marketing list from the quote form today). Use support@travelobuds.com.
California residents may have CCPA/CPRA rights of access, deletion, and to opt out of “sale” or “sharing” of personal information. We do not sell personal information as those statutes define sale. New York residents may have rights under the SHIELD Act regarding security of private information. EU/UK residents may complain to their supervisory authority (for example the ICO).
Once data sits in an airline PNR, some changes (legal name, date of birth) must go through that airline’s name-correction process. We cannot delete a ticket record the carrier is required to keep.
Children
The contact adult should submit the form. Passenger counts may include children. Unaccompanied-minor and infant rules are the operating airline’s, not ours.
Security
Leads are emailed to our domain mailbox and stored in a server file blocked from public web access. No transmission is perfectly secure. Do not put passport numbers or card data in the website form or chat widget. Send identity documents only on the secure channel named in a written quote.
Changes
Material changes will carry a new “last updated” date on this page.