Data we collect
We do not collect personally identifiable details about you unless you choose to submit them – via a membership application, event registration, publications order or other form of contact. Where we do this, we collect the information we need for that process and use it for that purpose.
We use Google Analytics to look at how our website is used, based on aggregated visitor data. This analysis does not identify individual users, but lets us see trends such as popular content, visitor countries, browsers/devices used, etc. We can then use this data to help improve the website.
We also utilise Invisible reCAPTCHA by Google, which may track your behaviour on pages with submission forms. This is to detect automated behaviour in order to eliminate spam. We obtain no data from the reCAPTCHA process.
Our web site uses a technology known as cookies to store small amounts of data on our visitors’ computers or devices. Cookies are small pieces of text data that can be placed on a visitor’s computer, normally to provide enhanced functionality and/or improved relevancy of information.
First party cookies (our website creates these):
PHPSESSID – this stores certain settings during your visit (such as your logged-in status or whether withdrawn/expired material appears in publication listings). This cookie can only be used by this website and should be automatically deleted when you close your browser. You may block creation of this cookie, but should expect reduced website functionality.
Third party cookies (may be added by a service provider we use, subject to your browser settings):
|Cookie Name||Default Expiry||Description|
|__utmt||10 minutes||Used to throttle request rate.|
|__utmc||End of browser session||Not used in ga.js. Set for interoperability with urchin.js. Historically, this cookie operated in conjunction with the __utmb cookie to determine whether the user was in a new session/visit.|
|__utmv||2 years from set/update||Used to store visitor-level custom variable data. This cookie is created when a developer uses the _setCustomVar method with a visitor level custom variable. This cookie was also used for the deprecated _setVar method. The cookie is updated every time data is sent to Google Analytics.|