Cookie Policy

Cookie policy

At Ford Money, we use technologies like cookies, pixels, and local storage to make our websites easier to use and to tailor content to be more relevant for you. This guide is designed to explain, as clearly as possible, what cookies are; the purpose of those used on our website; and what options you have to control or delete them – if you decide you want to.

What is a cookie?

Almost every website uses cookie technology. A cookie is a small file that saves Internet settings. It gets downloaded through a browser during the first visit to a website. When you next return to the site using the same device, the browser may check to see if a related cookie is present (i.e. containing the site name) and use the data inside the cookie to send back to the site.

This allows sites to recognise that the browser has visited before and, in some cases, vary the content shown to reflect that.

You can find more information about cookies at:

• www.allaboutcookies.org
• www.youronlinechoices.eu
• www.cookiepedia.co.uk

What Cookies do we use?

The cookies used on our website have been categorized below and based on the categories as described in ICC UK Cookie guide.
 

Category 1 – ‘Strictly Necessary’ Cookies

These cookies are essential in order to enable you to move around the website and use its features, such as accessing secure areas of the website. Without these cookies services you have asked for, like online account management functionality, cannot be provided.

• _boomr_akamaiXhrRetry
  This cookie is necessary for the Akamai cache function. A cache is used by the website to optimize the response time between the visitor and the website. The cache is usually stored on the visitor’s browser.
• AKA_A2
  This cookie is necessary for the Akamai cache function. A cache is used by the website to optimize the response time between the visitor and the website. The cache is usually stored on the visitor’s browser.  This cookie is used for Akamais advanced acceleration feature, which enables DNS Prefetch and HTTP2 Push.
• BA
  This cookie is necessary for the Akamai cache function. A cache is used by the website to optimize the response time between the visitor and the website. The cache is usually stored on the visitor’s browser. The users bandwidth results are stored within this cookie to help ensure the bandwidth test isn't repeated for the same user repeatedly for the Akamai cache functionality 
• RT
  This cookie is necessary for the Akamai cache function. A cache is used by the website to optimize the response time between the visitor and the website. The cache is usually stored on the visitor’s browser. This cookie contains information on the users session to support Akamais cache functionality 
• ak_bmsc
  This cookie is used by Akamai to optimize site security by distinguishing between humans and bots
• bm_sv
  This cookie is necessary for the Akamai cache function. A cache is used by the website to optimize the response time between the visitor and the website. The cache is usually stored on the visitor’s browser. The users bandwidth results are stored within this cookie to help ensure the bandwidth test isn't repeated for the same user repeatedly for the Akamai cache functionality 
• ASP.NET_SessionId
  Used by the .NET framework to track the session
• citrix_ns_id_.fordmoney.co.uk_%2F_wat
  This is a security cookie that ensures that your session has not been tampered with
• citrix_ns_id
  This is a security cookie that ensures that your session has not been tampered with
• NSC_GSLB_*
  There are a number of servers that support our site. This cookie ensures that users are split equally between these servers and stops traffic building up on one particular server and slowing down the service.
• NSC_*
  This cookie ensures your session stays stuck to one server during your visit. Without this you would be disconnected from the server on a regular basis. 
• Authenticate
  This cookie is used to remember you while you are logged in and move about the savings site.
• OFIS
  This cookie is used to remember you while you are logged in so that you don’t need to keep re-entering your information as you move about the savings site.
• _RequestValidationToken*
  These cookies are used to makes sure it's only you navigating through your session. It checks that no one else is accessing the same session from a different browser, such as potential fraudsters.
• FedAuth
  This cookie is used to confirm that you've been authenticated.
• AUTH
  This cookie is a Security Token used for authentication purposes
• Ofis_logon_cookie
  This cookie is used by the ‘remember me’ login function 
• unsupported-browsers-overlay-counter
  Used by Ford to determine whether to show the unsupported browser overlay when a user has visited the site with an unsupported browser
• guxacc-cookiedisclaimer
  Used to store if a user has previously seen the Cookie Disclaimer banner which contains legal information that describes to user what actions are performed with the use of cookies on the Ford website
• CookieConsent
  Used to store a users cookie opt-in settings. This is neccesary for the websites GDPR compliance
• guxfoe-cookiedisclaimer
  Used to store if a user has previously seen the Cookie Disclaimer banner which contains legal information that describes to user what actions are performed with the use of cookies on the Ford website
• acc-unsupported-browsers-overlay-counter
  Used by Ford to determine whether to show the unsupported browser overlay when a user has visited the site with an unsupported browser
• cookie-configuration
  Used to store a users cookie opt-in settings. This is neccesary for the websites GDPR compliance
• UPConsentNSSL
  This cookie stores the user’s GDPR status that they have confirmed by interacting with cookie banner or by selecting specific categories of cookies they would like to be opted into or out of on the manage my cookie preferences page.
  
   

Category 2 – ‘Performance’ Cookies

These cookies collect information about how visitors use a website, for instance which pages visitors go to most often, and if they get error messages from web pages. These cookies don’t collect information that identifies a visitor. All information these cookies collect is aggregated and therefore anonymous. It is only used to improve how a website works.

• dtCookie
  Tracks visit across multiple requests for Dynatrace performance monitoring 
• dtLatC
  Measures server latency for Dynatrace performance monitoring 
• dtPC
  Used by Dynatrace to identify proper endpoints and ideal location for performance montoring
• dtSa
  Used to store contextual information of user actions to persist across pages for Dynatrace performance monitoring
• rxec
  Used by Dynatrace to manage the availability and performance of the site and the impact on user experience in the form of deep transaction tracing, synthetic monitoring, real user monitoring, and network monitoring.
• rxlatency
  Measures server latency for Dynatrace performance monitoring 
• rxpc
  Used by Dynatrace to identify proper endpoints and ideal location for performance montoring
• rxsession
  Tracks visit across multiple requests for Dynatrace performance monitoring
• rxvisitid
  Sets a unique visit ID for the session for Dynatrace performance monitoring 
• rxVisitor
  Sets a unique visitor ID for the user for Dynatrace performance monitoring to identify the visitor to correlate sessions
• rxvt
  Stores timestamps for Dynatrace performance monitoring to identify when sessions start & end
• ruxitagentjs_*_Store  (e.g. ruxitagentjs_c1248d9aea60111f_Store)
  Used by Dynatrace to cache the last monitor beacon response, which contains the configuration for the real user monitoring JavaScript library for Dynatrace. It doesn't store any user-related data in localStorage
• dtDisabled
  Used by Dynatrace to manage the availability and performance of the site and the impact on user experience in the form of deep transaction tracing, synthetic monitoring, real user monitoring, and network monitoring.
• dtsrVID
  Used by Dynatrace to manage the availability and performance of the site and the impact on user experience in the form of deep transaction tracing, synthetic monitoring, real user monitoring, and network monitoring.
• dtsrE
  Used by Dynatrace to manage the availability and performance of the site and the impact on user experience in the form of deep transaction tracing, synthetic monitoring, real user monitoring, and network monitoring.
• dtsrTID
  Used by Dynatrace to manage the availability and performance of the site and the impact on user experience in the form of deep transaction tracing, synthetic monitoring, real user monitoring, and network monitoring.
• s_cc
  Used to determine if cookies are enabled for anonymous Adobe Analytics performance monitoring
• s_cp_pers
  Used to collect & persist the details of the last email campaign a user clicked through to the site from for Adobe Analytics performance monitoring
• s_fid
  Sets an anonymous fall-back unique visitor ID for the user where the Adobe s_vi cookie cannot be set due to 3rd party restrictions for Adobe Analytics performance monitoring
• s_p_s_prop8
  Used to collect & persist the traffic source type which referred the user for Adobe Analytics performance monitoring
• s_p13_pers
  Used to collect & persist internal campaign codes from internal links within the website for Adobe Analytics Peformance monitoring
• s_sq
  Used to collect information about the links clicked on by users for anonymous Adobe Analytics performance monitoring
• s_suite
  Used to collect the Adobe report suite ID relating to the site that the user is viewing
• s_vi_*
  Sets an anonymous visitor ID with date & time stamp to identify unique visitors for Adobe Analytics performance monitoring
• v_starting
  Used to indicate the start of a visit to capture where the user came from
• AMCV_*AdobeOrg
  Used to identify a unique visitor ID that can be used by Adobe Experience Cloud services
• AMCVS_*AdobeOrg
  Used as a flag indicating that the session has been initialised for use in Adobe Experience Cloud services
• s_ecid
  Used to store a copy of the Adobe Experience Cloud ID to allow persistent ID tracking in the 1st-party state and is used as a reference ID if the AMCV cookie has expired
• Stores a random ID which ensures that a user can be uniquely identified as a guest or logged -in user. Functions such as "Items last viewed " or retention of the logged -in state are connected with this cookie.
• _hjid
  This cookie is set when the customer first lands on a page with the Hotjar script. It is used to persist the Hotjar User ID, unique to that site on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID.. This allows the website to obtain data on visitor behaviour for statistical purposes.
• _hjIncludedInSample
  This session cookie is set to let Hotjar know whether that visitor is included in the sample which is used to generate funnels
• _hjRecordingEnabled
  This value is set when a Hotjar recording starts.  It is used to see if the user is already recording this particular session.
• _hjRecordingLastActivity
  This gets updated when a Hotjar visitor recording starts and when data is sent through the WebSocket (the visitor performs an action we record). This is later removed if the session becomes inactive and gets readded if the session resumes. 
• _hjTLDTest
  This checks if cookies can be loaded on the site by Hotjar, and is removed shortly afterward
• hjViewportId
  Sets a unique Hotjar ID for the users session. This allows the website to obtain data on visitor behaviour for statistical purposes.
• __hssc
  This cookie keeps track of sessions. This is used to determine if HubSpot should increment the session number and timestamps in the __hstc cookie. It contains the domain, viewCount (increments each pageView in a session), and session start timestamp. 
• __hssrc
  Whenever HubSpot changes the session cookie, this cookie is also set to determine if the visitor has restarted their browser. If this cookie does not exist when HubSpot manages cookies, it is considered a new session.
• __hstc
  The main cookie for tracking visitors for the HotJar Hubspot integration. It contains the domain, utk, initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session).
• hubspotutk
  This cookie is used to keep track of a visitor's identity. This cookie is passed to HubSpot on form submission and used when deduplicating contacts.
• ajs_group_id
  Used with Hotjars Segment integration to track users website behaviour anonymously for performance monitoring
• ajs_user_id
  Used with Hotjars Segment integration to track users website behaviour anonymously for performance monitoring
  
   

Category 3 – ‘Functionality’ Cookies

These cookies allow the website to remember choices you make (such as your user name, language or the region you are in) and provide enhanced, more personal features. For instance, a website may be able to provide you with local weather reports or traffic news by storing in a cookie the region in which you are currently located. These cookies can also be used to remember changes you have made to text size, fonts and other parts of web pages that you can customise. They may also be used to provide services you have asked for such as watching a video or commenting on a blog. The information these cookies collect may be anonymised and they cannot track your browsing activity on other websites.

• check
  Used by Adobe Target to determine if a visitor supports cookies. Set each time a visitor requests a page
• lp_custom_id
  Used to disqualify users from Adobe Target tests
• mbox
  Used by Adobe Target to provide the ability to test which online content and offers are more relevant to visitors within the Ford websites 
• mboxEdgeCluster
  Used by Adobe Target to provide the ability to test which online content and offers are more relevant to visitors within the Ford websites 
• optprg-popups-disable
  Used for Adobe Target to limit the number of times /duration of 15 mins a user sees the retargeting popups. 
• popup_information
  Used for Adobe Target to limit the number of times /duration of 15 mins a user sees the retargeting popups.
  
   

Category 4 – ‘Targeting/advertising’ Cookies

These cookies are used to deliver adverts more relevant to you and your interests. They are also used to limit the number of times you see an advertisement as well as help measure the effectiveness of the advertising campaign. They are usually placed by advertising networks with the website operator’s permission. They remember that you have visited a website and this information is shared with other organisations such as advertisers. Quite often targeting or advertising cookies will be linked to site functionality provided by the other organisation.

• _dp
  Used to determine if Audience Manager can set other cookies in the demdex.net domain in a third-party context 
• aam_uuid
  Used to assign a unique ID to a device so that Audience Manger can perform basic functions such as visitor identification, ID synchronization, segmentation, modelling and reporting for targeting purposes
• AAMC_fordeu_0
  Used to set region flag for Adobe Audience Manager
• demdex
  Used to assign a unique ID to a site visitor so that Audience Manger can perform basic functions such as visitor identification, ID synchronization, segmentation, modelling and reporting for targeting purposes
• dextp
  Records the last time Audience Manager made a data synchronization call with data provider ID & timestamp for targeting purposes
• dpm
  Used to record that a call from Adobe Audience Manager or the ID service is passing in data for synchronization or requesting an ID for targeting purposes.
• dst
  This is set by Audience Manager when there is an error sending data to a destination in the targeting workflow
• ev_sync_dd
  Third-party, ad exchange-specific cookie that syncs a users Adobe Experience Cloud ID with the partner ad exchange. It's created for new visitors and sends a synchronization request when it has expired.
• ev_sync_nx
  Third-party, ad exchange-specific cookie that syncs a users Adobe Experience Cloud ID with the partner ad exchange. It's created for new visitors and sends a synchronization request when it has expired.
• ev_sync_ix
  Third-party, ad exchange-specific cookie that syncs a users Adobe Experience Cloud ID with the partner ad exchange. It's created for new visitors and sends a synchronization request when it has expired.
• ev_sync_ax
  Third-party, ad exchange-specific cookie that syncs a users Adobe Experience Cloud ID with the partner ad exchange. It's created for new visitors and sends a synchronization request when it has expired.
• ev_sync_bk
  Third-party, ad exchange-specific cookie that syncs a users Adobe Experience Cloud ID with the partner ad exchange. It's created for new visitors and sends a synchronization request when it has expired.
• ev_sync_fs
  Third-party, ad exchange-specific cookie that syncs a users Adobe Experience Cloud ID with the partner ad exchange. It's created for new visitors and sends a synchronization request when it has expired.
• ev_sync_ox
  Third-party, ad exchange-specific cookie that syncs a users Adobe Experience Cloud ID with the partner ad exchange. It's created for new visitors and sends a synchronization request when it has expired.
• ev_sync_pm
  Third-party, ad exchange-specific cookie that syncs a users Adobe Experience Cloud ID with the partner ad exchange. It's created for new visitors and sends a synchronization request when it has expired.
• ev_sync_tm
  Third-party, ad exchange-specific cookie that syncs a users Adobe Experience Cloud ID with the partner ad exchange. It's created for new visitors and sends a synchronization request when it has expired.
• ev_sync_yh
  Third-party, ad exchange-specific cookie that syncs a users Adobe Experience Cloud ID with the partner ad exchange. It's created for new visitors and sends a synchronization request when it has expired.
• ev_sync_rc
  Third-party, ad exchange-specific cookie that syncs a users Adobe Experience Cloud ID with the partner ad exchange. It's created for new visitors and sends a synchronization request when it has expired.
• everest_g_v2
  This cookie is used by Adobe and carries out information about how the end user uses the website and any advertising that the end user may have seen before visiting the said website. 
• everest_session_v2
  This cookie is used by Adobe and carries out information about how the end user uses the website and any advertising that the end user may have seen before visiting the said website.
• gglck
  Used by Adobe for targeted ads and to document efficacy of each individual ad.
• anj
  Contains data denoting whether a cookie ID is synced with AppNexus Xandr partners which enables the ability to use data from outside the platform
• bounce
  Used by AppNexus Xandr to determines if a visitor leaves the website straight away for use in advertising targeting
• icu
  Used to select ads and limit the number of times a user sees a particular ad for the AppNexus Xandr platform. It contains information such as the number of times an ad has been shown, how recently an ad has been shown, or how many total ads have been shown.
• sess
  Used by AppNexus Xandr to test whether a browser is configured to accept cookies
• token
  Used as a security measure containing a unique value only to verify the origin of opt-out requests for AppNexus Xandr
• uids
  Contains a base 64 encoded JSON object which contains external unique randomly-generated values that enable other Prebid Server demand partners to distinguish browsers and mobile devices. It is used the AppNexus Xandr Prebid Server demand partners to select advertisements for delivery by the Platform and to measure the performance of, and attribute payment for, those advertisements.
• usersync
  Contains data denoting whether a cookie ID is synced with AppNexus Xandr partners. ID syncing enables our partners to use their data from outside the Platform on the Platform. (See our platform privacy page for more info.)
• uuid2
  Contains a unique randomly-generated value that enables AppNexus Xandr to distinguish browsers and devices. It is matched against information - such as advertising interest segments and histories of ads shown in the browser or device - provided by clients or other third parties and is used to select more relevant advertisements for delivery, and to measure the performance of, and attribute payment for, those advertisements.
• _fbp
  Used by Facebook to deliver, measure and improve the relevancy of their advertising and to deliver a series of advertisement products on Facebook 
• ATN
  Used by Facebook to deliver, measure and improve the relevancy of their advertising and to deliver a series of advertisement products on Facebook 
• fr
  Used by Facebook to deliver, measure and improve the relevancy of their advertising and to deliver a series of advertisement products on Facebook 
• tr
  Used by Facebook to deliver, measure and improve the relevancy of their advertising and to deliver a series of advertisement products on Facebook 
• AA003
  Used by Facebook to deliver, measure and improve the relevancy of their advertising and to deliver a series of advertisement products on Facebook 
• atdmt.com
  Used by Facebook to deliver, measure and improve the relevancy of their advertising and to deliver a series of advertisement products on Facebook 
• __Secure-3PAPISID
  Used by for targeting purposes to build a profile of the website visitor's interests in order to show relevant & personalised Google advertising 
• __Secure-3PSID
  Used by for targeting purposes to build a profile of the website visitor's interests in order to show relevant & personalised Google advertising 
• __Secure-APISID
  Used by for targeting purposes to build a profile of the website visitor's interests in order to show relevant & personalised Google advertising 
• __Secure-HSID
  Used for security purposes to store digitally signed and encrypted records of a user’s Google account ID and most recent sign-in time which allows Google to authenticate users, prevent fraudulent use of login credentials, and protect user data from unauthorised parties. This can also be used for targeting purposes to show relevant & personalised ad content
• __Secure-SSID
  Used to store information about how you use the website and any advertising that you may have seen before visiting this website, in addition to being used to help customise advertising on Google properties by remembering your most recent searches, your previous interactions with an advertiser's ads or search results and your visits to an advertisers website.
• _gcl_au
  Used to monitor how many times people who click on ads end up taking an action on the site (e.g. making a purchase) to allow Google advertising to determine that you clicked an ad and later visited the site. Not used by Google for personalised ad targeting and persists for a limited time only
• 1P_JAR
  Used to store information about how you use the website and any advertising that you may have seen before visiting this website, in addition to being used to help customise advertising on Google properties by remembering your most recent searches, your previous interactions with an advertiser's ads or search results and your visits to an advertisers website.
• AID
  Used for targeting purposes to store Google IDs so that your activity can be linked across devices (if you’ve previously signed in to your Google Account on another device), in order to show relevant & personalised advertising across all devices
• ANID
  Used by for targeting purposes to build a profile of the website visitor's interests in order to show relevant & personalised Google advertising 
• APISID
  Used by for targeting purposes to build a profile of the website visitor's interests in order to show relevant & personalised Google advertising 
• CONSENT
  Used to store Google Network advertising preferences for use in targeted advertising
• DSID
  Used for targeting purposes to store Google IDs so that your activity can be linked across devices (if you’ve previously signed in to your Google Account on another device), in order to show relevant & personalised advertising across all devices
• DV
  Used for targeting purposes to build a profile of the website visitor's interests in order to show relevant & personalised advertising 
• FLC
  Used by Google AdSense DoubleClick to limit the frequency of advertisements so that the user does not see the same advertisement repeatedly. This cookie expires when the session ends.
• HSID
  Used for security purposes to store digitally signed and encrypted records of a user’s Google account ID and most recent sign-in time which allows Google to authenticate users, prevent fraudulent use of login credentials, and protect user data from unauthorised parties. This can also be used for targeting purposes to show relevant & personalised ad content
• IDE
  Used for targeting purposes to build a profile of the website visitor's interests in order to show relevant & personalised Google advertising 
• NID
  Used to store preferences in a unique Google ID to remember your information, such as your preferred language (e.g. English), how many search results you wish to have shown per page (e.g. 10 or 20), and whether or not you wish to have Google’s SafeSearch filter turned on. These preferences can be used for optimised &/or personalised advertising on Google networks
• OGP
  Used by Google to store preferences and user information each time they visit web pages containing geographical maps of Google Maps. 
• OGPC
  Used by Google to store preferences and user information each time they visit web pages containing geographical maps of Google Maps.
• pagead/1p-conversion/#
  Used for targeting & performance purposes. Data is used for reporting, search query reports for optimisation purposes & time of day optimisations
• pagead/1p-user-list/#
  Used for targeting purposes. Audience lists are built based on user interaction of pages on the website. Data is used for search optimisation and as seeds for similar audience lists both to improve performance of media spend.
• SAPISID
  Used by for targeting purposes to build a profile of the website visitor's interests in order to show relevant & personalised Google advertising 
• SID
  Used for security purposes to store digitally signed and encrypted records of a user’s Google account ID and most recent sign-in time which allows Google to authenticate users, prevent fraudulent use of login credentials, and protect user data from unauthorised parties. This can also be used for targeting purposes to show relevant & personalised ad content
• SIDCC
  Used to store information about how you use the website and any advertising that you may have seen before visiting this website, in addition to being used to help customise advertising on Google properties by remembering your most recent searches, your previous interactions with an advertiser's ads or search results and your visits to an advertisers website.
• SSID
  Used to store information about how you use the website and any advertising that you may have seen before visiting this website, in addition to being used to help customise advertising on Google properties by remembering your most recent searches, your previous interactions with an advertiser's ads or search results and your visits to an advertisers website.
• TAID
  Used for targeting purposes to store Google IDs so that your activity can be linked across devices (if you’ve previously signed in to your Google Account on another device), in order to show relevant & personalised advertising across all devices
• test_cookie
  Used by Google to check if your browser supports cookies.
• UULE
  Used by for targeting purposes to build a profile of the website visitor's interests in order to show relevant & personalised Google advertising 
• .DDMMUI-PROFILE
  Used by for targeting purposes to build a profile of the website visitor's interests in order to show relevant & personalised Google advertising 
• XSRF-TOKEN
  Used by for targeting purposes to build a profile of the website visitor's interests in order to show relevant & personalised Google advertising 
• mt_mop
  Used for targeting purposes to optimise ad relevance by utilising visitor data from multiple websites provided by the MediaMath ad-exchanage and Google
• uuid
  Used for targeting purposes to optimise ad relevance by utilising visitor data from multiple websites provided by the MediaMath ad-exchanage and Google
• uuidc
  Used for targeting purposes to optimise ad relevance by utilising visitor data from multiple websites provided by the MediaMath ad-exchanage and Google
• id
  Used to record a unique ID for use in GroupM advertising targeting & optimisation and reporting & attribution
• mdata
  Used to record a unique ID, timestamp & cookie version for use in GroupM targeted advertising
• ov
  Used to verify the identity of consumers exercising their rights to make requests to MInsights under new data privacy laws
• syncdata_##
  Used to record a unique ID, timestamp & MInsights partner ID for use in GroupM targeted advertising
• t/v2/activity
  Used to record information that takes place by a user (such as a landing page visit or a purchase) which can be used to learn more about the traits that characterise a given audience and may be used to build retargeting segments for GroupM advertising
• xax_sync
  Used to record a unique ID, timestamp & MInsights partner ID for use in GroupM targeted advertising
• RMOPTOUT
  Used to verify the identity of consumers exercising their rights to make requests to MInsights under new data privacy laws
• optouts
  Used to verify the identity of consumers exercising their rights to make requests to MInsights under new data privacy laws
• optout
  Used to verify the identity of consumers exercising their rights to make requests to MInsights under new data privacy laws
• gdpr
  Used to verify the identity of consumers exercising their rights to make requests to MInsights under new data privacy laws
• bcookie
  Used to store a browser ID cookie for LinkedIn Advertising & Targeting purposes
• BizoData
  Used for LinkedIn Insight analytics for reporting & personalisation of advertising
• BizoID
  Used for LinkedIn Insight analytics for reporting & personalisation of advertising
• BizoNetworkPartnerIndex
  Used for LinkedIn Insight analytics for reporting & personalisation of advertising
• BizoUserMatchHistory
  Used for LinkedIn Insight analytics for reporting & personalisation of advertising
• bscookie
  Used to store a secure browser ID cookie for LinkedIn Advertising & Targeting purposes
• L1c
  Used to store a browser ID cookie for LinkedIn Advertising & Targeting purposes
• lang
  Used to remeber the users selected language version of the Ford website to potentially serve up content from LinkedIn advertising or pugins such as the share button in the stored language
• lidc
  Used for routing from LinkedIn Share buttons & advertising services
• UserMatchHistory
  Used for LinkedIn Insight analytics for reporting & personalisation of advertising. Used to track visitors on multiple websites, in order to present relevant advertisement based on the visitor's preferences.
• lissc
  Used for routing from LinkedIn Share buttons & advertising services
• fcookie
  Used to store a secure browser ID cookie for LinkedIn Advertising & Targeting purposes
• OMGID
  Stores an anonymous user ID to provide affiliate campaign measurement data for individual user sessions for the Optimise Advertiser and Publisher network
• OMGSession
  Stores a session ID to enable measurement and analytics data of performance marketing campaigns across the Optimise Advertiser and Publisher network
• ct0
  Used for Twitter Advertising & Targeting purposes
• guest_id
  Used for Twitter Advertising & Targeting purposes
• i/adsct
  Used for Twitter Advertising & Targeting purposes
• personalization_id
  Used for Twitter Advertising & Targeting purposes
  
   

Web Beacons

Some of our Web pages may contain electronic images known as Web Beacons (sometimes known as clear gifs) that allow us to count the number of users who have visited these pages.

Web Beacons collect only limited information, these include a cookie number; the time and date of a page view, and a description of the page where the Web Beacon resides.

We may also carry Web Beacons that are placed by third party advertisers. These Beacons do not carry any personally identifiable information and are only used to track the level of effectiveness of a particular campaign.

Controlling and deleting cookies

If you want to change how a browser uses cookies, including blocking or deleting cookies from the Ford Money website (or any other website in fact) you can do so by changing the browser settings.

To control cookies, most browsers allow you to either accept or reject all cookies, only accept certain types of cookies, or prompt you each time a site wishes to save a cookie. It’s also easy to delete cookies that are already saved on your device by a browser.

The processes for controlling and deleting cookies vary depending on which browser you use. To find out how to do so with a particular browser, you can use the Help function within it or alternatively you can visit http://www.aboutcookies.org which explains, step-by-step, how to control and delete cookies in most browsers.

Tracking Policy

At Ford Money we use Adobe Analytics to track anonymous usage information. We collect information about how visitors interact with our site.

We do not track any personal information. For example, if you opt-in for an email contact that action will be logged, but your email address will not.

Collected data can be used to help us improve our website and to deliver the best tailored experience.