End-User License Agreement
HAPTECH DEFENSE SYSTEMS
Haptech, Inc. (d/b/a Haptech Defense Systems) · 12715 Highway 90, Suite 140 · Luling, LA 70070 · contracts@haptech.com
HAPTECH SOFTWARE END USER LICENSE AGREEMENT
Haptech Hub · Haptech Manager · ERIS™ Device Firmware
Version 1.1 · Effective November 1, 2026 · Published at www.haptechdefense.com/eula
This End User License Agreement (“EULA”) has two parts. Part A applies only to government end users and appears first. Part B applies to all customers; for government end users, Part B applies as modified by Part A.
========================================================================
PART A — NOTICE TO GOVERNMENT END USERS
========================================================================
COMMERCIAL CUSTOMERS: Part A does not apply to you. Skip to Part B — Commercial Customers Start Here.
Part A applies only when the Software is acquired by or for a government end user. It modifies Part B as stated below, and for U.S. Government End Users it controls over any conflicting term of Part B. Capitalized terms not defined in Part A have the meanings given in Part B, Section 2.
A1. WHO PART A APPLIES TO
Sections A1 through A10 apply to each agency and instrumentality of the United States Government that acquires a license to the Software, whether directly from Haptech or through a prime contractor, a subcontractor at any tier, or an Authorized Reseller (each, a “U.S. Government End User”). Sections A11 and A12 apply to state, local, tribal and foreign government end users. This EULA binds the U.S. Government End User as licensee. It does not bind any employee, service member or other person acting on behalf of the U.S. Government in a personal capacity, including a person who selects “I Accept” at first launch.
A2. COMMERCIAL COMPUTER SOFTWARE
The Software and the Documentation are “commercial computer software” and “commercial computer software documentation” as those terms are defined in FAR 2.101 and DFARS Part 227 (including DFARS 252.227-7014(a) as codified and DFARS 227.7201 as revised by the FAR and DFARS overhaul class deviations), and were developed exclusively at private expense. Consistent with FAR 12.212 (FAR 12.107 under the FAR overhaul model deviation) and DFARS 227.7202-1 and 227.7202-3, the U.S. Government acquires only the rights in the Software and Documentation that this EULA grants to all other licensees, as modified by Part A. Any additional rights must be negotiated with Haptech and stated in a written contract or license addendum signed by Haptech. References in Part A to the FAR, the DFARS or a statute include any successor, renumbered or deviated provision.
A3. ORDER OF PRECEDENCE
If a term of this EULA conflicts with Federal law or with the contract, task order or delivery order under which the U.S. Government End User acquires the Software (the “Government Contract”), the conflicting term is deemed modified to the minimum extent necessary to comply, and the Government Contract controls.
A4. FEDERAL LAW AND DISPUTES
This EULA is governed by the Federal law of the United States. Any term of Part B that would subject the U.S. Government to the law of a state or foreign country, to binding arbitration, to a particular forum or venue, to a class-action waiver, to a jury-trial waiver, or to a time limit for bringing claims different from Federal law does not apply to the U.S. Government. Disputes will be resolved under the Contract Disputes Act (41 U.S.C. §§ 7101–7109) or other applicable Federal statute and the disputes clause of the Government Contract. Equitable or injunctive relief, attorney fees, costs and interest may be awarded against the U.S. Government only where expressly authorized by Federal statute.
A5. NO INDEMNIFICATION OR UNAUTHORIZED OBLIGATIONS
Any term of this EULA that would require the U.S. Government to defend or indemnify Haptech or any other person, or to pay any future fees, penalties, interest, legal costs or other amounts not authorized by the Government Contract — including Part B, Sections 18 and 21.6 — is unenforceable against the U.S. Government and is deemed stricken, consistent with FAR 52.212-4(u) and FAR 52.232-39. Neither the U.S. Government nor any authorized end user is bound by such a term because it appears in this EULA or because a person selected “I Accept.”
A6. NO UNILATERAL SUSPENSION OR TERMINATION
Haptech will not suspend, terminate or revoke any license or any function of the Software for a U.S. Government End User — including through the License Management and Security Features described in Part B, Section 5 — except as expressly allowed by the Government Contract or required by Federal law. If Haptech believes a U.S. Government End User has breached this EULA, Haptech will pursue its rights under the Contract Disputes Act or other applicable Federal statute and will continue performance as the Government Contract requires. The expiration of a Subscription Term that the U.S. Government has not renewed by written order is not a suspension or termination under this Section.
A7. CHANGES, RENEWALS AND TAXES
(a) A new version of this EULA, including one presented with an Update, binds a U.S. Government End User only if it does not materially change the Government Contract or is incorporated by bilateral modification. A change is material if it would change Government rights or obligations, increase Government prices, decrease the overall level of service, or limit any other Government right under the Government Contract.
(b) No Subscription Term or other paid periodic license or service renews automatically for a U.S. Government End User. Renewal requires a written order from an authorized contracting officer. The no-charge renewal of a license key under Part B, Section 5.5, where that Section applies, is not a renewal under this paragraph.
(c) Taxes and surcharges are payable by the U.S. Government only as provided in the Government Contract.
A8. PUBLIC INFORMATION
Neither this EULA nor any Haptech price list is confidential information with respect to the U.S. Government. Release of unit pricing and other information is governed by the Freedom of Information Act and other applicable law. The U.S. Government may retain Haptech Confidential Information as required by law, regulation or its records-retention procedures, and retained information remains subject to Part B, Section 15.
A9. DIAGNOSTICS, UPDATES AND NETWORK AUTHORIZATION
For U.S. Government End Users, Diagnostics Sharing (Part B, Section 10.5) is OFF by default and transmits Diagnostic Data only if an authorized Government representative turns it on consistent with the Government’s security authorizations. Updates (Part B, Section 8) are installed on a U.S. Government End User’s Hub only as authorized under the Government’s configuration-management or security process, and the automatic installation described in Section 8.2 does not apply unless the Government Contract or an authorized Government representative provides otherwise. Connecting a Hub or ERIS Device to any Government network, including a classified network such as SIPRNet, requires the Government’s own authorization, and Haptech makes no representation that the Software is approved for any such network unless Haptech states so in writing for a specific configuration (Part B, Section 11).
A10. ASSIGNMENT
Haptech will not assign this EULA, or delegate its obligations under it, as to a U.S. Government End User except as permitted by Federal law, including 41 U.S.C. § 6305 and FAR Subpart 42.12 (Subpart 42.9 under the FAR overhaul model deviation), or with the U.S. Government’s prior approval.
A11. STATE, LOCAL AND TRIBAL GOVERNMENT END USERS
If you are a state, local or tribal government entity in the United States, Part B applies to you, except that any term your governing law prohibits you from accepting — such as indemnification, the law or courts of another jurisdiction, binding arbitration, a jury-trial waiver, or a waiver of immunity — is deemed modified to the minimum extent necessary to comply with that law.
A12. FOREIGN GOVERNMENT END USERS
If you are a foreign government, or an agency, ministry, police force or armed force of a foreign government, your rights and obligations are as stated in your contract with Haptech or with the Authorized Reseller that supplied the Product, which controls over any conflicting term of this EULA. Where that contract does not address a subject, Part B applies. Where the U.S. Government acquires the Software for a foreign government (for example, through Foreign Military Sales), Sections A1 through A10 apply to the U.S. Government’s acquisition.
End of Part A.
========================================================================
PART B — COMMERCIAL CUSTOMERS START HERE
========================================================================
Part B applies to every customer. Government end users: Part B applies to you as modified by Part A.
PLEASE READ CAREFULLY BEFORE USING THE PRODUCT. BY SELECTING “I ACCEPT,” OR BY INSTALLING, ACCESSING OR USING THE SOFTWARE, YOU AGREE TO THIS EULA. IF YOU DO NOT AGREE, DO NOT USE THE SOFTWARE. YOU MAY RETURN THE HUB, OR ERIS DEVICES SUPPLIED WITHOUT A HUB, FOR A REFUND UNDER SECTION 3.
THIS EULA INCLUDES: LICENSE MANAGEMENT AND SECURITY FEATURES, INCLUDING PERIODIC LICENSE RENEWAL OVER THE INTERNET, WITHOUT WHICH THE HUB OPERATES IN A LIMITED MODE (SECTION 5); AUTOMATIC INSTALLATION OF HUB UPDATES (SECTION 8); AUTOMATIC SHARING OF DIAGNOSTIC DATA FOR SUPPORT AND PREDICTIVE MAINTENANCE, WHICH YOU CAN TURN OFF, AND, IN PLANNED FUTURE HUB RELEASES, OF BREATHING-RATE AND HEART-RATE DATA (SECTION 10); SAFETY REQUIREMENTS YOU MUST FOLLOW (SECTION 12); NO WARRANTY OF ANY KIND FOR THE SOFTWARE AND A WAIVER OF THE LOUISIANA WARRANTY AGAINST REDHIBITORY DEFECTS (SECTION 16); LIMITS ON HAPTECH’S LIABILITY (SECTION 17); AND BINDING ARBITRATION, A CLASS-ACTION WAIVER AND A JURY-TRIAL WAIVER (SECTION 21).
1. AGREEMENT AND ACCEPTANCE
1.1 Parties. This EULA is between Haptech, Inc. (d/b/a Haptech Defense Systems), a Louisiana corporation (“Haptech,” “we” or “us”), and the organization that acquires or uses the Product (“Customer” or “you”). If you accept this EULA on behalf of an organization, you represent that you are authorized to bind that organization, and “Customer” means that organization.
1.2 How You Accept. You accept this EULA by (a) selecting “I Accept” when Haptech Manager first starts or when a new version of this EULA is presented; (b) installing, accessing or using the Software; or (c) entering into a purchase contract with Haptech or an Authorized Reseller that incorporates this EULA.
1.3 Authorized Users. Customer must ensure that its Authorized Users comply with this EULA and is responsible for their acts and omissions in using the Product.
1.4 Record of Acceptance. Haptech Manager keeps a record of each acceptance, including the name or role entered by the person accepting, the organization, the date and time, the EULA version and the Hub serial number. When the Hub next connects through a Service Connection, including at license renewal, it sends Haptech a receipt of that record that contains the organization, the date and time, the EULA version and an identifier of the exact text accepted, the Hub serial number, the customer category and country recorded for the Hub, the acknowledgments given and the Notice Contact, but not the name or role of any individual. These records are evidence of Customer’s acceptance. Where Customer accepts this EULA under Section 1.2(b) or (c) for the Windows Release or for ERIS Devices used without a Hub (Sections 3.4 and 4.9), Haptech’s record of the Order is the record of acceptance.
1.5 Business Use Only. Haptech sells and licenses the Product only to businesses, government entities, educational institutions and other organizations for use in their operations, and not to individuals for personal, family or household purposes. Customer represents that it is acquiring and using the Product for business, government or institutional purposes, and that the person accepting this EULA does so in that capacity.
2. DEFINITIONS
In this EULA, the following terms have these meanings:
“Add-On” means a feature, module, tool or capability that Haptech designates as separately licensed, including Enhanced Data Capture. Add-Ons are licensed only under an Order.
“Additional Functions” has the meaning given in Section 4.2.
“Authorized Reseller” means a prime contractor, subcontractor at any tier, systems integrator, distributor or reseller that Haptech has authorized to sell, integrate or distribute the Product.
“Authorized User” means an employee, contractor, service member, instructor, trainee or other individual whom Customer permits to use the Product for Customer’s purposes.
“Base License” has the meaning given in Section 4.1.
“Beta Feature” has the meaning given in Section 4.8.
“Confidential Information” has the meaning given in Section 15.1.
“Continuity Event” has the meaning given in Section 8.7.
“Core Functions” has the meaning given in Section 4.1.
“Device Firmware” means the firmware and embedded software in an ERIS Device, including the firmware of its controllers, sensors and radios.
“Diagnostic Data” has the meaning given in Section 10.4.
“Documentation” means the user, maintenance, safety and interface documentation that Haptech provides for the Product, including the Operator and Safety Manual, safety notices, and the Open API interface documentation, as Haptech updates it from time to time.
“Enhanced Data Capture” means higher-rate, higher-resolution or higher-accuracy data capture and related reporting functions that Haptech designates as an Add-On.
“Equipment Data” has the meaning given in Section 10.1.
“ERIS Device” means an ERIS™ training weapon, weapon surrogate, drop-in kit or other device supplied by Haptech that is designed to connect to a Hub or, as provided in Section 4.9, to the Windows Release.
“Facility” means any location where Customer operates the Product.
“Haptech Manager” means Haptech’s application software that runs on the Hub, including its user interface and the Open API.
“Hub” means the Haptech Hub computer, together with its operating system, software image and configuration as supplied by Haptech.
“Integrated System” means a training system that combines the Product with other hardware or software, such as an instructor operator station (“IOS”) or a simulation system.
“Integrator Content” means software, content or interfaces created by or for an Authorized Reseller or Customer that interoperate with the Product through the Open API. Integrator Content does not include any part of the Software.
“License Management and Security Features” has the meaning given in Section 5.2.
“Limited Mode” has the meaning given in Section 5.5.
“Loaner Unit” has the meaning given in Section 4.5.
“Non-Identifying ID” has the meaning given in Section 10.1.
“Notice Contact” has the meaning given in Section 5.7.
“Open API” means the application programming interface, message set and protocols that Haptech makes available for external systems to communicate with Haptech Manager, as described in the Documentation.
“Open API Credentials” means the license keys, tokens, codes, signals or other credentials that Haptech issues to enable the Open API or other features of the Software.
“Operator and Safety Manual” means the Haptech ERIS Operator and Safety Manual, as published and updated by Haptech from time to time.
“Order” means a quote, purchase order, invoice, license certificate or other written ordering document accepted by Haptech or by an Authorized Reseller that identifies the Product and any Add-Ons, the applicable fees, and whether each Add-On license is perpetual or for a Subscription Term.
“Physiological Data” has the meaning given in Section 10.6.
“Product” means the Hub and ERIS Devices acquired by Customer, together with the Software installed on or supplied for them.
“Service Connection” has the meaning given in Section 11.1.
“Software” means, in object code form only, the Hub software image, Haptech Manager, the Open API, the Device Firmware, any Add-Ons and all Updates, together with the Documentation, but excluding Third-Party Components to the extent governed by their own licenses under Section 13.
“Subscription Term” means the period stated in an Order during which a subscription license to an Add-On is in effect.
“Support Period” has the meaning given in Section 8.6.
“Supported Network Configuration” has the meaning given in Section 11.1.
“Third-Party Components” has the meaning given in Section 13.1.
“Training Records” has the meaning given in Section 10.2.
“Update” means any patch, fix, update, upgrade, new version or new release of the Software that Haptech provides.
“Windows Release” means the earlier release of Haptech Manager, version 3.6.23 and earlier versions, that ran on Windows computers. Haptech makes only version 3.6.23 available, as provided in Section 4.9, and supports no Windows Release (Sections 4.1 and 4.9).
3. IF YOU DO NOT ACCEPT: DECLINE AND REFUND
3.1 Do Not Use. If you do not accept this EULA, select “Decline” and do not use the Software or the Hub.
3.2 Refund. If you decline this EULA at first launch, you may return the Hub for a refund of its purchase price, as follows:
(a) If you bought the Hub directly from Haptech, Haptech will issue the refund. If you bought it from an Authorized Reseller, including a distributor or prime contractor, that Authorized Reseller will issue the refund. Haptech requires its Authorized Resellers to honor this Section 3.
(b) You must request the return within 30 days after the Hub is delivered to you and obtain a return merchandise authorization (RMA) number from the party that sold you the Hub.
(c) You must return the Hub complete — with its power supply, accessories and Documentation — undamaged and, where available, in its original packaging, with proof of purchase. You may keep any ERIS Devices you acquired with the Hub, or return them under the seller’s return policy. ERIS Devices you keep remain subject to the Operator and Safety Manual and may be used as described in Section 4.9.
(d) If the Hub was sold as part of an Integrated System or a larger purchase, the refund is the portion of the purchase price attributable to the Hub and its Software, as stated in the Order or, if the Order does not state it, as reasonably determined by the seller from its then-current list prices.
(e) You must not have accepted this EULA or used the Hub beyond the steps needed to view and decline this EULA.
(f) Unless the seller agrees otherwise, return shipping is at your expense. Any lithium-ion battery you return must be shipped in compliance with the regulations that apply to shipping lithium batteries (Section 12.9).
3.3 Exclusive Remedy. A refund under this Section 3 is your sole remedy for declining this EULA. Declining this EULA does not affect your ownership of hardware you keep.
3.4 ERIS Devices Supplied Without a Hub. ERIS Devices that Haptech or an Authorized Reseller supplies without a Hub do not display this EULA; you accept this EULA for their Device Firmware by using them (Section 1.2(b)). If you do not accept this EULA, do not use them. You may return them, unused and complete, within 30 days after they are delivered to you, with an RMA number from the party that sold them to you, for a refund of their price; Sections 3.2(a), (d) and (f) apply, and that refund is your sole remedy for declining this EULA as to those ERIS Devices.
4. LICENSE GRANT
4.1 Base License. Subject to Customer’s compliance with this EULA, Haptech grants Customer a limited, non-exclusive, non-sublicensable license, transferable only under Section 9, to use the Core Functions of the Software in object code form, solely as installed on or supplied for the Hub and ERIS Devices that make up the Product and in accordance with the Documentation, for Customer’s internal training, evaluation, maintenance and integration purposes (the “Base License”). The “Core Functions” are the features that were available in the Windows Release, including its original Open API feature set, as implemented in the Haptech Manager software on the Hub, together with the Device Firmware functions needed to operate ERIS Devices through them, as listed in the Documentation. The Base License is included in the purchase price of the Product, requires no additional fee, and is perpetual for the life of the Product unless this EULA is terminated under Section 19. The Base License does not include Additional Functions or Add-Ons.
4.2 Additional Functions. The Software on the Hub also includes functions that were not available in the Windows Release, including features introduced in the Hub release and later Updates (“Additional Functions”). Additional Functions are not part of the Base License. For each Additional Function that Haptech has not designated as an Add-On, Haptech grants Customer a limited, non-exclusive, non-sublicensable license to use it under the same conditions as the Base License, at no additional charge, for as long as the Hub has a current license period under Section 5.5 (the “Additional Functions License”). Haptech may designate any Additional Function as an Add-On, begin charging for it, or withdraw it, effective at the start of a later license period, by giving Customer at least 60 days’ notice through Haptech Manager or to the Notice Contact. Haptech will never convert a Core Function into an Additional Function or an Add-On. The Documentation identifies which functions are Core Functions and which are Additional Functions.
4.3 Training and Entertainment Sessions. The Base License and the Additional Functions License permit Customer to operate the Product to provide training or entertainment sessions to Customer’s own trainees, students, clients or patrons at a Facility under Customer’s supervision, provided Customer complies with Section 12 and, where it applies, Section 18.2. Customer may not otherwise rent, lease, lend or make the Product or the Software available to third parties.
4.4 Add-Ons. Enhanced Data Capture and other Add-Ons are licensed only under an Order and on payment of the applicable fees. Each Order states whether an Add-On is licensed (a) perpetually or (b) on a subscription basis for a Subscription Term. A subscription renews only if the Order provides for renewal or Customer places a renewal Order. When a Subscription Term ends without renewal, the Add-On stops functioning, but the Base License and Customer’s access to Equipment Data already stored on the Hub are not affected. Add-Ons also pause while a Hub is in Limited Mode (Section 5.5), unless the Order for a perpetual Add-On states otherwise. Haptech may designate Additional Functions as Add-Ons only as provided in Section 4.2, and will never convert a Core Function into an Add-On. As of this version of this EULA, Haptech offers no paid Add-Ons or subscriptions: the Additional Functions are currently provided at no charge under the Additional Functions License, and license renewal under Section 5.5 is free of charge.
4.5 Evaluation, Demonstration and Loaner Units. If Haptech provides a Product or Add-On for evaluation, demonstration or loan — including a loaner unit supplied while Customer’s Product is being repaired — (each, a “Loaner Unit”), Customer may use the Loaner Unit only for the purpose and period that Haptech authorizes in writing (or 90 days if no period is stated), under this EULA. An evaluation or demonstration unit may not be used for operational training or any commercial purpose unless Haptech agrees in writing. Loaner Units remain Haptech’s property; Customer must keep them in good condition, is responsible for loss or damage to them other than normal wear, and must return them when the authorized period ends or Haptech requests them. Loaner Units and evaluation Add-Ons are provided “AS IS,” without warranty or refund right.
4.6 Documentation. Customer may use and copy the Documentation only as needed to use the Product under this EULA, and may provide the Operator and Safety Manual to its Authorized Users.
4.7 Licensed, Not Sold. The Software is licensed, not sold. Customer’s purchase of a Hub or ERIS Device transfers ownership of the hardware only. Haptech and its licensors reserve all rights not expressly granted in this EULA, and no rights are granted by implication or estoppel.
4.8 Beta Features. Haptech may make available features, Updates or Add-Ons that it labels as beta, preview, pilot, early-access or pre-release (“Beta Features”), which may include physiological monitoring when it is first released (Section 10.6). Beta Features are provided for testing and evaluation, “AS IS,” without warranty, support commitment or refund right. They may be incomplete, may change or be withdrawn at any time, and must not be relied on for operational training, qualification or any safety-related purpose. While a Beta Feature is enabled, Haptech may collect additional Diagnostic Data about it, as described when the Beta Feature is offered. Sections 16 and 17 apply to Beta Features.
4.9 ERIS Devices Used Without a Hub; the Windows Release. The Haptech Hub is the supported platform for ERIS Devices. Haptech makes the final Windows Release, version 3.6.23, available on request for use with ERIS Devices that are not connected to a Hub, and will issue no later Windows Release. The Windows Release, and the Device Firmware in ERIS Devices used without a Hub, are provided “AS IS,” without Updates, support or warranty, and subject to Sections 6, 12, 16 and 17; Section 5 does not apply to the Windows Release. Customer accepts this EULA for the Windows Release under Section 1.2(b) or (c). ERIS Devices with Device Firmware version 3.6.0 or later must be used only with Windows Release 3.6.23; earlier Windows Releases are not compatible with them. Because the Windows Release depends on radio and computing hardware that the Hub does not, later Device Firmware releases may not be compatible with the Windows Release, and Haptech may release Device Firmware that operates only with a Hub. Haptech is not obliged to keep any Device Firmware release compatible with the Windows Release; it will state in the Documentation for each Device Firmware release whether that release is compatible with it, and Customer may continue to use an earlier compatible Device Firmware version under Section 8.3. Haptech is not responsible for the compatibility of the Windows Release with any operating system or third-party software, and may stop making the Windows Release available at any time without affecting copies already delivered. The Windows Release is licensed, not sold; Haptech retains all right, title and interest in it; Sections 6, 14 and 15 apply to it as they apply to the Software; and it remains Haptech’s Confidential Information.
5. LICENSE MANAGEMENT AND SECURITY FEATURES
5.1 Open API Credentials. Where the Documentation provides for them, use of the Open API requires Open API Credentials issued by Haptech. Open API Credentials are Haptech Confidential Information. Customer and its Authorized Reseller may use them only to operate the Product and to develop Integrator Content under this EULA, may not share them outside their organizations except with each other for the Product, and must notify Haptech promptly if any are lost or compromised. Haptech may revoke and reissue compromised Open API Credentials.
5.2 License Management and Security Features. The Software includes license management and security features, including license keys and Open API Credentials, that verify licenses and Add-On entitlements and that Haptech may update, time-limit or revoke, remotely or by Update (the “License Management and Security Features”). Customer must not disable, bypass or interfere with them. Customer acknowledges that this Section 5 was brought to its attention and that Customer separately acknowledged it at first launch.
5.3 Suspension. Through the License Management and Security Features, Haptech may suspend some or all functions of a Hub, Haptech Manager, an Add-On or an ERIS Device, but only:
(a) to end an Add-On whose Subscription Term has expired without renewal, or whose fees remain unpaid 30 days after written notice under Section 5.7, limited to that Add-On;
(b) when amounts that Customer itself owes Haptech for the Product remain unpaid 30 days after Haptech gives written notice of non-payment under Section 5.7, or, where Customer bought the Product from an Authorized Reseller, when that Authorized Reseller certifies to Haptech in writing that Customer has not paid it for the Product and asks Haptech to suspend, with the same notice and cure period. An Authorized Reseller’s failure to pay Haptech is never a ground to suspend a Customer that has paid the Authorized Reseller;
(c) when Customer materially breaches this EULA and does not cure the breach within 30 days after written notice under Section 5.7, or immediately if Customer circumvents the License Management and Security Features, distributes the Software without authorization or breaches Section 6(k) or Section 20;
(d) when required by law, regulation or court order; or
(e) when Haptech reasonably determines that a safety or security issue presents a risk of injury, property damage, or compromise of a network or system. In that case Haptech will limit the suspension to the affected functions and to the time needed to address the issue, notify Customer as soon as practicable, and restore the affected functions, by Update or otherwise, once the issue is resolved.
5.4 Safe Operation. A suspension never affects any safety interlock, warning or other protective function, and is designed to take effect only when an affected ERIS Device is not firing or in an active training state (for example, at the next power cycle or while idle).
5.5 Periodic License Renewal. Each Hub’s license key is valid for a license period of 6 or 12 months, as Haptech sets for that Hub and as shown in Haptech Manager. The first license period begins when this EULA is first accepted on the Hub. To keep using all functions of the Hub, Customer must renew the license key (re-registering the Hub) before the license period ends by connecting the Hub to the internet through a Service Connection (Section 11.1) so that it can reach Haptech’s online license service, which renews the key automatically. A temporary connection is sufficient, and the Hub may be disconnected once renewal completes; Haptech Manager shows the result. Where the Documentation for the Hub’s release provides for it, Customer may instead renew a Hub that cannot be connected by loading a signed renewal file obtained from Haptech through Haptech Manager, as the Documentation describes. While connected, the Hub may also receive Updates and, if Diagnostics Sharing is ON, send Diagnostic Data (Section 10.5). Haptech Manager displays renewal reminders beginning 30 days before the license period ends. If the Hub attempts to renew during the last 30 days of the license period and renewal fails for a reason other than the Hub’s inability to reach Haptech’s license service through a Service Connection — for example, because that service is unavailable — the license period is extended automatically by a grace period of 14 days beyond its scheduled end, once per license period, or until renewal succeeds if sooner. If the license key is not renewed, the Hub operates in a limited mode until it is renewed (“Limited Mode”). In Limited Mode, the Core Functions, all safety functions, viewing this EULA and the Documentation, license renewal and export of Equipment Data and Physiological Data stored on the Hub continue to work, while the Additional Functions, predictive maintenance and all Add-Ons (unless the Order for a perpetual Add-On states otherwise) pause, as further described in the Documentation. The change to Limited Mode takes effect only as provided in Section 5.4, data stored on the Hub is not affected, and renewing the license key restores full operation. Haptech will not charge for, or unreasonably delay, renewal of the Base License. If Haptech stops providing renewals, Section 8.7 applies.
5.6 Government End Users. Sections 5.3 through 5.5 and 5.7 are subject to Part A, Section A6. Section 5.5 does not apply to U.S. Government End Users unless their Government Contract provides otherwise.
5.7 Notice, Cure and Reinstatement. The email address that Customer provided with its Order, as recorded by Haptech or the Authorized Reseller at the time of sale, is Customer’s contact for license notices (the “Notice Contact”). Haptech Manager shows the Notice Contact recorded for the Hub. Customer may add or change a Notice Contact address at any time by written request to support@haptech.com sent from the current Notice Contact or from another address that Haptech can verify as Customer’s; Haptech will record the change within two business days and confirm it by email to the previous and the new addresses, and the Hub shows the change when it next connects through a Service Connection. If no address was provided with the Order, Haptech Manager asks for one at first launch. Except for a suspension under Section 5.3(d) or (e), or an immediate suspension under Section 5.3(c), Haptech will, before suspending any function: (a) send written notice to the Notice Contact and display it in Haptech Manager, describing the reason for the suspension, what Customer must do to avoid it, and how to reach Haptech; (b) allow the 30-day cure period stated in Section 5.3, or any longer period that applicable law requires; and (c) send a final notice at least 10 days before the suspension takes effect. Haptech will consider in good faith any response Customer gives during the cure period. If a suspension results from Haptech’s error — for example, a payment that was made but not recorded — Haptech will restore the affected functions within one business day after confirming the error, at no charge, and will extend any affected license period by the time lost. Customer may contact Haptech at any time at support@haptech.com about a notice.
6. RESTRICTIONS
Except as expressly permitted by this EULA or by the license of a Third-Party Component, Customer must not, and must not permit anyone else to:
(a) copy the Software, except as installed on the Product or as the Documentation permits for backup and recovery;
(b) modify, translate or create derivative works of the Software;
(c) reverse engineer, decompile, disassemble or attempt to derive the source code of the Software, or extract firmware from any Hub or ERIS Device, except to the extent applicable law expressly permits it despite this restriction, or as the license of a Third-Party Component permits (including to debug modifications to libraries licensed under the GNU Lesser General Public License);
(d) install or run Haptech Manager or the Hub software on any hardware other than a Hub supplied by Haptech, or use the Software or the Open API to operate any weapon-simulation device other than an ERIS Device or a device that Haptech identifies in the Documentation as compatible;
(e) circumvent, disable or interfere with the License Management and Security Features, encryption or any other technical protection in the Software;
(f) disable, bypass, alter or interfere with any safety interlock, sensor, temperature or fault monitoring, warning or other protective function of the Product;
(g) sell, rent, lease, lend, sublicense, distribute or otherwise transfer the Software separately from the Product, or use it to provide hosting or service-bureau services, except as permitted by Sections 4.3, 7 and 9;
(h) remove, alter or obscure any proprietary notice, label, safety warning or marking on the Product or in the Software;
(i) use the Software or the Documentation to develop a product that competes with the Product;
(j) use the Product in violation of law or in any manner that endangers any person; or
(k) use the Software, the Open API, the Device Firmware or Equipment Data to aim, fire, control, target or guide any real weapon, munition or weapon system, or as part of any operational, fire-control, targeting or weapons-control system. The Product is designed, tested and licensed for training only. Haptech does not support any such use; any such use is at Customer’s sole risk, voids all warranties, and ends the license for the affected Product.
7. AUTHORIZED RESELLERS AND INTEGRATORS
7.1 Integration License. If Customer is an Authorized Reseller, Haptech also grants Customer, for as long as its authorization continues, a limited, non-exclusive, non-transferable license to use the Software, the Open API and the interface Documentation to develop, test, demonstrate, integrate and support Integrator Content and Integrated Systems that include the Product.
7.2 Distribution Conditions. An Authorized Reseller may distribute the Software only as installed on or supplied with the Product, and only if it:
(a) includes this EULA, by incorporation or attachment, in its contract with each customer and identifies Haptech as the licensor;
(b) before delivery, resets each Hub as the Documentation describes so that its customer must accept this EULA at first launch, does not remove, hide or bypass the acceptance screens, and does not accept this EULA on its customer’s behalf unless that customer authorizes it in writing;
(c) honors the decline-and-refund obligations in Section 3 for Hubs it sells;
(d) delivers the Operator and Safety Manual and all safety warnings with the Product, without alteration;
(e) makes no representation, warranty or commitment on Haptech’s behalf, and is solely responsible for any warranty or commitment it gives that is broader than this EULA; and
(f) complies with Section 20 and all applicable laws.
7.3 Integrator Content. As between Haptech and the Authorized Reseller or Customer that creates it, that party owns its Integrator Content. Integrator Content may include the message definitions and other portions of the interface Documentation needed to interoperate with the Open API, with Haptech’s copyright notice retained, but may not include any other part of the Software.
7.4 Responsibility. Each Authorized Reseller is responsible for its Integrator Content and Integrated Systems, including their safety, and for its compliance with this Section 7.
8. UPDATES, SUPPORT PERIOD AND CONTINUITY
8.1 Updates. Haptech may provide Updates for the Hub software, Haptech Manager, the Open API and Device Firmware. Updates reach a Hub by download whenever the Hub connects through a Service Connection. A Hub on a closed network must be connected through a Service Connection to receive Updates and may be disconnected afterwards, except that, where the Documentation for the Hub’s release provides for it, Customer may load a signed update file obtained from Haptech through Haptech Manager, as the Documentation describes; Haptech does not otherwise supply Updates on physical media. Updates are part of the Software and are governed by this EULA unless Haptech provides different terms with them.
8.2 Hub Updates Install Automatically. Updates for the Hub software, Haptech Manager and the Open API install automatically once they reach the Hub, and this cannot be turned off. To protect Customer’s operations: (a) an Update installs only when no ERIS Device is firing or in an active training state, for example at the next idle period or power cycle (Section 5.4); (b) Customer may defer an Update that Haptech has not designated as required for safety or security for up to 90 days after it reaches the Hub, after which it installs at the next opportunity; (c) release notes identifying any change to the Open API or to the Core Functions are available in Haptech Manager before and after installation; and (d) an Update delivered with a new version of this EULA installs only after Customer accepts that version (Section 8.5). Haptech uses reasonable efforts to keep each Update compatible with the Open API message set documented for the prior release.
8.3 Device Firmware Updates. Device Firmware Updates are not installed automatically. Haptech Manager notifies Customer when a Device Firmware Update is available, and Customer installs it on each ERIS Device when ready — through Haptech Manager where the Hub release delivers Device Firmware Updates to ERIS Devices, and otherwise by the method the Documentation describes for that release. Haptech may designate a Device Firmware Update as required for safety or security, and may condition support, warranty service, or the use of a Hub release with an ERIS Device on installation of that Update.
8.4 Responsibility for Updates. Haptech is not responsible for any problem that a required Update, or an Update that Customer deferred or declined to install, would have prevented. Updates may add, change or remove features, subject to Sections 4.2 and 4.4.
8.5 New Versions of This EULA. Haptech may publish new versions of this EULA. A new version applies only to Software delivered with it and only after Customer accepts it when it is presented at installation or first launch or, for Software that presents no screen, under Section 1.2(b) or (c). If Customer declines a new version, Customer may continue to use its current Software version under the version of this EULA it previously accepted, but may not install the Update. Continued use alone never changes the terms Customer has accepted.
8.6 Support Period. Haptech will make license renewals under Section 5.5, safety and security Updates, and product support available for each Hub for at least five years after the Hub is delivered to Customer (the “Support Period”), and will give at least 12 months’ notice, through Haptech Manager and to the Notice Contact, before it ends support for a Hub model.
8.7 End of Support and Continuity. Before the Support Period for a Hub ends, and in any case if Haptech ceases ordinary business operations, enters liquidation or dissolution, or stops providing renewals under Section 5.5 without a successor that assumes Haptech’s obligations under this EULA (each, a “Continuity Event”), Haptech will make available to Customer at no charge: (a) a permanent license key, delivered as a signed file that Customer loads on the Hub through Haptech Manager as the Documentation describes, or an Update, that removes the periodic renewal requirement so that the Base License, the Additional Functions enabled on the Hub at that time, and any perpetual Add-On continue to operate for the life of the Product; and (b) the then-current Documentation for Customer’s Software version (together, the “Continuity Release”). Haptech keeps the Continuity Release for each Hub ready for issue, and on a Continuity Event Haptech, its successor or its liquidator will issue it to Customer; Customer’s rights under Section 8.8 apply in addition. Haptech does not provide source code. Any escrow or other continuity arrangement beyond this Section 8.7 requires a signed agreement under Section 23.1(b).
8.8 Licenses in Bankruptcy. The licenses granted in this EULA are licenses of rights to “intellectual property” as defined in Section 101(35A) of the United States Bankruptcy Code. If Haptech becomes a debtor in a bankruptcy case, Customer retains, and may fully exercise, its rights and elections under 11 U.S.C. § 365(n).
9. TRANSFER
9.1 With the Product Only. Customer may transfer the Base License only together with the Hub or ERIS Device on which the Software is installed, to a new owner that accepts this EULA. Before the transfer, Customer must reset the Hub to its initial configuration — using the reset function in Haptech Manager where the Hub’s release provides one, or otherwise by asking Haptech to reset it — so that the new owner sets up the Hub and is presented with this EULA at first launch, and must transfer all Documentation with the Product.
9.2 Add-Ons and Credentials. Add-On licenses and Open API Credentials transfer only with Haptech’s prior written consent, which Haptech will not unreasonably withhold for perpetual Add-On licenses. Haptech may reissue Open API Credentials to the new owner.
9.3 Restrictions. No transfer may breach Section 20. Any transfer not permitted by this Section 9 is void.
9.4 Warranty Period. A transfer does not extend any warranty period.
10. EQUIPMENT DATA, DIAGNOSTIC DATA, PHYSIOLOGICAL DATA AND PRIVACY
10.1 Equipment Data. The Product generates data about its own operation during use — for example, trigger pulls, shot events and timing, ammunition counts, bolt and recoil events, magazine, battery, thermal and motor state, and device position and orientation (“Equipment Data”). Equipment Data is associated only with a device-generated identifier that does not identify any individual (a “Non-Identifying ID”) and does not include Physiological Data. The Product delivers Equipment Data to Customer’s systems through the Open API and stores session logs on the Hub. The Product is not designed to collect names, contact information, service numbers, scores or other information that identifies trainees, and Customer must not enter such information into the Software unless the Documentation expressly provides for it.
10.2 Rights in Equipment Data. Each party may use Equipment Data as provided in this Section 10, and neither party’s use requires the other’s consent. Customer may store, copy, combine with its own information and disclose the Equipment Data it receives through the Open API or exports from the Hub, for any purpose, without restriction or fee, and owns the records it creates by combining Equipment Data with its own information, including trainee identities and scores (“Training Records”). Haptech may use the Equipment Data it receives under Section 10.5, or that Customer otherwise provides, (a) to support and maintain the Product, to provide predictive maintenance and product-safety services, and to offer features to Customer, and (b) in a form that does not identify Customer, to improve the Product and to research, design and develop features, Add-Ons, products and services. Haptech does not receive Training Records and will not use Equipment Data to identify any individual.
10.3 Identifying Individuals. If Customer, its Integrated System or its IOS links a Non-Identifying ID to an individual, Customer is solely responsible for the resulting Training Records and any personal data in them, and for giving any notices and obtaining any consents that applicable law or Customer’s own policies require, including for Physiological Data and for its sharing with Haptech under Sections 10.6 and 10.7.
10.4 Diagnostic Data. “Diagnostic Data” means the technical information that the Hub sends to Haptech automatically under Section 10.5: the Equipment Data and device-health information described in the Documentation — such as fault and event records, logs, battery, thermal and motor data, shot and cycle counts, configuration, firmware versions and serial numbers — and, as provided in Section 10.6, Physiological Data. Diagnostic Data does not include Training Records or any information that identifies an individual. Separately from Diagnostic Data, whenever the Hub connects through a Service Connection it exchanges with Haptech’s license and update services only the information those services need to perform their functions: the Hub serial number, the software and firmware versions installed, the license key identifier, the acceptance receipt described in Section 1.4, and the status reports of the Hub’s update runtime — which software components are installed and running, their versions and configuration settings, and when each started, stopped or restarted — together with whether the Hub is connected. That exchange is not Diagnostic Data, and the Diagnostics Sharing setting does not affect it.
10.5 Diagnostics Sharing and Predictive Maintenance. When a Hub can connect to Haptech’s servers and the “Diagnostics Sharing” setting in Haptech Manager is ON, the Hub sends Diagnostic Data to Haptech automatically. Haptech uses it to support the Product and to provide predictive maintenance, which identifies components that may need service. Diagnostics Sharing is ON by default, except as provided in Part A, Section A9. Customer may turn it OFF at any time in Haptech Manager or, in a Hub release that does not yet show the setting in Haptech Manager, by instructing Haptech in writing, which Haptech will promptly carry out for that Hub through its Service Connection; if Customer does, predictive maintenance and other features that depend on Diagnostic Data may stop functioning. When it is OFF, Haptech receives Diagnostic Data only when Customer chooses to send it, for example in a support bundle or with a returned Product.
10.6 Physiological Data (Planned Feature). Physiological monitoring is not supported in the current Hub release. Haptech plans to add it in future Hub releases, and this Section 10.6 applies once a Hub runs a release that supports it. “Physiological Data” means breathing-rate, heart-rate and other data from physiological monitors connected to the Product, associated only with a Non-Identifying ID. If Customer enables physiological monitoring, the Hub stores Physiological Data separately from Equipment Data, in its own files or folders, so that it can be tracked, exported and deleted on its own. While Diagnostics Sharing is ON, Physiological Data is included in the Diagnostic Data sent to Haptech by default only for Hubs supplied to defense, military, law-enforcement or other government security customers, or to their contractors, for training their personnel. For all other Hubs — including Hubs used at entertainment venues or other Facilities open to members of the public, and any Hub located in the European Union, the European Economic Area or the United Kingdom — Physiological Data is sent only if Customer turns on the separate “Share Physiological Data” setting. Customer may turn that setting on only after obtaining any consent that applicable law requires for the uses described in Section 10.7, and may turn it off at any time without turning off Diagnostics Sharing. Haptech’s remote access to Physiological Data stored on the Hub is the same as for Equipment Data: through Diagnostics Sharing while Share Physiological Data is on, and through a service session approved under Section 11.6.
10.7 Haptech’s Use of Data. Haptech may use Diagnostic Data, Equipment Data as provided in Section 10.2, and any Training Records or other data that Customer chooses to provide for support, to provide support, warranty, repair, predictive maintenance and recall services; to maintain the safety and security of its products; and, in de-identified or aggregated form that does not identify Customer, to improve its products and services. While Share Physiological Data is on, Haptech may use the de-identified Physiological Data it receives for the same purposes as Equipment Data under Section 10.2 — including to offer features to Customer and to research, design and develop features, Add-Ons, products and services — in aggregated or de-identified form only, stored separately from Equipment Data, and never to identify, profile, diagnose or monitor any individual. Haptech will not sell Diagnostic Data, Equipment Data or Physiological Data, will not attempt to identify any individual from them, and will contractually require every party it shares them with to make the same commitments. Haptech shares them only with service providers that perform services for Haptech, such as repair and return-processing partners, under those commitments and under confidentiality obligations at least as protective as this EULA.
10.8 Retention and Deletion. Haptech keeps Diagnostic Data and Physiological Data for as long as needed for these purposes. Customer may ask Haptech to delete the Diagnostic Data or Physiological Data received from its Hubs, and Haptech will do so except where it must retain data by law or for an open warranty, safety or recall matter; aggregated results that identify neither Customer nor any individual may be kept.
10.9 Not a Medical Device. The Product is not a medical device. Physiological Data is collected for training feedback and product improvement only and must not be used to diagnose, treat or monitor any medical condition. Haptech’s product-safety uses under this Section 10 concern the safety of the Product, not the health of any individual.
10.10 Data on the Hub. Equipment Data session logs and any Physiological Data are stored on the Hub under Customer’s control. Customer is responsible for backing up, protecting, and lawfully retaining and deleting data on its Hubs, and for removing it before returning or transferring a Hub.
10.11 Storage and Safeguards. Haptech stores Diagnostic Data, Physiological Data and any data that Customer provides to Haptech on servers located in the United States, keeps Physiological Data separate from Equipment Data, and protects them with reasonable administrative, technical and physical safeguards. None of them is designed to identify any individual.
10.12 Privacy Notice. Haptech’s privacy notice, published at www.haptechdefense.com/privacy-policy and available in Haptech Manager, describes how Haptech handles data it receives from the Product and the limited personal data of Customer’s representatives that it holds, such as the Notice Contact and the names in acceptance records kept on the Hub. For Hub releases that support Physiological Data, the privacy notice includes a separate section on that data.
11. NETWORK USE AND SECURITY
11.1 Supported Network Configuration. As of this version of this EULA, the Supported Network Configurations are (a) a closed training network that is isolated from the internet, from any enterprise or operational network, and from any classified network, including SIPRNet; and (b) an internet connection, whether temporary or persistent, made through a firewall that permits only outbound connections, used solely to reach Haptech’s online license, update and diagnostics services and the cloud platform services on which Haptech operates them — the device-management service, the software registries, the storage service and public time services — each as Schedule 1 lists them (a “Service Connection”). Schedule 1 is part of this EULA; it lists, for each destination a Service Connection reaches, its purpose, its operator, the kind of data that travels, when, and the setting that controls it. Haptech may designate additional Supported Network Configurations for specific Software versions in the Documentation or release notes.
11.2 Unsupported Connections. CUSTOMER CONNECTS A HUB OR ERIS DEVICE TO ANY NETWORK OTHER THAN A SUPPORTED NETWORK CONFIGURATION — INCLUDING THE INTERNET OTHER THAN THROUGH A SERVICE CONNECTION, AN ENTERPRISE OR OPERATIONAL NETWORK, OR A CLASSIFIED NETWORK — ENTIRELY AT CUSTOMER’S OWN RISK. TO THE FULLEST EXTENT PERMITTED BY LAW, HAPTECH HAS NO LIABILITY FOR ANY UNAUTHORIZED ACCESS, MALWARE, LOSS OR CORRUPTION OF DATA, COMPROMISE OF A NETWORK OR SYSTEM, OR OTHER LOSS ARISING FROM AN UNSUPPORTED CONNECTION.
11.3 Customer Security Responsibilities. Customer is responsible for the physical and network security of its Products, including restricting physical access to Hubs and ERIS Devices, creating the administrator account for Haptech Manager at first launch — using the setup code printed on the Hub where the Hub’s release requires one — and protecting its password, protecting Open API Credentials, installing security Updates, and obtaining any security authorization or accreditation required before connecting a Product to any network.
11.4 Security Assessments. Customer may perform non-destructive vulnerability scanning and configuration assessment of a Hub on its own network as required for its security authorization, provided that Customer does not decompile or extract the Software or circumvent license management, and that Customer reports any vulnerability it finds to Haptech confidentially.
11.5 Vulnerability Reports. Customer should report suspected security vulnerabilities to Haptech at the address in Section 22. Haptech will use reasonable efforts to investigate reported vulnerabilities and, where appropriate, address them through Updates, but does not warrant that the Software is free of vulnerabilities (Section 16).
11.6 Service Access. Apart from the automatic license, Update and Diagnostics Sharing functions described in this EULA, Haptech does not access a Hub remotely unless Customer requests or approves a remote service session, in Haptech Manager or in writing. During an approved session, Haptech may view the Hub’s configuration, logs, Equipment Data and, where sharing is on, Physiological Data, adjust settings, install Updates and take the other steps needed to diagnose and resolve the issue, and the Hub records the session. Customer may end a session at any time.
11.7 Updates to Schedule 1. Haptech may update Schedule 1 without publishing a new version of this EULA to reflect a change in the name, address, protocol, port or operator of a listed destination, to remove a destination, or to add a destination of a kind already listed that carries no new kind of data and reaches no new recipient. Haptech makes such an update by posting the updated Schedule at www.haptechdefense.com/eula and in Haptech Manager and by notice to the Notice Contact — at least 30 days before an added destination takes effect, and promptly for any other change — and the update does not require re-acceptance of this EULA. A change that would send a new kind of data, send data to a recipient other than Haptech and the platform services on which Haptech operates its services, or remove a control listed in Schedule 1 is made only in a new version of this EULA under Section 8.5.
12. SAFETY — READ BEFORE USE
12.1 Operator and Safety Manual; Safety Notices. Customer and every Authorized User must read and follow the Operator and Safety Manual and the warnings on the Product. Until Haptech publishes the Operator and Safety Manual, this Section 12 and the Documentation supplied with the Product govern safe use. Safety notices, bulletins and recall notices that Haptech issues are published in the Documentation available in Haptech Manager, and Haptech may also send them to the Notice Contact. Customer must review them when they appear and give them to its Authorized Users.
12.2 Training Devices, Not Toys; No Live Ammunition. ERIS Devices are professional training devices, not toys, and must never be given to or used by anyone under the minimum age in Section 12.4. Keep live ammunition out of the training area. Never load live ammunition into, or attempt to fire live ammunition from, an ERIS Device or a weapon fitted with an ERIS drop-in kit. Before installing a drop-in kit in a host weapon, clear the weapon and verify that it is unloaded, as the Documentation describes. Handle every ERIS Device with the same muzzle and trigger discipline as a live weapon, and aim only at the training screen or target area that the instructor designates.
12.3 Supervision. Training must be supervised by a qualified instructor or range safety officer who briefs every Authorized User on these safety requirements before use. Customer must establish and enforce Facility safety rules, inspect the Product before each use, and remove any damaged or malfunctioning Product from service.
12.4 Minimum Age. Authorized Users must be at least 17 years old. Users under 18 may use the Product only with the consent of a parent or guardian and under direct supervision.
12.5 Recoil Force. ERIS Devices generate recoil forces comparable to those of the weapon being simulated. Hold and brace the device as trained. Persons who are pregnant, or who have a heart condition, an injury to the shoulder, neck, back, wrist or hand, or any other medical condition that recoil or physical exertion could aggravate, should consult a physician before use.
12.6 Moving Parts and Pinch Points. The bolt, charging handle and other moving parts are driven by an electric motor and can move suddenly whenever an ERIS Device is powered, including when the device returns the bolt to battery on its own. Keep fingers, hands, hair and clothing clear of the ejection port, bolt path, charging handle and other moving parts, and power the device off before clearing a malfunction, cleaning it or performing maintenance.
12.7 Hot Surfaces. The area over the linear motor, the bolt area when the bolt is open, and the metal surface of the battery pack can become hot during extended or rapid firing. Temperature sensors monitor the linear motor, the battery pack and the power electronics in the grip, but surfaces can still be hot to the touch. Allow the device to cool before touching these areas, changing batteries or performing maintenance.
12.8 Magnets and Magnetic Fields. The linear motor in each ERIS Device contains strong permanent magnets and produces magnetic fields during operation. Keep ERIS Devices at least 15 cm (6 in) away from pacemakers, defibrillators and other implanted medical devices, and away from magnetic media and magnetically sensitive equipment. Persons with implanted medical devices should consult their physician before use.
12.9 Lithium-Ion Batteries. Use only batteries, magazines and chargers supplied or approved by Haptech. Do not crush, puncture, open, short-circuit, overheat or immerse a battery. Stop using, and isolate, any battery that is swollen, damaged, leaking or unusually hot, or that gives off odor or smoke. Charge only under supervision and on a non-flammable surface, and store, ship and dispose of batteries in accordance with applicable law, including the rules for shipping lithium batteries, which also apply to Products returned to Haptech or an Authorized Reseller.
12.10 Eye Protection and Laser Emitters. Haptech recommends eye protection for everyone in the training area. Haptech recognizes that training doctrine may not allow trainees to wear eye protection except during specific drills, such as drills conducted in protective masks; whenever eye protection is not worn, Customer is responsible for assessing and accepting that risk. Some ERIS Devices include a laser emitter used for shot detection. Laser emitters are Class 1 or Class 3R, as marked on each device. Never look into a laser emitter or aim it at anyone’s eyes, and avoid direct eye exposure to the beam of a Class 3R device.
12.11 Hub and Electrical Safety. Operate the Hub indoors, or as the Documentation otherwise permits, with adequate ventilation and only on its supplied power source. Do not open the Hub or an ERIS Device enclosure except as the Documentation instructs.
12.12 Incidents. Customer must promptly report to Haptech any incident involving injury, property damage, fire or smoke, or any malfunction that creates a safety risk, and cooperate with Haptech’s investigation and with any recall or safety notice.
12.13 Risk Assessment. Customer is responsible for assessing the risks of each Facility and training activity and for ensuring that each Authorized User is fit to participate.
12.14 Transport, Storage and Public Display. ERIS Devices resemble real firearms. Customer must transport them in closed cases, store them securely, keep them out of public view, and not display or expose them in any public place other than a Facility under Customer’s control. Customer must comply with all federal, state and local laws that apply to imitation or look-alike firearms, including laws on their marking, sale, transport, display and alteration, and must not remove or alter any marking that Haptech applies to comply with those laws except where the law permits.
12.15 California Proposition 65. Products sold into California carry on their labels the warning that California’s Proposition 65 requires. The warning that applies to each ERIS Device is also stated in that device’s Documentation. For more information go to www.P65Warnings.ca.gov.
13. THIRD-PARTY AND OPEN-SOURCE COMPONENTS
13.1 Third-Party Components. The Software includes components licensed to Haptech by third parties, including open-source software such as the Linux operating system on the Hub (“Third-Party Components”). Each Third-Party Component is licensed under its own terms, which are listed with the applicable copyright notices in the third-party notices included with the Software and available in Haptech Manager, and are available from Haptech on request. Where those terms grant broader rights than this EULA or require terms different from this EULA, they control for that component, and nothing in this EULA restricts those rights.
13.2 Source Code Offer. For any Third-Party Component licensed under the GNU General Public License, the GNU Lesser General Public License or another license that requires source code to be made available, Haptech will provide the corresponding source code on written request to the address in Section 22, for at least three years after Haptech last distributes the relevant Software version, for a charge no greater than Haptech’s cost of physically performing the distribution.
13.3 Third-Party Products. Breathing monitors and other third-party devices that connect to the Product are governed by their manufacturers’ terms. Haptech is not responsible for third-party devices, Integrator Content or Integrated Systems.
14. INTELLECTUAL PROPERTY AND FEEDBACK
14.1 Ownership. Except for Integrator Content under Section 7.3, Haptech and its licensors own all right, title and interest in and to the Software, the Documentation, the Open API and the ERIS™ technology, and all patents, copyrights, trade secrets, trademarks and other intellectual property rights in or related to the Product, including all modifications and derivative works of any of them.
14.2 No Filings. Customer will not file any patent application, trademark application or other claim of ownership covering the Software, the Product, or Haptech’s technology or Confidential Information, and will not assist anyone else to do so.
14.3 Trademarks. “Haptech,” “Haptech Defense Systems,” “ERIS” and related logos are trademarks of Haptech. This EULA grants no right to use them except to identify the Product accurately. Customer may not use Haptech’s name or trademarks to endorse or promote Customer’s products or services without Haptech’s prior written consent.
14.4 Feedback. If Customer provides suggestions or feedback about the Product, Haptech may use them without restriction or compensation.
14.5 Patent Notice. The Product is covered by one or more patents and pending patent applications listed at www.haptechdefense.com/patents, which is provided to give notice under 35 U.S.C. § 287(a). The list is also shown in Haptech Manager.
15. CONFIDENTIALITY
15.1 Confidential Information. The Software, including its object code, structure and organization; Open API Credentials; non-public Documentation, including interface documentation and specifications; and any other non-public technical or business information that Haptech discloses in connection with the Product are Haptech’s “Confidential Information.” This EULA itself is not confidential.
15.2 Protection. Customer will use Confidential Information only to exercise its rights under this EULA, will protect it with at least the care it uses for its own confidential information of similar importance and never less than reasonable care, and will disclose it only to its Authorized Users, Authorized Resellers and contractors who need it for that purpose and are bound by confidentiality obligations at least as protective as this Section 15.
15.3 Exclusions. These obligations do not apply to information that Customer can show is or becomes public through no fault of Customer, was known to Customer without restriction before receiving it, was independently developed without use of Confidential Information, or was rightfully received from a third party without restriction. Customer may disclose Confidential Information when required by law or court order, after giving Haptech prompt notice where lawful so that Haptech may seek protection.
15.4 Duration. These obligations continue for as long as Customer holds Confidential Information and, for trade secrets, for as long as they remain trade secrets.
16. WARRANTIES AND DISCLAIMERS
16.1 No Software Warranty. TO THE FULLEST EXTENT PERMITTED BY LAW, THE SOFTWARE, THE OPEN API, OPEN API CREDENTIALS, UPDATES, BETA FEATURES, THE WINDOWS RELEASE AND THE DOCUMENTATION ARE PROVIDED “AS IS,” WITH ALL FAULTS AND WITHOUT WARRANTY OF ANY KIND. HAPTECH AND ITS LICENSORS DISCLAIM ALL EXPRESS, IMPLIED AND STATUTORY WARRANTIES, INCLUDING WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, NON-INFRINGEMENT, ACCURACY AND QUIET ENJOYMENT, AND ANY WARRANTY THAT THE SOFTWARE WILL BE UNINTERRUPTED, ERROR-FREE, SECURE OR FREE OF VULNERABILITIES, OR THAT EQUIPMENT DATA WILL BE ACCURATE OR COMPLETE.
16.2 Hardware Remedy. Any warranty for Product hardware is provided solely by the written limited warranty that accompanies the Product: the Limited Warranty & Repair Policy in Haptech’s Terms and Conditions of Sale for Products bought directly from Haptech, or the warranty of the Authorized Reseller for Products bought from it. Under Haptech’s limited warranty, Customer’s sole and exclusive remedy is repair, replacement or refund, at Haptech’s option. No hardware warranty covers the Software, which is governed by Section 16.1.
16.3 Waiver of Warranty Against Redhibitory Defects. WITH RESPECT TO THE SOFTWARE, AND WITH RESPECT TO THE PRODUCT EXCEPT AS PROVIDED IN ANY EXPRESS WRITTEN LIMITED WARRANTY FOR PRODUCT HARDWARE, CUSTOMER EXPRESSLY WAIVES THE WARRANTY AGAINST REDHIBITORY DEFECTS AND THE WARRANTY OF FITNESS FOR USE PROVIDED BY LOUISIANA CIVIL CODE ARTICLES 2520 THROUGH 2548, AND ANY RIGHT TO RESCISSION OF THE SALE OR REDUCTION OF THE PRICE ON THOSE GROUNDS. CUSTOMER ACKNOWLEDGES THAT THIS WAIVER HAS BEEN BROUGHT TO ITS ATTENTION AND EXPLAINED IN THIS SECTION, AND THAT CUSTOMER SEPARATELY ACKNOWLEDGED IT AT FIRST LAUNCH.
16.4 Equipment Data and Predictive Maintenance. Equipment Data, Training Records derived from it, predictive maintenance alerts and other instrumentation outputs are provided for guidance only. Haptech does not warrant that predictive maintenance will identify every condition that requires service, and Customer remains responsible for inspecting the Product before each use under Section 12.3. Haptech does not warrant Equipment Data for, and Customer is solely responsible for any use of it or of Training Records in, any qualification, certification, personnel, disciplinary, medical or legal decision.
16.5 Mandatory Rights. Some jurisdictions do not allow the exclusion of certain warranties. Where a warranty cannot be excluded, it is limited to the shortest duration and narrowest scope that the law permits, and the remedies in Section 16.2 apply.
17. LIMITATION OF LIABILITY
17.1 Excluded Damages. TO THE FULLEST EXTENT PERMITTED BY LAW, HAPTECH AND ITS LICENSORS AND SUPPLIERS WILL NOT BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, EXEMPLARY OR PUNITIVE DAMAGES, OR FOR ANY LOSS OF PROFITS, REVENUE, BUSINESS OR GOODWILL, LOSS OR CORRUPTION OF DATA, COST OF SUBSTITUTE GOODS OR SERVICES, OR BUSINESS INTERRUPTION, ARISING OUT OF OR RELATED TO THIS EULA OR THE PRODUCT, UNDER ANY THEORY OF LIABILITY, EVEN IF ADVISED OF THEIR POSSIBILITY.
17.2 Liability Cap. TO THE FULLEST EXTENT PERMITTED BY LAW, HAPTECH’S TOTAL LIABILITY ARISING OUT OF OR RELATED TO THIS EULA OR THE PRODUCT WILL NOT EXCEED THE AMOUNT CUSTOMER PAID FOR THE PRODUCT GIVING RISE TO THE CLAIM OR, FOR A CLAIM RELATING TO AN ADD-ON, THE FEES CUSTOMER PAID FOR THAT ADD-ON DURING THE 12 MONTHS BEFORE THE CLAIM AROSE.
17.3 Exceptions. NOTHING IN THIS EULA EXCLUDES OR LIMITS ANY LIABILITY THAT CANNOT BE EXCLUDED OR LIMITED UNDER APPLICABLE LAW, INCLUDING, WHERE LOUISIANA CIVIL CODE ARTICLE 2004 APPLIES, LIABILITY FOR INTENTIONAL OR GROSS FAULT OR FOR CAUSING PHYSICAL INJURY TO THE OTHER PARTY.
17.4 Allocation of Risk. The price of the Product and the fees for Add-Ons reflect the allocation of risk in Sections 16 through 18.
17.5 Protection of Resellers and Suppliers. Sections 16 and 17 also protect Haptech’s Authorized Resellers, licensors and suppliers with respect to the Software, the Open API and the Documentation, and each of them may enforce those Sections. An Authorized Reseller remains responsible for any broader warranty it gives (Section 7.2(e)) and for its Integrator Content and Integrated Systems (Section 7.4).
18. INDEMNIFICATION
18.1 By Customer. Customer will defend, indemnify and hold harmless Haptech and its officers, directors, employees and agents from and against third-party claims, and the resulting losses, damages, fines, costs and reasonable attorney fees, to the extent arising out of: (a) use of the Product by Customer or its Authorized Users in breach of this EULA, the Documentation or Section 12, including any use described in Section 6(k); (b) any modification of the Product not made or authorized by Haptech; (c) any connection of a Product to a network other than a Supported Network Configuration; (d) Customer’s linking of Non-Identifying IDs to individuals or other handling of personal data; or (e) Integrator Content or any Integrated System — except, in each case, to the extent caused by Haptech’s gross fault or willful misconduct.
18.2 Multi-User Training and Entertainment Facilities. If Customer operates the Product at a commercial, retail, entertainment, training or other Facility where multiple users — including members of the public, students, clients or patrons — use the Product, Customer will also defend, indemnify and hold harmless Haptech from and against third-party claims for bodily injury, death or property damage arising out of that operation, except to the extent caused by Haptech’s gross fault or willful misconduct or solely by Haptech’s negligence. Customer must maintain commercial general liability insurance covering that operation with limits of at least US$1,000,000 per occurrence and US$2,000,000 in the aggregate, name Haptech as an additional insured, and provide evidence of coverage on request.
18.3 Procedure. The indemnified party will give the indemnifying party prompt written notice of any claim (a delay relieves the indemnifying party only to the extent it is prejudiced), allow it to control the defense and settlement, and provide reasonable cooperation at the indemnifying party’s expense. The indemnifying party may not settle a claim in a way that admits fault by the indemnified party or imposes any obligation on it without its written consent. The indemnified party may participate with its own counsel at its own expense.
18.4 Government End Users. This Section 18 does not apply to U.S. Government End Users (Part A, Section A5) and applies to other government end users only as provided in Part A.
18.5 Infringement Claims. Haptech will defend Customer against any third-party claim that the Software, as delivered by Haptech and used in accordance with this EULA, infringes a United States patent, copyright or trademark, and will pay the damages and costs finally awarded against Customer or agreed by Haptech in settlement, under the procedure in Section 18.3. Haptech has no obligation for a claim that arises from Integrator Content, an Integrated System, a modification not made by Haptech, use of the Software with products or data not supplied by Haptech, use after Haptech offers a non-infringing Update, or use in breach of this EULA. If the Software is, or in Haptech’s opinion is likely to be, the subject of an injunction, Haptech may obtain the right for Customer to continue using it, modify or replace it so that it is non-infringing, or, if neither is commercially reasonable, terminate the affected license and refund the price paid for the affected Software less a reasonable allowance for use. This Section 18.5 grants no license to any party, states Haptech’s entire liability and Customer’s exclusive remedy for infringement claims, and is subject to Section 17.
19. TERM, SUSPENSION AND TERMINATION
19.1 Term. This EULA takes effect when Customer accepts it and continues until terminated. Each Add-On subscription lasts for its Subscription Term.
19.2 Termination by Customer. Customer may terminate this EULA at any time by ceasing all use of the Software.
19.3 Termination by Haptech. Haptech may terminate this EULA, or the license for the affected Product or Add-On, by written notice if Customer materially breaches this EULA and does not cure the breach within 30 days after written notice, or immediately if Customer breaches Section 5.2, Section 6(e), Section 6(f), Section 6(k) or Section 20.
19.4 Effect of Termination. When this EULA or a license terminates, all rights to the affected Software end, Customer must stop using it, and Haptech may suspend the affected functions as provided in Section 5.3. Sections 4.9, 6, 8.7, 8.8, 10.2, 10.7 through 10.12, 14 through 18, and 20 through 23, and any other provisions that by their nature should survive, survive termination.
20. EXPORT CONTROLS AND SANCTIONS
Customer will comply with all U.S. and other applicable export control and economic sanctions laws in using, exporting, re-exporting or transferring the Product. Haptech classifies the Product as EAR99 under the U.S. Export Administration Regulations and does not consider it subject to the International Traffic in Arms Regulations; Customer remains responsible for its own export determinations and for any authorization that its destination, end user or end use requires. Customer represents that neither it nor any of its Authorized Users is located in, organized under the laws of, or ordinarily resident in any country or region subject to comprehensive U.S. sanctions, or is listed on, or owned or controlled by a party listed on, any U.S. government restricted-party list. Customer will not export, re-export or transfer the Product to any such country, region or party, or for any use prohibited by those laws.
21. GOVERNING LAW, DISPUTE RESOLUTION, ARBITRATION, CLASS-ACTION WAIVER AND JURY-TRIAL WAIVER
21.1 Governing Law. This EULA is governed by the laws of the State of Louisiana, without regard to its conflict-of-laws rules. The United Nations Convention on Contracts for the International Sale of Goods does not apply.
21.2 Informal Resolution. Before starting an arbitration or court action, a party must send the other a written notice describing the dispute and the relief sought, and the parties will try in good faith to resolve the dispute for 60 days.
21.3 Binding Arbitration. Any dispute, claim or controversy arising out of or relating to this EULA or the Product that is not resolved informally will be resolved by final and binding arbitration administered by JAMS under its Comprehensive Arbitration Rules & Procedures (or, where they apply, its Streamlined Arbitration Rules & Procedures), before a single arbitrator seated in New Orleans, Louisiana. If JAMS is unavailable or declines to administer an arbitration, the arbitration will be administered by the American Arbitration Association under its Commercial Arbitration Rules, before a single arbitrator seated in New Orleans, Louisiana. The arbitrator may hold hearings by videoconference. Judgment on the award may be entered in any court of competent jurisdiction.
21.4 Class-Action Waiver. EACH PARTY MAY BRING CLAIMS AGAINST THE OTHER ONLY IN ITS INDIVIDUAL CAPACITY, AND NOT AS A PLAINTIFF OR CLASS MEMBER IN ANY PURPORTED CLASS, COLLECTIVE, CONSOLIDATED OR REPRESENTATIVE PROCEEDING. THE ARBITRATOR MAY NOT CONSOLIDATE THE CLAIMS OF MORE THAN ONE CUSTOMER OR PRESIDE OVER ANY FORM OF CLASS OR REPRESENTATIVE PROCEEDING. IF THIS CLASS-ACTION WAIVER IS FOUND UNENFORCEABLE AS TO A PARTICULAR CLAIM OR REQUEST FOR RELIEF, THAT CLAIM OR REQUEST — AND ONLY THAT ONE — WILL BE SEVERED AND DECIDED BY A COURT UNDER SECTION 21.5, AND THE REMAINDER OF THE DISPUTE WILL PROCEED IN ARBITRATION.
21.5 Exceptions and Courts. Either party may bring an individual action in small-claims court. Either party may seek injunctive or other equitable relief in court to protect its intellectual property or Confidential Information or to prevent irreparable harm, and Haptech may bring an action in court to collect undisputed amounts owed. For any such court action, the parties consent to the exclusive jurisdiction and venue of the state courts sitting in Orleans Parish, Louisiana, and the United States District Court for the Eastern District of Louisiana.
21.6 Attorney Fees. The prevailing party in any arbitration or court action under this EULA may recover its reasonable attorney fees and costs.
21.7 Jury-Trial Waiver. TO THE FULLEST EXTENT PERMITTED BY LAW, EACH PARTY KNOWINGLY, VOLUNTARILY AND INTENTIONALLY WAIVES ANY RIGHT TO A TRIAL BY JURY IN ANY COURT ACTION ARISING OUT OF OR RELATING TO THIS EULA OR THE PRODUCT, INCLUDING ANY ACTION UNDER SECTION 21.5 AND ANY ACTION BROUGHT IF THE AGREEMENT TO ARBITRATE IN SECTION 21.3 IS FOUND UNENFORCEABLE. EACH PARTY ACKNOWLEDGES THAT IT IS A BUSINESS OR ORGANIZATION ACTING THROUGH AN AUTHORIZED REPRESENTATIVE (SECTION 1.5), THAT IT HAS HAD THE OPPORTUNITY TO CONSULT COUNSEL, AND THAT THIS WAIVER IS A MATERIAL INDUCEMENT FOR THE OTHER PARTY TO ENTER INTO THIS EULA.
21.8 Government End Users. This Section 21 does not apply to U.S. Government End Users (Part A, Section A4) and applies to other government end users only as provided in Part A.
22. NOTICES
Notices to Haptech must be in writing and sent to: Haptech, Inc. (d/b/a Haptech Defense Systems), Attn: Contracts, 12715 Highway 90, Suite 140, Luling, LA 70070, with a copy by email to contracts@haptech.com. Haptech may give notice to Customer by email to the Notice Contact (Section 5.7) or to the contact information Customer provides with its Order or registration, by mail to that address, or through Haptech Manager. Customer must keep its Notice Contact current by the request described in Section 5.7. Notices are effective when received, and a notice displayed in Haptech Manager is received when the Hub is next used.
23. GENERAL
23.1 Entire Agreement; Order of Precedence. This EULA, together with any Order, the Documentation and, for hardware bought directly from Haptech, Haptech’s Terms and Conditions of Sale, is the entire agreement between the parties about the Software and supersedes all prior or contemporaneous understandings about it. If these documents conflict: (a) Part A controls for government end users as stated there; (b) a written agreement signed by an authorized representative of Haptech that covers the Software — such as a supply agreement, subcontract or reseller agreement — controls over this EULA to the extent of any conflict; (c) an Order controls as to fees, quantities and the license term of Add-Ons; and (d) otherwise, this EULA controls with respect to the Software. Pre-printed terms on a Customer purchase order do not apply.
23.2 Amendment. This EULA may be amended only by a new version accepted under Section 8.5 or by a written agreement signed by authorized representatives of Haptech and Customer, except that Haptech may, by notice to Customer under Section 22 and without publishing a new version, change its notice address and email address in Section 22, and designate a different nationally recognized arbitration administrator and its rules for arbitrations started after the notice, and update Schedule 1 as Section 11.7 provides.
23.3 Assignment. Customer may not assign or transfer this EULA except with the Product under Section 9 or with Haptech’s prior written consent. Haptech may assign this EULA to an affiliate or to a successor in a merger, acquisition or sale of all or substantially all of the assets of the business to which this EULA relates, provided the successor assumes Haptech’s obligations under this EULA, and subject to Part A, Section A10.
23.4 Severability. If any provision of this EULA is held invalid or unenforceable, it will be enforced to the maximum extent permissible, and the remaining provisions remain in effect, subject to Section 21.4.
23.5 No Waiver. A failure or delay in enforcing any provision of this EULA is not a waiver of it.
23.6 Force Majeure. Haptech is not liable for any delay or failure to perform caused by events beyond its reasonable control, including internet, telecommunications, power or cloud-service outages, cyberattacks, epidemics, government actions, and failures of suppliers or carriers.
23.7 Relationship. The parties are independent contractors. Authorized Resellers are not Haptech’s agents and cannot bind Haptech.
23.8 No Third-Party Beneficiaries. Except for Haptech’s licensors and suppliers, and Authorized Resellers under Section 17.5, each of which may enforce the provisions of this EULA that protect it, this EULA creates no rights for any third party.
23.9 Language. This EULA is written in English. Any translation is provided for convenience only, and the English version controls.
23.10 Electronic Acceptance. Customer agrees that its electronic acceptance of this EULA is a valid signature and that this EULA is an enforceable written agreement.
23.11 Headings. Headings are for convenience only and do not affect interpretation.
23.12 Questions. Questions about this EULA may be sent to contracts@haptech.com.
========================================================================
SCHEDULE 1 — SERVICE CONNECTION DESTINATIONS
========================================================================
S1.1 What this Schedule is. This Schedule is part of this EULA (Section 11.1). It lists every destination a Hub reaches over a Service Connection, with the purpose of each connection, who operates the destination, the kind of data that travels, when the connection is made, and the setting that controls it. A Hub makes outbound connections only and never accepts an inbound connection over a Service Connection. On a closed training network (Section 11.1(a)) none of these connections is made. Haptech operates its online services on a commercial cloud platform; the destinations below are identified by operator and purpose, and the exact host names are shown in Haptech Manager where the Hub’s release supports it and are available from Haptech on request. Haptech may update this Schedule as Section 11.7 provides.
S1.2 The service channel. Purpose: license validation and renewal, the acceptance receipt (Section 1.4), the status reports of the Hub’s update runtime, the delivery of Updates and notices and, while Diagnostics Sharing is ON, Diagnostic Data (Section 10.5). Operator: Haptech, on the platform’s device-management and messaging service. Protocol: AMQP over TLS, port 5671, outbound; where port 5671 is not available on Customer’s network, the same channel over WebSockets on port 443; and HTTPS on port 443 for the Hub’s registration of its identity and components with the same service. Data: the information Section 10.4 names for the service channel, and Diagnostic Data only while Diagnostics Sharing is ON. When: whenever a Service Connection is available. Control: the Diagnostics Sharing setting governs the Diagnostic Data this channel carries; the channel itself stops only when the Service Connection is disconnected.
S1.3 Software downloads. Purpose: downloading Updates — the Hub software, Haptech Manager, the Open API, Device Firmware Updates and new versions of this EULA — and the platform’s own runtime components. Operators: Haptech, on the platform’s container registry and the storage endpoint that serves its contents, for Haptech’s software; the platform vendor’s public registry and package index, for the runtime components. Protocol: HTTPS, port 443, outbound. Data: signed, digest-verified software downloaded to the Hub; nothing is uploaded. When: when Haptech publishes an Update; the Hub may also check the platform vendor’s package index daily for updates to the runtime components. Control: Section 8.2’s deferral for Updates not designated as required for safety or security.
S1.4 Support uploads. Purpose: sending a support bundle to Haptech when Customer asks for support and chooses to send one (Section 10.5). Operator: Haptech, on the platform’s storage service. Protocol: HTTPS, port 443, outbound. Data: the support bundle Customer chooses to send. When: only when Customer sends it. Control: Customer’s own action.
S1.5 Time. Purpose: setting the Hub’s clock. Operators: public time services — two operators of authenticated time (Network Time Security), Cloudflare and Netnod, where the Hub’s provisioning supports it; otherwise the public time servers of NIST and Cloudflare (plain NTP). Protocol: for authenticated time, the NTS key exchange on TCP port 4460 and NTP on UDP port 123; for plain NTP, UDP port 123; outbound. Data: time only. When: at start-up and periodically. Control: none; the Documentation for the Hub’s release states which applies.
S1.6 Operating-system security updates. Purpose: security updates for the Hub’s operating system. Operator: the operating-system vendor’s package archive. Protocol: HTTPS, port 443, outbound. Data: package downloads only. When: a daily check. Control: none. Other operating-system services that would reach other recipients are disabled when the Hub is provisioned.
S1.7 Name resolution. Purpose: resolving the names of the destinations above. Operator: the resolver Customer’s network provides. Protocol: DNS, UDP and TCP port 53. Data: the host names above. Control: Customer.
S1.8 Certificate verification. When verifying a TLS connection listed above, the platform’s libraries may download a missing issuer certificate from the issuing certificate authority’s server (HTTP or HTTPS, port 80 or 443, outbound; certificates only; rarely). If Customer enables certificate sign-in in Haptech Manager and installs its own trust store, the Hub checks the revocation status of the certificates presented to it with the certificate authority Customer designates (a Customer-designated destination, S1.10). Otherwise the Hub performs no online revocation checking.
S1.9 What a Hub does not reach. The platform’s runtime telemetry service, which is disabled in every Haptech deployment; any device-provisioning service, because Haptech issues each Hub’s identity; and no other recipient.
S1.10 Customer-designated destinations. Where Customer configures the Hub to use a system that Customer operates or designates — the name resolver of S1.7, a time source on Customer’s network, a collector for the Hub’s logs, or a certificate authority for certificate sign-in — that system is Customer’s own destination, not a Service Connection destination: Customer’s configuration is the control, no data goes to Haptech or to the platform by that connection, and this Schedule does not list it.
------------------------------------------------------------------------
Haptech Software End User License Agreement · Version 1.1 · © 2026 Haptech, Inc. All rights reserved. ERIS is a trademark of Haptech, Inc.