Javascript is currently disabled. This site requires Javascript to function correctly. Please enable Javascript in your browser!

Cookies Policy

Pennine Trout Farm & Fishery. Cookies Policy.

Our Cookie Policy.

About Cookies.

This document was created using a Contractology template available at http://www.freenetlaw.com.

This website uses cookies. By using this website and agreeing to this policy, you consent to http://www.penninetroutfarmandfishery.co.uk use of cookies in accordance with the terms of this policy. Cookies are files sent by web servers to web browsers, and stored by the web browsers. The information is then sent back to the server each time the browser requests a page from the server. This enables a web server to identify and track web browsers. There are two main kinds of cookies: session cookies and persistent cookies.  Session cookies are deleted from your computer when you close your browser, whereas persistent cookies remain stored on your computer until deleted, or until they reach their expiry date

Refusing Cookies.

Most browsers allow you to refuse to accept cookies.  
In Internet Explorer, you can refuse all cookies by clicking “Tools”, “Internet Options”, “Privacy”, and selecting “Block all cookies” using the sliding selector.  In Firefox, you can adjust your cookies settings by clicking “Tools”, “Options” and “Privacy”. For further information on refusing cookies please refer to:-

PC or Mac Browsers.

  1. Chrome.
  2. Firefox.
  3. Internet Explorer.
  4. Safari OSX.
Blocking cookies will have a negative impact upon the usability of some websites.

Cookies On Our Site.

http://www.penninetroutfarmandfishery.co.uk uses the following cookies on this website, for the following purposes:
  1. A cookie with the name .ASPXANONYMOUS" is created by asp.net anonymous authentication(http://msdn.microsoft.com/en-us/library/91ka2e6a.aspx ).
  2. Language  - Used to record the default language for the website if it cannot be identified from your browser. In this case it is set to English.
  3. Authentication - This cookie is used as part of the ASP.Net forms authentication.
  4. DOTNETNUKE, dnn* - These cookies are used by DotNetNuke and the ASP.NET forms authentication and form state. (http://helpful.knobs-dials.com/index.php/Utma,_utmb,_utmz_cookies). If cookie DOTNETNUKE is blocked we will not recognise you have logged in.
  5. Portalroles - The portals role cookie is persistent but it only exists for 1 minute - and it's contents are encrypted as well as containing a portalid to make sure that they only apply for that portal. We use the expiry here as we want to be sure to refresh the users portal roles to pick up any alterations that may have occurred e.g. if an admin has added the user to new roles. There is no way to disable this cookie in the current release of the CMS software.
  6. Utma, _utmb, _utmc,  _utmz cookies - These cookies are used to collect information about how visitors use our site. 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. (http://helpful.knobs-dials.com/index.php/Utma,_utmb,_utmz_cookies)
  7. Nid,Pref -Google tracking and safe browsing cookies. Google’s NID and PREF cookies are set by browsers to protect users against known intrusive sites. If you arrive at one of these sites it allows your browser to take action or notify you. Users can stop these cookies being set by turning off their browser’s ‘safe browsing’ mode. (http://www.google.com/intl/en_uk/policies/privacy/).
  8. analytics.js - The analytics.js JavaScript library is party of Universal Analytics and uses a single first-party cookie containing an anonymous identifier used to distinguish users. By default, this library sets cookies on the top level domain, excluding the leading dot, and sets the cookie path to the root level (/).
  9. ga.js - The ga.js JavaScript library uses first-party cookies to:
    1. Determine which domain to measure.
    2. Distinguish unique users.
    3. Remember the number and time of previous visits.
    4. Remember traffic source information.
    5. Determine the start and end of a session.
    6. Remember the value of visitor-level custom variables.
Asset 1