Skip to Navigation
Introduction
Railsware Products Studio LLC, United States of America company registered office: 925 N La Brea Ave, Suite 400, office 560, West Hollywood, CA 90038, US (“Railsware”, “us”, “our”, or “we”), focuses on assuring that the mailtrap.io website (“Site”) and the Mailtrap application (the “Application”), as well as the general ecosystem provides a safe environment for both website visitors and application users (“Customer”, “You”). We need to collect, process and store some Navigational information in order to provide you with an ability to review the Mailtrap website content and use the Application.
This web page explains how Railsware uses cookies, web beacons and other technologies and for what purposes. It also describes how the Site visitors and Application users can exercise their rights to control our use of the Navigational Information.
Cookies Definition and Categories
Cookies are small files which are received from a web server and are either stored on your web browser until its expiry date, or until the end of each session. You may not agree to accept cookies and refuse them.
Our Site and Application incorporates different cookies that are divided into several categories:
- Essential cookies are necessary to provide you with our Site’s and Application core services and functionality, such as enable Application sign-in.
- Analytics cookies help us understand how our Site and Application are being used, how good our marketing campaigns perform, and based on the information – customize and enhance both the Site and Application for you.
- Performance cookies improve the Site’s and Application performance by leveraging non-essential functionality, such as allow remembering the last position a Site’s visitor or an application user watched the video before this process was interrupted due problems with internet connection or other reasons.
Railsware Products Studio LLC, United States of America company registered office: 925 N La Brea Ave, Suite 400, office 560, West Hollywood, CA 90038, US (“Railsware”, “us”, “our”, or “we”), focuses on assuring that the mailtrap.io website (“Site”) and the Mailtrap application (the “Application”), as well as the general ecosystem provides a safe environment for both website visitors and application users (“Customer”, “You”). We need to collect, process and store some Navigational information in order to provide you with the ability to review the Mailtrap website content and use the Application.
This web page explains how Railsware uses cookies, web beacons, and other technologies and for what purposes. It also describes how the Site visitors and Application users can exercise their rights to control our use of the Navigational Information.
Cookies Served Through our Site and Application
| Cookie Name | Expiration Date | Description | Category | Company or service that provides this cookie |
| _ga | 2 years | Used to distinguish users. | Analytics | Google Analytics |
| _gid | 24 hours | Used to distinguish users. | Analytics | Google Analytics |
| _gat | 1 minute | Used to throttle request rate. | Analytics | Google Analytics |
| _gcl_au | 3 months | Used for experimenting with advertisement efficiency across websites using their services. | Analytics | Google Analytics |
How to opt-out from Google Analytics cookies: To refuse these cookies, please follow the general browser rules explained in the ‘Disabling Cookies’ part of this document, or visit: this page
| Cookie Name | Expiration Date | Description | Category | Company or service that provides this cookie |
| _A_FirstTouchURL, _A_LastTouchURL, _A_source, _A_visits, firstTouchGA, ref_id, hs_type | 2 years | Collects information about how visitors use our sites. | Performance and Analytics | HelpScout |
| 2fa_ | 30 minutes | Keeps track of your two-factor authentication status. | Performance and Analytics | HelpScout |
| PHPSESSID | None. Session cookie | Login session ID allows you to have multiple browser windows logged in to your account. | Performance and Analytics | HelpScout |
| mhash | 30 days | Security token that allows us to ensure your session hasn’t been tampered with. | Performance and Analytics | HelpScout |
| folder_sort | 1 day | Allows us to remember what sorting options you have set, so when you return we can rebuild the same view(s). | Performance and Analytics | HelpScout |
| hs_tvar | 1 year | Tracking for A/B testing. | Performance and Analytics | HelpScout |
How to opt-out from HelpScout cookies: Note: if you refuse these cookies, some of the Site content or the Application functionality will not be available to you.
If you still want to refuse these cookies, please follow the general browser rules explained in the ‘Disabling Cookies’ part of this document.
| Cookie Name | Expiration Date | Description | Category | Company or service that provides this cookie |
| __hssc | 30 minutes | Used to keep track of sessions and to determine if the session number should be incremented. It includes the domain, viewCount (increments each pageView in a session), and session start timestamp. | Analytics | HubSpot |
| __hssrc | None. Session cookie | Used to determine if the user has restarted the browser. If it does not exist, the assumption is that it is a new session. | Analytics | HubSpot |
| __hstc | 2 years | Used to identify the domain, initial timestamp (first visit), last timestamp (last visit), hubspotutk (see below), current timestamp (this visit), and session number (counts each subsequent session). | Analytics | HubSpot |
| hubspotutk | 10 years | Used to keep track of a visitor’s identity and de-duplicate contacts. | Analytics | HubSpot |
How to opt-out from HubSpot cookies: To refuse these cookies, please follow the general browser rules explained in the ‘Disabling Cookies’ part of this document
| Cookie Name | Expiration Date | Description | Category | Company or service that provides this cookie |
| __hssc | 3 months | Used to help deliver our advertising to people who have already visited our website when they are on Facebook or a digital platform powered by Facebook Advertising. | Analytics |
How to opt-out from Facebook cookies: To refuse these cookies, please follow the general browser rules explained in the ‘Disabling Cookies’ part of this document
| Cookie Name | Expiration Date | Description | Category | Company or service that provides this cookie |
| auth_token, lang, twll, __utmz, secure_session, guest_id, __utma, remember_checked, remember_checked_on, __utmb, personalization_id | 2-5 years | Used to help deliver our advertising to people who have already visited our website when they are on Twitter. | Analytics |
How to opt-out from Twitter cookies: To refuse these cookies, please follow the general browser rules explained in the ‘Disabling Cookies’ part of this document
| Cookie Name | Expiration Date | Description | Category | Company or service that provides this cookie |
| mf_[session] | None. Session cookie | This cookie identifies the browser session while it happens. The cookie is deleted as soon as the session ends, meaning when the user leaves the website. | Analytics | Mouseflow |
| mf_user | 90 days | This cookie establishes whether the user is a returning or first time visitor. This is done simply by a yes/no toggle – no further information about the user is stored. | Analytics | Mouseflow |
How to opt-out from Mouseflow cookies: To refuse these cookies, please follow the general browser rules explained in the ‘Disabling Cookies’ part of this document
| Cookie Name | Expiration Date | Description | Category | Company or service that provides this cookie |
| _clck | 1 year | Persists the Clarity User ID and preferences, 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. | Analytics | Microsoft, Inc. (Clarity) |
| _clsk | 1 day | Connects multiple page views by a user into a single Clarity session recording. | Analytics | Microsoft, Inc. (Clarity) |
| CLID | 1 year | Identifies the first-time Clarity saw this user on any site using Clarity. | Analytics | Microsoft, Inc. (Clarity) |
| ANONCHK | 10 minutes | Indicates whether MUID is transferred to ANID, a cookie used for advertising. Clarity doesn’t use ANID and so this is always set to 0. | Analytics | Microsoft, Inc. (Clarity) |
| MR | Session | Indicates whether to refresh MUID. | Analytics | Microsoft, Inc. (Clarity) |
| MUID | 1 year | Identifies unique web browsers visiting Microsoft sites. These cookies are used for advertising, site analytics, and other operational purposes. | Analytics | Microsoft, Inc. (Clarity) |
| SM | Session | Used in synchronizing the MUID across Microsoft domains. | Analytics | Microsoft, Inc. (Clarity) |
How to opt-out from Microsoft, Ing. (Clarity) cookies: To refuse these cookies, please follow the general browser rules explained in the ‘Disabling Cookies’ part of this document
| Cookie Name | Expiration Date | Description | Category | Company or service that provides this cookie |
| _mailtrap_session | 2 weeks | Used to enable login into the Application. | Essential | Mailtrap |
| popup_marketing | 1 year, or straight after a user closes the popup | Used to show popup that advises a user to upgrade a Mailtrap application account. | Essential | Mailtrap |
| hide_cookies_banner | 1 year | Used to show this document and use of cookies pop up, which is asking to provide consent. | Essential | Mailtrap |
| remember_user_token | 2 weeks | Used to remember user session to avoid login each time. | Essential | Mailtrap |
How to opt-out from Mailtrap cookies: Note: if you refuse these cookies, some of the Site content or the Application functionality will not be available to you.
If you still want to refuse these cookies, please follow the general browser rules explained in the ‘Disabling Cookies’ part of this document.
Disabling Cookies
Website visitors and the Application users have the right to opt out from using the cookies on the Site and as part of the Application. To reject these cookies you can either follow the instructions provided in the table above, or amend your web browser settings and either accept or refuse these cookies.
Opting out from the Essential cookies may result in not being able to access certain functionality that is available on our Site and as part of the Application.
Here are the links to different web browsers where you can amend your browser preferences, and either enable or disable cookies:
In addition, you can also opt-out from the targeted advertising, like Google Adwords. In order to do so, please visit https://support.google.com/ads/answer/2662922?hl=en
Web Beacons
In addition to cookies, we may use other technologies, like web beacons to track user behavior on the Site and the Application. In contrast to cookies, web beacons are small pieces of code (pixel) embedded into the website.
Web beacons provide the data on what pages website users visit and when, allowing to group them by shared behavior and advertise to them. Web beacons may also rely on cookies that help record such activities, as conversion. That is why disabling cookies may result in incorrect web beacon functioning.
We will update this information in order to reflect any changes that refer to web beacons, cookies or other technologies and are implemented on our Site or Application. To keep up-to-date with our latest Navigational Information statement, please visit and review this web page from time to time. Please note that the last review date is indicated at the top of this page.
Contact Details
For any questions relating to the use of cookies and other technologies, please contact us at privacy@mailtrap.io
4. Obligations of Processor
4.1. Data processing
Mailtrap as the Processor agrees and warrants to process Personal Data only on behalf of the Controller and in compliance with its instructions and the Data Processing Addendum unless the instructions are unlawful; if it cannot provide such compliance for whatever reasons, it agrees to inform promptly the Controller of its inability to comply, in which case the Controller is entitled to suspend the transfer of data and/or terminate the contract.
4.2. Security
Mailtrap as the Processor shall take the appropriate technical and organizational measures (specified in Appendix 2) to adequately protect Personal Data against accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to Personal Data.