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 |
| 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 Google 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 |
| cebs | Used by Crazy Egg to track the current user session internally. | Performance | Session |
| cebsp | Used by Crazy Egg to determine if a survey should be shown. | Performance | Session |
| _ce.s | Track a recording visitor session unique ID, tracking host and start time | Performance | 1 year |
| 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 |
| 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 |
| 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 |
Cookies Policy
| Cookie | Name | Purpose |
| Cookie Notification | Isf_cookies | This cookie is set when the cookie notification bar is closed.
This cookie stores information about your visit and preferences, allowing us to customise our site targeted to your individual interests. |
| Downloads | Isf_downloaded | This cookie is set when data is submitted via downloaded forms.
This cookie stores information about your downloads, allowing us to customise our site and messaging targeted to your individual interests. |
| Last Visited Page | Isf_event_referer | This cookie stores the last visited page to aid navigation. |
| Google Analytics | _ga | Google Analytics cookie is used to distinguish users.
This cookie allows us to estimate our audience size and usage patterns. |
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
London
You can also contact us via email at info@securityforum.org or by calling +44 (0) 203 875 6868. 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