No public evidenceCryptlex and GDPR
CertReports found no public GDPR evidence for Cryptlex 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
- Issued or listed
- 15 Feb 2019
- Scope
- In order to provide services to our users (our customers and customers' customers), Cryptlex collects certain types of data from them. This section will describe how these two types of data are collected and used by Cryptlex. Data entered or transferred into Cryptlex by Users remains the property of the User and may not be shared with a third party by Cryptlex without express consent from the User. 1..1 Collection of User data from our customers Information in this category includes the information they provide when registering to use our services and further use of our services. This data is primarily stored within Cryptlex and a part of it may also be stored in third-party services. 1.1.1 Personal information stored within Cryptlex First name, last name, email, company name Stripe customer and subscription unique identifiers IP addresses for rate limiting (stored temporarily) 1.1.2 Personal information stored in third-party services Name and email (through Hubspot, MailChimp and Intercom) Company name (through Hubspot) Links to social media profiles (through Hubspot) Credit card information (securely stored within Stripe) Website usage (through Google Analytics) Geographic location (through Google Analytics) Name, email and IP addresses in crash reports (through Bugsnag retained for seven days) IP addresses in request logs (through Papertrail archived for one year) 1.2 Collection of User data from our customers' customers Information in this category includes the information they store when adding license users, information collected at the time of license activation to identify the user device required for node locked licensing and additional metadata stored along with user or license activation data which may or may not contain personally identifiable information. This data is only stored within Cryptlex and is entirely owned by them. This data is never shared with any third parties outside of our logging, crash reporting and other infrastructure-related services. 1.2.1 Personal information stored within Cryptlex First name, last name, email User metadata (may or may not contain personal data) Geo-location data License activation metadata (may or may not contain personal data) Following device details associated with license activation: Hostname of the device Username of the device (hashed using SHA256) Operating system of the device Virtual machine being run on the device Fingerprint of the device generated using various hardware components (hashed using SHA256) IP address of the device 1.2.2 Personal information stored in third party services Name, email and IP addresses in crash reports (through Bugsnag retained for seven days) IP addresses in request logs (through Papertrail archived for one year)
| Source | Captured | Quote | Links |
|---|---|---|---|
Data Privacy Framework list Official registry · HTTP 200 | 17 Sep 2026 | Cryptlex: Inactive | Live pagesha256 3e449430af |
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 Cryptlex 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 Developer tools category) whose GDPR row is verified or vendor-stated, ranked by similarity.
No Developer tools vendor has GDPR evidence in the index yet.