Crowle Parish Hall and Recreation Trust

Cookies

​

What are Cookies?

​

Cookies are small text files that are saved to your computer. We use cookies to remember users during a visit, upon return to the site, and are required to enable certain functionality. In addition, cookies are used to help us understand how our customers use our websites and we use this information to help plan improvements to the site enabling us to get to know you better. For example, using persistent cookies allows us to recognise you when you return to the site, identify your preferences so as to provide you with a more personalised service and speed up searches that you conduct when visiting. We do not use cookies to collect or store personally identifiable information about you.

​

Below are details of how we currently use cookies, with details of how you can manage their use.

​

 

How to control the use of Cookies

​

If you wish to restrict or block the use of cookies on your computer when you visit our website, you can do this through your browser settings. The "Help" function within your browser should give details of how to manage cookies and how to delete cookies already on your computer.

​

Some functionality on our website may not work when viewed with your browser that has cookies disabled. In particular, you will not be able to complete product purchases or manage your account.

 

 

How we use Cookies

​

Both Crowle Parish Hall Trust and third parties make use of cookies when you visit websites. The following is a description of the types of cookie that we use, why they are used and details of the individual cookies.

​

​

Session Cookies

​

Session cookies are used by us to recognise a user throughout a visit. This enables us to remember information that you have entered such as the product you have selected during a purchase which can then be used at each stage of processing your purchase. Session cookies are also used to remember you when you log in for the duration of your visit.

​

• ForceFlashSite - When viewing a mobile site (old mobile under m.domain.com) it will force the server to display the non-mobile version and avoid redirecting to the mobile site

​​

• hs - Security

​​

• XSRF-TOKEN - Security

​​

• SSR-caching - Indicates how a site was rendered

​​

• TS* - Security

​​

• TS01******* - Security

​​

• TSxxxxxxxx (where x is replaced with a random series of numbers and letters) - Security

 

• TSxxxxxxxx_d (where x is replaced with a random series of numbers and letters) - Security

​

 

Persistent Cookies

​

Persistent cookies allow us to retain information and settings about a user for more than one session. These cookies stay on a computer or a device until they expire or a user removes them. They enable us to recognise a user when they return to our site, identify their preferences so as to provide a user with a more personalised service and speed up searches a user conducts when visiting the site. They allow us to tailor marketing and servicing messages to users based on what we know users have or haven’t done in previous sessions. We are able to optimise the website for a user’s return to the site knowing whether they have previously bought something or whether they may need support to complete a service transaction.

​

• smSession - Identifies logged in site members

​

• svSession - Identifies unique visitors and tracks a visitor’s sessions on a site

​

 

Website analytics Cookies

​

Website analytics cookies enable us to see how people use our website. This gives us the information to be able to make improvements, to make the site easier to use and based on the areas of the site people find most useful.

​

• _ga - Used to distinguish Users

​

• _gid - Used to distinguish Users

​

• __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.

​

• __utmt - Used to throttle request rate.

​

• __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.

​

• __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.

​

• __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.

​

​

​