Cookie Policy

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

Name Provider Purpose Expiry Type
messagesUtk HubSpot This cookie is used to recognize visitors who chat with you via the chatflows tool. If the visitor leaves your site before they're added as a contact, they will have this cookie associated with their browser. With the Consent to collect chat cookies setting turned on: If you chat with a visitor who later returns to your site in the same cookied browser, the chatflows tool will load their conversation history.
The messagesUtk cookie will be treated as a necessary cookie. When the Consent to collect chat cookies setting is turned off, the messagesUtk cookie is controlled by the Consent to process setting in your chatflow. HubSpot will not drop the messagesUtk cookie for visitors who have been identified through the Visitor Identification API. The analytics cookie banner will not be impacted. This cookie will be specific to a subdomain and will not carry over to other subdomains. For example, the cookie dropped for info.example.com will not apply to the visitor when they visit www.example.com, and vice versa. It contains an opaque GUID to represent the current chat user.
6 Months HTTP
__zlcstore www.apsoparts.com This cookie is necessary for the chat-box function on the website to function. Persistent HTML
CookieConsent HubSpot Stores the user's cookie consent state for the current domain 1 year HTTP
form_key www.apsoparts.com Ensures visitor browsing-security by preventing cross-site request forgery. This cookie is essential for the security of the website and visitor. Session HTTP
mage-cache-sessid www.apsoparts.com This cookie is used in context with load balancing - This optimizes the response rate between the visitor and the site, by distributing the traffic load on multiple network links or servers. 1 day HTTP
mage-cache-storage www.apsoparts.com Used to optimize the loading speed on the website. This is done by pre-loading some procedures in the visitors' browser. Persistant HTML
mage-cache-storage-section-invalidation www.apsoparts.com Used to optimize the loading speed on the website. This is done by pre-loading some procedures in the visitors' browser. c HTML
mage-cache-storage-section-invalidation www.apsoparts.com This cookie is used in context with load balancing - This optimizes the response rate between the visitor and the site, by distributing the traffic load on multiple network links or servers. 1 day HTTP
mage-cache-timeout www.apsoparts.com This cookie is necessary for the 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. Persistant HTML
mage-messages www.apsoparts.com Necessary for the functionality of the website's chat-box function. 1 day HTTP
PHPSESSID www.apsoparts.com Preserves user session state across page requests. 1 day HTTP
private_content_version www.apsoparts.com  This cookie is necessary for the 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. 1 year HTTP
product_data_storage www.apsoparts.com Necessary for the compare-products function on the website. Persistant HTML
 recently_compared_product www.apsoparts.com Necessary for the compare-products function on the website. 1 day HTTP
X-Magento-Vary www.apsoparts.com This cookie is necessary for the 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. 1 day HTTP
_GRECAPTCHA Google This cookie is used to distinguish between humans and bots. This is beneficial for the website, in order to make valid reports on the use of their website. 179 days HTTP
CONSENT [x2] Google
YouTube
Used to detect if the visitor has accepted the marketing category in the cookie banner. This cookie is necessary for GDPR-compliance of the website. 2 years HTTP
rc::a Google This cookie is used to distinguish between humans and bots. This is beneficial for the website, in order to make valid reports on the use of their website. Persistent HTML
rc::b Google This cookie is used to distinguish between humans and bots. Session HTML
rc::c Google This cookie is used to distinguish between humans and bots. Session HTM
li_gc Google Stores the user's cookie consent state for the current domain 179 days HTTP
hubspotutk HupSpot This cookie keeps track of a visitor's identity. It is passed to HubSpot on form submission and used when deduplicating contacts. It contains an opaque GUID to represent the current visitor. 30 Minutes HTTP
_hssrc HubSpot 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. It contains the value "1" when present. Session HTTP

Preference cookies  enable a website to remember information that changes the way the website behaves or looks, like your preferred language or the region that you are in.

Name Provider Purpose Expiry Type
section_data_ids www.apsoparts.com Used in context with the shopping cart functionality. Remembers any wish-list products and visitor credentials when checking out. 1 day HTTP
store www.apsoparts.com Determines the preferred language of the visitor. Allows the website to set the preferred language upon the visitor's re-entry. 1 year HTTP
 STUID www.apsoparts.com Tracks the user’s interaction with the website’s search-bar-function. This data can be used to present the user with relevant products or services. 1 day HTTP
STVID www.apsoparts.com Tracks the user’s interaction with the website’s search-bar-function. This data can be used to present the user with relevant products or services. 1 day HTTP

Analytical cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

Name Provider Purpose Expiry Type
ga Google Registers a unique ID that is used to generate statistical data on how the visitor uses the website. 399 days HTTP
_ga_# Google Used by Google Analytics to collect data on the number of times a user has visited the website as well as dates for the first and most recent visit. 399 days HTTP
_gat Google Used by Google Analytics to throttle request rate 1 day HTTP
_gid Google Registers a unique ID that is used to generate statistical data on how the visitor uses the website. 1 day HTTP
ln_or LinkedIn Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator. 1 day HTTP
product_data_storage www.apsoparts.com Determines which products the user has viewed, allowing the website to promote related products. 1 day HTTP
recently_compared_product_previous www.apsoparts.com Necessary for the compare-products function on the website. 1 day HTTP
recently_viewed_product_previous www.apsoparts.com Collects information on which products have been viewed by the visitor - This is used for optimizing the specific visitor's navigation on the website. 1 day HTTP
ZD-buid www.apsoparts.com Unique id that identifies the user on recurring visits. Persistent HTML
AnalyticsSyncHistory LinkedIn Used in connection with data-synchronization with third-party analysis service. 29 days HTTP
__hszc HubSpot The main cookie for tracking visitors. It contains the domain, hubspotutk, initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session). 6 Months HTTP

Advertising cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

ZName Provider Purpose Expiry Type
_gcl_au Google Used by Google AdSense for experimenting with advertisement efficiency across websites using their services. 3 months HTTP
all www.apsoparts.com Tracks the user’s interaction with the website’s search-bar-function. This data can be used to present the user with relevant products or services. Persistent HTML
recently_compared_product www.apsoparts.com This cookie is used to determine which products the visitor has viewed. This information is used to promote related products and optimize ad-efficiency. Persistent HTML
recently_compared_product_previous www.apsoparts.com Collects information on which products have been viewed by the visitor - This is used for optimizing the specific visitor's navigation on the website. Persistent HTML
recently_viewed_product www.apsoparts.com Collects information on which products have been viewed by the visitor - This is used for optimizing the specific visitor's navigation on the website. Persistent HTML
recently_viewed_product_previous www.apsoparts.com Collects information on which products have been viewed by the visitor - This is used for optimizing the specific visitor's navigation on the website. Persistent HTML
section_data_clean www.apsoparts.com Determines which products the user has viewed, allowing the website to promote related products. 1 day HTTP
used www.apsoparts.com Tracks the user’s interaction with the website’s search-bar-function. This data can be used to present the user with relevant products or services. Persistent HTML
IDE Google Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user. 1 year HTTP
pagead/landing [x2] Google Collects data on visitor behaviour from multiple websites, in order to present more relevant advertisement - This also allows the website to limit the number of times that they are shown the same advertisement. Session Pixel
test_cookie Google Used to check if the user's browser supports cookies. 1 day HTTP
ads/ga-audiences Google Used by Google AdWords to re-engage visitors that are likely to convert to customers based on the visitor's online behaviour across websites. Session Pixel
pagead/1p-user-list/# Google Tracks if the user has shown interest in specific products or events across multiple websites and detects how the user navigates between sites. This is used for measurement of advertisement efforts and facilitates payment of referral-fees between websites. Session Pixel
bcookie LinkedIn Used by the social networking service, LinkedIn, for tracking the use of embedded services. 1 year HTTP
UserMatchHistory LinkedIn Ensures visitor browsing-security by preventing cross-site request forgery. This cookie is essential for the security of the website and visitor. 29 days HTTP
VISITOR_INFO1_LIVE YouTube Tries to estimate the users' bandwidth on pages with integrated YouTube videos. 179 days HTTP
YSC YouTube Registers a unique ID to keep statistics of what videos from YouTube the user has seen. Session HTTP
yt.innertube::nextId YouTube Registers a unique ID to keep statistics of what videos from YouTube the user has seen. Persistent HTML
ytidb::LAST_RESULT_ENTRY_KEY YouTube Stores the user's video player preferences using embedded YouTube video Persistent HTML
yt-remote-cast-available YouTube Stores the user's video player preferences using embedded YouTube video Session HTML
yt-remote-connected-devices YouTube Stores the user's video player preferences using embedded YouTube video Persistent HTML
yt-remote-device-id YouTube Stores the user's video player preferences using embedded YouTube video Persistent HTML
yt-remote-fast-check-period YouTube Stores the user's video player preferences using embedded YouTube video Session HTML
yt-remote-session-app YouTube Stores the user's video player preferences using embedded YouTube video Session HTML
yt-remote-session-name YouTube Stores the user's video player preferences using embedded YouTube video Session HTML

Unclassified cookies are cookies that we are in the process of classifying, together with the providers of individual cookies.


We do not use cookies of this type.
 

We and our advertising partners process your personal data using technology such as cookies in order to serve advertising, analyse our traffic and deliver customised experiences for you. You have a choice in who uses your data and for what purposes

Ad Settings

Some partners do not ask for your consent to process your data, instead, they rely on their legitimate business interest. View our list of partners to see the purposes they believe they have legitimate interest for and how you can object to it.

Find out more about how your personal data is processed and set your preferences below.

PURPOSESACCEPT ALL | REJECT ALL

You can set your consent preferences and determine how you want your data to be used based on the purposes below. Each purpose has a description so that you know how we and our partners use your data.

Store and/or access information on a device

Vendors can:

Store and access information on the device such as cookies and device identifiers presented to a user.
 Select basic ads

 Legitimate Interest

To do basic ad selection vendors can:

Use real-time information about the context in which the ad will be shown, to show the ad, including information about the content and the device, such as: device type and capabilities, user agent, URL, IP address
Use a user’s non-precise geolocation data
Control the frequency of ads shown to a user.
Sequence the order in which ads are shown to a user.
Prevent an ad from serving in an unsuitable editorial (brand-unsafe) context Vendors cannot:
Create a personalised ads profile using this information for the selection of future ads without a separate legal basis to create a personalised ads profile.
N.B. Non-precise means only an approximate location involving at least a radius of 500 meters is permitted.
 Create a personalised ads profile

 Legitimate Interest

To create a personalised ads profile vendors can:

Collect information about a user, including a user's activity, interests, demographic information, or location, to create or edit a user profile for use in personalised advertising.
Combine this information with other information previously collected, including from across websites and apps, to create or edit a user profile for use in personalised advertising.
 Select personalised ads

 Legitimate Interest

To select personalised ads vendors can:

Select personalised ads based on a user profile or other historical user data, including a user’s prior activity, interests, visits to sites or apps, location, or demographic information.
 Create a personalised content profile

 Legitimate Interest

To create a personalised content profile vendors can:

Collect information about a user, including a user's activity, interests, visits to sites or apps, demographic information, or location, to create or edit a user profile for personalising content.
Combine this information with other information previously collected, including from across websites and apps, to create or edit a user profile for use in personalising content.
 Select personalised content

 Legitimate Interest

To select personalised content vendors can:

Select personalised content based on a user profile or other historical user data, including a user’s prior activity, interests, visits to sites or apps, location, or demographic information.
 Measure ad performance

 Legitimate Interest

To measure ad performance vendors can:

Measure whether and how ads were delivered to and interacted with by a user
Provide reporting about ads including their effectiveness and performance
Provide reporting about users who interacted with ads using data observed during the course of the user's interaction with that ad
Provide reporting to publishers about the ads displayed on their property
Measure whether an ad is serving in a suitable editorial environment (brand-safe) context
Determine the percentage of the ad that had the opportunity to be seen and the duration of that opportunity
Combine this information with other information previously collected, including from across websites and apps Vendors cannot: *Apply panel- or similarly-derived audience insights data to ad measurement data without a Legal Basis to apply market research to generate audience insights (Purpose 9)
 Measure content performance

 Legitimate Interest

To measure content performance vendors can:

Measure and report on how content was delivered to and interacted with by users.
Provide reporting, using directly measurable or known information, about users who interacted with the content
Combine this information with other information previously collected, including from across websites and apps. Vendors cannot:
Measure whether and how ads (including native ads) were delivered to and interacted with by a user.
Apply panel- or similarly derived audience insights data to ad measurement data without a Legal Basis to apply market research to generate audience insights (Purpose 9)
 Apply market research to generate audience insights

 Legitimate Interest

To apply market research to generate audience insights vendors can:

Provide aggregate reporting to advertisers or their representatives about the audiences reached by their ads, through panel-based and similarly derived insights.
Provide aggregate reporting to publishers about the audiences that were served or interacted with content and/or ads on their property by applying panel-based and similarly derived insights.
Associate offline data with an online user for the purposes of market research to generate audience insights if vendors have declared to match and combine offline data sources (Feature 1)
Combine this information with other information previously collected including from across websites and apps. Vendors cannot:
Measure the performance and effectiveness of ads that a specific user was served or interacted with, without a Legal Basis to measure ad performance.
Measure which content a specific user was served and how they interacted with it, without a Legal Basis to measure content performance.
 Develop and improve products

 Legitimate Interest

To develop new products and improve products vendors can:

Use information to improve their existing products with new features and to develop new products
Create new models and algorithms through machine learning Vendors cannot:
Conduct any other data processing operation allowed under a different purpose under this purpose
SPECIAL PURPOSES

Ensure security, prevent fraud, and debug

To ensure security, prevent fraud and debug vendors can:

Ensure data are securely transmitted
Detect and prevent malicious, fraudulent, invalid, or illegal activity.
Ensure correct and efficient operation of systems and processes, including to monitor and enhance the performance of systems and processes engaged in permitted purposes Vendors cannot:
Conduct any other data processing operation allowed under a different purpose under this purpose. Note: Data collected and used to ensure security, prevent fraud, and debug may include automatically-sent device characteristics for identification, precise geolocation data, and data obtained by actively scanning device characteristics for identification without separate disclosure and/or opt-in.
Technically deliver ads or content

To deliver information and respond to technical requests vendors can:

Use a user’s IP address to deliver an ad over the internet
Respond to a user’s interaction with an ad by sending the user to a landing page
Use a user’s IP address to deliver content over the internet
Respond to a user’s interaction with content by sending the user to a landing page
Use information about the device type and capabilities for delivering ads or content, for example, to deliver the right size ad creative or video file in a format supported by the device Vendors cannot:
Conduct any other data processing operation allowed under a different purpose under this purpose
 

 

FEATURES

Match and combine offline data sources

Vendors can:

Combine data obtained offline with data collected online in support of one or more Purposes or Special Purposes.
Link different devices

Vendors can:

Deterministically determine that two or more devices belong to the same user or household
Probabilistically determine that two or more devices belong to the same user or household
Actively scan device characteristics for identification for probabilistic identification if users have allowed vendors to actively scan device characteristics for identification (Special Feature 2)
Receive and use automatically-sent device characteristics for identification

Vendors can:

Create an identifier using data collected automatically from a device for specific characteristics, e.g. IP address, user-agent string.
Use such an identifier to attempt to re-identify a device. Vendors cannot:
Create an identifier using data collected via actively scanning a device for specific characteristics, e.g. installed font or screen resolution without users’ separate opt-in to actively scanning device characteristics for identification.
Use such an identifier to re-identify a device.
SPECIAL FEATURESACCEPT ALL | REJECT ALL

 Use precise geolocation data

Vendors can:

Collect and process precise geolocation data in support of one or more purposes. N.B. Precise geolocation means that there are no restrictions on the precision of a user’s location; this can be accurate to within several meters.
 Actively scan device characteristics for identification

Vendors can:

Create an identifier using data collected via actively scanning a device for specific characteristics, e.g. installed fonts or screen resolution.
Use such an identifier to re-identify a device.
Coo

About

 

Cookies are small text files that can be used by websites to make a user's experience more efficient.

The law states that we can store cookies on your device if they are strictly necessary for the operation of this site. For all other types of cookies we need your permission.

This site uses different types of cookies. Some cookies are placed by third party services that appear on our pages.

You can at any time change or withdraw your consent from the Cookie Declaration on our website.

Learn more about who we are, how you can contact us and how we process personal data in our Privacy Policy.

Please state your consent ID and date when you contact us regarding your consent.