Skip to content

Cookies

On our sites, we sometimes place small data files on your computer. These small files are known as 'cookies'.

They improve the performance of our sites by:

  • remembering information about you, so you don’t have to keep re-entering it whenever you visit a new page
  • recognising that you may already have given a username and password so you don't need to do it for every web page requested
  • remembering IP addresses relating to your computer or device to improve navigation of our sites and to control access to particular content or materials reserved to subscribers
  • measuring how you use the site so we can make sure it meets your needs

Our cookies aren’t used to identify you personally. To learn more about cookies and how to manage them, visit AboutCookies.org.

Royalsociety.org

This following section provides particular information about cookies on the following websites:

Content Management System

We may use a content management system which uses the cookies to deliver web pages and control access to protected areas of our sites.

The following cookies are set by the content management system on https://royalsociety.org:

Name Type 1st/3rd party Expiration
ASP.NET_SessionId Session 1st End of session

Measuring website usage (Google Analytics)

We use Google Analytics to collect information about how people use our sites. We do this to make sure it’s meeting its users’ needs and to understand how we could do it better. Google Analytics stores information about what pages you visit, how long you are on the site, how you got here and what you click on. This information cannot be used to identify you and we do not allow Google to use our analytics data. The following cookies are set by Google Analytics:

Name Type 1st/3rd party Expiration
_ga Persistent 1st 2 years

Youtube

We embed videos from Youtube. Youtube uses cookies to help maintain the integrity of video statistics, prevent fraud and improve their site experience. If you view a video, Youtube may also set additional cookies.

Qualaroo

We use Qualaroo to provide in-page surveys so that we can gather customer feedback and improve our site. Qualaroo uses cookies to ensure you don't see a survey you've completed multiple times.

AddThis

We use AddThis to provide convenient page sharing functionality. AddThis uses cookies to personalise its service.

Twitter

We embed feeds from Twitter to help users to access content on social media. Twitter uses cookies for authentication, preferences, analytics and to personalise content.

Facebook

We embed feeds from Facebook to help users to access content on social media. Facebook uses cookies for authentication, preferences, analytics and to personalise content.

Royalsocietypublishing.org

Cookie Name
Purpose
Type
Details
acceptsCookies/Access, cks Site Cookie Acceptance. These cookies are used to record if the end user's browser accepts the use of cookies session Strictly necessary for login and pay-per-view activities. Usually this will not be used unless the end user requests a service that makes use of cookies. Info held: text string 'true'.
foxycart, cme, personify For ecommerce solutions Site Cookie, defined time interval These cookies are required for control flow between Drupal and the e-commerce providers to reload cart, to make login attempts, to keep transaction session.
highwire_alerts_user_email For storing user email for alerts, if user is not logged in and wants to subscribe to alerts Site Cookie, defined time interval Will hold email address only.
hw-shib-return-uri Store return url for shibboleth request Site Specific, defined time internal This value is the url of the article that is requesting user to login via Shibboleth.
hw-shib-target Authentication. Redirects the end user back to their requested content after they have logged in via Shibboleth session Strictly necessary for the end user to be able to go to the page they want after a login to the journal via Shibboleth. Info held: the address the end user wants to access after login.
hw_uservoucher Authentication. Allows mobile device users to maintain access to their licenced content while off their institution's site persistent Strictly necessary to keep an end user's mobile device logged in. Must be requested by end user. Info held: registered institution and authorization information for the device
login, login-dev Authentication. Authenticates the end user session Strictly necessary for the end user to be able to login to the journal websites. Info held: authentication token.
pfaTrans Authentication. Stores transaction identifiers that allow us to identify what content an end-user has purchased persistent (3 day duration) Strictly necessary for an end user to purchase content, eg pay-per-view of an article. It is only populated when the end user purchases something. Info held: one or more transaction identifiers.
seat_id Authentication. Authenticates the end user via an institution with limited concurrent users This is not currently operational on our site Strictly necessary for an end user to login via an institution that wishes to limit the number of concurrent logins ('seats'). Info held: a seat id
sass-fsauthz Publisher Content Management Control. Authenticates the end user to access embargoed content session Strictly necessary for the end user to be able to login before content goes live. This is a maintenance cookie and not accessible on the public site. Info held: authentication token.
show_e_letter_form This cookie will be set for eletters functionality Site Cookie, defined time interval Used to show eletters form inline
_utma, _utmb, _utmc, _utmz Google Analytics. These cookies are used to collect information about how visitors use our site in general. persistent We use the information to compile reports and to help us improve the site. The cookies collect information in an anonymous form, including the number of visitors to the site, where visitors have come to the site from and the pages they visited. IP geolocation only goes down to the city level.