Cookie Policy

[Ikenna]

At Ford, 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 what cookies are; the purpose of those used on Ford websites; and what options you have to control or delete them – if you decide you want to.

Click here to manage your cookie preferences

What is a Cookie?

Almost every website uses cookie technology. A cookie is a small file that a server downloads to your personal computer (PC) or mobile when you visit a website. When you next return to the site using the same device, your PC checks to see if it has a cookie that the website recognises. If it has such a cookie, it communicates with the website and enables the website to read the information held in that.  This allows the site to recognise that the browser has been visited before and, in some cases, may alter the content shown to reflect this.

You can find more information about cookies at:

• www.allaboutcookies.org
• www.youronlinechoices.eu
• www.google.co.uk/policies/technologies/cookies

What Cookies do we use?

The cookies used on this website have been categorised below.

Category 1 – ‘Strictly Necessary Cookies

These cookies are essential in letting you move around the website and use its features, such as accessing secure areas of the website. Without these cookies, services you have asked for such as shopping baskets or e-billing, cannot be provided.

Cookie	Cookie’s Description
AWSALB	AWS sticky session cookie required for load balancer routing. See this document for further information.
AWSALBCORS	For continued stickiness support with CORS use cases after the Chromium update, we are creating additional stickiness cookies for each of these duration-based stickiness features named AWSALBCORS (ALB). See https://forums.aws.amazon.com/ann.jspa?annID=7413 for further information.
!lithiumSSO:{client_id}	Used for passing authentication information to Khoros. This cookie is a cancel cookie. Khoros sets this cookie so that we don't re-read the original lithiumSSO cookie set with SSO.
LiSESSIONID	Session management. If this isn’t present the user cannot log in and is treated as an anonymous user.
LithiumUserInfo	Session management
LithiumUserSecure	Secure Session management
LithiumVisitor	Replaces VISITOR_BEACON. Khoros currently uses both for backward compatibility. This cookie computes billing visits, registered billing visits, visits, registered visits, and unique visitor’s metrics. The cookie is encrypted and stores when it was first issued, when it was last seen by Khoros, a unique visitor ID (which is unique per visitor’s browser).
PushyAuthToken	Authenticates the user for a session with Realtime Notifications service (Pushy).
VISITOR_BEACON	Computes billing visits, registered billing visits, visits, registered visits, and unique visitors metrics. The cookie is encrypted and stored when it was first issued when it was last seen by Khoros, the user ID, and its own unique ID.
VISITORID	Distinguishes between human and bot traffic.
LithiumCookiesAccepted	Stores the information of whether the user has given the explicit consent by clicking "Accept" on the cookie banner to drop Type 2, Type 3 & Type 4 cookies. This cookie will store '1' if the user has explicitly clicked "Accept" in the cookie banner and store '2' if the user clicked "Reject".

Category 2- ‘Performance’ Cookies

These cookies collect information about how our visitors use the website. For example, it enables us to know 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 collected by these cookies is aggregated and therefore anonymous. It is only ever used to improve how our website works.

Cookie	Cookie’s Description
_ga	Distinguishes users using a unique ID. It is used by Google Analytics to calculate visitor, session, and campaign data. By default, the configuration setting that sets this cookie is disabled. File a Support ticket to request enablement.
mPulse	mPulse enables real-time performance monitoring and analysis of the community and helps improve over...
JSESSIONID	Cookie is used to store a session identifier in order to monitor session counts for a community inst...

Category 3 – ‘Functionality' Cookies

These cookies allow the website to remember any choices you make. This could include your username, language or the region you are in, and provide more enhanced, and personal features. These cookies can also be used to remember changes you have made to text size, fonts and other parts of web pages that you’ve customised.

They may also be used to provide services you have asked for, such as watching a video or commenting on a blog. Information collected by these cookies collect may be anonymised and therefore cannot track your browsing activity on other websites.

Cookie	Cookie’s Description
­­lia.anon.{setting or config name}	Stores community-wide configurations and settings for anonymous users.
liSdkOptions:{communityId}	Dropped when a Studio user navigates to Studio > Advanced > SDK and clicks Submit after checking the View as anonymous checkbox. The cookie allows developers to sign out of the community but still have it find the URL to use for rendering a skin that is hosted via the Community Plugin SDK. This cookie is used only on-stage sites.
lithium.anonymous. usersetting.{setting name}	Remembers user preferences.
lithium.anonymous. usersetting.profile. language	Remembers language preferences.
lithiumLogin:{community id}	Keeps users logged in when they make a request after their session has expired. It is triggered when a user checks Save login name and password. The cookie is encrypted and includes a unique user secure ID in the database.
LithiumNotifications	Temporarily stores Realtime Notification messages (Toast messages).
P{poll_id}U{user_id}R{reset_count}	Tracks when a user has voted in a poll and tracks the answer value. The cookie is used to prevent a user from voting multiple times in a single poll. The cookie is only placed if Use cookies to prevent multiple votes is enabled in Community Admin.
ValueSurveyParticipation	Stores a timestamp storing the creation time of this cookie, which is used in value survey trigger logic.
ValueSurveyVisitorCount	Stores the survey visit count of the user, which is used in logic that determines when a survey is triggered. This cookie is used in conjunction with the ValueSurveyParticipation cookie. When the ValueSurveyParticiation is set, the count for the ValueSurveyVisitorCount cookie is reset to 0.

Category 4: Targeting/advertising Cookies

These cookies are used to deliver adverts more relevant and suited to you and your interests. They’re 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 what websites you have visited, and this information is shared with other organisations such as advertisers. Quite often, targeting cookies will be linked to site functionality provided by the other organisation.

Cookie	Cookie’s Description
_pendo_meta.*	Cookie is used by Communities to show in-app feature guides in the "Community Admin" section
_pendo_accountId.*	Cookie is used by Communities to show in-app feature guides in the "Community Admin" section
_pendo_visitorId.*	Cookie is used by Communities to show in-app feature guides in the "Community Admin" section