JavaScript is turned off in your web browser. To take full advantage of Ribose features, please enable JavaScript and refresh the page.

Ribose Use of Cookies

Last revised on: Nov 22, 2014

Introduction

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.

This page describes the cookies we use for our service and why.

Disabling cookies

You may set your browser to refuse cookies. However, some Services may not function properly if cookies are disabled.

More information

If you have questions about our use of cookies, please email privacy@ribose.com.

List of cookies and their usage

  • identifier:
    _indigo_session
    type:
    Session associated with Ribose Services
    duration:
    Deleted when the browser closes
    description:
    Stores a unique identifier for the session of each computer or device using Ribose. Does not track any personal information, and is required for Services to function correctly.
  • identifier:
    JSESSIONID
    type:
    Session associated with New Relic
    duration:
    Deleted when the browser closes
    description:
    The JSESSIONID cookie is used to store a session identifier such that New Relic can monitor session counts for an application.
  • identifier:
    PREF
    type:
    Preference cookie associated with Google
    duration:
    2 years
    description:
    The PREF cookie may store your Google preferences and other information, in particular your preferred language (e.g., English), how many search results you wish to have shown per page (e.g., 10 or 20), and whether or not you wish to have Google’s SafeSearch filter turned on.
  • identifier:
    NRAGENT
    type:
    Metrics associated with New Relic
    duration:
    Deleted when the browser closes
    description:
    This cookie is used to communicate between the New Relic server aggregating end user metrics and the agent(s) running in the associated web application. A token identifies and correlates application tier transaction traces with corresponding browser traces.

Get Started

Getting Started