Cookies Policy
Introduction
Welcome to Shieldpay’s cookies policy. Shieldpay respects your privacy and is committed to protecting your personal data. Our cookie policy is a statement of policy on what cookies are active on our website, what user data we track, for what purpose and where this data is sent.
This policy is separate to our privacy notice which sets out how we collect, obtain and process your data.
You can find our privacy notice on our website. This cookies policy is provided in a layered format so you can click through to the specific areas. Please also use the Definitions section to understand the meaning of some of the terms used in this cookies policy.
Shieldpay Ltd is responsible for your personal data – collectively referred to as Shieldpay, we, us or our as set out in this policy – we have no control over third party cookies. If you have any questions about this policy or how we handle your personal information, please contact us on privacy@shieldpay.com or visit our Support section on our website.
Shieldpay are registered with Information Commissioner’s Office, and you have the right to complain to them should you find that we have not satisfactorily processed cookies in line with this policy, our regulatory obligations or your legal rights.
TABLE OF CONTENTS
1. The use of cookies by Shieldpay
Why we use Cookies
We use cookies to distinguish you from other Shieldpay users on our website(s). This helps us to provide you with a good experience when you browse our website(s) and also allows us to improve our services and our website(s).
A cookie is a small file of letters and numbers that we store on your browser or the hard drive of your computer if you agree. Cookies contain information that is transferred to your computer's hard drive.
Blocking Cookies
You can block cookies by activating the setting on your browser that allows you to refuse the setting of all or some cookies. In order to block cookies, follow the instructions provided by your browser (usually located within the “settings”, “help” “tools” or “edit” facility). Many browsers are set to accept cookies until you change your settings.
If you use your browser settings to block all cookies (including essential cookies) you may not be able to access all or parts of the website(s). For example, we may not be able to recognise your computer or mobile device and you may need to log in every time you visit our website(s).
How you find more information on cookies
For further information about cookies, including how to see what cookies have been set on your computer or mobile device and how to manage and delete them, visit www.allaboutcookies.org and www.youronlinechoices.com/uk.
2. Which cookies we use
We use the following cookies:
Strictly necessary cookies. These are cookies that are required for the operation of the website(s). For example, they include cookies that enable you use to log into secure areas of the website(s).
Analytical/performance cookies. These allow us to recognise and count the number of visitors, track views of content and to see how users move around the website(s) when and how they are using it. This helps us to improve the way the website(s) works, by ensuring that Shieldpay users are finding what they are looking for easily.
Functionality cookies. These are used to recognise you when you return to the website(s) or if you have logged into the website(s) already. This enables us to personalise our content for you, greet you by name and remember your preferences.
Tracking cookies. These enable us to track use of content from the website(s) (on third party services, such as posts on social media networks), in accordance with your third-party settings and your permission, which enables us to provide you with personalised experiences when interacting with our website or services.
Targeting cookies. These cookies record your visit to the website(s), the pages you have visited and the links you have followed. We will use this information to make the website(s) more relevant to your interests. In accordance with our legitimate interests, we may also share this information with third parties for this purpose. Where we use such cookies for the purposes of marketing or commercial messages we will seek to obtain your permission before doing so.
You can find more information about the individual cookies we use and the purposes for which we use them in the table below:
|
Cookie Name |
Provider |
Purpose |
Duration |
|
Strictly Necessary |
|||
|
__cf_bm |
Hubspot |
|
1 day |
|
__cf_bm |
Shieldpay |
Used by Cloudflare to read and filter requests from bots. |
30 min |
|
__cfruid |
Shieldpay |
Used by Cloudflare to manage incoming traffic and to have better visibility on the origin of a particular request. |
Session: deleted after user exits |
|
__zlcstore |
Shieldpay |
To store the status of the chat. |
Persistent |
|
ASP.NET_SessionId |
Shieldpay |
Stores a ‘Session ID’ which is used by Microsoft .NET Framework to deliver the web pages to the visitor |
Session: deleted after user exits |
|
ASPXAUTH |
Shieldpay |
A cookie to identify if the user is authenticated (that is, has their identity been verified). |
1 day |
|
AWSALBCORS |
Shieldpay |
To provide load balancing functionality. |
6 days |
|
bscookie |
|
|
1 year |
|
cookietest |
Shieldpay |
Used to determine if the website user browser supports cookies |
Session |
|
li_gc |
|
Used to store consent of guests regarding the use of cookies for non-essential purposes |
179 days |
|
ZD-suid |
Shieldpay |
Used to store a unique session ID. |
Persistent
|
|
.AspNet.Two |
Shieldpay |
Facilitate two factor authentication |
Session: deleted after user exits |
|
__Request |
Shieldpay |
Anti forgery token (prevent CSRF attack). It guarantees that the poster is the one who gets the form. |
Session: deleted after user exits |
|
.AspNet.Application |
Shieldpay |
Created when you use cookie authentication in your application. This cookie is created by the server on user request and is stored by the browser. |
Session: deleted after user exits |
|
Statistics |
|||
|
_dc_gtm_UA-# |
Shieldpay |
Statistics |
1 day |
|
_ga |
Shieldpay |
ID used to identify users
|
2 years |
|
_ga_# |
Shieldpay |
ID used to identify users
|
2 years |
|
_gid |
Shieldpay |
ID used to identify users for 24 hours after last activity
|
1 day |
|
_gat |
Shieldpay |
This cookie is used to throttle request rate. These are third party cookies that are placedon your device to allow us to use the Google Analytics service. These cookies are used to collect information about how visitors use our website. |
1 minute |
|
_vwo_uuid_v2 |
Shieldpay |
Statistics |
1 year |
|
AnalyticsSync |
|
|
29 days |
|
ZD-buid |
Shieldpay |
Used by Zendesk to store unique user ID. |
Persistent |
|
Preferences |
|||
|
lidc |
|
Used by the social networking service, LinkedIn, for tracking the use of embedded services.
|
1 day |
|
ZD-store |
Shieldpay |
To provide Zendesk functions across pages. |
Persistent |
|
__hssc |
Shieldpay |
This is used to determine if HubSpot should increment the session number and timestamps in the __hstc cookie. |
30 minutes |
|
__hssrc |
Shieldpay |
Whenever HubSpot changes the session cookie, this cookie is also set to determine if the visitor has restarted their browser. |
Session: deleted after user exits |
|
__hs_initial_opt_in |
Shieldpay |
This cookie is used to prevent the banner from always displaying when visitors are browsing in strict mode. |
7 days |
|
__hs_opt_out |
Shieldpay |
This cookie is used by the opt-in privacy policy to remember not to ask the visitor to accept cookies again. |
6 months |
|
__hstc |
Shieldpay |
The main cookie for tracking visitors. (Hubspot) |
6 months |
|
wooTracker |
Shieldpay |
Woopra tracks customer’s web and mobile activity, forms, and provides customer Analytics |
1 month |
|
ln_or |
Shieldpay |
Used to determine if Oribi analytics can be carried out on a specific domain (LinkedIn) |
1 day |
|
onfido-js-sdk |
Shieldpay |
Woopra tracks customer’s web and mobile activity, forms, and provides customer Analytics |
1 month |
|
Marketing |
|||
|
__ptq.gif |
Hubspot |
Sends data to the marketing platform Hubspot about the visitor's device and behaviour. Tracks the visitor across devices and marketing channels. |
Session |
|
__zlcmid |
Shieldpay |
Used to store a unique user ID. |
1 year |
|
_gcl_au |
Shieldpay |
Used by Google AdSense for experimenting with advertisement efficiency across websites using their services. |
3 months |
|
ads/ga-audiences |
|
Used to store information for remarketing purposes. |
Session |
|
bcookie |
|
Used by LinkedIn to track the use of embedded services. |
1 year |
|
UserMatchHistory |
|
These cookies are set by LinkedIn for advertising purposes, including: tracking visitors so that more relevant ads can be presented, allowing users to use the 'Apply with LinkedIn' or the 'Sign-in with LinkedIn' functions, collecting information about how visitors use the site, etc.
|
29 days |
|
VISITOR_INFO1 |
Youtube |
Tries to estimate the users' bandwidth on pages with integrated YouTube videos.
|
179 days |
|
YSC |
Youtube |
Registers a unique ID to keep statistics of what videos from YouTube the user has seen. |
Session |
|
ytidb::LAST_RESULT |
Youtube |
Stores the user's video player preferences using an embedded YouTube video. |
Persistent |
You can choose which cookies we can set by selecting your specific cookie preference.
You can withdraw your consent at any time. You can also use your browser setting to block all cookies (including essential cookies), however, if you do so, you may not be able to access all or parts of our website.
3. Third party cookies
The following third parties may also use cookies, over which we have no control. These cookies are likely to be analytical, performance or targeting cookies:
Google
DirectID
Visual Website Optimizer
LinkedIn
Hubspot
You should always check such third parties’ websites and policies to ensure you are in agreement with how they use cookies and process your data.