Cookies Policy

About us

This website is operated by the Information Security Forum Limited (the ‘ISF’), a UK registered company (04822538). Our registered address is Information Security Forum Limited, Elder House St Georges Business Park, 207 Brooklands Road, Weybridge, Surrey, United Kingdom, KT13 0TS.

The purpose of this document

This document is intended to help website users understand which cookies we use, explain what a cookie is, why we use cookies and who to contact if wishing to discuss the use of cookies.

What are cookies?

Cookies are small text files which we place on your computer to aid accessibility when browsing our website and using website features. They also allow us to maintain website connections and provide other information relating to your use of our website.

Why use cookies?

Cookies help to deliver a tailored webpage, they also help us understand which webpages, features and content are most popular. They aid accessibility and help manage your connection by storing previously entered information such as your name, contact details and logon credentials.

Cookies we use

The ISF may place the following cookies onto your computer:

Name Purpose Cookie Type Expiry
complianceCookieISF The cookie is set to record the user consent for the cookies. Necessary 1 year
PHPSESSID The PHPSESSID cookie enables the website to store serialised state data. It is used to establish a user session and to pass state data via a temporary cookie, which is commonly referred to as a session cookie. (expires when you close your browser) Necessary Session
__atuvc This cookie is set by Addthis to make sure you see the updated count if you share a page and return to it before our share count cache is updated. Functional 13 months
__atuvs This cookie is set by Addthis to make sure you see the updated count if you share a page and return to it before our share count cache is updated. Functional 30 minutes
NID This is a preference cookie set by Google. This cookie contains an ID that is used by Google to set your preferences. It is required by the site to enable Google’s reCAPTCHA service which is used to protect various parts of the site from attack by bots. Functional 6 months
visitor_id[accountid] The visitor cookie includes a unique visitor ID and the unique identifier for your account. The account identifier makes sure that the visitor is tracked on the correct Pardot account. The visitor value is the visitor_id in your Pardot account. This cookie is set for visitors by the Pardot tracking code. Functional
pi_opt_in[accountid] The pi_opt_in cookie is set with a true or false value when the visitor opts in or out of tracking. If a visitor opts in, the value is set to true, and the visitor is cookied and tracked. If the visitor opts out or ignores the opt-in banner, the opt-in cookie value is set to false. The visitor cookie is disabled, and the visitor is not tracked. Functional
visitor_id[accountid]-hash The visitor hash cookie contains the account ID and stores a unique hash. This cookie is a security measure to make sure that a malicious user can’t fake a visitor from Pardot and access corresponding prospect information. Functional
_ga/_gat/_gid These cookies are set by Goolge to collect information about how visitors use the website. We use the information to compile reports and to help us improve the website. The cookies collect information in a way that does not directly identify anyone, including the number of visitors to the website and blog, where visitors have come to the website from and the pages they visited. Performance 1 minute
loc This cookie is set by Addthis to store location data. Performance 13 months
ssc These cookies track sharing when the AddThis functionality is used Performance 13 months
uvc Measures how often we see an AddThis user Performance 13 months
xtc Anonymously tracks user behaviour on the websites that allow a user to share pages on social media using the AddThis tool. AddThis log the anonymous use to generate usage trends to improve the relevance of their services and advertising. Performance 2 years
YSC This cookie is set by Youtube and is used to track the views of embedded videos. Performance session
VISITOR_INFO1_LIVE This cookie is set by Youtube. Used to track the information of the embedded YouTube videos on a website. Performance 6 months
vuid This cookie is set by Vimeo to store the user’s usage history. Performance 2 years
vuid This cookie is set by Livestream to store the user’s usage history. Performance 2 years
__hstc This cookie is set to track 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). Performance 13 months
_hjTLDTest 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. Performance Session
_hjid Hotjar cookie that is 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 behavior in subsequent visits to the same site will be attributed to the same user ID. Performance 1 year
hubspotutk This cookie is used to keep track of a visitor’s identity. This cookie is passed to HubSpot on form submission and used when deduplicating contacts. Performance 13 months
__hssrc Whenever HubSpot changes the session cookie, this cookie is also set. We set it to 1 and use it to determine if the visitor has restarted their browser. If this cookie does not exist when we manage cookies, we assume it is a new session. Performance session
__hstc The main cookie for tracking visitors. It contains the domain, utk (see below), initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session). Performance 2 years
__Secure-3PSID For targeting purposes to build a profile of the website visitor’s interests in order to show relevant & personalised Google advertising Advertising 2 years
Secure-3PAPISID For targeting purposes to build a profile of the website visitor’s interests in order to show relevant & personalised Google advertising Advertising 2 years
__Secure-3PSIDCC For targeting purposes to build a profile of the website visitor’s interests in order to show relevant & personalised Google advertising Advertising 1 year

We do not use so-called tracking cookies that monitor your use of other websites, nor do we us cookies that gather data on your browsing activities for marketing purposes.

Personal data we collect via cookies

Cookies capture your computer’s unique online electronic identifier; this is known as an IP address. Your IP address is considered to form personal data under data privacy laws, other personal data may be data relating to your name and contact details.

You can prevent one provider, Google, from capturing any data relating to your use of our website by visiting http://tools.google.com/dlpage/gaoptout.

You can also block cookies by activating the appropriate setting within your browser. However, doing so may impact your use of this website.

Please see our privacy policy for further information on how we collect, use and protect your personal data, including your IP address.

Further information

Please contact our Data Protection Officer if you have any questions regarding the use of cookies by writing to:

The Data Protection Officer

Information Security Forum
10 Eastcheap
London
EC3M 1AJ
You can also contact us via email at info@securityforum.org or by calling +44 (0)203 875 6868.Changes to this Notice

We may change the content within this Notice from time to time. This may be necessary for example to:

  • reflect changes to relevant laws;
  • changes to how we process personal data; and
  • changes to cookie functionality.

Any changes will be published via www.securityforum.org