Cookie Policy

What are 'cookies'?

'Cookies' are text files that are stored by the browser on your computer or mobile phone. They allow websites to store such things as user preferences. Cookies are useful because they allow a website to recognize a user's device and to make the site work better for you. They also help FOSI understand how people use the website.

What does FOSI use cookies for?

FOSI uses first party cookies for analytical purposes and third party cookies when embedded videos are played from YouTube.

FOSI uses 'analytics' cookies to help make our website better for those who visit it regularly. Analytics cookies help to establish what users like and do not like and as well as how we can improve user experience. Every time a user visits our website, web analytics software provided by a third party generates an anonymous analytics cookie. These cookies can tell us whether or not they have visited the site before. Their browser will tell us if they have these cookies, and if not, we generate new ones. This allows us to track how many individual unique users we have, and how often they visit the site.

FOSI embeds videos from our official YouTube channel using YouTube’s privacy-enhanced mode. This mode may set cookies on your computer once you click on the YouTube video player, but YouTube will not store personally-identifiable cookie information for playbacks of embedded videos using the privacy-enhanced mode. To find out more please visit YouTube’s embedding videos information page.

How do I turn cookies off?

Users can chose to restrict or block cookies set by us, or any other website. This will need to be done through your browser settings.

More information

For more information please see our Privacy Policy, or contact fosi@fosi.org

Cookies used on FOSI.org

Name Description Expiration
__utma This cookie is a Google Analytics cookie and is typically written to the browser upon the first visit to your site from that web browser. If the cookie has been deleted by the browser operator, and the browser subsequently visits your site, a new __utma cookie is written with a different unique ID. This cookie is used to determine unique visitors to our site and it is updated with each page view. Additionally, this cookie is provided with a unique ID that Google Analytics uses to ensure both the validity and accessibility of the cookie as an extra security measure. 2 years from set/update.
__utmb This cookie is a Google Analytics and is used to establish and continue a user session with our site. When a user views a page on the site, the Google Analytics code attempts to update this cookie. If it does not find the cookie, a new one is written and a new session is established. Each time a user visits a different page on your site, this cookie is updated to expire in 30 minutes, thus continuing a single session for as long as user activity continues within 30-minute intervals. This cookie expires when a user pauses on a page on our site for longer than 30 minutes. You can modify the default length of a user session with the _setSessionCookieTimeout() method. 30 minutes from set/update.
__utmc This Google Analytics  cookie is no longer used by the ga.js tracking code to determine session status. Historically, this cookie operated in conjunction with the __utmb cookie to determine whether or not to establish a new session for the user. For backwards compatibility purposes with sites still using the urchin.js tracking code, this cookie will continue to be written and will expire when the user exits the browser. However, if you are debugging site tracking and you use the ga.js tracking code, you should not interpret the existence of this cookie in relation to a new or expired session. Not set.
__utmz This Google Analytics  cookie stores the type of referral used by the visitor to reach a site, whether via a direct method, a referring link, a website search, or a campaign such as an ad or an email link. It is used to calculate search engine traffic, ad campaigns and page navigation within a site. The cookie is updated with each page view to the site. 6 months from set/update.
NREUM NREUM is a New Relic cookie. This cookie is only created in browsers that do not support the Navigation Timing API. When a browser supports the Navigation Timing API, a native interface can be used to determine navigation start time. Navigation start time is required to measure end user response time. The cookie is written when the current page unloads (as the next navigation begins).Firefox versions 7 or higher support the Navigation Timing API. However, a bug exists in Firefox's early implementations of the Navigation Timing API that New Relic Browser works around by using this cookie. When the browser is closed.
NRAGENT The NRAGENT cookie is a New Relic Cookie. This cookie is created only when a token is handed out to an end user by the New Relic server. End user metrics are communicated to New Relic servers via a JSONP request from the browser (script retrieval). The returned JavaScript contains a call to set the token identifier which is written to the cookie on the next navigation (when the page unloads). This achieves a cross-domain communication between New Relic servers and the New Relic agent. 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. When the browser is closed.
JSESSIONID The JSESSIONID cookie is a New Relic Cookie. The JSESSIONID cookie is used to store a session identifier so that New Relic can monitor session counts for an application. The cookie value is generated by Jetty. When the browser is closed.
Adobe Typekit This cookie collects information about the fonts and typography being served on our website. Adobe use cookies within Typekit to track usage statistics. The information is used for the purposes of billing and compliance, and may include the following:Fonts servedKit IDAccount ID (identifies the customer the kit is from)Service providing the fonts (e.g., Typekit or Edge Web Fonts)Application requesting the fonts (e.g., Adobe Muse)Server serving the fonts (e.g., Typekit servers or Enterprise CDN)Hostname of page loading the fontsThe amount of time it takes the web browser to download the fontsThe amount of time it takes from the web browser downloading the fonts until the fonts are applied When browser is closed.
Facebook Connect Facebook Connect, also called Log in with Facebook, like OpenID, is a set of authentication APIs from Facebook that developers can use to help their users connect and share with such users' Facebook friends (on and off Facebook) and increase engagement for their website or application.For more information, visit Facebook's Cookie Policy. When you log out of Facebook.