
Mohami and GDPR
CertReports found no public GDPR evidence for Mohami as of unknown date. This does not mean the vendor is non-compliant. It means CertReports found no public evidence at the last check.
Evidence
- Kind
- listing
- Scope
- 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.
| Source | Captured | Quote | Links |
|---|---|---|---|
Data Privacy Framework list Official registry · HTTP 200 | 17 Sep 2026 | Railsware Products, Inc.: Inactive | Live pagesha256 989f77fab9 |
- Kind
- listing
- Issued or listed
- 7 Jan 2019
- Scope
- Mohami processes personal data in order to receive and process orders and provide services for the software add-on products it provides. It processes the personal data of its customers, which are typically organizations. It does not disclose personal information to any third parties except for its own vendors, where necessary for such vendors to provide services to Mohami, such as email providers.
| Source | Captured | Quote | Links |
|---|---|---|---|
Data Privacy Framework list Official registry · HTTP 200 | 17 Sep 2026 | Mohami: Inactive | Live pagesha256 7533c1c5f6 |
What GDPR means, and what it does not
"GDPR compliant" is a claim, not a certification. The verifiable facts are a public DPA, SCC usage, an EU representative, data residency options and a Data Privacy Framework listing.
Read the GDPR guide and browse all vendors with evidenceQuestions buyers ask
Is Mohami GDPR compliant?
There is no GDPR certification in general use. The verifiable facts are a public data processing agreement, standard contractual clauses, an EU representative and a Data Privacy Framework listing. See the legal artefacts and the DPF row on this page, each with its capture date.
How does CertReports verify this?
Every state carries a capture date, a source and a snapshot link. Registry rows come from the official registry data; vendor statements come from the vendor’s own page or trust centre; nothing is inferred. Vendors can dispute any row and corrections ship within two business days.
Alternatives with GDPR evidence
Similar vendors (shared product tags or the Collaboration category) whose GDPR row is verified or vendor-stated, ranked by similarity.