Cookie Policy

What are cookies?

Cookies are widely used tiny pieces of software (files) that are installed on a computer or mobile device when an individual visits a website.

Windows Explorer, which is one of the main internet browsers, will usually store these files in a folder called ‘cookies’ in ‘documents and permissions’ on computers running Microsoft Windows.

Cookies allow websites to recognise that a user on an individual computer has previously visited the site. The cookies save some information about that user for when they access the site again in the future.

By using and browsing the Lynx Forecourt website, you consent to cookies being used in accordance with our policy. If you do not consent, you must turn off cookies or refrain from using the site.

Most browsers allow you to turn off cookies. To do this, look at the ‘help’ menu on your browser. Switching off cookies may restrict your use of the website and/or delay or affect the way in which it operates.

What types of cookies are there?

Broadly, there are 4 types of cookie:

Strictly necessary cookies. These are cookies that are essential to make a website work and enable features that users have specifically asked for. These types of cookies are commonly used with e-billing. Without use of cookies, these features of the website could not operate.

Performance cookies. These cookies collect anonymous information about users for the purpose of assessing the performance of a website. Common uses include well-known web analytics tools such as ‘Google Analytics’.

Functionality cookies. These are cookies that automatically remember choices that users have previously made in order to improve their experience next time they visit a website. For example, where users select their preferred settings and layout.

Targeting or Advertising cookies. These cookies are similar to performance cookies, in that they collect information about users’ behaviour. However, this information is used at individual user level to advertise products and services to users on the basis of the behavioural information collected.

What cookies are used on the Lynx Forecourt website?

Used to customize the view of admin interface/main site interface for logged in users.2 weeks

Service Cookie Name Description Expiration Time
Google Analytics gtag.js and analytics.js _ga Used to distinguish users. 2 years
_gid Used to distinguish users. 24 hours
_gat Used to throttle request rate. If Google Analytics is deployed via Google Tag Manager, this cookie will be named _dc_gtm_<property-id>. 1 minute
AMP_TOKEN Contains a token that can be used to retrieve a Client ID from AMP Client ID service. Other possible values indicate opt-out, inflight request or an error retrieving a Client ID from AMP Client ID service. 30 seconds to 1 year
_gac_<property-id> Contains campaign related information for the user. If you have linked your Google Analytics and AdWords accounts, AdWords website conversion tags will read this cookie unless you opt-out. 90 days
Google Analytics ga.js __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. 2 years from set/update
__utmt Used to throttle request rate. 10 minutes
__utmb Used to determine new sessions/visits. The cookie is created when the javascriptlibrary executes and no existing __utmb cookies exists. The cookie is updated every time data is sent to Google Analytics. 30 mins from set/update
__utmc Not used in ga.js. Set for interoperability with urchin.js. Historically, this cookie operated in conjunction with the __utmbcookie to determine whether the user was in a new session/visit. End of browser session
__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. 6 months from set/update
__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. 2 years from set/update
Google Maps NID, OGPC, APISID These cookies are used by Google to store user preferences and information when viewing pages with Google maps on them. From 1 month to 6 months
Google 1P_JAR, CONSENT, APISD, HSID, S, SIDCC, NID, SID Google uses these cookies, based on recent searches and interactions, to customise ads on Google websites. From 1 month to 20 years
DV, UULE These cookies are used by Google to collect information about how visitors use our site. 1 day
OTZ A cookie used by Google Analytics that provides an aggregate analysis of Website visitors 1 week
Twitter _ga, _gid, lang, kdt,
syndication_guest_id, dnt, guest_id,
personalization_id, twid, netpu, guest_id,
tfw_exp, remember_checked_on,
twitter_ads_id, co, auth_token
These are Twitter cookies that are used on websites with Twitter feeds and / or Twitter sharing functionalities. For more information, please see https://help.twitter.com/en/rules-and-policies/twitter-cookies From session duration to 2 years
Facebook pl, c_user, act, fr, wd, xs, presence, sb, lu, spin, dpr These cookies are used for re-targeting, optimisation, reporting and attribution of online adverts From session to 10 years
datr A Facebook cookie that monitors your Facebook account for suspicious behaviour such as failed login attempts or attempts to create spam accounts
LinkedIn li_oatml, lidc, bcookie, __utma, VID, ELOQUA, _ga, liap, _guid, _lipt Used by the social networking service, LinkedIn, for tracking the use of embedded services. From Session to 2 years
cookie_notice_accepted This cookie enables you to accept our cookie statement once every year. 1 year
WordPress wp-settings-, wp-settings-time
wordpress_test_cookie Checks if cookies are enabled to provide appropriate user experience. Session
wordpress_logged_in_ Checks whether or not the current visitor is a logged in WordPress.com user. Session
wordpress_sec_ Essential WordPress session management cookies for logged in users. Session
itsec-hb-login-* Set by WP Security Plugin to change the backend login URL for additional security. Session