 |
||||||||||||
|
||||||||||||
|
|
Data Security BookingBuilder Desktop reads information from your profiles, including travelers names, addresses and credit card numbers. It also reads confirmation details from supplier web sites, which include traveler names and itineraries. How does it keep this data secure? Data security is of the utmost importance to us. Our approach is very simple: No personally identifiable information is transmitted to our servers. We do not collect or store this data. Instead, let's say that you are completing a booking on JetBlue. BookingBuilder Desktop opens JetBlue's web site. When you reach the page that asks for traveler information, BookingBuilder Desktop reads the name, address and credit card from a GDS profile, and then fills in the web browser. All of this happens on your local computer; no information has been transmitted outside your computer at this point. When you then click the "submit" button on JetBlue's web site, the browser encrypts the data and sends it directly to JetBlue. BookingBuilder Desktop faciliates sending this information directly to the supplier web sites and does not send the data via our servers. When the browser sends this data to the various web sites, these sites typically use SSL, which is a long-established, secure method to transmit sensitive information. Since sensitive information is never transmitted to our servers, there are no new data security considerations imposed by BookingBuilder Desktop What Data is Transmitted? BookingBuilder Desktop does transmit certain information to our servers. It never transmits personally identiable information or credit card numbers. For support purposes, it sends some basic technical information about each computer: The version of Windows, the amount of RAM, which GDS is in use, the version of IE installed, which .NET Framework versions are installed, the version of BookingBuilder Desktop installed, whether Terminal Services is running, and the login name. This information helps us diagnose any problems and might come up, and gives us very valuable information to help guide future development. The login name is used to determine which settings apply to that computer, since you can assign separate settings to different login names. Build 59 and newer also send statistical data to our server. This includes which GDS availability commands matched city pairs flown by suppliers enabled in your installation, how many times the Notification dialog was clicked, how many times supplier sites were opened, how many times profiles were copied into the web sites, how many times confirmations were read, city pairs and fares from confirmations (no traveler information whatsoever, so no names or addresses are transmitted), and information regarding the use of Instant Fare Quote. None of the statistical data contains any personally indentifiable information or any credit cards. It does contain airline and city pair data, but no record locators or confirmation numbers. Without the record locators and confirmations, there is no way that the data can be associated with a particular traveler. This information is very valuable to us, since it shows us exactly how BookingBuilder Desktop is used and which features are used most often. Our development decisions are based in large part on this information, and it greatly contributes to constantly improving BookingBuilder Desktop. |
|
||||||||
Copyright ©2004-2007 LaunchMagic.com, Inc. All rights reserved. |
 |
|
||||||
BookingBuilder Technologies |