Cookies are small text files that are placed on your computer by websites that you visit. They are widely used to make websites work, or work more efficiently, as well as to provide information to the owners of the site. The table below explains the cookies used by GetHarley.com and why.

For more information on how we process your personal information (whether collected on our website or through the provision of our services) please see our Privacy page.

Our website may contain social sharing buttons and links to and from other websites (such as LinkedIn and Facebook) we do not own or control. These websites have their own privacy and cookie policies.

Cookies table

Cookie	Name	Expiry period	Purpose
Universal analytics (Google)	_ga	2 years	Distinguishes users.
	Universal analytics (Google)	_gid	24 hours	Distinguishes users.
	Universal analytics (Google)	_gat	60 seconds	Throttle request rate.
	Universal analytics (Google)	_utma	2 years	Used by Google Analytics to identify unique visitors vs. returning visitors.
	Universal analytics (Google)	_utmt	10 minutes	Throttle request rate.
	Universal analytics (Google)	_utmb	30 minutes	General visitor page visit tracking.
	Universal analytics (Google)	_utmc	Session	Identified unique visitors and returning visitors. Tracks where the user visit came from (e.g. search result).
	Universal analytics (Google)	_utmz	6 months	Stores visitor level variable data.
	Universal analytics (Google)	_utmv	2 years	You can learn more about Google Analytics’ data practices here.
Facebook analytics	_fbp	3 months	Stores and tracks user visits across websites.
Heroku	heroku-session-affinity	24 hours	Associates all HTTP requests coming from an end-user with a single Heroku's application instance. This cookie contains no private application information and doesn’t require request- or response-related data to function.
Hotjar	_hjSessionUser	1 year	Used to persist the Hotjar User ID, unique to that site on the browser. This ensures that behaviour in subsequent visits to the same site will be attributed to the same user ID.
	Hotjar	_hjSession	30 minutes	Holds current session data. This ensures subsequent requests within the session window will be attributed to the same Hotjar session.
	Hotjar	_hjSessionTooLarge	Session	Causes Hotjar to stop collecting data if a session becomes too large. This is determined automatically by a signal from the WebSocket server if the session size exceeds the limit.
	Hotjar	_hjSessionRejected	Session	If present, this cookie will be set to '1' for the duration of a user's session, if Hotjar rejected the session from connecting to our WebSocket due to server overload.
	Hotjar	_hjSessionResumed	Session	Set when a session/recording is reconnected to Hotjar servers after a break in connection.
	Hotjar	_hjid	1 year	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 behaviour in subsequent visits to the same site will be attributed to the same user ID.
	Hotjar	_hjRecordingLastActivity	Session	This should be found in Session storage (as opposed to cookies). This gets updated when a user recording starts and when data is sent through the WebSocket (the user performs an action that Hotjar records).
	Hotjar	_hjTLDTest	Session	When the Hotjar script executes we try to determine the most generic cookie path we should use, instead of the page hostname. This is done so that cookies can be shared across subdomains (where applicable). To determine this, we try to store the _hjTLDTest cookie for different URL substring alternatives until it fails. After this check, the cookie is removed.
	Hotjar	_hjUserAttributesHash	Session	User Attributes sent through the Hotjar Identify API are cached for the duration of the session in order to know when an attribute has changed and needs to be updated.
	Hotjar	_hjCachedUserAttributes	Session	Stores User Attributes which are sent through the Hotjar Identify API, whenever the user is not in the sample. Collected attributes will only be saved to Hotjar servers if the user interacts with a Hotjar Feedback tool, but the cookie will be used regardless of whether a Feedback tool is present.
	Hotjar	_hjLocalStorageTest	Less than a second	Used to check if the Hotjar Tracking Script can use local storage. If it can, a value of 1 is set in this cookie. The data stored in_hjLocalStorageTest has no expiration time, but it is deleted almost immediately after it is created.
	Hotjar	_hjIncludedInPageviewSample	30 minutes	Lets Hotjar know whether that user is included in the data sampling defined by the site’s pageview limit.
	Hotjar	_hjIncludedInSessionSample	30 minutes	Lets Hotjar know whether that user is included in the data sampling defined by the site's daily session limit.
	Hotjar	_hjAbsoluteSessionInProgress	30 minutes	Used to detect the first pageview session of a user. This is a True/False flag set by the cookie.
	Hotjar	_hjFirstSeen	Session	Set to identify a new user’s first session. It stores a true/false value, indicating whether this was the first time Hotjar saw this user. It is used by Recording filters to identify new user sessions.
	Hotjar	_hjViewportId	Session	Stores information about the user viewport such as size and dimensions.
Partnerize Analytics	_tPHG-PS	1 year	Partnerize’s tracking cookie, deployed either upon a user’s clicking of a link on a partner website, or upon the loading of a customer’s image to a partner website.
Payments (Stripe)	_stripe_mid _stripe_sid	1 year 30 minutes	Both cookies detect and prevent fraud using device characteristics (browser, screen or device).
Advertising	_gcl_aw	90 days	Analytics and advertising Advertising (AdSense for Search)
	Advertising	_gsas	3 months	Stores number of service requests
	Advertising	gcl_dc	90 days	Analytics and advertising
	Advertising	_gcl_au	3 months	Stores and tracks conversions by GoogleAds
Cookies	CookieControl	3 months	Used to remember the user’s cookie preferences.
	Cookies	euconsent	3 months	Used to store the IAB TCF consent string and consent information.

How do I change my cookie settings?

You can change your cookie preferences at any time by visiting “cookie preferences” at the bottom of our homepage. You may need to refresh your page for your settings to take effect.

Alternatively, most web browsers allow some control of most cookies through the browser settings. To find out more about cookies, including how to see what cookies have been set, visit:

https://www.aboutcookies.org https://www.allaboutcookies.org

To opt out of being tracked by Google Analytics across all websites, visit:

https://tools.google.com/dlpage/gaoptout.