Other Covered Entities

Mailtrap application
Smart Checklist add-on for Jira

Industries

  • Information and Communications Technology
  • Software
  • Application Software

Participation

Swiss-U.S. Data Privacy Framework Framework: Inactive - Lapse

Original Certification Date: 7/12/2019
Inactive Start Date: 8/10/2020

EU-U.S. Data Privacy Framework Framework: Inactive - Lapse

Original Certification Date: 7/12/2019
Inactive Start Date: 8/10/2020

Purpose of Data Collection

Mailtrap: When a person signs up for a Mailtrap subscription plan, Railsware may collect, process and store the their first and last name, email and posting address. We do not store their card details on any of our internal resources / databases, but transfer them instantly to the Payment Card Industry Data Security Standard compliant service provider for further processing. To receive an online payment, we collect billing address(es), card details: number, cardholder name, card number, expiry date, Postal Code and the Card Security Code (CSC) or the Card Verification Value (CVV). We collect this data to let clients use our product. Railsware may collect information through our Site and Application. The data we gather from user devices: it's type, IP address, the browser you are using, OS, as well as the referral site from which a user entered the Mailtrap website. We may also monitor online behavior, including the time of visit, online activity at the website including the URL clickstream through the Site, the pages visited, the time spent viewing them, and the frequency of visits. We gather this data automatically through the commonly used data-gathering technologies, like cookies and web beacons in order to understand how Customers and website visitors browse the Site and use the Application. This data helps us manage the Site and Application, analyze general online behavior and usage trends, and provide targeted advertisements. We also collect non-persinalized demographic information about our Application user and Site visitor base that helps us tailor both the Site's content and the Application functionality in order to meet your expectations and requirements. When a client browses the Site or use the Application, we collect Personal and Navigational Information along with the unique User IDs. In addition, we aggregate extra data that refers to the user flow, such as the start and the end of a web session, page views, purchase and checkout. We may associate this data with the information we store within the analytics software to Personal Information that you submitted to us. We do this to enhance our Application and Site content and UX, as well as use this data to improve the Application functionality, our marketing communication and analytics. A user may log into our Site and Application using either GitHub or Google Sign-in authentication system. When a user does it, he/she gives us access to full name and email address. Smart Checklist for Jira add-on Atlassian provides us with the technical and billing contacts of the Add-on evaluation user or Customer, including their first and last name, the name of the company and the country where it is based, as well as their Jira instance subscription tier, and the Partner name and their email if the latter assisted you with the Add-on integration. We keep the record of this data. When a client enters the Add-on Marketplace pages, we will gather the following data from devices: the device type, the browser you are using, OS, the source you used to enter the Marketplace page. We may also monitor user online behavior, including the time of visit, online activity on the Add-on Marketplace pages including the URL clickstream, the pages visited, the time spent viewing them, and the frequency of your visits. We also collect non-persinalized demographic information about the Add-on Marketplace pages visitors that helps us improve the content and tailor it to their requirements. We may also collect, process and store the add-on usage history and statistics. This data helps us manage Add-ons, analyze general online behavior and add-on usage trends, which, in the end, allows us to understand what functionality users expect and require from the product. We gather this data automatically through the commonly used data-gathering technologies, like cookies, beacons and other.

Dispute Resolution

Questions or Complaints?

If you have a question or complaint, please contact Railsware Products, Inc. at:

Olga Rusnak
Marketing Specialist
Railsware Products, Inc.
118 Coalpit Hill Road
Danbury, Connecticut 06810


Appropriate statutory body with jurisdiction to investigate any claims against Railsware Products, Inc. regarding possible unfair or deceptive practices and violations of laws or regulations covering privacy Federal Trade Commission