Cookie Policy
Cookies Policy
Last updated: 30/06/2020
Cookies Policy
Last updated: 30/06/2020
Cycling Scotland ("us", "we", or "our") uses cookies on www.cycling.scot (the "Service"). By using the Service, you consent to the use of cookies.
Our Cookies Policy explains what cookies are, how we use cookies, how third-parties we may partner with may use cookies on the Service, your choices regarding cookies and further information about cookies.
Cookies are small pieces of text sent by your web browser by a website you visit. A cookie file is stored in your web browser and allows the Service or a third-party to recognize you and make your next visit easier and the Service more useful to you.
Cookies can be "persistent" or "session" cookies.
When you use and access the Service, we may place a number of cookies files in your web browser.
We use cookies for the following purposes: to enable certain functions of the Service, to provide analytics, to store your preferences, to enable advertisements delivery, including behavioral advertising.
We use both session and persistent cookies on the Service and we use different types of cookies to run the Service:
- Essential cookies. We may use essential cookies to authenticate users and prevent fraudulent use of user accounts.
In addition to our own cookies, we may also use various third-parties cookies to report usage statistics of the Service, deliver advertisements on and through the Service, and so on.
Details of the third party cookies used by our website are set out below:
CloudFlare
The CloudFlare cookie that Cycling Scotland uses has the name of: __cfduid
It is set by the CloudFlare service to identify trusted web traffic. It does not correspond to any user id in the web application, and does not store any personally identifiable information. You can find out what this cookie does at: https://support.cloudflare.com/hc/en-us/articles/200170156-What-does-the-CloudFlare-cfduid-cookie-do-
Google Remarketing – DoubleClick
Cycling Scotland website uses Google’s remarketing technology (DoubleClick). This allows us to display relevant ads based on what pages on the Cycling Scotland website you have viewed. The advertising will be displayed using cookies. This cookie doesn't record any personal information or identify you personally.
If you would prefer to not receive any targeted advertising, you can deactivate the use of cookies for these purposes through Google by visiting https://www.google.com/settings/ads/.
Google has its own independent data protection policy which can be accessed at https://www.google.com/intl/en/policies/privacy/.
Facebook Conversion Tracking Pixel
Cycling Scotland may from time to time use Facebook Advertising, Facebook Pixel Re-Marketing, and communications. This tool allows Cycling Scotland to understand and deliver ads and make them more relevant to you. The collected data remains anonymous and Cycling Scotland cannot see the personal data of any individual user.
However, the collected data is saved and processed by Facebook. Facebook may be able to connect the data with your Facebook account and use the data for their own advertising purposes (in accordance with Facebook’s Data Use Policy found under https://www.facebook.com/about/privacy/. Facebook has ultimate control of the information gathered through Facebook Advertising, Facebook Pixel Re-Marketing, and communications. You can opt-out of Facebook’s use of cookies and Facebook Pixel Re-Marketing through settings on your Facebook Account.
Hotjar
We use Hotjar in order to better understand our users’ needs and to optimize this service and experience. Hotjar is a technology service that helps us better understand our users’ experience (e.g. how much time they spend on which pages, which links they choose to click, what users do and don’t like, etc.) and this enables us to build and maintain our service with user feedback. Hotjar uses cookies and other technologies to collect data on our users’ behavior and their devices. This includes a device's IP address (processed during your session and stored in a de-identified form), device screen size, device type (unique device identifiers), browser information, geographic location (country only), and the preferred language used to display our website. Hotjar stores this information on our behalf in a pseudonymized user profile. Hotjar is contractually forbidden to sell any of the data collected on our behalf.
For further details, please see the ‘about Hotjar’ section of Hotjar’s support site.
We use Google Analytics to analyse the use of our website to ensure that the website is functioning well and is useful to users.
Our analytics service provider generates statistical and other information about website use by means of cookies.
The analytics cookies used by our website are as follows:
|
Cookie Name |
Expiration Time |
Description |
|---|---|---|
|
_ga |
|
Used to distinguish users. |
|
_gid |
|
Used to distinguish users. |
|
_gat |
|
Used to throttle request rate. This cookie does not store any user information, it's just used to limit the number of requests that have to be made to Google Analytics. |
|
__utma |
2 years from set/update |
This cookie is used to determine new and returning visitors. It has an expiration time of 2 years. If the ga.js library is executed and no _utma cookie exists, this will be recorded as the users’ first visit and a _utma cookie will be set. If a _utma cookie is already in place, the expiration time is reset and the user is recorded as a return visitor. |
|
__utmt |
|
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 |
|
These cookies work in tandem to calculate visit length. Google __utmb cookie demarks the exact arrival time, then Google __utmc registers the precise exit time of the user.
This cookie is used to determine a new session. The cookie is set when the ga.js library executes and there is no _utmb cookie in place. It has an expiration time of 30 minutes, therefore if a user is inactive for a period longer than this, a new cookie will be set when the library executes and the interaction will be recorded as a new session. |
|
__utmc |
End of browser session |
These cookie work in tandem to calculate visit length. Google __utmb cookie demarks the exact arrival time, then Google __utmc registers the precise exit time of the user.
Given__utmc cannot tell if a browser or website session ends. Therefore, if no new page view is recorded in 30 minutes the cookie is expired. |
|
__utmz |
6 months from set/update |
This cookie is used to determine the traffic source, medium, campaign name and campaign term which delivered the user to your website. It is created when the javascript library executes and expires after 6 months. This helps Google collect the data which can then help them to determine which traffic sources assist conversions within the multi-channel section of Analytics. |
|
__utmv |
2 years from set/update |
This cookie is used for storing visitor-level custom variable data. It is created when the _setCustomVar method is used with a visitor level custom variable. Like the _utma cookie, this cookie expires after 2 years and is reset each time the user visits your site before the expiration of the cookie. |
The information generated relating to our website is used to create reports about the use of our website.
Our analytics service provider's privacy policy is available at http://www.google.com/policies/privacy/.