Cookie policy

1 Introduction

This Cookie Policy describes the use of cookies by the Gate Software group of companies (brand name “ALLOut Security”). Website address is: https://alloutsecurity.com/

Please also see our separate Privacy Policy, available on our website.

2 What are cookies?

Cookies are small text files which are transferred from our websites, applications or services and stored on your device.  This data often consists of a string of numbers and letters that identifies your computer, but it may also contain other information.

We will not use cookies except strictly necessary cookies until you have explicitly confirmed your consent.

3 Why do we use cookies?

We use cookies for purposes such as:
- Authenticating users when you log in to the website (through reCAPTCHA).
- Remembering user preferences and settings.
- Analysing site traffic and trends.
- Making your website interactions faster and more secure.
- Detecting fraud.

4 What cookies do we use?

The categories of cookies we use are:

Strictly necessary cookies.
ALLOut cookies: These are cookies that are required to enable you to browse our website and use its features, for example, to log into secure areas of our website.
- mfn-builder
- itsec_interstitial_browser
- wam_assigned_roles[0]
- wordpress_logged_in_
- wordpress_sec_
- wordpress_test_cookie
Google Recaptcha is a spam prevention system (Google Recaptcha) to ensure that our site is spam free. Read more here and here
- _GRECAPTCHA
- UULE
- NID
- CONSENT
Performance cookies: Google Analytics and Pardot allow us to recognise and count the number of visitors and see how visitors navigate our website e.g. how long a visitor stays at your site and which links they clicked on). This helps us to improve the way our website works. Vimeo cookies are placed by vimeo embedded videos, to allow you to view videos placed on the website.
Third-party cookies. Selected third parties may also set cookies on our website, for example to remember your preferences and settings, help you sign in, and analyse how well our website is working. In addition to the above, see LinkedIn Insight Tag: Conversion tracking gathers insights into post-click and view-through conversions of our LinkedIn ads campaigns.
For more information about a third party’s privacy practices, please consult the third party’s website or privacy or cookie policy.

5 How can you disable cookies?

ALLOut Security website visitors who do not wish to have any cookies placed on their computers should set their browsers to refuse cookies before using this website.  You can use the controls in your internet browser to limit how the website uses cookies and to withdraw your consent by clearing or blocking cookies.

As soon as you enter the website, you will be asked to click to confirm that you agree to or decline use of cookies, or to set your preferences regarding strictly necessary cookies, performance cookies, and third-party cookies. You can also go to “Privacy Settings” (bottom right corner of the screen) at any time to adjust your preferences or withdraw your consent and to find out more about the cookies we use.

Please note that you will not be able to log into the customer portal if cookies are disabled and you may not have access to certain features on the website. Removing all cookies from your device could also affect your subsequent visit to the website.

Cookie Policy last updated 16 May 2022

Discover our industry leading expertise

Industry Insights

Mitigating Controls – Should you use them?
July 1, 2021
Mitigating controls are never as desirable as an effective segregation of duties, but in some situations, a breach of a security rule may just have to exist.

Access Denied: How to avoid Role Permission Help-Desk Questions
June 30, 2021
Top tips for setting up best practice, process-based roles that will help to ensure your organization and its employees face minimal business interruption.
Watch On-Demand

Upcoming live events

No upcoming webinars found

Empower your security team

Save time, enhance risk visibility and be audit-ready with ALLOut Security for JD Edwards.

Request a Demo

Cookie name	Default expiration time	Description
_ga	2 years	Used to distinguish users.
_gid	24 hours	Used to distinguish users.
_ga_<container-id>	2 years	Used to persist session state.
_gac_gb_<container-id>	90 days	Contains campaign related information. If you have linked your Google Analytics and Google Ads accounts, Google Ads website conversion tags will read this cookie unless you opt-out. Learn more.

visitor_id<accountid>	The visitor cookie includes a unique visitor ID and the unique identifier for your account. For example, the cookie name visitor_id12345 stores the visitor ID 1010101010. The account identifier, 12345, 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.
pi_opt_in<accountid>	If Tracking Opt-in preferences is enabled, 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.
visitor_id<accountid>-hash	The visitor hash cookie contains the account ID and stores a unique hash. For example, the cookie name visitor_id12345-hash stores the hash “855c3697d9979e78ac404c4ba2c66533”, and the account ID is 12345. 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.
lpv<accountid>	This LPV cookie is set to keep Pardot from tracking multiple page views on a single asset over a 30-minute session. For example, if a visitor reloads a landing page several times over a 30-minute period, this cookie keeps each reload from being tracked as a page view.
pardot	A session cookie named pardot is set in your browser while you’re logged in to Pardot as a user or when a visitor accesses a form, landing page, or page with Pardot tracking code. The cookie denotes an active session and isn’t used for tracking.

Cookie name	Default expiration time	Description
_ga	2 years	Used to distinguish users.
_gid	24 hours	Used to distinguish users.
_ga_<container-id>	2 years	Used to persist session state.
_gac_gb_<container-id>	90 days	Contains campaign related information. If you have linked your Google Analytics and Google Ads accounts, Google Ads website conversion tags will read this cookie unless you opt-out. Learn more.

visitor_id<accountid>	The visitor cookie includes a unique visitor ID and the unique identifier for your account. For example, the cookie name visitor_id12345 stores the visitor ID 1010101010. The account identifier, 12345, 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.
pi_opt_in<accountid>	If Tracking Opt-in preferences is enabled, 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.
visitor_id<accountid>-hash	The visitor hash cookie contains the account ID and stores a unique hash. For example, the cookie name visitor_id12345-hash stores the hash “855c3697d9979e78ac404c4ba2c66533”, and the account ID is 12345. 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.
lpv<accountid>	This LPV cookie is set to keep Pardot from tracking multiple page views on a single asset over a 30-minute session. For example, if a visitor reloads a landing page several times over a 30-minute period, this cookie keeps each reload from being tracked as a page view.
pardot	A session cookie named pardot is set in your browser while you’re logged in to Pardot as a user or when a visitor accesses a form, landing page, or page with Pardot tracking code. The cookie denotes an active session and isn’t used for tracking.

Cookie policy

1 Introduction

2 What are cookies?

3 Why do we use cookies?

4 What cookies do we use?

5 How can you disable cookies?

1 Introduction

2 What are cookies?

3 Why do we use cookies?

4 What cookies do we use?

5 How can you disable cookies?

Discover our industry leading expertise

Industry Insights

Mitigating Controls – Should you use them?

On-demand webinars

Access Denied: How to avoid Role Permission Help-Desk Questions

Upcoming live events

Empower your security team