Cookie Policy

ARC MICROTECH LIMITED – COOKIE POLICY

Please read this cookie policy carefully as it contains important information on who we are and how we use cookies on our website. This policy should be read together with our Privacy Policy which sets out how and why we collect, store, use and share personal information generally, as well as your rights in relation to your personal information and details of how to contact us and supervisory authorities if you have a complaint.

Who We Are

This website is operated by ARC MICROTECH LIMITED (collectively referred to as “Arc Microtech“, “we“, “us” or “our” in this cookie policy).

For more information about Arc Microtech see our homepage.

Our Website

This cookie policy only relates to your use of our website.

Throughout our website we may link to other websites owned and operated by certain trusted third parties who make additional products and services available to you. These other third-party websites may also use cookies or similar technologies in accordance with their own separate policies. For privacy information relating to these other third-party websites, please consult their policies as appropriate.

Cookies

A cookie is a small text file which is placed onto your device (eg computer, smartphone or other electronic device) when you use our website. We use cookies on our website. These help us recognise you and your device and store some information about your preferences or past actions.

For example, we may monitor how many times you visit the website, which pages you go to, traffic data, location data and the originating domain name of your internet service provider. This information helps us to build a profile of our users. Some of this data will be aggregated or statistical, which means that we will not be able to identify you individually.

For further information on our use of cookies, including a detailed list of your information which we and others may collect through cookies, please see below.

For further information on cookies generally, including how to control and manage them, visit the guidance on cookies published by the UK Information Commissioner’s Office, www.aboutcookies.org or www.allaboutcookies.org.

Consent to use Cookies

We will ask for your permission to place cookies or other similar technologies on your device, except where they are essential for us to provide you with a service that you have requested (e.g. to enable you to put items in your shopping basket and use our check-out process).

You can choose not to consent or you can block cookies at a later date by activating the setting on your browser that allows you to refuse the setting of all or some cookies.

Our use of Cookies

The table below provides more information about the cookies we use and why:

Cookie Name Purpose More information
WordPress wordpress_[hash] cookie Users are those people who have registered an account with the WordPress site.

On login, WordPress uses the wordpress_[hash] cookie to store your authentication details. Its use is limited to the Administration Screen area, /wp-admin/

After login, WordPress sets the wordpress_logged_in_[hash] cookie, which indicates when you’re logged in, and who you are, for most interface use.

WordPress also sets a few wp-settings-{time}-[UID] cookies. The number on the end is your individual user ID from the users database table. This is used to customize your view of admin interface, and possibly also the main site interface.

https://wordpress.org/support/article/cookies/
WordPress Non-Version-Specific Data #

 

The actual cookies contain hashed data, so you don’t have to worry about someone gleaning your username and password by reading the cookie data. A hash is the result of a specific mathematical formula applied to some input data (in this case your user name and password, respectively). It’s quite hard to reverse a hash (bordering on practical infeasibility with today’s computers). This means it is very difficult to take a hash and “unhash” it to find the original input data.

WordPress uses the two cookies to bypass the password entry portion of wp-login.php. If WordPress recognizes that you have valid, non-expired cookies, you go directly to the WordPress Administration Screen. If you don’t have the cookies, or they’re expired, or in some other way invalid (like you edited them manually for some reason), WordPress will require you to log in again, in order to obtain new cookies.

https://wordpress.org/support/article/cookies/
WooCommerce

Session Cookie

woocommerce_cart_hash Helps WooCommerce determine when cart contents/data changes. https://docs.woocommerce.com/document/woocommerce-cookies/#section-2
WooCommerce

Session Cookie

woocommerce_items_in_cart Helps WooCommerce determine when cart contents/data changes. https://docs.woocommerce.com/document/woocommerce-cookies/#section-2
WooCommerce

Cookie (2 days’ duration)

wp_woocommerce_session_ Contains a unique code for each customer so that it knows where to find the cart data in the database for each customer. https://docs.woocommerce.com/document/woocommerce-cookies/#section-2
WooCommerce

Session Cookie

woocommerce_recently_viewed Powers the Recent Viewed Products widget. https://docs.woocommerce.com/document/woocommerce-cookies/#section-2
WooCommerce

Session Cookie

store_notice[notice id] Allows customers to dismiss the Store Notice. https://docs.woocommerce.com/document/woocommerce-cookies/#section-2
WooCommerce

Cookie (2 days’ duration)

woocommerce_snooze_suggestions__[suggestion] Allows dashboard users to dismiss Marketplace suggestions, if enabled. https://docs.woocommerce.com/document/woocommerce-cookies/#section-2
WooCommerce

Cookie (1 month duration)

woocommerce_dismissed_suggestions__[context] Count of suggestion dismissals, if enabled. https://docs.woocommerce.com/document/woocommerce-cookies/#section-2
WooCommerce

Session Cookie

tk_ai Stores a randomly-generated anonymous ID. This is only used within the dashboard (/wp-admin) area and is used for usage tracking, if enabled. https://docs.woocommerce.com/document/woocommerce-cookies/#section-2
Polylang PLL_COOKIE Polylang uses a cookie to remember the language selected by the user when they revisit the website. This cookie is also used to get the language information when not available in another way.
Google Analytics Google Analytics is a tool that helps website owners measure how users interact with website content and generates detailed statistics about the visitors to a website. The cookies are used to store details on how long a visitor spends on a website and where they came from.  We use this information to improve our Service and our website. The Google Analytics Opt-out Browser Add-on is available for Internet Explorer, Google Chrome, Mozilla Firefox, Apple Safari and Opera. https://developers.google.com/analytics/devguides/collection/analyticsjs/cookie-usage
Google Analytics

(2 years’ duration)

_ga Used to distinguish users. https://developers.google.com/analytics/devguides/collection/analyticsjs/cookie-usage
Google Analytics

(24 hours’ duration)

_gid Used to distinguish users. https://developers.google.com/analytics/devguides/collection/analyticsjs/cookie-usage
Google Analytics

(1 minute duration)

_gat Used to throttle request rate. If Google Analytics is deployed via Google Tag Manager, this cookie will be named _dc_gtm_<property-id>. https://developers.google.com/analytics/devguides/collection/analyticsjs/cookie-usage
Google Analytics (30 seconds to 1 year duration) AMP_TOKEN Contains a token that can be used to retrieve a Client ID from AMP Client ID service. Other possible values indicate opt-out, inflight request or an error retrieving a Client ID from AMP Client ID service. https://developers.google.com/analytics/devguides/collection/analyticsjs/cookie-usage
Google Analytics (90 days duration)

 

_gac_<property-id> Contains campaign related information for the user. https://developers.google.com/analytics/devguides/collection/analyticsjs/cookie-usage
Google Analytics

(2 years from set/update)

__utma Used to distinguish users and sessions. The cookie is created when the javascript library executes and no existing __utma cookies exists. The cookie is updated every time data is sent to Google Analytics. https://developers.google.com/analytics/devguides/collection/analyticsjs/cookie-usage
Google Analytics

(10 mins’ duration)

__utmt Used to throttle request rate. https://developers.google.com/analytics/devguides/collection/analyticsjs/cookie-usage
Google Analytics

(30 mins from set/update)

__utmb Used to determine new sessions/visits. The cookie is created when the javascript library executes and no existing __utmb cookies exists. The cookie is updated every time data is sent to Google Analytics. https://developers.google.com/analytics/devguides/collection/analyticsjs/cookie-usage
Google Analytics

(End of browser session)

__utmc Not used in ga.js. Set for interoperability with urchin.js. Historically, this cookie operated in conjunction with the __utmb cookie to determine whether the user was in a new session/visit. https://developers.google.com/analytics/devguides/collection/analyticsjs/cookie-usage
Google Analytics

(6 months’ duration)

__utmz Stores the traffic source or campaign that explains how the user reached our Service or website. The cookie is created when the javascript library executes and is updated every time data is sent to Google Analytics. https://developers.google.com/analytics/devguides/collection/analyticsjs/cookie-usage
Google Analytics

(2 years from set/update)

__utmv Used to store visitor-level custom variable data. This cookie is created when a developer uses the _setCustomVar method with a visitor level custom variable. This cookie was also used for the deprecated _setVar method. The cookie is updated every time data is sent to Google Analytics. https://developers.google.com/analytics/devguides/collection/analyticsjs/cookie-usage
Google Analytics

(18 months’ duration)

__utmx Used to determine a user’s inclusion in an experiment. https://developers.google.com/analytics/devguides/collection/analyticsjs/cookie-usage
Google Analytics

(18 months’ duration)

__utmxx Used to determine the expiry of experiments a user has been included in. https://developers.google.com/analytics/devguides/collection/analyticsjs/cookie-usage
Google Analytics

(Depends on the length of the experiment but typically 90 days.)

_gaexp Used to determine a user’s inclusion in an experiment and the expiry of experiments a user has been included in. https://developers.google.com/analytics/devguides/collection/analyticsjs/cookie-usage

Third-Party Access to the Cookies

The cookies we use will only be accessed by us and those third parties named in the table above for the purposes referred to in this cookie policy. Those cookies will not be accessed by any other third party.

How to Turn off all Cookies and Consequences of doing so

If you do not want to accept any cookies, you may be able to change your browser settings so that cookies (including those which are essential to the services requested) are not accepted. If you do this, please be aware that you may lose some of the functionality of our website.

For further information about cookies and how to disable them please go to the guidance on cookies published by the UK Information Commissioner’s Office, www.aboutcookies.org or www.allaboutcookies.org

How to Contact us

Please contact us if you have any questions about this cookie policy or the information we hold about you.

If you wish to contact us please send an email to admin@arcmicrotech.com.

Changes to this Policy

This policy was published on 2nd January 2020.

We may change this policy from time to time, when we do, we will inform you via a notification on our website or by email.