website terms and conditions
Includes our website terms and conditions, statement regarding the security of this website, our privacy policy and disclaimer.

security statement

The lock icon at the bottom of your screen indicates when you are in a secure section of the Privileges website. The Privileges secure site uses a 128-bit Verisign Digital Certificate (Further information about this feature can be found at http://www.verisign.com). This ensures the confidentiality of your information, and is also used to help confirm that the server you are passing information to is Privilege's server. If any other Internet user intercepts the communication they will only be able to see it in an encrypted form.

When you connect to a secure web server, such as the online forms area of this website, you ask that server to authenticate itself. This authentication is quite a complex process involving public keys, private keys and a digital certificate. The certificate tells you that an independent third party has agreed that the server belongs to the company it claims to belong to.

Privileges uses secure socket layer (SSL) encryption for its forms that are transmitted using the Internet. SSL encrypts web communication, allowing us to protect sensitive personal information. SSL security makes eavesdropping on secure web traffic almost impossible.

Verisign SSL certificates are compatible with all recent browsers, including Microsoft Internet Explorer 5.01 (build 5.00.2920) and above and Netscape Netscape Navigator and Communicator 4.6 and above. If you are using a Macintosh operating system the certificate is compatible with Internet Explorer 5.2.2 and above. The Privileges website is compliant with Internet Explorer 6.0 and above, Firefox 2.0 and above and Netscape 7.0 and above.

Privileges do not recommend the use of older browsers for secure transactions.

A session is only valid for a certain period of time after your last activity with the server. If no activity is detected in the set time frame (for example 20 minutes), then your session is logged off and the 'session cookie' (login token) is no longer valid. Once your session expires, you will have to log on again to authenticate yourself for another session.

Last updated: Monday, 10 November 2008