Cookie Policy
You can set your devices to accept all cookies, to notify you when a cookie is issued, or not to receive cookies at any time.
Securitas uses cookies on the website in order to enhance your experience, but not all cookies, or similar technologies, are necessary for the website to function. You accept the usage of some or all categories of cookies on our website by selecting the “Accept” button, or by adjusting the settings, in the cookie information banner on the bottom of the page.
What are cookies
A cookie is a small text file containing an identifier (a string of letters and numbers) that is sent by a web server to a web browser, and stored by the browser. The identifier is then sent back to the server each time the browser requests a page from the server. Cookies are used to enable web pages to function more efficiently as well as providing information to the web page owner. Cookies also make it possible to distinguish users from each other, which can give the user a more positive experience of the website.
The term cookie is the most used term but “cookies” actually describe a range of technologies, such as;
- Pixel tags,
- Mobile device identifiers, and
- Web storage used in desktop software or mobile devices.
When we refer to “cookies” in this policy we mean all such technologies.
There are a few different categories of cookies, including:
Session and persistent cookies
- Session cookies – these are cookies which expire once you close your web browser, and
- Persistent cookies – these are cookies which stay on your device for a set period of time or until you delete them.
First and third party cookies
- First-party cookies – these are cookies set by the website that you are visiting at the time, either by us, or by a third party at our request,
- Third-party cookies – these are cookies that are set by a party other than that of the website you are visiting. If you visit Securitas website or use Securitas services and another party sets a cookie through that website this would be a third-party cookie.
Cookies used on this website
We will/may send to you the following cookies:
- Campaign Page cookie
- Disclaimer Page cookie
- Language selector cookie
- Site Catalyst cookie
- Social media cookies (e.g. Facebook, LinkedIn, Google Analytics, and similar)
- YouTube video cookie
Our websites may include social media features or widgets, such as the Facebook Like button. Use of these features may allow them to collect your IP address, detect which page you are visiting on our site, and set a cookie to enable the feature to function properly. Your interactions with these features are governed by the privacy policy of the third party providing the function.
Google Analytics
Securitas uses Google Analytics, a web analytics service provided by Google, Inc. Google Analytics sets a cookie in order to evaluate your use of the website and compile reports for us on activity on the website.
Google stores the information collected by the cookie on servers. Google may also transfer this information to third parties where required to do so by law, or where such third parties process the information on Google's behalf. Google will not associate your IP address with any other data held by Google. By using the Securitas website, you consent to the processing of data about you by Google in the manner and for the purposes set out above.
Google’s privacy policy is available at: www.google.com/privacypolicy.html
How we use cookies
During the course of any visit to the Securitas website, the pages you see, along with any cookies, are downloaded to your device. Many websites do this, because cookies enable website publishers to do useful things like find out whether the device (and probably its user) has visited the website before. This is done on a repeat visit by examining any cookie left there on the last visit.
In order to be able to provide relevant information to our visitors, we need aggregated statistical visitor data that is collected by means of cookies.
Managing your cookies
Securitas will not use cookies to collect personally identifiable information about you. However, if you wish to restrict or block the cookies which are set by Securitas, or indeed any other website, you can do this through your browser settings on your computer or by not accepting cookies on the website. Each browser or mobile app is different, so check the "Help" menu of your browser to learn how to change your cookie preferences.
Alternatively, you may wish to visit https://www.aboutcookies.org/ which contains comprehensive information on how to do this on a wide variety of browsers. You will also find details on how to delete cookies from your computer as well as more general information about cookies. For information on how to do this on the browser of your mobile phone you will need to refer to your handset manual.
Browsing cookies
You can withdraw your consent for us to use cookies whenever you want by deleting the cookie “CookiesAccept” from our domain and reloading the website.
Please note that if you refuse cookies you may not be able to use all features within the website.
Mobile identifiers
On your mobile device, your operating system may provide you with additional options to opt out of tracking or to otherwise reset your mobile identifiers. For example, you may use the “Limit Ad Tracking” setting (on iOS devices) or a setting to “Opt out of Internet-Based Ads” (on Android).
How we use cookies
During the course of any visit to the Securitas website, the pages you see, along with any cookies, are downloaded to your device. Many websites do this, because cookies enable website publishers to do useful things like find out whether the device has visited the website before.
In order to be able to provide relevant information to our visitors, we need aggregated statistical visitor data that is collected by means of cookies.
Cookie List
A cookie is a small piece of data (text file) that a website – when visited by a user – asks your browser to store on your device in order to remember information about you, such as your language preference or login information. Those cookies are set by us and called first-party cookies. We also use third-party cookies – which are cookies from a domain different than the domain of the website you are visiting – for our advertising and marketing efforts. More specifically, we use cookies and other tracking technologies for the following purposes:
Strictly Necessary Cookies
These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms. You can set your browser to block or alert you about these cookies, but some parts of the site will not then work. These cookies do not store any personally identifiable information.
|
Cookie Name |
Cookies Used |
Host |
Purpose |
|
__cfduid |
Third Party |
cloudflare.com |
Used to override any security restrictions based on the IP address the visitor is coming from. |
|
ai_user |
First Party |
securitas.ie |
This is a unique user identifier cookie enabling counting of the number of users accessing the application over time. |
|
OptanonAlertBoxClosed |
First Party |
securitas.ie |
This cookie is set by websites using certain versions of the cookie law compliance solution from OneTrust. |
|
ARRAffinity |
First Party |
securitas.ie |
Used by Azure, it keeps track of connecting users by giving them a so-called 'affinity' cookie. This ensures the link between clients and the server they connect to for the entirety of their session. |
|
ASP.NET_SessionId |
First Party |
securitas.ie |
Used to identify the users' session on the server. The session used to store data in between off HTTP requests on server. |
|
OptanonConsent |
First Party |
securitas.ie |
Used to store cookie consent preferences. |
|
.EPiForm_VisitorIdentifier |
First Party |
securitas.ie |
This cookie is used to identify who is interacting with the application. |
|
__RequestVerificationToken |
First Party |
securitas.ie |
This is an anti-forgery token designed to stop unauthorised posting of content to the website. |
|
.EPiForm_BID |
First Party |
securitas.ie |
This cookie is for distinguishing one browser from other browsers that a visitor is using while surfing the internet. |
Performance Cookies
These cookies allow us to count visits and traffic sources, so we can measure and improve the performance of our site. They help us know which pages are the most and least popular and see how visitors move around the site. All information these cookies collect is aggregated and therefore anonymous. If you do not allow these cookies, we will not know when you have visited our site.
|
Cookie Name |
Cookies Used |
Host |
Purpose |
|
_ga |
First Party |
securitas.ie |
Monitors the performance of the website. |
|
_gid |
First Party |
securitas.ie |
Monitors the performance of the website. |
|
_gat_UA- |
First Party |
securitas.ie |
Targeting and advertising. |
|
_gat |
First Party |
securitas.ie |
Monitors the performance of the website. |
|
_ga_xxxxxx |
First Party |
securitas.ie |
Track page views and count sessions. |
|
_gid_xxxxx |
First Party |
securitas.ie |
Monitors the performance of the website. |
|
ai_session |
First Party |
securitas.ie |
Monitors the performance of the website. |
|
ai_user |
First Party |
securitas.ie |
Monitors the performance of the website. |
|
_hjIncludedInPageviewSample |
First Party |
securitas.ie |
Set to determine if a user is included in the data sampling defined by your site's pageview limit. |
|
_hjIncludedInSessionSample |
First Party |
securitas.ie |
Set to determine if a user is included in the data sampling defined by your site's daily session limit. |
|
_hjAbsoluteSessionInProgress |
First Party |
securitas.ie |
Used to detect the first pageview session of a user. |
|
_hjTLDTest |
First Party |
securitas.ie |
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. |
|
_hjHasCachedUserAttributes |
First Party |
securitas.ie |
Enables us to know whether the data set in _hjUserAttributes Local Storage item is up to date or not. |
|
_hjUserAttributesHash |
First Party |
securitas.ie |
Enables us to know when any User Attribute has changed and needs to be updated. |
|
_hjCookieTest |
First Party |
securitas.ie |
Checks to see if the Hotjar Tracking Code can use cookies. |
|
_hjLocalStorageTest |
First Party |
securitas.ie |
Checks if the Hotjar Tracking Code can use Local Storage. |
|
_hjSessionStorageTest |
First Party |
securitas.ie |
Checks if the Hotjar Tracking Code can use Session Storage. |
|
_hjSessionUser_{site_id} |
First Party |
securitas.ie |
"Set when a user first lands on a page. Persists the Hotjar User ID which is unique to that site. Ensures data from subsequent visits to the same site are attributed to the same user ID." |
|
_hjid |
First Party |
securitas.ie |
Hotjar cookie. This cookie is set when the customer first lands on a page with the Hotjar script. It is used to persist the random 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. |
|
_hjFirstSeen |
First Party |
securitas.ie |
Identifies a new user's first session on a website, indicating whether or not Hotjar's seeing this user for the first time. |
Functional Cookies
These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third-party providers whose services we have added to our pages. These cookies enable the personalisation of content, the recognition of users and remember user preferences (for example, your choice of language or region). They do not store directly personal information, but are based on uniquely identifying your browser and internet device. If you do not allow these cookies, then some or all of these services may not function properly.
|
Cookie Name |
Cookies Used |
Host |
Purpose |
|
EPI-MAR-<Content GUID> |
First Party |
securitas.ie |
Records a visitors interaction with a running optimization test. |
|
_grecaptcha |
Third Party |
google.com |
To be able to distinguish between humans and bots to avoid spam |
|
ld_session_origin |
Third Party |
leadoo.com |
To be able to detect where the current session begin. |
|
ld_al_exp |
Third Party |
leadoo.com |
To be able to see when the session is about to expire. |
|
ld_bot_consent |
Third Party |
leadoo.com |
To be able to know if a user has given consent to be tracked or not. |
|
ld_BOTID_open_time |
Third Party |
leadoo.com |
To be able to identify one bot from another technically. |
|
_hjSession_{site_id} |
First Party |
securitas.ie |
"Holds current session data. Ensures subsequent requests in the session window are attributed to the same session." |
|
_hjSessionTooLarge |
First Party |
securitas.ie |
"Causes Hotjar to stop collecting data if a session becomes too large. Determined automatically by a signal from the WebSocket server if the session size exceeds the limit." |
|
_hjSessionRejected |
First Party |
securitas.ie |
"If present, set to '1' for the duration of a user's session, when Hotjar has rejected the session from connecting to our WebSocket due to server overload. Applied in extremely rare situations to prevent severe performance issues." |
|
_hjSessionResumed |
First Party |
securitas.ie |
Set when a session/recording is reconnected to Hotjar servers after a break in connection. |
Targeting Cookies
These cookies record user's visit to a website, the individual pages visited and the links followed. These cookies can be set by us or a third party (for example, an advertising network) which also monitors traffic on other websites, this type of cookies may also be used to track user's movements across different website and to create profiles of their general online behaviour. Information collected by tracking cookies is commonly used to serve users with targeted online advertising and offers. These cookies do not store directly personal information, but are based on uniquely identifying your browser and internet device. If you do not allow these cookies, you will experience less targeted advertising.
|
Cookie Name |
Cookies Used |
Host |
Purpose |
|
ARRAffinitySameSite |
First Party |
securitas.ie |
Used for load balancing to make sure the visitor page requests are routed to the same server in any browsing session. |
|
VISITOR_INFO1_LIVE |
Third Party |
youtube.com |
Enables personalised recommendations on YouTube based on past views and searches |
|
YSC |
Third Party |
youtube.com |
Ensures that requests within a browsing session are made by the user, and not by other sites. This cookie prevent malicious sites from acting on behalf of a user without that user's knowledge. |
|
_guid |
Third Party |
Linkedin.com |
Used to identify a LinkedIn member for advertisements via Google Ads. |
|
li_giant |
Third Party |
Linkedin.com |
Indirect identifier for groups of LinkedIn Members used for conversion tracking |
|
UserMatchHistory |
Third Party |
Linkedin.com |
To provide ad delivery or retargeting for marketing purposes. |
|
_fbp |
Third Party |
Facebook.com |
This cookie is set by Facebook for the purpose of advertisement and analytics. |
|
fr |
Third Party |
Facebook.com |
To provide ad delivery or retargeting for marketing purposes. |
|
li_fat_id |
Third Party |
Linkedin.com |
This cookie is set by LinkedIn for LinkedIn Ads ID syncing, to remember a user’s language setting, facilitate data center selection, and store performed actions on the website |
|
cusid |
Third Party |
clickdimensions.com |
This cookie is used to establish and continue a user session with the site. |
|
cuvid |
Third Party |
clickdimensions.com |
This cookie is used to determine unique visitors to the site and it is updated with each page view. |
|
cuvon |
Third Party |
clickdimensions.com |
Used to signal the last time a visitor viewed a page. |
|
DYID |
Third Party |
dynamicyield.com |
To be able to personalize the customer experience and also for experimentation (A/B testing different experiences) |
|
_dyid |
First Party |
securitas.com |
To be able to personalize the customer experience and also for experimentation (A/B testing different experiences) |
|
_dyid_server |
First Party |
securitas.com |
To be able to personalize the customer experience and also for experimentation (A/B testing different experiences) |
|
_cfduid |
Third Party |
dynamicyield.com |
To be able to personalize the customer experience and also for experimentation (A/B testing different experiences) |
|
DYSES |
Third Party |
dynamicyield.com |
To be able to personalize the customer experience and also for experimentation (A/B testing different experiences) |
|
_dy_lu_ses |
First Party |
securitas.com |
To be able to personalize the customer experience and also for experimentation (A/B testing different experiences) |
|
_dy_ses_load_seq |
First Party |
securitas.com |
To be able to personalize the customer experience and also for experimentation (A/B testing different experiences) |
|
_dy_soct |
First Party |
securitas.com |
To be able to personalize the customer experience and also for experimentation (A/B testing different experiences) |
|
_dy_csc |
First Party |
securitas.com |
To be able to personalize the customer experience and also for experimentation (A/B testing different experiences) |
|
_dyexps, _dy_att_exps |
First Party |
securitas.com |
To be able to personalize the customer experience and also for experimentation (A/B testing different experiences) |
|
_dy_c_exps, _dy_c_att_exps |
First Party |
securitas.com |
To be able to personalize the customer experience and also for experimentation (A/B testing different experiences) |
|
_dy_device |
First Party |
securitas.com |
To be able to personalize the customer experience and also for experimentation (A/B testing different experiences) |
|
_dyprd |
First Party |
securitas.com |
To be able to personalize the customer experience and also for experimentation (A/B testing different experiences) |
|
_dyprdobj |
First Party |
securitas.com |
To be able to personalize the customer experience and also for experimentation (A/B testing different experiences) |
|
_dysvar |
First Party |
securitas.com |
To be able to personalize the customer experience and also for experimentation (A/B testing different experiences) |
|
_dy_csc_ses |
First Party |
securitas.com |
To be able to personalize the customer experience and also for experimentation (A/B testing different experiences) |
|
_dy_toffset |
First Party |
securitas.com |
To be able to personalize the customer experience and also for experimentation (A/B testing different experiences) |
|
_dyus_<section_id> |
First Party |
securitas.com |
To be able to personalize the customer experience and also for experimentation (A/B testing different experiences) |
|
_dyrc |
First Party |
securitas.com |
To be able to personalize the customer experience and also for experimentation (A/B testing different experiences) |
|
_dyfs |
First Party |
securitas.com |
To be able to personalize the customer experience and also for experimentation (A/B testing different experiences) |
|
dy_fs_page |
First Party |
securitas.com |
To be able to personalize the customer experience and also for experimentation (A/B testing different experiences) |
|
_dybatch |
First Party |
securitas.com |
To be able to personalize the customer experience and also for experimentation (A/B testing different experiences) |
|
_dycmc |
First Party |
securitas.com |
To be able to personalize the customer experience and also for experimentation (A/B testing different experiences) |
|
_dyjsession |
First Party |
securitas.com |
To be able to personalize the customer experience and also for experimentation (A/B testing different experiences) |
|
_dy_cs_storage_items |
First Party |
securitas.com |
To be able to personalize the customer experience and also for experimentation (A/B testing different experiences) |
|
_dy_df_geo |
First Party |
securitas.com |
To be able to personalize the customer experience and also for experimentation (A/B testing different experiences) |
|
_dy_geo |
First Party |
securitas.com |
To be able to personalize the customer experience and also for experimentation (A/B testing different experiences) |
|
_dy_svar_<section_id> |
First Party |
securitas.com |
To be able to personalize the customer experience and also for experimentation (A/B testing different experiences) |
|
_dyaud_sess |
First Party |
securitas.com |
To be able to personalize the customer experience and also for experimentation (A/B testing different experiences) |
|
_dyuss_<section_id> |
First Party |
securitas.com |
To be able to personalize the customer experience and also for experimentation (A/B testing different experiences) |
|
_dynuss_<section_id> |
First Party |
securitas.com |
To be able to personalize the customer experience and also for experimentation (A/B testing different experiences) |
|
_dy_cweather_<section_id> |
First Party |
securitas.com |
To be able to personalize the customer experience and also for experimentation (A/B testing different experiences) |
|
_dy_weather_<section_id> |
First Party |
securitas.com |
To be able to personalize the customer experience and also for experimentation (A/B testing different experiences) |
|
_dy_tsrc |
First Party |
securitas.com |
To be able to personalize the customer experience and also for experimentation (A/B testing different experiences) |
|
_dyaud_nchc |
First Party |
securitas.com |
To be able to personalize the customer experience and also for experimentation (A/B testing different experiences) |
|
_dyaud_page |
First Party |
securitas.com |
To be able to personalize the customer experience and also for experimentation (A/B testing different experiences) |
|
_dycnst |
First Party |
securitas.com |
To be able to personalize the customer experience and also for experimentation (A/B testing different experiences) |
|
_dy_device |
First Party |
securitas.com |
To be able to personalize the customer experience and also for experimentation (A/B testing different experiences) |
|
_dycst |
First Party |
securitas.com |
To be able to personalize the customer experience and also for experimentation (A/B testing different experiences) |
|
_fbp |
First Party |
securitas.com |
To be able to measure Facebook campaigns and effectiveness of the campaigns |
|
bscookie |
Third Party |
linkedin.com |
To be able to measure Linkedin campaigns and effectiveness of the campaigns |
|
UserMatchHistory |
Third Party |
linkedin.com |
This cookie is used by LinkedIn Ads to help measure advertising performance. More information can be found in Linkedin cookie policy |
|
lang |
Third Party |
linkedin.com |
This cookie is used to set default locale/language. |
|
bcookie |
Third Party |
linkedin.com |
This cookie is used by LinkedIn for identifying the Browser ID. It is set from LinkedIn share buttons and ad tags. |
|
lidc |
Third Party |
linkedin.com |
This cookie is used for routing from Share buttons and ad tags |
|
AnalyticsSyncHistory |
Third Party |
linkedin.com |
This cookie is used by LinkedIn Ads to help measure advertising performance. More information can be found in Linkedin cookie policy |
|
ld_id |
Third Party |
leadoo.com |
To be able to identify the user's device. |
|
ld_co |
Third Party |
leadoo.com |
To be able to keep track of which company a user is from. |
|
ld_cinf |
Third Party |
leadoo.com |
To be able to track company firmographics about the company the visitor is representing and do personalization on its basis. |
|
ld_session_id |
Third Party |
leadoo.com |
To be able to securely hook a client to a server and vice versa and thus keep up the connection. |
|
ld_env |
Third Party |
leadoo.com |
To be able to collect website visitor source and send that to the server. |
|
(Etag header) |
Third Party |
iapi.leadoo.com |
To be able to connect two sessions together. |
|
lidc |
Third Party |
linkedin.com |
This cookie is used for routing from Share buttons and ad tags |
|
sec_utm |
First Party |
securitas.ie |
The purpose of this cookie is to track the effectiveness of marketing campaigns. |
|
userSource |
First Party |
securitas.ie |
To be able to collect UTM Tags for users after revisiting the website |
Contact information
If you have any queries or concerns about the policies set out above, please do not hesitate to contact Securitas Ireland via the contact details below:
Contact our privacy team on
Security breach management team
Att: Data Privacy
Securitas Security Services Ireland
Suite 7/8, Bracetown Business Park,
Clonee,
Dublin 15, D15 K8NP
Republic of Ireland
Email address: gdpr@securitas.ie
Contact our data protection officer on
Mr. Paul Leonard
Att: Data Protection Officer
Securitas Security Services Ireland
Suite 7/8, Bracetown Business Park,
Clonee,
Dublin 15, D15 K8NP
Republic of Ireland
Email address: paul.leonard@securitas.ie
