We use a number of different cookies on our site. If you do not know what cookies are, or how to control or delete them, we recommend you visit http://www.aboutcookies.org for detailed guidance.
The list below describes the cookies we use on this site and what we use them for. Currently we operate an ‘implied consent’ policy which means that we assume you are happy with this usage. If you are not happy, then you should either not use this site, or you should delete the cookies having visited the site, or you should browse the site using your browser’s anonymous usage setting (called “Incognito” in Chrome, “InPrivate” for Internet Explorer, “Private Browsing” in Firefox and Safari, etc.).
We may use a cookie file containing information that can identify the computer you are working from. The cookie file is anonymous as it only gives us details of your IP address, Operating System (Windows, Linux or OS X), Browser (e.g. Internet Explorer, Google Chrome, or other, plus the version) and Domain (whether you are accessing the site from NZ or elsewhere). We may use the information generated by “cookies” to:
- Track traffic patterns to and from our sites such as the pages you visit, the time you spend on each page, the date and time of your visit, and referring pages (pages you came from or go to)
- To store information about your preferences, and so allow us to customise our site according to your individual interests; and
- enable you to use certain services as a member without having to log on each time and to visit member-restricted areas of the site.
These are cookies that are set by this website directly.
You can find out more about Google’s position on privacy as regards its analytics service at https://www.google.com.
content management system
LOGIN AND SECURITY
When sign in is required in our web-based sites and portals, a temporary authentication (session) cookie may be used, and users can make these persistent by checking the “remember me” checkbox on the login form.
The portal’s role cookie is persistent but it only exists for 1 minute — and its contents are encrypted as well as containing a portal ID to make sure that they only apply for that portal. We use the expiry here as we want to be sure to refresh the users portal roles to pick up any alterations that may have occurred, e.g. if an admin has added the user to new roles.