Privacy is a very serious matter for Leavetown. We understand that booking online involves significant trust in us. We appreciate and value your trust and are committed to ensuring the security and confidentiality of your personal information.
Be cautious about using a public computer, as it may contain keylogger software designed to steal your login credentials. If you do decide to use a public computer to make a reservation on the Leavetown website, do not forget to sign out from the website when you have finished using the public computer.
When you call Leavetown, we may verify your identity by asking for information such as your current address, booking number 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 Leavetown 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 Leavetown website, 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 Leavetown. Please contact firstname.lastname@example.org if you encounter this error.
If you suspect that any of your personal information has been compromised or fraudulent charges have been made on your credit card as a result of your interaction with Leavetown, please contact us immediately for assistance by contacting us through the website or calling 1-877-902-1616.
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 website to notify you of any significant changes to our Security Protocols and indicate at the bottom of the policy when it was most recently updated.
These protocols are effective as of 1 March, 2014.