The cookies used on our publicly available website and those used on our supply chain management platform, which is restricted to Achilles’ customers only, are different. As such, the cookie information for the website and the platform are provide separately in this notice.
We update this cookie notice from time to time in response to changes in applicable laws and regulations and to changes on our website. When changes are made, we will update the ‘Last Updated’ date at the top of this page.
Please review this cookie notice periodically to check for updates.
Cookies are small text files and web beacons (sometimes called ‘pixels’) are small graphic images. They are downloaded to your device when you visit a website or receive certain emails unless you have set your browser to stop them.
We use several types of cookies on the public Achilles webiste. The types of cookie and web beacons we use on our website include:
These are essential to the operation of our website or platform and enable you to browse and use all features of the website or application.
Functionality cookies remember the choices you make when you visit our website or platform. This includes, for example, your choice of language and text sizing. They remember your preferences on return visits and tailor your use of our website or platform.
These cookies collect anonymous information about your use of our website or platform such as the pages you visit most often, how you arrived at the site or application and error message you receive. These do not collect any personal information and are used to improve our website or platform performance.
These are placed on our public website by trusted third-party suppliers to Achilles and help us count visitors to our website from advertisements we have placed on other websites or from emails we have sent to you. They provide aggregated information which we use to monitor the success of our marketing campaigns. We collect information about your use of our website to advertise using remarketing services, including Google Ads, to serve you ads that relate to your activity on our site. We do not use marketing cookies or pixels on our supply chain management platform.
Further technical details of each cookie used on this website can be found for our website and platform in the tables below. You can also learn more about cookies by going to http://www.allaboutcookies.org/.
You can manage and delete cookies and web beacons through your web browser. Each browser manages cookies differently, but you can learn more about cookie settings in the most common browsers using the links below:
• Safari for Mac
• Safari for iOS
• Internet Explorer
We use the following cookies on our public website at www.achilles.com:
|Achilles.com||PHPSESSID||Cookie generated by applications based on the PHP language. This is a general purpose identifier used to maintain user session variables. It is normally a random generated number, how it is used can be specific to the site, but a good example is maintaining a logged-in status for a user between pages.||Session|
|Achilles.com||catAccCookies||UK Cookie Consent WordPress plugin. Stores the user’s cookie consent for the current domain||30 days|
|Cloudflare||_cfduid||Used to by Cloudflare to help protect against DDOS attacks.||1 year|
|Achilles.com||_icl_visitor_lang_js||Remembers the user’s selected language version of a website||24 hours|
|Achilles.com||wpml_browser_redirect_test||Determines language selection for website visitors and redirect the website visitor to the correct language based on location. This language setting is then stored.||Session|
|Linked-In||lang||Remembers the user’s selected language version of a website||Session|
|Google.com||_dc_gtm_UA-#||Associated with sites using Google Tag Manager to load other scripts. Without it, other scripts may not function correctly.||1 day|
|Google.com||_ga||Monitors the use and performance of our website –distinguishes unique users by assigning a randomly generated number||2 years|
|Google.com||_gid||Used to distinguish users on Google Analytics in order to count user visits and traffic sources so that we can measure and improve the site performance||1 day|
|Google.com||Collect||Used to send data to Google analytics about your device and behavior. Usage of the site by your devices and marketing channels is tracked||Session|
|Achilles.com||_fbp||Used by Facebook to deliver a series of advertisement products from third party advertisers.||3 months|
|Google Analytics||_gat||This cookie is associated with Google Universal Analytics. It is used to throttle the request rate – limiting the collection of data on high traffic sites||1 day|
|Hubspot||_hssrc||This cookie is used to keep track of a visitor’s identity. It is passed to HubSpot on form submission and used when deduplicating contacts.||13 months|
|Hubspot||_hstc||Used for tracking visitors. 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).||13 months|
|Hubspot||_ptq.gif||Sends data to the marketing platform Hubspot about the visitor’s device and behaviour. Tracks the visitor across devices and marketing channels.||Session|
|Google.com||Ad/ga-audiences||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|
|Linkedin.com||bcookie||Browser ID cookie for sharing the content of the website via social media||2 years|
|Linkedin.com||bscookie||Browser ID cookie for tracking he use of embedded services||2 years|
|ads.linkedin.com||BizoID||LinkedIn Ad analytics to enable user-based content||29 days|
|Facebook.com||fr||Used by Facebook to deliver a series of advertisement products from third party advertisers||3 months|
|Hubspot||hubspotutk||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.||Session|
|Double click||IDE||Used 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|
|i/adsct||The cookie is used by Twitter.com in order to determine the number of visitors accessing the website through twitter advertisement content.||Session|
|Linkedin.com||lidc||Used by Linkedin for tracking the use of embedded services||1 day|
|Personalization_id||This cookie is set by Twitter – The cookie allows the visitor to share content from the website onto their Twitter profile.||2 years|
|Double click||Test_cookie||Used to check if the user’s browser supports cookies||1 day|
|Facebook.com||tr||Used by Facebook to deliver a series of advertisement products from third party advertisers||Session|
|linkedin.com||UserMatchHistory||LinkedIn Ad analytics used to track visitors on multiple websites in order to present relevant adverts based on visitor preferences||29 days|
We use the following cookies within our supply chain management platform. Access to the platform is restricted to authorised users working for Achilles’ customers:
|SnapEngage||SnapABugHistory||Used to keep track of the visitor visits and last chats.||12 Months|
|SnapEngage||SnapABugRef||Records visitor origin and site entry to display the referring URL to a chat agent to gain insight into the source of the visitor and the context of the chat.||2 Hours|
|SnapEngage||SnapABugVisit||Used to keep track of visitor visits and display number of visits and returning visits to a chat agent.||Session|
|SnapEngage||SnapABugChatSession||Set during an active chat in progress to keep track of the session so that a chat can persist across the pages of the site.||16 Minutes|
|SnapEngage||SnapABugNoProactiveChat||Used to control whether or not the SnapEngage chat widget should re-prompt the visitor with a proactive chat message.||30 Minutes|
|SnapEngage||SnapABugChatPoll||Tracking of the index of the chat messages received.||16 Minutes|
|SnapEngage||SnapABugChatView||Enforces that only one chat window is available for the user per active chat session.||16 Minutes|
|SnapEngage||SnapABugBanned||Records when a visitor is banned from chatting by agent (ban command) to prevent future chats.||30 Days|
|SnapEngage||SnapABugChatWindow||Records the position and minimized status of the chat box when the visitor navigates across the page.||30 Minutes|
|SnapEngage||SnapABugMinimizeStashCookie||Used for the detection of new messages while the chat is minimised.|
|SnapEngage||SnapABugAgentAvatar||Stores the agent image URL in order to show the agent avatar on the minimise state of the chat.||16 Minutes|
|MyAchilles||mystage_Green||Used to identify which swing environment is being presented to the client.||Session|
|MyAchilles||tykapi_stage||Used to identify which swing environment is being presented to the client.||Session|
|Userlane||userlane_context||Used to manage session information||Session|
|Userlane||userlane_user||Randomised identifier to identify a user, stored as a cookie.||Session|
|Azure B2C||x-ms-cpim-cache||Used for maintaining the request state.||Session|
|Azure B2C||x-ms-cpim-csrf||Cross-Site request forgery token used for CRSF protection.||Session|
|Azure B2C||x-ms-cpim-sso||Used for maintaining the SSO session. This cookie is set as persistent, when Keep Me Signed In is enabled.||Session|
|Azure B2C||x-ms-cpim-trans||Used for tracking the transactions (number of authentication requests to Azure AD B2C) and the current transaction.||Session|
|Heap||_hp2_id.APP_ID||Used to store user_id, identity, other ids||13 Months|
|Heap||_hp2_ses_props.APP_ID||Used to store timestamp and cookie domain/path||30 Minutes|
|Heap||_hp2_props.APP_ID||Used to store properties set by addEventProperties API||13 Months|
|Heap||_hp2_hld.*||Used to determine which domain a cookie can be set on||Session|