HeliumOS Product Schedule: Helium Network Integration
EFFECTIVE SINCE
October 9, 2026
LAST UPDATED
October 9, 2026
1. Applicability and Interpretation
1.1 Applicability. This Product Schedule forms part of the HeliumOS Terms and Conditions posted at helium.com/legal/heliumos (the “Terms”).
1.2 Definitions. Capitalized terms used but not defined in this Product Schedule have the meanings given in the Terms.
“Daily Active Subscriber” means, for any day (UTC), each Eligible Subscriber whose device successfully authenticates through the Helium Network Interfaces at least once on that day.
“Data Usage” has the meaning given in Section 5.2.
“Eligible Subscriber” means each subscriber of Customer and, if the Order Form permits, each subscriber of a wholesale customer of Customer identified in the Order Form (each, a "Wholesale Customer"), in each case whose device Customer has enabled for Helium Network Integration, for as long as that device remains enabled.
“Monthly Subscriber Count” means, for any calendar month, the average of the number of Daily Active Subscribers on each day of that month, rounded to the nearest whole number.
“Partner Subscriber ID” has the meaning given in Section 3.3.
"Premium Support Addendum" has the meaning given in the Terms, and "Downtime" has the meaning given in the Premium Support Addendum.
1.3 Version and Updates. Nova Labs may update this Product Schedule under Section 19 of the Terms.
1.4 Precedence. If this Product Schedule conflicts with the Terms with respect to Helium Network Integration, this Product Schedule controls, subject to Section 2.4 of the Terms.
2. Service Description
2.1 Overview. Helium Network Integration enables the devices of Eligible Subscribers to authenticate to, and transfer data through, access points on the Helium Network using Helium Network Interfaces. Nova Labs (d/b/a Helium) founded and continues to provide operational support for the Helium Network. The access points on the Helium Network are owned, deployed, and maintained by Access Point Operators, as described in Section 5.1 of the Terms. Nova Labs' commitments under this Product Schedule are limited to the Helium Network Interfaces.
2.2 Helium Network Interfaces. For this Service, the Helium Network Interfaces consist of: (a) authentication and authorization systems that pass Eligible Subscriber authentication requests between access points and the AAA option selected under Section 3.1; (b) systems that route and account for Eligible Subscriber sessions; and (c) usage measurement and reporting systems.
2.3 Coverage Footprint. The Service is available only where access points on the Helium Network are deployed and operating, as that footprint exists from time to time. Access Point Operators may add, relocate, or remove access points at any time without notice to Nova Labs or Customer. Coverage maps, access point counts, and network statistics published by Nova Labs are informational only and are not commitments.
2.4 Exclusions. The Service does not include cellular service, carrier core network elements, devices, SIMs, eSIMs, Passpoint credentials issued by third parties, or Customer applications. Each of these is a Third-Party Service or a Customer System. Any Client Software that Nova Labs provides for this Service is licensed under Section 3.9 of the Terms.
2.5 Website Descriptions. Marketing materials and website descriptions of the Helium Network or this Service are not warranties or specifications. The Documentation and this Product Schedule govern.
2.6 Network Agreements. Section 5.3 of the Terms governs the relationship between this Service and any Network Agreement, including the migration of access under a Migrated Agreement to this Service.
3. Integration
3.1 AAA Options. Customer shall select one of the following in the Order Form:
(a) Nova Labs-Hosted AAA. Nova Labs hosts an AAA server on Customer’s behalf as part of the Helium Network Interfaces, configured using the credentials and subscriber information that Customer provides.
(b) Customer-Hosted AAA. Customer operates an AAA server that meets the requirements in the Documentation.
(c) Carrier Federation. Nova Labs forwards authentication requests through RADIUS or RadSec federation to an AAA server operated by Customer’s carrier partner.
For options (b) and (c), the AAA server is a Customer System. Nova Labs is not responsible for its availability, configuration, or authentication decisions.
3.2 Authentication Methods. Supported authentication methods are those identified in the Documentation, which may include EAP-SIM, EAP-AKA, EAP-AKA’, and EAP-TLS with Passpoint. Customer is responsible for provisioning Passpoint profiles and credentials on Eligible Subscriber devices, whether through its own systems, its carrier partner, or Client Software.
3.3 Partner Subscriber ID. Customer shall assign each Eligible Subscriber a unique, opaque identifier (a “Partner Subscriber ID”). A Partner Subscriber ID shall not contain any name, telephone number, email address, IMSI, or other information that directly identifies an individual. Customer shall maintain the mapping between Partner Subscriber IDs and its subscribers. Nova Labs uses Partner Subscriber IDs to authenticate, meter, report, and bill. If the selected authentication method transmits an IMSI or other carrier identifier in unencrypted form, Nova Labs processes that identifier to complete authentication and records it in the authentication logs of the Helium Network Interfaces. Nova Labs purges IMSIs and other carrier identifiers from those logs within ninety (90) days after collection. Nova Labs uses IMSIs and other carrier identifiers in those logs only for the purposes in Sections 7.2(b) and 7.2(c), and does not use them to meter, report, or bill. Customer may prevent transmission of unencrypted IMSIs by enabling the IMSI encryption or anonymous identity features supported by its carrier and identified in the Documentation.
3.4 Onboarding. Before Nova Labs enables production traffic, Customer shall complete the integration testing described in the Documentation. Nova Labs may decline to enable production traffic until that testing is complete. Integration work beyond the Documentation requires an SOW.
3.5 Technical Changes. Nova Labs shall give Customer at least thirty (30) days' notice of any change to the technical specifications of the Helium Network Interfaces, including endpoints, protocols, and certificates, that requires Customer to change Customer Systems or their configuration. Nova Labs may give shorter notice where a change is needed to address a security risk. Other changes, including optimizations and new features that do not affect existing functionality, require no notice. Customer shall implement each change that requires notice by its effective date. This Section 3.5 is subject to Section 3.7 of the Terms.
4. Customer Responsibilities
In addition to Customer's obligations under Section 6 of the Terms, Customer shall, with respect to this Service:
(a) maintain its carrier relationships, subscriber accounts, SIMs, eSIMs, and credentials;
(b) designate Eligible Subscribers and keep its Partner Subscriber ID mapping accurate;
(c) provide all support to its subscribers, with Nova Labs providing support only to Customer under Appendix A to the Terms;
(d) ensure that its subscriber terms and privacy notices: (i) disclose that subscriber devices may connect automatically to Wi-Fi access points operated by third parties, including access points on the Helium Network; (ii) include a disclaimer of warranties, an exclusion of indirect and consequential damages, and a limitation of liability, each applying to Customer’s suppliers; and (iii) include acceptable use restrictions no less protective than Section 3.4 of the Terms;
(e) be responsible for all Data Usage by Eligible Subscribers, including unauthorized or fraudulent usage through Customer’s credentials or subscriber accounts, except to the extent caused by Nova Labs' breach of the Agreement; and
(f) not state or imply to its subscribers that Nova Labs provides service to them.
5. Usage Metrics, Pricing, and Reporting
5.1 Usage Metrics. The Usage Metrics for this Service are Data Usage and, if the Order Form states a per-subscriber fee, the Monthly Subscriber Count.
5.2 Data Usage. “Data Usage” means the total data uploaded and downloaded by all Eligible Subscriber devices through the Helium Network in a calendar month, as recorded in the accounting records of the Helium Network Interfaces. For billing, Data Usage is aggregated across all Eligible Subscribers under the Order Form and rounded to the nearest whole gigabyte. One gigabyte equals 1,000,000,000 bytes.
5.3 Pricing. Customer shall pay the per-gigabyte rate stated in the Order Form for all Data Usage, together with any per-subscriber, platform, or minimum fees stated in the Order Form. No Usage Allowance applies unless the Order Form states one. Fees are owed for all Data Usage, whether or not Customer charges or collects from its subscribers.
5.4 Measurement. Nova Labs measures each Usage Metric from the records of the Helium Network Interfaces, and those measurements control as provided in Section 8.2 of the Terms. Customer’s records, including carrier records, do not override Nova Labs' measurements. Customer may use its records to support a dispute under Section 8.6 of the Terms.
5.5 Reports. Each month, Nova Labs will make available a standard usage report showing: (a) total Data Usage; (b) the Monthly Subscriber Count; and (c) daily Data Usage. Additional, custom, or more detailed reporting, and data feeds, are available only if stated in the Order Form and may be subject to additional Fees.
5.6 Disputes. Disputes regarding Usage Metrics are governed by Section 8.6 of the Terms. On request, Nova Labs will provide reasonable supporting data, which may be aggregated or pseudonymized.
6. Traffic Management and Suspension
6.1 Interface Protection. Nova Labs may apply reasonable measures through the Helium Network Interfaces to protect their security, integrity, and performance, including rate limiting, authentication throttling, and blocking malformed or malicious traffic.
6.2 Subscriber Suspension. Nova Labs may suspend authentication through the Helium Network Interfaces for any Eligible Subscriber, device, or Partner Subscriber ID if Nova Labs reasonably believes the related activity: (a) involves fraud, abuse, or unauthorized access; (b) threatens the security or integrity of the Helium Network Interfaces; or (c) violates Section 3.4 of the Terms. Nova Labs shall notify Customer promptly, and in advance where practicable. Nova Labs shall restore access after the issue is resolved to Nova Labs' reasonable satisfaction. A suspension under this Section 6.2 is not a breach of the Agreement.
6.3 Account-Level Suspension. If activity under Customer’s account presents a material security risk to the Helium Network Interfaces, Nova Labs may suspend the Service for the affected traffic on notice to Customer. Any such suspension shall be limited in scope and duration to what is reasonably necessary.
6.4 Restrictions. Customer shall not: (a) route traffic of any device other than an Eligible Subscriber device through the Service; (b) make access through the Service available to anyone other than its own subscribers or, if the Order Form permits, the subscribers of Wholesale Customers; or (c) use the Service to provide fixed broadband or backhaul service. If the Order Form permits Wholesale Customers: (i) Customer is responsible for each Wholesale Customer's and its subscribers' use of the Service as if that use were Customer's own; (ii) Customer represents and warrants that it has all rights and consents needed for Nova Labs to process the data of those subscribers under the Agreement, including the DPA; and (iii) no Wholesale Customer has any rights under the Agreement.
7. Data
7.1 Categories. To provide this Service, Nova Labs processes the following Customer Data: (a) Partner Subscriber IDs; (b) authentication attributes, including IMSIs or other carrier identifiers where the selected authentication method transmits them; (c) device identifiers, such as MAC addresses; (d) the identifier and location of each access point used by an Eligible Subscriber device, to the extent associated with that device’s sessions; (e) session start and end times, Data Usage, and connection quality metrics; and (f) credentials, certificates, and subscriber information that Customer provides for Nova Labs-Hosted AAA.
7.2 Purposes. Nova Labs processes this Customer Data only to: (a) authenticate, route, measure, bill, and report; (b) troubleshoot and provide support; (c) secure the Service and prevent fraud and abuse; (d) record On-Chain Records under Section 7.4; and (e) create Aggregated Data for use under Section 10.3 of the Terms, in each case subject to Section 10.2 of the Terms and the DPA.
7.3 Access Point Operators. Access Point Operators are independent third parties and are not Nova Labs' agents, subcontractors, or Subprocessors. Eligible Subscriber traffic and authentication messages transit equipment of Access Point Operators. Those messages may include identifiers that Eligible Subscriber devices transmit, including IMSIs or other carrier identifiers where the selected authentication method transmits them in unencrypted form, and RADIUS responses from the Helium Network Interfaces may return those identifiers to the access point as part of the authentication exchange. Except for those authentication messages, Nova Labs does not provide Customer Personal Data or CPNI to Access Point Operators. Customer is responsible for selecting authentication methods and identity-privacy settings, such as anonymous outer identities or IMSI encryption, appropriate to that architecture.
7.4 On-Chain Records. On-Chain Records for this Service record data transfer by access point and time period. They do not contain any Partner Subscriber ID, IMSI, MAC address, or other identifier of an Eligible Subscriber or device. Customer Personal Data is not used to determine any reward issued by the Helium protocol to Access Point Operators. Those rewards are determined programmatically by the protocol, not by Nova Labs, as described in Section 5.2 of the Terms.
7.5 Retention. Except as provided in Section 3.3 for IMSIs and other carrier identifiers, Nova Labs retains Customer Data for this Service for up to twelve (12) months from collection, after which it is deleted or converted into Aggregated Data. Nova Labs may retain billing records for longer as needed to support invoices and disputes and as required by Applicable Law. Section 10.9 of the Terms governs return and deletion at termination or expiration. On-Chain Records cannot be altered or deleted.
7.6 Carrier Data. To the extent Customer Data includes CPNI or other subscriber data disclosed by a carrier, Customer shall notify Nova Labs in writing of any carrier-imposed handling requirements. Nova Labs shall comply with requirements that are reasonable and consistent with the Agreement.
8. Maintenance and Outages
8.1 Planned Maintenance. Nova Labs will give Customer at least seventy-two (72) hours’ notice of planned maintenance to the Helium Network Interfaces that is reasonably expected to materially affect authentication or routing. Nova Labs will give notice of emergency maintenance as soon as practicable.
8.2 Unplanned Outages. Nova Labs will notify Customer promptly of any outage of the Helium Network Interfaces that Nova Labs reasonably believes is materially affecting Eligible Subscribers. To the extent known, the notice will describe the nature and scope of the outage and the estimated time to resolution. Nova Labs will provide periodic updates until the outage is resolved. Nova Labs has no obligation to notify Customer of outages of individual access points or changes in coverage.
9. Support for Helium Network Integration
Service levels for this Service are available only under a Premium Support Addendum. This Section 9 sets out how issues with this Service are classified for support purposes.
9.1 Service Levels. Downtime, the availability commitment, and service credits for this Service are set out in the Premium Support Addendum.
9.2 Exclusions. If Customer purchases Premium Support, then in addition to the exclusions in the Premium Support Addendum, Downtime does not include any period attributable to:
(a) the failure, removal, or unavailability of any access point or its backhaul;
(b) coverage gaps or capacity limits of the Helium Network;
(c) Customer-Hosted AAA, Carrier Federation AAA, or any carrier core network element;
(d) devices, SIMs, Passpoint profiles, or Client Software as configured by Customer;
(e) suspension under Section 6; or
(f) the Helium protocol or its blockchain.
9.3 P1 Critical Issues. For this Service, a failure of the Helium Network Interfaces affecting seventy-five percent (75%) or more of authentication or accounting requests, or all or substantially all Eligible Subscribers, is a P1 Critical issue. Any other Downtime is a P2 High issue.
9.4 Reports and Dashboards. Unavailability of reports, dashboards, or APIs that does not affect authentication or routing is not Downtime. It is supported as a P2 High issue.
10. Disclaimers Specific to Helium Network Integration
10.1 No Network Warranties. Nova Labs does not warrant or guarantee: (a) the coverage, capacity, throughput, latency, or availability of the Helium Network or any access point in any location; (b) that any device will discover, select, or remain connected to any access point; (c) acceptance or authentication of any device or subscriber by a carrier or AAA server; (d) any particular volume of offloaded traffic or cost savings; or (e) the acts or omissions of Access Point Operators, including with respect to their equipment, their backhaul, or their compliance with Applicable Law.
10.2 Rewards. Section 5.2 of the Terms applies. Customer has no right to, or obligation with respect to, any reward issued by the Helium protocol.
10.3 Regulatory Matters. Sections 5.4 and 6.6 of the Terms apply to this Service, including Customer’s responsibility for emergency services obligations to its subscribers.
