The websites available through the domain names mailtrack.io, maildoc.io and all subdomains or sections ("Website") are operated by Mailtrack, and use cookies and similar technologies that store and retrieve information when you browse. A Cookie is a text file that stores on your computer, tablet, smartphone or any other similar device, information about your browsing or use. In general, these technologies can serve a wide variety of purposes, such as recognising you as a user, obtaining information about your browsing habits, or personalising the way the content is displayed and, depending on the information they contain and the way your computer is used, can serve to recognise it. When we use the term "Cookies" we also refer to other similar technologies for installing and/or collecting information on or about your device, both our own and those of third parties (including, but not limited to: pixels, flash cookies, web beacons, bugs, etc.). Sometimes, these technologies work together with cookies to collect and store information, either to provide you with certain functionalities or services on our Website, or to show you advertising on third-party platforms, taking into account your browsing.
This explanation is a general overview of what is meant by Cookies for information purposes only. The Cookies and similar technologies that we specifically use are detailed in the cookie settings panel accessible on our website.
However, this technology only obtains information related to the number of pages viewed, the city to which the IP address from which you are accessing is assigned, the number of new users, the frequency and recidivism of the visits, visiting time, the browser or the operator or type of terminal from which the visit takes place. In no case is data obtained about the user’s name, surname, postal address or other similar data.
The specific uses we make of these technologies are described below.
If you have accepted the download of cookies, you are agreeing that we host these cookies on your computer or device for the purposes expressed herein.
If you decide not to accept our cookies, you may continue to use our Website as usual, although your user experience may be slightly impaired.
The information stored in the cookies of our Website is used exclusively by us, except for those identified below as “third-party cookies”, which are used and managed by external entities to provide us with services requested by us to improve our services and the user experience when browsing our Website.
Depending on the entity that manages them, cookies may be first-party cookies or third-party cookies.. First-party cookies are those sent to the user's terminal equipment from a computer or domain managed by the Web publisher itself, from which the service requested by the user is provided. Third-party cookies are those that are sent to the user’s terminal computer from a computer or domain that is not managed by the Web publisher, but by another entity that processes the data obtained through cookies.
According to its purpose for which the data obtained are processed. Considering the purpose for which cookies are used, cookies may be technical, when they allow the navigation or use of the different options or services that exist on the website, platform or application, including those that the editor uses to allow the management and operation of the website; preferences or customization, which allows the user to remember information so that the user can access the service with certain characteristics that can differentiate his or her experience from that of other users, for example the language; analysis or measurement that allows the person responsible for them to monitor and analyse the behaviour of the users of the websites to which they are linked, including the quantification of the impacts of the advertisements; or, behavioral advertising, which store information about the behavior of the users obtained through the continuous observation of their browsing habits, which allows to develop a specific profile to show advertising according to it.
Depending on the length of time they remain on the computer, a distinction can be made between session cookies or persistent cookies. Session cookies are a type of cookies designed to collect and store data while the user accesses a website. Persistent cookies are a type of cookies that keeps data stored in the terminal and can be accessed and processed for a period defined by the cookie manager, which can range from a few minutes to several years.
Below is a table containing the cookies, tags or other similar devices used in this Website, and information on the purpose, duration and management (first-party cookies or third – party cookies) of each of them.
| COOKIE | PURPOSE | DURATION | MANAGEMENT |
|---|---|---|---|
| mt-user-ids | Registers the user IDs used to log in. | 5 years | First-party cookies |
| mt-accounts | Registers the number of different users you log in with. | 5 years | First-party cookies |
| mt-correlation-id | Registers a temporary ID to track the user’s login process (getting-started). | 1 hour | First-party cookies |
| _gat | This cookie is used to differentiate between the different tracking objects created in the session. | 1 minute | Third-party cookies |
| _gid | It is used to store and update a unique value for each page visited. | 1 day | Third-party cookies |
| _ga | These cookies are used to distinguish users. | 2 years | Third-party cookies |
| _gat_client2 | This cookie is used to speed up analysis requests to Google Analytics servers | 1 minute | Third-party cookies |
| _sp_id.<id> | This cookie stores a unique user ID | 2 years | First-party cookies |
| __stripe_mid | Payment | 1 year | Third-party cookies |
| PHPSESSID | Authentication. | 15 days | First-party cookies |
| mt-authorization | Authentication. | 1 month | First-party cookies |
| mt-a-<id> | Authentication. | 1 month | First-party cookies |
| SIDCC, SAPISID, HSID, APISID, SSID, SID, HSID, ANID, NID, 1P_JAR, CONSENT, COMPASS | Advertising Cookie. Measures ad performance and provides product recommendations based on statistical data These cookies contain a unique randomly generated value that allows the Platform to distinguish browsers and devices. | Persistent | Third-party cookies |
| __Secure-3PAPISID, | Advertising. These cookies are used to deliver ads more relevant to you and your interests. | 2 years | Third-party cookies |
| __Secure-3PSIDCC | Advertising. These cookies are used to deliver ads more relevant to you and your interests. | 1 year | Third-party cookies |
| __Secure-3PSID | Advertising. These cookies are used to deliver ads more relevant to you and your interests. | 2 years | Third-party cookies |
| _gac_<id> | Advertising. Contains campaign related information for the user. | 90 days | Third-party cookies |
| OTZ | They allow you to optimize and personalize the advertisements displayed when browsing. It serves to analyze patterns of traffic to the web, duration of the browser session. It is related to the Google Adwords personalized advertising system. | 8 days | Third-party cookies |
| SEARCH_SAMESITE | This cookie is used for the correct sending of data to Google. | 6 months | Third-party cookies |
| _gcl_au | Used by Google AdSense for experimenting with advertisement efficiency across websites using their services. | 3 months | Third-party cookies |
| AMCV_<variable name>@AdobeOrg | This cookie is used for storage and analysis of LinkedIn users. | 2 years | Third-party cookies |
| liap | Advertising Cookie for the efficient management of advertising spaces. These cookies contain a unique randomly generated value that allows the platform to distinguish between browsers and devices. | Persistent | Third-party cookies |
| VID | Advertising Cookie for the efficient management of advertising spaces. These cookies contain a unique randomly generated value that allows the platform to distinguish between browsers and devices. | Of session | Third-party cookies |
| mt-accept-cookies | Cookie to remember if the user had accepted cookies. | 1 year | First-party cookies |
| mt-cookies-settings | Stores user’s cookie preferences | 1 year | First-party cookies |
| bcookie | Advertising Cookie for the efficient management of advertising spaces. These cookies contain a unique randomly generated value that allows the platform to distinguish between browsers and devices. | Persistent | Third-party cookies |
| lissc | Advertising cookie | 1 year | Third-party cookies |
| _hjClosedSurveyInvites | Hotjar cookie that is set once a visitor interacts with an External Link Survey invitation modal. It is used to ensure that the same invite does not reappear if it has already been shown. | 365 days | Third-party cookies |
| _hjDonePolls | Hotjar cookie that is set once a visitor completes a survey using the On-site Survey widget. It is used to ensure that the same survey does not reappear if it has already been filled in. | 365 days | Third-party cookies |
| _hjMinimizedPolls | Hotjar cookie that is set once a visitor minimizes an On-site Survey widget. It is used to ensure that the widget stays minimized when the visitor navigates through your site. | 365 days | Third-party cookies |
| _hjShownFeedbackMessage | Hotjar cookie that is set when a visitor minimizes or completes Incoming Feedback. This is done so that the Incoming Feedback will load as minimized immediately if the visitor navigates to another page where it is set to show. | 365 days | Third-party cookies |
| _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. | 365 days | Third-party cookies |
| _hjRecordingLastActivity | This should be found in Session storage (as opposed to cookies). This gets updated when a visitor recording starts and when data is sent through the WebSocket (the visitor performs an action that Hotjar records). | Session | Third-party cookies |
| _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. | Session | Third-party cookies |
| _hjUserAttributesHash | User Attributes sent through the Hotjar Identify API are cached for the duration of the session in order to know when an attribute has changed and needs to be updated. | Session | Third-party cookies |
| _hjCachedUserAttributes | This cookie stores User Attributes which are sent through the Hotjar Identify API, whenever the user is not in the sample. These attributes will only be saved if the user interacts with a Hotjar Feedback tool. | Session | Third-party cookies |
| _hjLocalStorageTest | This cookie is used to check if the Hotjar Tracking Script can use local storage. If it can, a value of 1 is set in this cookie. The data stored in_hjLocalStorageTest has no expiration time, but it is deleted almost immediately after it is created. | Under 100ms | Third-party cookies |
| _hjIncludedInPageviewSample | This cookie is set to let Hotjar know whether that visitor is included in the data sampling defined by your site's pageview limit. | 30 minutes | Third-party cookies |
| _hjIncludedInSessionSample | This cookie is set to let Hotjar know whether that visitor is included in the data sampling defined by your site's daily session limit. | 30 minutes | Third-party cookies |
| _hjAbsoluteSessionInProgress | This cookie is used to detect the first pageview session of a user. | 30 minutes | Third-party cookies |
| _hjFirstSeen | This is set to identify a new user’s first session. It stores a true/false value, indicating whether this was the first time Hotjar saw this user. It is used by Recording filters to identify new user sessions. | Session | Third-party cookies |
| hjViewportId | This stores information about the user viewport such as size and dimensions. | Session | Third-party cookies |
| _hjRecordingEnabled | This is added when a Recording starts and is read when the recording module is initialized to see if the user is already in a recording in a particular session. | Session | Third-party cookies |
| _fbc | Here the relationship between the user identifier and the Facebook ad is saved. | 2 years | Third-party cookies |
| _fbp | A unique identifier of the user is stored here. | 90 days | Third-party cookies |
If you prefer to avoid the use of cookies on the Website, considering the aforementioned limitations, you should firstly disable the use of cookies in your browser and secondly delete the cookies saved in your browser associated to the Website.
You can restrict, block or delete cookies from this Website at any time by modifying your browser settings according to the guidelines below. Although the parameterization of each browser is different, it is common for cookies to be set up in the menu of “Preferences” or “Tools”. For more details on the settings of cookies in your browser, please refer to the ‘Help’ menu of your browser.
You can find information on how to manage or disable cookies at the following addresses:
At any time THE MAIL TRACK COMPANY, S.L., can modify the cookie policy so please check it periodically as changes may occur.
If you need help in setting cookies with your browser, please send us an e-mail to privacy@mailtrack.io and we will contact you as soon as possible with the necessary information.