Version: 2026-10-01 · Effective date: October 1, 2026 · Licensor: ForgeZen Labs LLC, 4030 Wake Forest Rd Ste 349, Raleigh, North Carolina 27609 (DataNivra)
This End User Licence Agreement (the EULA) governs the installation and use of the Installable Software by the organisation that obtains it (Customer). By installing, copying or using the Installable Software, or by signing an Order Form that references this EULA, Customer agrees to it. If the person installing the software does not have authority to bind Customer, they must not install or use it.
Where the Installable Software is used with DataNivra's Hosted Service (SaaS-connected use), the Terms of Service and the Order Form also apply. Capitalised terms not defined here have the meanings given in the Terms of Service.
1. Scope
In plain English: this EULA covers the software you install and run yourself.
1.1 Covered software. This EULA applies to the following Installable Software, in object-code form, together with its updates and the Documentation:
- the DataNivra Agent and test data management engine, including industry packs, container images and deployment packages (for example Docker, Docker Compose, Helm and cloud network packages);
- the DataNivra CLI and the licence command-line tool;
- the DataNivra SDKs (for example the Python and TypeScript SDKs);
- any self-hosted control-plane edition that DataNivra makes available to Customer (today a Docker Compose scaffold, available on request).
1.2 Relationship to the Terms. The Terms of Service govern Customer's Subscription, Fees, confidentiality, data protection and the Hosted Service. If this EULA and the Terms of Service conflict about the Installable Software, this EULA prevails, except that an Order Form prevails over both.
2. Licence grant
In plain English: you may install and use the software internally, within what you have paid for, while your Subscription or licence is active.
2.1 Grant. Subject to this EULA and payment of the applicable Fees, DataNivra grants Customer a non-exclusive, non-transferable, non-sublicensable, revocable licence, for the Subscription Term or the licence term stated in the Order Form or Licence File, to install and use the Installable Software in the Customer Environment solely for Customer's internal business purposes and within its Entitlements.
2.2 Users and contractors. Customer may allow its Users, including contractors acting on Customer's behalf, to use the Installable Software under this EULA. Customer is responsible for their compliance.
2.3 Copies. Customer may make the copies reasonably necessary for installation, high availability, testing, disaster recovery and backup, provided all proprietary notices are reproduced.
2.4 SDKs and CLI. Customer may incorporate the SDKs into its own internal applications, scripts and pipelines solely to interact with the Platform. Customer may not distribute the SDKs or CLI to third parties except as part of such internal use.
2.5 Evaluation. Installable Software obtained for a Trial or evaluation may be used only for evaluation during the Trial, preferably with synthetic or non-production data, and is provided as is.
3. Licence files, deployment binding and offline grace period
In plain English: self-hosted editions check a cryptographically signed licence file locally (production licence files are issued on request). They do not contact DataNivra to do so. When a licence expires there is a short grace period, after which licensed operations stop until you install a renewed licence.
3.1 Licence Files. Self-hosted control-plane editions (a scaffold, available on request) require a Licence File issued by DataNivra: a document signed with a DataNivra Ed25519 signing key that records the licensee, the Plan, the Entitlements (limits, features, industry packs and support level), the validity period and the deployment it is bound to. Production licence files are issued on request after DataNivra's production signing-key ceremony, which is pending at the effective date of this EULA.
3.2 Deployment binding. Each Licence File is bound to a Deployment ID configured for the Customer's installation. The software refuses a Licence File whose Deployment ID does not match. Customer may not use one Licence File for more deployments than it covers; additional or replacement deployments need a new or amended Licence File.
3.3 Local verification only. Licence verification is performed entirely within the Customer Environment. The Installable Software does not transmit licence, usage or Customer Data to DataNivra for the purpose of licence enforcement.
3.4 Validity and offline grace period. A Licence File is valid from its start date until its expiry date. After the expiry date, the software continues to operate with full Entitlements for the Offline Grace Period stated in the Licence File (fourteen (14) days unless the Licence File states another period of up to ninety (90) days) and reports that it is in its grace period so that operators can renew.
3.5 Behaviour after expiry. When the Offline Grace Period ends, or if a Licence File is not yet valid, invalid, bound to another deployment or cannot be verified, the software fails closed: operations that depend on Entitlements (for example enrolling agents, adding data sources, requesting datasets, creating or running jobs and enabling industry packs) are refused until a valid Licence File is installed. Refusal does not delete data that is already stored in the Customer Environment.
3.6 Clock integrity. The software records the latest time it has observed and refuses to operate on a licence if the system clock moves materially backwards, to prevent the licence term from being extended by changing the clock. Customer must keep system clocks accurate.
3.7 Renewal. A renewed Licence File can be installed at any time without downtime, provided it is valid, names the same licensee and does not shorten the licence.
3.8 No tampering. Customer will not modify, forge, share or reuse a Licence File, or bypass, disable or interfere with licence verification or Entitlement enforcement.
4. SaaS-connected use
4.1 In SaaS-connected use, the Agent communicates with the Hosted Service over outbound HTTPS in order to receive work and to report Control-Plane Metadata, as described in the Terms of Service and the Data Processing Addendum. The Agent applies an egress guard designed to prevent Customer Source Data, credentials and secret values from being sent to the Hosted Service. Customer must not modify or disable that guard.
5. Restrictions
In plain English: do not copy, reverse engineer, redistribute or tamper with the software.
5.1 Customer will not, and will not permit anyone to:
- copy, modify, adapt, translate or create derivative works of the Installable Software, except as expressly permitted by this EULA;
- reverse engineer, decompile or disassemble the Installable Software, or otherwise attempt to derive its source code, except to the extent that applicable law expressly permits this despite this restriction;
- sell, rent, lease, lend, sublicense, distribute, host for third parties or otherwise transfer the Installable Software;
- remove or alter proprietary, licence or third-party notices;
- use the Installable Software beyond its Entitlements, outside the Customer Environment, or after the licence has ended;
- circumvent licence verification, deployment binding, Entitlement enforcement, audit logging, the egress guard or any other security or privacy control;
- use the Installable Software with data that Customer has no right or lawful basis to process, or to route Customer Source Data, credentials or secret values to the Hosted Service; or
- use the Installable Software in breach of export-control or sanctions laws.
6. Ownership and third-party components
In plain English: DataNivra owns the software. Open-source parts keep their own licences.
6.1 Ownership. The Installable Software is licensed, not sold. DataNivra and its licensors retain all right, title and interest in it. It is proprietary software and is not licensed under any open-source licence. All rights not expressly granted are reserved.
6.2 Customer Data. As between the parties, Customer owns Customer Data and Outputs processed or produced by the Installable Software.
6.3 Third-party and open-source components. The Installable Software includes third-party open-source components. Their licence and notice texts are reproduced in the THIRD_PARTY_NOTICES.txt file distributed with every DataNivra container image and source distribution. Those components are licensed to Customer under their own licences, which govern them, and nothing in this EULA limits rights that those licences grant. Where such a licence (for example the LGPL) entitles Customer to replace or relink a component, DataNivra will not treat that as a breach of this EULA.
7. Updates and support
7.1 Updates. During the Subscription Term, DataNivra may provide updates, patches and new versions. Customer is responsible for applying them. DataNivra may stop supporting older versions, and security fixes may be provided only for supported versions, as described in the Documentation or Order Form.
7.2 Support. Support is provided at the level of Customer's Plan or Order Form. Support requests must not contain Customer Source Data, credentials or secret values.
8. Verification and audit
In plain English: we may ask you to confirm that you are using the software within your licence, with reasonable notice, at most once a year.
8.1 Self-certification. On DataNivra's reasonable request, not more than once in any twelve-month period, Customer will certify in writing that its use of the Installable Software complies with this EULA and its Entitlements.
8.2 Audit. If DataNivra has a reasonable, documented basis to believe that Customer is not in compliance, DataNivra (or an independent auditor bound by confidentiality) may, on at least 30 days' written notice, during normal business hours and in a manner that does not unreasonably interfere with Customer's operations, review the records reasonably necessary to verify compliance. Audits will not require access to Customer Source Data. Customer will promptly pay Fees for any use beyond its Entitlements at the rates in its Order Form. DataNivra bears the cost of the audit unless it reveals under-payment of more than 5%.
9. Term and termination
9.1 Term. This EULA applies from first installation until the licence ends under the Order Form or Licence File, or until this EULA or the Terms of Service are terminated.
9.2 Termination. DataNivra may terminate this EULA by notice if Customer materially breaches it and does not cure the breach within thirty (30) days of notice. It ends automatically when Customer's Subscription or licence ends.
9.3 Effect. On termination, Customer must stop using the Installable Software and uninstall and delete it (other than copies in routine backups, which Customer will not restore for use). Customer Source Data, Outputs and local workspaces remain in the Customer Environment and under Customer's control.
10. Warranty disclaimer
10.1 Except for any warranty expressly given in the Terms of Service or an Order Form, the Installable Software is provided as is and as available. To the maximum extent permitted by law, DataNivra disclaims all warranties, express or implied, including warranties of merchantability, fitness for a particular purpose, title and non-infringement, and does not warrant that the Installable Software will be error-free or uninterrupted.
10.2 Automated classification is decision support, and certification of a dataset is not a guarantee that it is anonymous or that its use is lawful. DataNivra does not warrant that use of the Installable Software satisfies any legal or regulatory requirement, including under HIPAA, the GDPR or UK GDPR, the CCPA/CPRA, GLBA or PCI DSS.
11. Limitation of liability
11.1 Section 15 (Limitation of liability) of the Terms of Service applies to this EULA. Where no Terms of Service apply (for example to a Trial without an Order Form), DataNivra's total liability arising out of or relating to this EULA is limited to US $100, and DataNivra is not liable for indirect, incidental, special, consequential or punitive damages or for loss of profits, revenue, goodwill or data, to the maximum extent permitted by law.
12. Export control
12.1 The Installable Software may be subject to export-control and sanctions laws. Customer will not export, re-export, transfer or make it available in breach of those laws, and will not use it for any prohibited end use.
13. Governing law and general
13.1 This EULA is governed by the laws of the State of North Carolina, United States, excluding its conflict-of-laws rules, and the courts of the state courts located in Wake County, North Carolina, and the United States District Court for the Eastern District of North Carolina, as applicable have exclusive jurisdiction, as provided in the Terms of Service.
13.2 Customer may not assign this EULA except together with its Subscription as permitted by the Terms of Service. If any provision is unenforceable, the rest remains in effect. This EULA, together with the Terms of Service and Order Form, is the entire agreement about the Installable Software.
13.3 Notices under this EULA are given as described in the Terms of Service.