Jetsetter Information Security Policy
Smarter Travel Media LLC and its subsidiaries and affiliates, including JetSetter Inc., dba Jetsetter (collectively, “Jetsetter”), respect your concerns about information security. Jetsetter is committed to protecting the security of the information we collect and maintain about our most important asset - our customers.
How We Protect Information about our Customers
Information Security Tips for Protecting Yourself
On the Phone
When you call Jetsetter Customer Support, we may verify your identity by asking for information such as your current shipping address, order information or the last four digits or expiration date of the credit card we have on file for your account.
When you go to Login or Check Out pages on the Jetsetter websites, you will notice the closed lock icon at the top or bottom of your browser or the “HTTPS://” prefix in the URL. This means you have established a secure SSL connection and that all data transmitted through this connection will be encrypted. If you are receiving SSL Certificate errors when accessing the Jetsetter websites, that means that the domain name in the SSL certificate does not match the address that is in the address bar of the browser. Alternatively, it may mean that your browser is misconfigured and does not accept the root certificate used by Jetsetter. Please contact firstname.lastname@example.org if you encounter this error.
If you suspect that any account information has been compromised or fraudulent charges have been made on your Jetsetter account, please contact Customer Support immediately for assistance by contacting us through the website or calling 877-JSET-USA/877-573-8872.
Updates to this Information Security Policy
This Information Security Policy may be updated periodically and without prior notice to you to reflect changes in our information security practices. We will post a prominent notice on our websites to notify you of any significant changes to our Information Security Policy and indicate at the bottom of the policy when it was most recently updated.
Historical Modifications 5/18/2010: Initial version posted 1/14/2011: Modification to Security Policy 4/24/2013: Modification to Security Policy