Cookie Policy

Website visitors


Borthcat is designed to allow users to browse and search for the holdings of archives, libraries and museums. Public users are not asked to log in and are not asked for any personally identifying information.


Borthcat collects cookies to enable browsing and loading of certain types of content. A cookie is a string of information that a website stores on a visitor’s computer, and that the visitor’s browser provides to the website each time the visitor returns. Visitors to Borthcat who do not wish to have cookies placed on their computers should set their browsers to refuse cookies. However, certain features (such as the Clipboard) may not function properly without the aid of cookies.


Borthcat supports integration with Google Analytics (https://www.google.com/analytics/) for the purposes of gathering statistics on page views, site usage, user location, and other data on site visits. All data collected by Google Analytics are stored and processed by Google, according to the Google Ads Data Processing Terms (https://privacy.google.com/businesses/processorterms/).


None of the information gathered through the use of cookies or Google Analytics is used for any purpose other than those described above.


Logged-in users


Users who log in have user accounts with usernames and passwords. These data are collected solely for the purpose of enabling users to log in to the software and are not disclosed to third parties. All Borthcat user passwords are stored in encrypted form to enhance data security.


Use of cookies on Borthcat


Cookies are small text files that are placed on your computer by websites that you visit. They are widely used in order to make websites work, or work more efficiently, as well as to provide information to the owners of the site. The information below lists the cookies used on Borthcat and provides an explanation of their purposes.


__utma
Used to distinguish users and sessions. The cookie is created when the javascript library executes and no existing __utma cookies exists. The cookie is updated every time data is sent to Google Analytics.

__utmb
Used to determine new sessions/visits. The cookie is created when the javascript library executes and no existing __utmb cookies exists. The cookie is updated every time data is sent to Google Analytics.

__utmc
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.

__utmt
Used to throttle request rate.

__utmv
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.

__utmz
Stores the traffic source or campaign that explains how the user reached your site. The cookie is created when the javascript library executes and is updated every time data is sent to Google Analytics.

has_js
Most commonly associated with the Drupal content management system. Drupal uses this cookie to indicate whether or not the visitors browser has JavaScript enabled.

symfony
Cookie associated with the Symfony framework for developing PHP applications. Exact purpose is unclear but as it is usually a session cookie, can be treated as necessary.


Most web browsers allow some control of most cookies through the browser settings. To find out more about cookies, including how to see what cookies have been set, visit www.aboutcookies.org or www.allaboutcookies.org

Find out how to manage cookies on popular browsers:

Google Chrome
Microsoft Edge
Mozilla Firefox
Microsoft Internet Explorer
Opera
Apple Safari

To find information relating to other browsers, visit the browser developer's website.

To opt out of being tracked by Google Analytics across all websites, visit http://tools.google.com/dlpage/gaoptout