J2G — Privacy Notice

Version 1.0 — Effective date: 14 April 2026 — Applies to: J2G desktop application (all supported platforms)

This notice describes the personal data that the J2G desktop application (the “Software”) transmits to the Licensor during license activation and use, and how that data is handled. It supplements the general Privacy Policy. If anything in this notice conflicts with the general Privacy Policy for the Software only, this notice prevails.

1. Who is the Controller

  • Legal name: ФОП Березняк Віталій Вячеславович (Individual Entrepreneur Berezniak Vitalii Viacheslavovych)
  • РНОКПП: 3279403914
  • Registered address: УКРАЇНА, 61098, Харківська область, м. Харків, Холодногірський район, вул. Полтавський Шлях, буд. 188, кв. 146 (Latin: 61098, Kharkivska oblast, m. Kharkiv, Kholodnohirskyi raion, vul. Poltavskyi Shliakh 188, apt. 146, Ukraine)
  • Trading as: NexWright / J2G
  • Contact: support@nexwright.com

2. What the Software Transmits

2.1. On every launch / activation / heartbeat

The Software transmits to the licensing service the following fields, and only these fields:

Field Content Purpose
license_key The alphanumeric key issued to you Authenticate and look up the licence
fingerprint_hash A one-way SHA-256 hash derived from stable hardware and OS identifiers Bind the licence to an Instance, detect key sharing
version Software version and build ID Licence-compatibility checks, security patching
os_family windows / macos / linux Support scope
os_major Major version (e.g. 14, 22.04) Support scope
activated_at Timestamp of first activation on this Instance Licence lifecycle
last_seen_at Timestamp of current heartbeat Detect dormant Instances
credits_consumed_delta Count of Pipeline credits used since last heartbeat Quota enforcement

2.2. Optional: support bundle

If you explicitly ask for support and the support agent asks you to send a “support bundle”, the Software can generate a zip archive containing application logs and a machine-readable configuration snapshot. The support bundle is generated locally, shown to you before transmission, and only sent to us if you click Send. You may redact content before sending.

2.3. What the Software does not transmit

The Software does not collect or transmit:

  • the content of any Jenkinsfile or other Jenkins configuration file you read;
  • the content of any .gitlab-ci.yml or other GitLab CI configuration file the Software produces;
  • repository URLs, branch names, or commit IDs;
  • pipeline names, job names, or stage names;
  • environment-variable values, credentials, API tokens, SSH keys, or any secret material;
  • file paths or directory names on your machine;
  • the raw values from which fingerprint_hash is derived (MAC addresses, CPU IDs, disk serials, etc.) — only the one-way hash is transmitted.

3. Why We Process This Data

Purpose Legal basis (UA DP Law / GDPR)
Verifying that your licence key is valid Contract performance / Art. 6(1)(b) GDPR
Binding a licence to an Instance (anti-sharing, anti-piracy) Contract performance / Art. 6(1)(b) GDPR; legitimate interest in preventing fraud / Art. 6(1)(f) GDPR
Enforcing Pipeline-credit quotas Contract performance / Art. 6(1)(b) GDPR
Detecting and investigating licence abuse Legitimate interest / Art. 6(1)(f) GDPR
Responding to your support request (support bundle) Contract performance / your consent
Complying with tax and accounting obligations Legal obligation / Art. 6(1)(c) GDPR (UA tax law)

We do not use telemetry to build user profiles, to show you ads, or for any purpose unrelated to the Software licence.

4. How Long We Keep It

Category Retention
Licence-activation record (key, fingerprint hash, timestamps) While the licence is active + 3 years (to handle warranty, renewal, anti-fraud)
Heartbeat log (last-seen, version, credit deltas) 90 days rolling, then aggregated / anonymised
Support bundles 180 days from closure of the support ticket, then deletion
Accounting records tied to the purchase Period required by Ukrainian tax law (currently 1 095 days / 3 years from the reporting period)

5. Who We Share It With

  • Hosting provider(s) for the licensing service — acting as a processor on our documented instructions.
  • Payment service provider and banks — for the purchase that produced the licence key (only the minimum data needed to link the payment to the licence).
  • Professional advisors — accountants, legal counsel, under confidentiality.
  • Competent authorities — when legally required.

We do not sell, rent, or trade telemetry data, and we do not share it with any third party for marketing, analytics, advertising, or profiling.

6. International Transfers

Servers used for the licensing service may be located in Ukraine and/or in other countries. Where data is transferred outside Ukraine or the EU/EEA, we rely on a recognised transfer mechanism (for example, Standard Contractual Clauses approved by the European Commission) and apply supplementary measures where needed. On request we will tell you in which country a specific processing takes place and what safeguards apply.

7. Your Rights

You have the rights described in Section 9 of the general Privacy Policy, including the rights to access, rectification, erasure, restriction, portability, objection, withdrawal of consent, and to lodge a complaint with a supervisory authority.

To exercise any of these rights with respect to J2G telemetry, contact support@nexwright.com with your licence key.

Offline use

If you stop using the Software and never reconnect, heartbeat reporting naturally ceases. If you want us to proactively delete the licence-activation record before the retention period expires, ask us in writing; we will process the request unless we have a legitimate reason to keep the record (for example, pending support, anti-fraud investigation, or statutory retention).

8. Children

The Software is a professional developer tool aimed at business users. It is not designed for, and not knowingly offered to, minors.

9. Changes to this Notice

We may update this notice from time to time. The current version is always published at this page. Material changes will be announced on the product page and inside the Software at least 14 days before they take effect.

10. Contact