On the website https://vigilant.es we use cookies to facilitate the relationship of visitors with our content and to allow us to compile statistics on the visitors we receive.
In compliance with Directive 2009/136 / CE, developed in our ordinance by the second paragraph of article 22 of the Law on Information Society Services, following the guidelines of the Spanish Agency for Data Protection, we proceed to inform you in detail of the use that is made on our website.
Cookies are small files that are recorded in the browser used by each visitor to our website so that the server can remember the visit of that user later when they access our content again. This information does not reveal your identity, or any personal data, neither does it access the content stored on your pc, but it does allow our system to identify you as a specific user who has previously visited the web, viewed certain pages, etc. and it also allows you to save your personal preferences and technical information such as visits made or specific pages you visit.
The purpose of cookies is to provide the User with faster access to the selected Services.
If you do not want cookies to be saved in your browser or you prefer to receive information each time a cookie requests to be installed, you can configure your browsing options to do so. Most browsers allow the management of cookies in 3 different ways:
- Cookies are always rejected;
- The browser asks if the user wants to install each cookie;
- Cookies are always accepted;
Your browser may also include the ability to select in detail the cookies you want to be installed on your computer. Specifically, the user can normally accept any of the following options:
- reject cookies from certain domains;
- reject third-party cookies;
- accept cookies as non-persistent (they are deleted when the browser is closed);
- allow the server to create cookies for a different domain.
To allow, know, block or eliminate the cookies installed on your computer, you can do so by configuring the browser options installed on your computer.
You can find information on how to configure the most used browsers in the following locations:
Internet Explorer: Tools -> Internet Options -> Privacy -> Settings. For more information, you can consult Microsoft support or browser Help.
Firefox: Tools -> Options -> Privacy -> History -> Custom Settings. For more information, you can consult Mozilla support or browser Help.
Chrome: Settings -> Show advanced options -> Privacy -> Content settings. For more information, you can consult Google support or browser Help.
Safari: Preferences -> Security. For more information, you can consult Apple support or browser Help.
Regarding third-party cookies, that is, those that are unrelated to our website, we cannot be responsible for the content and veracity of the privacy policies that they include, so the information we offer you is always with reference to the source.
Below we inform you in detail of the cookies that can be installed from our website. Depending on your navigation, all or only some of them may be installed.
| Name | Category | Description | Property | Duration |
| wordpress_ | Functionality | It is activated during login and saves the authentication details. | Own | 1 year |
| wordpress_logged_in_ | Functionality | It is activated during login and saves the authentication details. | Own | 1 year |
| wp-settings- | Functionality | It is used to customize the User Interface. | Own | 1 year |
| _utma | Analysis | It is used to distinguish users and sessions. | Third parties | 2 years |
| _utmc | Analysis | Not used in ga.js. It is configured to interact with urchin.js. | Third parties | End of session |
| _utmz | Analysis | Stores the traffic source or the campaign that explains how the user got to the site. | Third parties | 6 months |
| catAccCookies | Functionality | It contains a code to verify that the cookie policy has been accepted. | Own | 1 day |
| autoptimize_feed | Functionality | Cookie used by the photo gallery when larger images are shown in a “pop-up window”. | Third parties | 1 year |
| fusion_metabox_tab_513 | Functionality | We do not know the origin of the cookie | Third parties | Unknown origin |
| fusion_metabox_tab_989 | Functionality | We do not know the origin of the cookie | Third parties | Unknown origin |
| cc_cookie_accept | Functionality | Permanent cookie that remembers whether or not the user accepts the use of cookies on this website | Third parties | Permanent |
| __utmz | Functionality | Anonymous browsing data that allows to know what is consulted and how to navigate within the webs. | Third parties | Session |
| _ga | Analysis | Used to distinguish users | Third parties | 2 years |
| ci_session | Functionality | Cookie associated with Codeigniter to build PHP-based applications. Used for Vigilant’s own applications | Own | Session |
| _gid | Analysis | Used to distinguish users | Third parties | 2 years |
| __hssrc | Functionality | Every time HubSpot changes the session cookie, this cookie is also set. It is used to determine if the visitor has restarted their browser. If this cookie does not exist when we manage cookies, it is assumed to be a new session. | Third parties | Session |
| hubspotutk | Functionality | Tracks the visitor. That information is transferred to Hubspot when the form is filled in to avoid duplicate contacts. | Third parties | 10 years |
| fusionredux_current_tab | Functionality | Cookie to improve the usability of the web | Third parties | 3 days |
| __hstc | Functionality | The main cookie for visitor tracking. Contains the domain, utk, initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session). | Third parties | 2 years |
| _drip_client_6994213 | Functionality | Technical cookie whose purpose is to improve the user experience of use. | Own | Persistent |
| __hssc | Functionality | This cookie keeps track of sessions. It is used to determine if we should increase the session number and timestamps in the __hstc cookie. Contains the domain, viewCount (increments each pageView in a session), and the session start timestamp. | Third parties | 30 minutes |
| _uetsid | Analysis | It is used to distinguish users. | Third parties | 30 minutes |
| wp-settings-time- | Functionality | It is used to customize the User Interface. | Own | End of session |
| pll_language | Functionality | Polylang is an extension for making multilingual WordPress websites. | Own | 1 year |
| fr | Analysis | Cookie to measure Facebook campaigns. | Third parties | 3 moths |
| driftt_aid | Functionality | Cookie used by Drift, chat service | Third parties | 2 years |
| _fbp | Functionality | Facebook cookie used to track visits to websites | Third parties | 3 months |
| driftt_eid | Functionality | Cookie used by Drift, chat service | Third parties | End of session |
| chat_user_token | Functionality | 1MillionBot cookie that creates a unique randomly generated ID that allows a user to be identified, and related to their information stored in the database of the chatbot in question. | Third parties | 5 years |
| et_bloom_unlockedoptin | Functionality | These cookies are stored when a user provides their email to view private content, so that if that user returns to the site, they do not have to enter their information again to view the same content. | Third parties | 1 year |
| et_bloom_optin_optin_2_mailchimp | Functionality | Bloom cookie used to collect email for visitor subscriptions and link them to the Mailchimp service | Third parties | Session |
| et_bloom_optin_optin_2 | Functionality | Bloom cookie used to collect email for visitor subscriptions | Third parties | Session |
This Cookies Policy can be modified according to legislative and regulatory requirements, or in order to adapt said policy to the instructions issued by the Spanish Agency for Data Protection, therefore Users are advised to visit it periodically.
When significant changes occur in this Cookies Policy, Users will be notified either through the web or through email to registered Users.