End User License Agreement

Effective date: October 28, 2026. Version 1.1.

The English text of this document is the governing version. A translation is provided for convenience only.

This End User License Agreement applies to the CyberArmor.AI Endpoint Agent for macOS, Windows and Linux and its components, to the CyberArmor.AI Protect browser extension for Chrome, Edge, Firefox and Safari, to the CyberArmor.AI ROS 2 Security Agent, to the CyberArmor.AI apps for iOS, watchOS and Android, and to the other CyberArmor.AI client software described in Section 1, whether obtained from CyberArmor AI, Inc., from an app or extension store, or from an Authorized Partner.

1. Definitions

Capitalized terms have the meanings below.

1.1 "CyberArmor.AI", "we", "us" or "our" means CyberArmor AI, Inc., a Delaware corporation.

1.2 "Software" means, in object-code form, together with its Documentation and any Updates:

• (a) the Endpoint Agent: the CyberArmor.AI endpoint agent for macOS, Windows and Linux and its components, including the background service, the local policy engine, the local AI-traffic proxy, the clipboard helper, the menu bar or system tray status application, the macOS Endpoint Security system extension, the Windows event-tracing sensor, the Linux kernel monitoring program, the browser native-messaging host, and the hooks it installs into AI coding assistants;
• (b) the Browser Extension: CyberArmor.AI Protect for Chrome, Edge, Firefox and Safari;
• (c) the Mobile Apps: the CyberArmor.AI apps for iOS and Android, the Safari extension and the watchOS app delivered with the iOS app, and the CyberArmor.AI extension for Firefox for Android;
• (d) the ROS 2 Security Agent: the CyberArmor.AI security agent for robots and autonomous systems that run the Robot Operating System 2 (ROS 2), including its security node, its actuator, stop-control, sensor-integrity and command-inspection modules, and its local decision engine;
• (e) the Developer Components: the CyberArmor.AI runtime application self-protection (RASP) agents and client software development kits for Python, Go, Java, Node.js, .NET, C and C++, PHP, Ruby and Rust, the LangChain and LlamaIndex integrations, and the CyberArmor.AI command-line tool; and
• (f) any other CyberArmor.AI client software that is distributed with, or states that it is governed by, this Agreement, including integrated development environment extensions and office add-ins.

1.3 "Agreement" means this End User License Agreement, including its appendices.

1.4 "Customer Agreement" means the agreement under which the Subscriber obtained its subscription to the Software, whether a master subscription agreement, order form, pilot or evaluation agreement or other agreement signed with us, an online order accepted by us (including a subscription bought through the checkout on our website, together with the Terms of Use that govern it), or an agreement with an Authorized Partner that incorporates this Agreement. The "Commercial Agreement" referred to in the CyberArmor.AI software license file (LICENSE) is a Customer Agreement.

1.5 "Subscriber" means the person who holds the subscription to the Software and is our customer under this Agreement. A Subscriber is either an Organization or a Consumer. Organizations and Consumers are equally our customers. Where this Agreement says "Subscriber", it applies to both; where it says "Organization" or "Consumer", it applies only to that kind of Subscriber.

1.6 "Organization" means a company, public body, non-profit or other legal entity, or a natural person acting for the purposes of his or her trade, business or profession, that obtains a subscription to the Software and deploys it on devices or robots it owns or manages.

1.7 "Consumer" means a natural person who subscribes to the Software for himself or herself, or for his or her household or family, for personal, family or household purposes and not for the purposes of a trade, business or profession, including the holder of a family plan.

1.8 "Household Member" means a person, other than the Consumer, who uses a device that the Consumer has enrolled under the Consumer's subscription, such as a member of the Consumer's family.

1.9 "End User" means a natural person who uses a device, browser or robot on which the Software is installed, including an employee, contractor or other person whom an Organization authorizes to use a device it manages, a Consumer, and a Household Member.

1.10 "Administrator" means an End User whom the Subscriber has given administrative rights over its Deployment, such as the right to set Policy, enroll devices or view security events. A Consumer is the Administrator of his or her own subscription. Under the Managed Service, we also act as an Administrator for the devices the Subscriber has placed in it.

1.11 "Authorized Partner" means a reseller, managed service provider, distributor, co-selling partner or other third party that we have authorized in writing to resell, deploy, manage or support the Software, including under the partner's own brand.

1.12 "Deployment" means the instance of the CyberArmor.AI service to which a copy of the Software is enrolled, whether it is hosted by us, hosted by an Authorized Partner, or run by the Organization on its own infrastructure, including an air-gapped installation.

1.13 "Policy" means the rules and settings that the Subscriber, or an Authorized Partner acting for it, configures in its Deployment, or that apply by default under the Subscriber's plan, which determine what the Software inspects, warns about, redacts, blocks, quarantines, records and reports and, for the ROS 2 Security Agent, which robot commands it allows, limits, holds or stops.

1.14 "Model Pack" means a package of machine-learning models and related files that we sign and make available for the Software to run on the device, together with any license terms that accompany it.

1.15 "Security Content" means the data the Software receives to do its job, other than Policy and Model Packs, including URL reputation snapshots, known-good and known-bad file hash lists, detection rules, the AI service catalog and signed policy bundles.

1.16 "Updates" means patches, fixes, new versions, Model Packs and Security Content that we make available for the Software.

1.17 "Documentation" means the user guides, installation guides and other technical documentation for the Software that we make available, as updated from time to time.

1.18 "Subscription Term" means the period during which the Subscriber holds a current subscription to the Software, including an evaluation or pilot period, as stated in the Customer Agreement, and, for a Consumer's subscription that renews automatically, each renewal period until the subscription is cancelled.

1.19 "Entitlement" means the quantity of the Software the Subscriber is licensed to use, measured in devices, users, seats, robots, plan members or another unit stated in the Customer Agreement or in the description of the Subscriber's plan.

1.20 "Third-Party Components" means software, models, data and other material that we license from third parties and include or distribute with the Software, as described in Section 12.

1.21 "Privacy Policy" means the CyberArmor.AI Privacy Policy at https://cyberarmor.ai/privacy, as updated from time to time.

1.22 "Terms of Use" means the CyberArmor.AI Terms of Use at https://cyberarmor.ai/terms, which govern the CyberArmor.AI service, portals and consoles, and the billing, renewal and cancellation of subscriptions bought online.

1.23 "DPA" means the data processing agreement between the Organization and us, or between the Organization and an Authorized Partner where the partner processes personal data for the Organization, that governs processing of personal data on the Organization's behalf.

1.24 "Managed Service" means the service described in Section 6.5, under which a Subscriber asks us to administer the Software on some or all of its enrolled devices on its behalf.

1.25 "Device Management" means the mobile device management facilities that the iOS, iPadOS and Android operating systems provide, through which a device-management service installs a management profile on a phone or tablet and applies settings, apps and certificates to it. A phone or tablet enrolled in Device Management is a "managed" mobile device; any other phone or tablet is "unmanaged".

2. Scope and acceptance

2.1 Who the parties are. This Agreement is between us and the Subscriber. For an Organization, the Organization is the party; for a Consumer, the Consumer is the party personally. We offer the Software to Consumers and to Organizations on equal terms. Where this Agreement treats them differently, it does so because the law treats consumers and businesses differently, or, for phones and tablets only, as Section 7.3 describes for managed and unmanaged devices.

2.2 Acceptance by an Organization. An Organization accepts this Agreement by signing or accepting a Customer Agreement that refers to it; by completing an online order; by having an Administrator or other authorized person accept it in an installer, an enrollment screen, an app or a CyberArmor.AI portal; or by installing, deploying or using the Software. A person who accepts this Agreement on behalf of an Organization represents that he or she has authority to bind the Organization. If that person does not have that authority, or the Organization does not accept this Agreement, the Software must not be installed or used.

2.3 Unattended and mass deployment. The Software can be installed without a person present, for example through a device management system or a robot's build image. Supplying an acceptance on the command line (for example the option --eula yes or the Windows Installer property ACCEPT_EULA=YES), force-installing the Browser Extension through browser policy, deploying a Mobile App through mobile device management, or installing a package with a command-line or device-management tool that does not display this Agreement, is acceptance of this Agreement by the Organization for every device or robot on which the Software is installed in that way. The installers record the acceptance, its date and time, the device and the agreement version. Choosing a silent or quiet installation mode is not by itself acceptance, and the installers refuse to proceed without one.

2.4 Acceptance by a Consumer. A Consumer accepts this Agreement personally by completing the checkout for a subscription on our website, by accepting it in an installer, an app's enrollment screen or a CyberArmor.AI portal, or by installing or using the Software under the Consumer's subscription. A Consumer must have reached the age of majority where he or she lives, and in any case be at least 18 years old.

2.5 End Users. End Users who are not the Subscriber do not become parties to the Subscriber's commercial terms and are not personally responsible for the Subscriber's fees, Entitlements or obligations under Section 8. Each End User must comply with Section 9. An End User who is shown this Agreement on a managed device and continues acknowledges the notices in Sections 7 and 13 and agrees to Section 9.

2.6 Consumer rights. Nothing in this Agreement excludes or limits any right that a Consumer has under the consumer protection law of the place where he or she lives that cannot be excluded or limited by contract, including any statutory right to cancel, to a refund, or to a remedy for software that is faulty or not as described. Where such a law applies, this Agreement is read as giving the Consumer at least that right.

2.7 Business use of a consumer plan. A plan offered for personal, family or household use may not be used for a trade, business or profession. A person who subscribes for a business is an Organization, whatever plan was bought, and the terms of this Agreement that apply to Organizations apply to that subscription.

2.8 Order of precedence. If this Agreement conflicts with a Customer Agreement signed by us, the Customer Agreement controls to the extent of the conflict, except that Sections 5, 8, 12 and 17 apply in addition to the Customer Agreement unless it expressly overrides them by section number. If there is no Customer Agreement signed by us, this Agreement, the Terms of Use, the order and, for an Organization, the DPA together are the agreement between the Subscriber and us.

2.9 The LICENSE file. Copies of the Software may carry a file named LICENSE that states the terms on which source code made available to a licensee may be used. Where both that file and this Agreement apply, the narrower restriction governs, and nothing in this Agreement grants rights in source code.

3. License grant

3.1 Grant to an Organization. Subject to the Organization's continuing compliance with this Agreement and the Customer Agreement, and to payment of the applicable fees, we grant the Organization a limited, non-exclusive, non-transferable, non-sublicensable (except as stated in Section 3.4), revocable license, during the Subscription Term and only within its Entitlement, to:

• (a) install and run the Software on devices, in browsers and on robots that the Organization owns, leases or manages, or that its End Users use for the Organization's business with the Organization's authorization;
• (b) enroll those copies to the Organization's Deployment and use them to enforce the Organization's Policy;
• (c) integrate the Developer Components into the Organization's own applications and services, and run them there, solely to protect those applications and services; and
• (d) make a reasonable number of copies of the installation packages for backup, testing and distribution through the Organization's own software deployment and device management systems,

in each case solely for the Organization's internal business purposes and in accordance with the Documentation.

3.2 Grant to a Consumer. Subject to the Consumer's continuing compliance with this Agreement and payment of the applicable fees, we grant the Consumer a limited, non-exclusive, non-transferable, non-sublicensable, revocable license, during the Subscription Term and within the plan the Consumer bought, to install and run the Software on devices, in browsers and on robots that the Consumer owns or controls and that the Consumer or Household Members use, to enroll them to the Consumer's subscription, to integrate the Developer Components into applications the Consumer builds for personal, non-commercial use, and to use the Software for personal, family and household purposes, in accordance with the Documentation. A Consumer receives the same components and the same protection as an Organization.

3.3 Entitlement and counting. Unless the Customer Agreement or the plan states otherwise, each enrolled device or robot counts as one device, and each person who uses an enrolled device or browser counts as one user, for as long as the device or person remains enrolled. A device that is re-imaged and re-enrolled counts once when the earlier enrollment is retired. The Deployment records enrollments, and the Subscriber may view and retire them in its portal. If an Organization exceeds its Entitlement, it will within thirty (30) days either retire the excess enrollments or purchase the additional Entitlement at the then-applicable rate, pro-rated for the rest of the Subscription Term. Where a Consumer's plan states that it includes a number of devices or members and the Consumer enrolls more, protection is not switched off for that reason; we may ask the Consumer to retire the excess enrollments or to move to a plan that includes them.

3.4 Affiliates, contractors and partners. The Organization may permit its affiliates, its contractors and outsourced service providers, and an Authorized Partner engaged by it, to install, administer and operate the Software on the Organization's behalf and for its benefit. The Organization remains responsible for their compliance with this Agreement.

3.5 Evaluation, pilot and demonstration use. If we or an Authorized Partner provide the Software for evaluation, a pilot or a proof of concept, or without charge, the license in Section 3.1 or 3.2 applies only for the evaluation period stated in writing or, if none is stated, for thirty (30) days, solely to evaluate whether to purchase a subscription, and the Software is provided as described in Section 19.3. The demonstration modes of the Browser Extension and of the iOS app connect to nothing and may be used by anyone to preview the Software without an account.

3.6 Release candidates and preview features. Builds labelled as a release candidate (for example a version containing "rc"), beta or preview, and features that the Documentation or the CyberArmor.AI capability status page at https://cyberarmor.ai/status describes as anything other than production-deployed, are "Preview Features". Preview Features are provided for evaluation, may change or be withdrawn without notice, are not covered by any support or service commitment, and are provided as described in Section 19.3. The Subscriber decides whether to deploy Preview Features to its devices and robots.

3.7 Reservation of rights. The Software is licensed, not sold. We and our licensors retain all right, title and interest in and to the Software. All rights not expressly granted in this Agreement are reserved, and no right is granted by implication or estoppel.

4. Authorized Partners and partner-branded distribution

4.1 Distribution by an Authorized Partner. An Authorized Partner may distribute the Software to a Subscriber, and may deploy, configure, administer and support it for the Subscriber, under a separate written agreement between the partner and us. Where the Subscriber obtains the Software through an Authorized Partner:

• (a) this Agreement governs the Subscriber's use of the Software, and the license in Section 3 is granted by us directly to the Subscriber;
• (b) fees, payment, support, service levels and the partner's own services are governed by the Subscriber's agreement with the Authorized Partner. The Authorized Partner is not our agent and has no authority to make any promise, warranty or commitment on our behalf;
• (c) the Authorized Partner may host the Subscriber's Deployment, may act as the Subscriber's processor or service provider for the data the Software sends to that Deployment, and may have access to that data through the partner console, as agreed between the Subscriber and the partner; and
• (d) if the Authorized Partner's authorization ends, or the partner fails to pay us for the Subscriber's subscription, we may, but need not, offer the Subscriber a direct subscription or a transfer to another Authorized Partner on our then-current terms. If we do neither, the license ends at the end of the period for which we have been paid.

4.2 Partner branding. Where its agreement with us allows, an Authorized Partner may distribute the Software, its installers and its user-facing text under the partner's own name, logo and product name. Where it does:

• (a) the Software remains our property and is licensed under this Agreement, and references in this Agreement to CyberArmor.AI continue to mean CyberArmor AI, Inc.;
• (b) the Authorized Partner must present this Agreement, or terms we have approved in writing that are no less protective of us, to the Subscriber before installation, and those terms must identify CyberArmor AI, Inc. as the licensor of the Software; and
• (c) the NOTICE file and the third-party license texts described in Section 12 must be carried unchanged, because the licenses of the Third-Party Components require it.

4.3 No partner may expand rights. No Authorized Partner may grant a Subscriber rights in the Software broader than those in this Agreement, or waive any restriction in Section 5, unless we have agreed in writing.

5. Restrictions

5.1 Except as expressly permitted by this Agreement or by a Customer Agreement signed by us, the Subscriber will not, and will not allow any End User or third party to:

• (a) copy, sell, resell, rent, lease, lend, sublicense, distribute, publish or otherwise make the Software available to any third party, or use it to provide a service bureau, hosting, managed security or similar service to third parties, unless it is an Authorized Partner acting under its agreement with us;
• (b) reverse engineer, decompile or disassemble the Software, or otherwise attempt to derive its source code, model weights, algorithms or non-public interfaces, except to the extent that applicable law expressly permits it despite this restriction, and then only after giving us written notice and a reasonable opportunity to provide the information the Subscriber needs;
• (c) modify, translate or create derivative works of the Software, except configuration that the Documentation describes;
• (d) disable, circumvent, bypass or interfere with the Software's enforcement of Policy, its tamper protections, its license, enrollment or Entitlement controls, or its verification of signatures on Updates, Model Packs, Policy or commands, other than through the controls the Software and the Documentation provide to Administrators, such as uninstalling, pausing inspection where Policy allows it, or changing Policy;
• (e) extract, decrypt, copy or use any Model Pack, model, weight file or Security Content separately from the Software, or use any of them to develop, train or improve any other model or product;
• (f) use the Software, or any output of it, to build, train or improve a product or service that competes with the Software;
• (g) publish or disclose to any third party the results of any benchmark, performance, comparative or detection-effectiveness test of the Software without our prior written consent;
• (h) remove, alter or obscure any proprietary, copyright, trademark, license or attribution notice in the Software, including the NOTICE file;
• (i) use the Software to monitor, intercept, inspect or interfere with the devices, accounts, network traffic or communications of any person other than the Subscriber's own End Users on devices, browsers and robots the Subscriber is entitled to manage, or in any way that violates the rights of any person or any applicable law;
• (j) use the Software to identify, track or act against any person on the basis of a characteristic protected by law, or for surveillance unrelated to information security, data protection, acceptable-use enforcement, safety or legal compliance;
• (k) use the Software as the sole safeguard in any environment in which its failure could lead to death, personal injury or severe physical or environmental damage, including as the only means of stopping a robot or limiting its motion;
• (l) access or use any non-public application programming interface of the Software or a Deployment, other than as the Software itself does; or
• (m) exceed the Subscriber's Entitlement, except as Section 3.3 allows a Consumer.

5.2 Security testing of the Subscriber's own installation. Despite Sections 5.1(b), (d) and (g), the Subscriber may inspect, audit, security-test, fuzz and penetration-test its own installation of the Software and its own Deployment, and may disclose the results to us. Public disclosure of a vulnerability is governed by our vulnerability disclosure process at https://cyberarmor.ai/security. Testing must not target infrastructure that serves other customers, and must not go further than needed to demonstrate a finding.

6. Roles: the Subscriber and its End Users

6.1 The Subscriber controls the Software. The Subscriber, or an Authorized Partner acting for it, chooses which components to install, enrolls devices, browsers and robots, sets Policy (or, for a Consumer, chooses among the settings the plan offers), chooses what evidence is captured, decides who may see security events, and decides whether End Users may pause inspection or remove components. We do not configure the Software for the Subscriber unless it asks us to, under a Customer Agreement or the Managed Service.

6.2 Organizations: we act on the Organization's instructions. For personal data that the Software sends to a Deployment we host for an Organization, the Organization is the controller (or business) and we act as its processor (or service provider) on its documented instructions, as described in the Privacy Policy and the DPA. Where an Authorized Partner hosts the Deployment, the partner acts in that role and we may act as the partner's subprocessor. Where the Organization hosts the Deployment itself, the data does not reach us unless the Organization sends it to us, for example in a support request.

6.3 Consumers: we are the controller. Where a Consumer's devices report to a Deployment we host, we are the controller of that data, including data we receive through the Managed Service and Device Management, and we use it only to provide the protection the Consumer subscribed to, as described in the Privacy Policy. The Consumer decides which devices to enroll and which settings to use, and is responsible for the notices in Section 8.6.

6.4 Questions from End Users. An End User of an Organization who wants to know what the Software collects on a managed device, or who wants to exercise a data protection right, should ask the Organization. If we receive such a request about data we process for the Organization, we will refer it to the Organization as the DPA provides. A Consumer or a Household Member may contact us directly at privacy@cyberarmor.ai.

6.5 The Managed Service. A Subscriber may ask us to manage its devices for it.

• (a) Opting in. A Consumer may ask us to manage some or all of the Consumer's enrolled devices, and an Organization may do so where its Customer Agreement provides for it. The request is made in the customer portal, in an app or at checkout, is recorded with its date and the devices it covers, and can be changed at any time. We manage no device unless the Subscriber has opted in for it.
• (b) What we do. For each device in the Managed Service, we act as its Administrator: we choose and change Policy settings within the protection level and the choices the Subscriber has made, apply Updates and Model Packs, review the security events the device reports, and tell the Subscriber about events that need its attention. For a phone or tablet, we also enroll the device in Device Management, through a device-management service that we operate or that a service provider operates for us. Enrollment installs a management profile on the device, which the person using the device must accept, and applies the certificate, settings and app configuration that the Managed Service needs.
• (c) What we can see. Through the Software, we see what Appendix A describes for each component. Through Device Management, we see the information that the operating system gives a device-management service for that kind of enrollment, such as the device model, operating-system version and device identifiers, whether the management profile and the CyberArmor.AI apps are installed, and the configuration we applied. The Privacy Policy lists it.
• (d) What we do not do. We do not use the Managed Service or Device Management to read the content of messages, email, photos, contacts or personal files, to track a device's location, to erase or lock a device, or to install apps other than CyberArmor.AI software.
• (e) Withdrawing. The Subscriber may withdraw a device from the Managed Service at any time, in the customer portal or by emailing support@cyberarmor.ai. The person using an unsupervised iPhone or iPad, or an Android device, may also remove the management profile in the device's settings. When a device leaves the Managed Service, we stop administering it and remove the management profile where the operating system lets us. The Software keeps protecting the device under the Policy last in force, which the Subscriber may then change, at the level that an unmanaged device of its kind receives (Section 7.3), until the Software is uninstalled or the subscription ends. Data already reported is kept and deleted as the Privacy Policy describes.
• (f) Who controls the data. For a Consumer, we are the controller of the data we receive through the Managed Service, as Section 6.3 states. For an Organization, the Managed Service does not change the roles in Section 6.2: we act on the Organization's instructions.
• (g) Care and responsibility. We will configure the Software under the Managed Service with reasonable care and in line with the Subscriber's choices. Section 13 still applies: a managed device is not guaranteed to be protected against every threat. The Managed Service carries no service level, response time or monitoring hours unless a Customer Agreement states them. The Subscriber remains responsible for choosing which devices to place in the Managed Service and, for a Consumer, for the notices and agreement Section 8.6 requires.

7. What the Software does on a device

This Section describes what the Software is capable of doing. What it does on a given device or robot depends on which components are installed, on the operating-system approvals the device user has granted, and on the Subscriber's Policy. Appendix A lists the data each component processes and where it is sent.

7.1 Endpoint Agent. As configured by the Subscriber, the Endpoint Agent can:

• (a) inspect AI-service traffic: route the device's web traffic through a proxy that runs on the device, by changing the device's system proxy settings and those of supported developer tools. To inspect encrypted traffic, it generates a root certificate on the device and adds it to the device's trusted certificate store; the private key of that certificate stays on the device. The proxy can decrypt traffic that passes through it. It inspects the content of requests to and responses from AI services and other destinations the Subscriber's Policy names, checks the addresses of other destinations against Policy, and does not record the content of other traffic;
• (b) check web addresses against the Subscriber's URL Trust Gate and against Security Content before a page or resource loads, and block destinations Policy forbids;
• (c) examine files that AI tools and AI coding assistants read or upload, and files written to watched locations, for sensitive data and malicious content, and compare files against hash lists;
• (d) examine the clipboard, where the clipboard component is installed, to find sensitive data before it can be pasted into an AI tool, and redact or clear it as Policy directs;
• (e) observe processes and file activity using operating-system facilities: on macOS, an Endpoint Security system extension that the device user must approve; on Windows, Event Tracing for Windows; on Linux, a kernel monitoring program. This includes which AI applications run and which files they open;
• (f) act on what it finds: warn the person at the keyboard, redact content, block a request or upload, quarantine a file, and, where the Subscriber has enabled it, stop a process that it has attributed to ransomware-like activity;
• (g) run machine-learning models on the device from a signed Model Pack, so that much of the evaluation happens on the device;
• (h) carry out signed administrative actions that the Subscriber authorizes, such as applying approved software updates through the operating system's package managers or running a signed remote command; and
• (i) report security events, enforcement decisions, device inventory and health, and the Software's own status to the Subscriber's Deployment, in records that are digitally signed so that changes can be detected.

7.2 Browser Extension. As configured by the Subscriber, the Browser Extension can:

• (a) send the address of each page the browser navigates to (without its query string or fragment) to the Subscriber's URL Trust Gate before the page loads, and block or warn about pages the gate identifies as harmful;
• (b) examine text typed or pasted into AI services and warn, redact or block before it is sent. This happens in the browser or, where the Endpoint Agent is installed, in its local engine. Where neither can decide, the text of a prompt being submitted is sent to the Subscriber's Deployment to be scanned;
• (c) send files uploaded to AI services to be scanned, on the device where the Endpoint Agent's local engine can do it and otherwise by the Subscriber's Deployment, and hold or block the upload as Policy requires;
• (d) record each warning, redaction, block and blocked upload as an enforcement event, and record page visits as hourly counts per website or, where the Deployment requests it, as individual events; and
• (e) where the Endpoint Agent is installed, ask its local engine for verdicts through a native-messaging connection on the device.

The Browser Extension does not send the text of the pages a person reads. It sends the text of prompts for storage only if the Subscriber turns on prompt logging, which is off by default. It sends nothing before it is enrolled to a Deployment.

7.3 Mobile Apps. On every phone or tablet, managed or not:

• (a) the CyberArmor.AI app for iOS and iPadOS filters domain-name lookups on the device against Policy and reports counts, not the names looked up, and its Safari extension works as described in Section 7.2 inside Safari;
• (b) the watchOS app shows the iPhone app's counters and makes no network connections of its own;
• (c) the Android app filters domain-name lookups through a local VPN connection that carries only those lookups, and reports lookups that Policy blocked and lookups to AI services; and
• (d) a Mobile App does nothing until it is enrolled to the Subscriber's Deployment.

Apple and Google allow some protections only on a phone or tablet enrolled in Device Management. On phones and tablets, and only there, a managed device can therefore be protected more than an unmanaged one:

• (e) managed iPhone or iPad: Device Management can enroll the app without anyone typing an enrollment token, set the DNS resolver the filter uses, and install and trust a certificate created for that device. That certificate lets the app's app-proxy extension inspect the full address and request body of traffic from other apps to AI services, and redact or block it on the device, rather than seeing only the domain name. The app-proxy extension has been built but has not yet been validated on a device, so it is a Preview Feature (Section 3.6);
• (f) unmanaged iPhone or iPad: outside Safari, the app sees domain names only, and a Policy that needs the content of a request is shown as advisory, not enforced. iOS does not let any app read the content of other apps' traffic on an unmanaged device; and
• (g) Android: no management mode lets any app inspect the encrypted content of other apps' traffic, so protection is at the level of domain names whether or not the device is managed. On a managed Android device, Device Management can require the filter to stay on and prevent the app from being removed.

On computers, in browsers and on robots, the protection is the same whether or not a device is in the Managed Service. The Privacy Policy describes each app in detail.

7.4 ROS 2 Security Agent. As configured by the Subscriber, the ROS 2 Security Agent runs on the robot's computer and can:

• (a) monitor the ROS 2 graph: discover topics, services and DDS participants, track who publishes and subscribes, and report floods, unexpected participants and exposed services such as parameter-changing services;
• (b) check robot motion commands against speed, acceleration, rate, geofence and safety-zone limits. In observe mode, which is the default, it reports violations and the robot receives exactly the commands it would have received without the agent. In interpose mode, which the Subscriber must switch on by wiring the robot's motor driver to a separate output topic, it forwards limited commands, and replaces or drops commands that Policy rejects, so that the robot's behavior changes;
• (c) hold a stop: latch a software emergency stop and software motion inhibits, which persist across restarts of the agent and are released only with a signed release token or locally by an authorized person;
• (d) check sensor readings for values that are out of range, stale, replayed, stuck or arriving at the wrong rate;
• (e) inspect command text sent to the robot, such as voice-command transcripts, steps produced by an AI planner, and requests from apps, and allow, redact, hold for a person's confirmation, or block each one, on the robot, using signed Policy; and
• (f) report security events and its own status on the robot's ROS 2 topics and to the Subscriber's Deployment.

Decisions are made on the robot. The Deployment is used to deliver signed Policy and to receive telemetry, and is not asked for a decision. Telemetry about command text carries the categories of what was found, a hash and the length of the text, and never the command text itself or the value matched. Section 13.5 applies to every use of the ROS 2 Security Agent.

7.5 Developer Components. The RASP agents and client software development kits run inside applications that the Organization builds. As the Organization configures them, they check AI requests and responses made by those applications against Policy, and warn, redact or block, and report enforcement events to the Organization's Deployment, as the Documentation for each language describes.

7.6 On the device first; the Deployment when needed. Where the device can decide, content is evaluated on the device. Where it cannot (for example, because no Model Pack is active or a check requires the server), content may be sent to the Subscriber's Deployment to be scanned, and the result is returned to the device. Whether content is then kept as evidence is decided by the Subscriber's Policy; content capture is off by default.

7.7 What the person at the keyboard sees. The Software is designed to tell the person at the keyboard when it blocks, redacts or warns and, on macOS and Windows, to show whether protection is on. The macOS installer lets the person installing choose optional components. These notices supplement, and do not replace, the notice the Subscriber must give under Section 8.

7.8 No hidden functions. The Software contains no function designed to collect data for advertising, to sell data, or to collect data unrelated to the security service. A material expansion of what a component collects will be described in the Privacy Policy and the Documentation before it takes effect.

8. Notice and consent obligations

8.1 Lawful basis. Before installing the Software on any device or robot, or the Browser Extension in any browser, the Organization is solely responsible for ensuring that it has every right, lawful basis, notice and consent that applicable law, its contracts and its collective agreements require for the monitoring, inspection, interception, blocking and data processing that the Software will perform under its Policy, including under laws that govern employee monitoring, interception of communications, computer misuse, privacy and data protection, and consultation of works councils or employee representatives.

8.2 Notice to End Users. The Organization will give each End User clear notice, before the Software is active on a device or browser the End User uses, of at least: that the Software is installed; the categories of activity and data it inspects and records under the Organization's Policy; the purposes; who can see the results; how long they are kept; and whom to contact with questions. Any template notice we provide is not legal advice, and the Organization remains responsible for the content of its notice.

8.3 Devices the Organization does not own. The Organization will install the Software on a personally owned device only with the owner's informed agreement, and will configure Policy so that it does not inspect more than its legitimate purposes need.

8.4 Robots. The Organization is responsible for telling the people who operate or work near a robot running the ROS 2 Security Agent what the agent does, and for any notice or consent the law requires for the command text, including voice-command transcripts, that the agent inspects.

8.5 Responsibility. We are not responsible for the Organization's choice of Policy, for any failure by the Organization to give notice or obtain consent, or for the Organization's use of the information the Software produces, including any employment decision.

8.6 Consumers and their households. A Consumer may enroll only devices and browsers that the Consumer owns or controls. Before enrolling a device that a Household Member uses, the Consumer will tell that person that the Software is installed and what it does, and, for an adult, will obtain that person's agreement. A Consumer who places a device that a Household Member uses in the Managed Service must first have that person's agreement or, for a child, act as this Section describes. A Consumer must not use the Software to monitor another adult without that adult's knowledge, or to monitor anyone in a way that the law forbids. The Software is not directed to children; a Consumer who enrolls a device a child uses must be the child's parent or legal guardian, or act with that person's permission, and is responsible for doing so in accordance with applicable law.

9. End User terms

9.1 Each End User will:

• (a) use the Software only as the Subscriber permits, and comply with an Organization's acceptable-use policies;
• (b) not disable, uninstall, tamper with or circumvent the Software, or use another device, browser, profile, network path or tool for the purpose of avoiding the Subscriber's Policy, unless the Subscriber permits it, for example through a pause control it has enabled;
• (c) not attempt to access data, devices, robots or Deployments that the End User is not authorized to access; and
• (d) treat as confidential any non-public information about the Software that the End User receives through it.

9.2 An End User's right to use the Software comes only through the Subscriber, and ends when the Subscriber's rights end or when the Subscriber withdraws its authorization.

9.3 Nothing in this Agreement limits any right an End User has under data protection, consumer or employment law, or makes an End User liable to us for the Subscriber's obligations.

10. Data processing and privacy

10.1 Where to find the detail. The categories of personal data the Software processes, the purposes, the recipients and the retention periods are described in the Privacy Policy and, for Organizations, in the DPA. Appendix A summarizes them for the Software. If this Agreement and the DPA conflict about personal data, the DPA controls.

10.2 Where data goes. The Software sends data only to the Deployment to which it is enrolled, and to the services that Deployment directs it to, for example to download Updates, Model Packs and Security Content. The Software does not send product data to us when the Deployment is hosted by the Organization or by an Authorized Partner, unless the Organization or the partner chooses to send it to us, for example in a support request.

10.3 Third-party services the Subscriber enables. Some functions use third-party services only if the Subscriber enables them and supplies its own credentials, for example AI model providers reached through the Deployment. When the Subscriber does so, data is sent to that third party on the Subscriber's instructions, under the Subscriber's own agreement with it, and the Subscriber is responsible for complying with that third party's terms.

10.4 Service data. We may use technical data about the operation of the Software, such as version, health, error and performance counters, and Entitlement counts, to provide, support, secure and improve the Software and to verify compliance with this Agreement. We do not use the content the Software inspects, or personal data processed for a Subscriber, to train or improve models offered to other customers, and we do not sell personal data or use it for advertising.

10.5 Security. We maintain the technical and organizational measures described in the DPA for Deployments we host for Organizations, and equivalent measures for Consumers' data. The Organization is responsible for the security of Deployments it hosts. Every Subscriber is responsible for protecting its enrollment tokens and Administrator credentials, and for configuring the Software in accordance with the Documentation.

10.6 Data location. A Deployment we host stores and processes the Subscriber's data in the region agreed when the Subscriber subscribed, and we do not move that data to another region without the Subscriber's consent, except for the limited categories listed in section 5 of the Privacy Policy. We host Deployments only for Subscribers in the United States and for consumers and businesses in Singapore. Every other Subscriber runs its Deployment on its own infrastructure, or on an Authorized Partner's, in its own country; that Deployment does not send product data to us, and anything shared with us for support is redacted and de-identified first.

11. Updates, Model Packs and Security Content

11.1 Updates. We may provide Updates during the Subscription Term. Depending on the Subscriber's settings, the Software may download and apply Updates automatically. Each Update is verified against our digital signature before it is applied, and a version older than the one installed is refused. Updates are part of the Software and are governed by this Agreement unless they come with different terms.

11.2 Model Packs. Model Packs are delivered to devices only if the Subscriber's subscription includes them and the Subscriber has enabled them. A Model Pack may include models created by us and models created by third parties under their own licenses (Section 12). Model Packs may be used only by the Software on the enrolled device.

11.3 Security Content. Security Content is compiled from our own work and from third-party sources, some of which have their own license terms, and attributions they require travel with the content. Security Content may be used only by the Software and may change at any time.

11.4 Supported versions. We support the versions of the Software that the Documentation identifies as supported. Older versions may stop working with a Deployment, may stop receiving Security Content, or may be refused enrollment.

11.5 Changes. We may change or discontinue features of the Software. If we remove a material feature during a paid Subscription Term, the Customer Agreement's remedies apply or, if it has none, the Subscriber may terminate the affected subscription and receive a pro-rated refund of prepaid fees for the remainder of the term. For an Organization, that is its sole remedy; a Consumer also keeps the rights described in Section 2.6.

12. Third-party and open-source components

12.1 The Software includes Third-Party Components. Each is licensed to the Subscriber by its copyright holder under its own license, not under this Agreement. Where the license of a Third-Party Component conflicts with this Agreement, that license controls as to that component, and nothing in this Agreement restricts any right that license grants.

12.2 The Third-Party Components, their licenses and the required attributions are listed in the NOTICE file distributed with the Software and in the license files that accompany each component. They include:

• (a) open-source libraries under permissive licenses such as MIT, BSD and Apache-2.0, including mitmproxy, which the local proxy uses;
• (b) machine-learning models and model code included in or delivered with Model Packs, including OpenAI Whisper (MIT) in a conversion by SYSTRAN (MIT), and models published under the Apache-2.0 and MIT licenses, run with ONNX Runtime (MIT);
• (c) the Linux kernel monitoring program, which we wrote and license under the GNU General Public License version 2, as the Linux kernel requires;
• (d) known-bad file hash lists derived from the ClamAV virus database, which are distributed as separate files under the GNU General Public License version 2;
• (e) components under the GNU Lesser General Public License, which the Subscriber may replace as that license permits; and
• (f) for the ROS 2 Security Agent, the ROS 2 client libraries and message packages it uses at run time, which are installed with ROS 2 under their own licenses and are not distributed by us.

12.3 To obtain source code that the license of a Third-Party Component entitles the Subscriber to receive, contact legal@cyberarmor.ai.

13. Security features: no guarantee

13.1 No product detects everything. The Software is designed to reduce the risk of sensitive data reaching AI services and of other security threats. It does not detect, prevent or stop every threat, attack, malicious web page or file, or every disclosure of sensitive data. Detection by machine-learning models and rules is probabilistic: the Software will sometimes miss something it should have flagged, and will sometimes flag, redact or block something harmless. We do not publish detection accuracy figures, and no statement by us, our Authorized Partners or our representatives is a promise of any particular detection result.

13.2 Configuration matters. What the Software protects depends on which components are installed and enabled, on whether the device user has granted the operating-system approvals some components need, on the Subscriber's Policy, including whether it chooses to fail open or closed when a check cannot be completed, and on network conditions. The Software reports when it is not enforcing or cannot complete a check, and the Subscriber is responsible for monitoring those reports.

13.3 Actions on the device. Blocking, redacting, quarantining a file or stopping a process can interrupt work and, in rare cases, cause the loss of unsaved data. The Subscriber decides whether to enable these actions, and should keep backups and test Policy before deploying it widely.

13.4 Part of a layered defense. The Software is not a substitute for backups, other security controls, security monitoring, training, or the Subscriber's own legal and compliance judgment. Compliance mappings and reports produced by the Software or a Deployment are aids to the Subscriber's own assessment, not a certification that the Subscriber complies with any law or standard.

13.5 Robots: not a safety system. The ROS 2 Security Agent is a security product. It is not a functional-safety system, it has not been certified under any safety standard (for example IEC 61508, ISO 13849, ISO 10218 or ISO 13850), and it is not a substitute for hardware emergency stops, safety-rated controllers, guarding, or the robot manufacturer's and integrator's safety design and validation. Its software emergency stop and motion inhibits depend on the robot's computer, its operating system, ROS 2 and the motor driver all working, and may not act when any of them fails. Interpose mode changes how the robot moves and is off unless the Subscriber switches it on. Before deploying the ROS 2 Security Agent on a robot that can move or exert force, and again before switching on interpose mode or changing a limit, the Organization is responsible for carrying out the risk assessment and testing that the robot's use requires, and for keeping a hardware emergency stop that works independently of the Software. The ROS 2 Security Agent's components are Preview Features under Section 3.6 unless the capability status page says otherwise.

14. Confidentiality

14.1 The Software, including its non-public interfaces, Model Packs, Security Content and any source code we make available, the Documentation that is not publicly available, and any non-public pricing are our confidential information. The Subscriber will use it only to exercise its rights under this Agreement, will protect it with at least reasonable care, and will disclose it only to its personnel, affiliates, contractors and Authorized Partners who need it for that purpose and are bound by confidentiality obligations no less protective than these.

14.2 If the Subscriber and we have signed a Customer Agreement or a non-disclosure agreement that contains confidentiality terms, those terms apply instead of Section 14.1 to the extent they cover the same information.

14.3 Information is not confidential if it is or becomes public through no fault of the recipient, was lawfully known to the recipient without restriction before receipt, is received lawfully from a third party without restriction, or is independently developed without use of our confidential information. A recipient may disclose confidential information when required by law, after giving us notice where the law allows.

15. Ownership and feedback

15.1 We and our licensors own the Software, the Documentation, Model Packs, Security Content and all intellectual property in them. The Subscriber owns its Policy and the data the Software processes for it, subject to the rights of End Users and third parties.

15.2 If the Subscriber or an End User gives us suggestions or feedback about the Software, we may use them without restriction or obligation.

15.3 CyberArmor.AI and the CyberArmor.AI logo are our trademarks. This Agreement grants no right to use them, except as an Authorized Partner's agreement with us allows.

16. Fees and verification

16.1 Organizations. Fees for an Organization's subscription are set by the Customer Agreement or, for a subscription obtained through an Authorized Partner, by the Organization's agreement with that partner.

16.2 Subscriptions bought online. For a subscription bought through the checkout on our website, the price, the billing period, and whether and when the subscription renews are shown before the purchase is completed, and the Terms of Use govern billing, automatic renewal, cancellation and refunds. A Consumer may cancel at any time, as the Terms of Use describe, and cancellation takes effect at the end of the billing period already paid for, unless the law gives the Consumer a right to cancel sooner or to a refund.

16.3 Verification. The Deployment counts enrollments for Entitlement purposes. On written request, no more than once in any twelve-month period, the Organization will within thirty (30) days provide a written statement, signed by an authorized officer, of the number of devices, robots and users on which the Software is installed. For a Deployment that the Organization hosts, we may, on thirty (30) days' written notice and no more than once in any twelve-month period, verify that statement against the Organization's records during normal business hours, at our expense unless the verification shows that the Organization exceeded its Entitlement by more than five per cent, in which case the Organization will reimburse the reasonable cost of the verification and pay for the excess. This Section 16.3 does not apply to Consumers.

17. Export control and sanctions

17.0 Compliance with law. We do our best to comply with all applicable national, state, local and international laws and regulations, including data protection, privacy, consumer protection, export control and sanctions laws, in every country where we offer CyberArmor.AI.

17.1 Laws that apply. The Software contains encryption and is subject to the export control and economic sanctions laws of the United States and of other countries, including the U.S. Export Administration Regulations and the regulations administered by the U.S. Department of the Treasury's Office of Foreign Assets Control. The Subscriber will comply with those laws, and will obtain any license or authorization they require, when it exports, re-exports or transfers the Software or allows it to be accessed from another country.

17.2 Representations. The Subscriber represents that it is not, and is not owned or controlled by, a person or entity on any U.S. or other applicable restricted-party list, and is not located in, organized under the laws of, or ordinarily resident in a country or region subject to comprehensive U.S. sanctions. The Subscriber will not install, use, transfer or allow access to the Software in any such country or region, by or for any such person, or for any end use those laws prohibit.

17.3 What we may do. We may, at any time and without liability, screen orders, enrollments and downloads against the countries and parties those laws restrict, and refuse, suspend or block an order, a download, an enrollment or an Update where we believe that providing it could breach those laws. We take the export restrictions in force when a version of the Software is released into account in deciding where we make it available. Any screening we carry out is for our own compliance; it does not guarantee that any use of the Software complies with those laws, and it does not relieve the Subscriber of its obligations under this Section.

17.4 Import and use laws. The Subscriber is responsible for complying with any law of the country in which it uses the Software that governs the import or use of encryption or security software, including any requirement to register, notify or obtain approval. Authorized Partners are responsible for those requirements in the countries in which they distribute the Software.

18. Term, termination and uninstallation

18.1 Term. This Agreement starts when it is accepted under Section 2 and continues for the Subscription Term.

18.2 Termination. This Agreement and the licenses in it end automatically when the Subscription Term ends, the Customer Agreement terminates, or a Consumer's cancellation takes effect. Either party may terminate this Agreement on written notice if the other materially breaches it and does not cure the breach within thirty (30) days after written notice describing it. We may suspend or terminate the license immediately on notice if the Subscriber breaches Section 5, Section 8.6 or Section 17, or if continued use would violate law.

18.3 Effect of termination. When this Agreement ends, the Subscriber will stop using the Software and, within thirty (30) days, uninstall it from every device, browser and robot and destroy all copies of it in its possession, except copies retained in archival backups that are not restored to use, or that law requires it to keep. The Software may stop enforcing Policy and stop receiving Updates and Security Content when the subscription ends.

18.4 Uninstallation. We provide uninstallers and Documentation for each component. Uninstalling the Endpoint Agent is designed to remove the root certificate it created, restore the proxy settings it changed, remove its system extension and helpers, and stop its reporting, as described in the Documentation for each platform. Uninstalling the Browser Extension removes the data it stored in the browser. Before removing the ROS 2 Security Agent from a robot in interpose mode, the Organization must reconnect the motor driver to its original command topic. Data already sent to a Deployment is retained and deleted as described in the Privacy Policy, the Customer Agreement and the DPA.

18.5 Survival. Sections 1, 5, 8, 12, 13, 14, 15, 16, 17, 18.3, 18.5, 19, 20, 21, 22, 23 and 24 survive termination.

19. Warranties and disclaimer

19.1 Organizations. Any warranty to an Organization for the Software, and any remedy for breach of it, is stated in the Customer Agreement and nowhere else. An Authorized Partner's warranty binds only that partner.

19.2 Consumers. A Consumer has the warranties and remedies that the consumer protection law of the place where he or she lives gives and does not allow a contract to exclude. Section 19.3 does not limit them.

19.3 Disclaimer. EXCEPT AS EXPRESSLY STATED IN A CUSTOMER AGREEMENT SIGNED BY US, AND EXCEPT FOR THE RIGHTS DESCRIBED IN SECTIONS 2.6 AND 19.2, THE SOFTWARE, MODEL PACKS, SECURITY CONTENT, EVALUATION USE AND PREVIEW FEATURES ARE PROVIDED "AS IS" AND "AS AVAILABLE". TO THE MAXIMUM EXTENT PERMITTED BY LAW, WE AND OUR LICENSORS DISCLAIM ALL OTHER WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, INCLUDING ANY WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, NON-INFRINGEMENT, ACCURACY OR QUIET ENJOYMENT, AND ANY WARRANTY ARISING FROM COURSE OF DEALING OR USAGE OF TRADE. WE DO NOT WARRANT THAT THE SOFTWARE WILL BE UNINTERRUPTED OR ERROR-FREE, THAT IT WILL DETECT OR PREVENT ANY PARTICULAR THREAT OR DISCLOSURE, THAT IT WILL STOP OR LIMIT A ROBOT IN EVERY CIRCUMSTANCE, OR THAT IT WILL MEET THE SUBSCRIBER'S REGULATORY OR COMPLIANCE REQUIREMENTS.

20. Limitation of liability

20.1 Excluded damages. TO THE MAXIMUM EXTENT PERMITTED BY LAW, NEITHER PARTY WILL BE LIABLE UNDER OR IN CONNECTION WITH THIS AGREEMENT FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, EXEMPLARY OR PUNITIVE DAMAGES, OR FOR ANY LOSS OF PROFITS, REVENUE, BUSINESS, GOODWILL OR ANTICIPATED SAVINGS, LOSS OR CORRUPTION OF DATA, OR THE COST OF SUBSTITUTE PRODUCTS, HOWEVER CAUSED AND UNDER ANY THEORY OF LIABILITY, EVEN IF ADVISED OF THEIR POSSIBILITY.

20.2 Cap. TO THE MAXIMUM EXTENT PERMITTED BY LAW, EACH PARTY'S TOTAL LIABILITY UNDER OR IN CONNECTION WITH THIS AGREEMENT WILL NOT EXCEED THE FEES PAID AND PAYABLE TO US FOR THE SOFTWARE IN THE TWELVE (12) MONTHS BEFORE THE EVENT GIVING RISE TO THE LIABILITY OR, FOR EVALUATION USE OR SOFTWARE PROVIDED WITHOUT CHARGE, ONE HUNDRED U.S. DOLLARS (US$100). WHERE THE SUBSCRIBER OBTAINED THE SOFTWARE THROUGH AN AUTHORIZED PARTNER, THE FEES ARE THOSE WE RECEIVED FOR THE SUBSCRIBER'S SUBSCRIPTION.

20.3 Exceptions. Sections 20.1 and 20.2 do not limit the Subscriber's liability for breach of Section 5, Section 8 or Section 17, for fees owed, or under Section 21; either party's liability for infringement or misappropriation of the other party's intellectual property; or liability that cannot be limited by law, including liability for death or personal injury caused by negligence, or for fraud.

20.4 Customer Agreement. If a Customer Agreement signed by us contains a limitation of liability, it applies instead of this Section 20.

20.5 Consumers. For a Consumer, Sections 20.1 and 20.2 apply only to the extent the law of the place where the Consumer lives allows, and do not limit our liability for loss that was a reasonably foreseeable result of our breach of this Agreement where that law does not allow such a limit. Some jurisdictions do not allow the exclusion or limitation of incidental or consequential damages, so these limits may not apply to a Consumer.

20.6 End Users. We have no liability to End Users who are not the Subscriber under this Agreement beyond what applicable law requires, and those End Users have no liability to us under it except for their own wilful breach of Section 9.

21. Indemnity by the Organization

21.1 The Organization will defend us, our affiliates and our personnel against any claim, demand, proceeding or regulatory investigation brought by a third party, including an End User or a regulator, arising from the Organization's Policy, its breach of Section 8, its use of the Software in breach of Section 5.1(i), (j) or (k), or its deployment of the ROS 2 Security Agent contrary to Section 13.5, and will pay the damages, fines, penalties and reasonable costs finally awarded or agreed in settlement, to the extent the law permits.

21.2 We will promptly notify the Organization of the claim, give it control of the defense and settlement (provided no settlement imposes an admission or obligation on us without our consent), and provide reasonable cooperation at the Organization's expense.

21.3 Any indemnity we give the Organization is stated in the Customer Agreement and nowhere else. This Section 21 does not apply to Consumers.

22. U.S. Government end users

The Software and Documentation are "commercial products", "commercial computer software" and "commercial computer software documentation" as those terms are used in 48 C.F.R. 2.101, 12.212 and 227.7202. Consistent with those regulations, the U.S. Government and its agencies acquire only the rights in the Software and Documentation that this Agreement grants to all other licensees. Any provision of this Agreement that is inconsistent with federal procurement law does not apply to a U.S. Government licensee to the extent of the inconsistency.

23. Governing law and disputes

23.1 Governing law. This Agreement is governed by the laws of the State of Delaware, United States, without regard to its conflict-of-laws rules. The United Nations Convention on Contracts for the International Sale of Goods and the Uniform Computer Information Transactions Act do not apply.

23.2 Courts for Organizations. Except as provided in Section 23.3, the state and federal courts located in the State of Delaware have exclusive jurisdiction over any dispute between an Organization and us arising out of or relating to this Agreement, and each party consents to their jurisdiction. THE ORGANIZATION AND WE EACH WAIVE ANY RIGHT TO A JURY TRIAL IN ANY SUCH DISPUTE.

23.3 Arbitration for Organizations outside the United States. If the Organization is organized or has its principal place of business outside the United States, any dispute arising out of or relating to this Agreement will be finally resolved by arbitration under the Rules of Arbitration of the International Chamber of Commerce by one arbitrator appointed under those Rules. The seat of arbitration is Wilmington, Delaware, the language is English, and judgment on the award may be entered in any court of competent jurisdiction. This Section exists because an arbitral award can be enforced in most countries under the New York Convention, where a court judgment often cannot.

23.4 Injunctive relief. Either party may seek injunctive or other equitable relief in any court of competent jurisdiction to protect its intellectual property or confidential information.

23.5 Consumers. Sections 23.2 and 23.3 do not apply to a Consumer. A Consumer may bring proceedings in the courts of the place where he or she lives, or in the state or federal courts located in the State of Delaware, and the choice of Delaware law in Section 23.1 does not deprive a Consumer of the protection of the mandatory law of the place where he or she lives. Before starting proceedings, we each agree to try for thirty (30) days to resolve the dispute informally, starting with an email to legal@cyberarmor.ai or, from us, to the Consumer's account email address. A Consumer who lives in the European Union may also use the alternative dispute resolution bodies that the law of his or her country makes available.

24. General

24.1 Entire agreement. This Agreement, together with the Customer Agreement, the order, the Terms of Use, the DPA and the documents they incorporate, is the entire agreement about the Software and supersedes prior agreements about it. Terms in any purchase order or other document of the Subscriber do not apply.

24.2 Changes to this Agreement. We may update this Agreement. An updated Agreement applies to an Organization from the start of its next Subscription Term, or earlier if the Organization accepts it, for example when an installer for a new version asks for acceptance of the new agreement version. We will tell a Consumer about a material change by email at least thirty (30) days before it takes effect; it applies from the Consumer's next renewal, and a Consumer who does not agree may cancel before then. A change does not apply to a dispute that arose before it.

24.3 Assignment. The Subscriber may not assign or transfer this Agreement without our prior written consent, except that an Organization may assign it to a successor to all or substantially all of its business or assets that is not our competitor and that assumes it in writing. We may assign it to an affiliate or a successor, and we will not do so in a way that reduces a Consumer's rights under it. Any other attempted assignment is void.

24.4 Severability and waiver. If a provision is held unenforceable, it will be enforced to the maximum extent permitted and the rest of the Agreement remains in effect. A failure to enforce a provision is not a waiver.

24.5 Force majeure. Neither party is liable for a failure or delay caused by events beyond its reasonable control, other than a failure to pay.

24.6 Independent parties. The parties are independent contractors.

24.7 Third-party beneficiaries. Licensors of Third-Party Components may enforce Section 12 as it applies to their components, and Apple Inc. is a third-party beneficiary to the extent Appendix B applies. There are no other third-party beneficiaries.

24.8 Notices. Notices to us must be sent by email to legal@cyberarmor.ai. Notices to an Organization may be sent to the contact in the Customer Agreement or to an Administrator's email address in the Deployment. Notices to a Consumer may be sent to the email address of the Consumer's account.

24.9 Language. This Agreement is written in English, and the English text controls, except where the law of the place where a Consumer lives requires otherwise. A translation, including the Simplified Chinese display of this page, is provided for convenience only.

24.10 Electronic acceptance. Acceptance by electronic means, including a click in an installer, an app or a checkout, or a command-line acceptance recorded under Section 2.3, has the same effect as a handwritten signature.

25. Contact

Legal and license questions: legal@cyberarmor.ai. Privacy and data requests: privacy@cyberarmor.ai. Security vulnerabilities: security@cyberarmor.ai. Support and subscription questions: support@cyberarmor.ai, or the Authorized Partner that supplied the Software.

Appendix A. Data the Software processes

This Appendix summarizes the data each component processes as installed and configured. It does not expand what the Subscriber's Policy allows, and the Privacy Policy and the DPA control. "Deployment" means the Subscriber's CyberArmor.AI deployment.

Appendix B. Additional terms for apps obtained from the Apple App Store

If the Software is obtained from the Apple App Store, the following terms also apply. If they conflict with the rest of this Agreement, this Appendix controls for that app.

B.1 This Agreement is between the Subscriber (an Organization or a Consumer) and us only, and not with Apple Inc. ("Apple"). We, not Apple, are solely responsible for the app and its content.

B.2 The license to use the app is limited to use on Apple-branded products that the user owns or controls, as permitted by the Usage Rules in the Apple Media Services Terms and Conditions, except that the app may be accessed by other accounts associated with the purchaser through Family Sharing or volume purchasing.

B.3 We are solely responsible for maintenance and support of the app. Apple has no obligation to provide any maintenance or support for it.

B.4 If the app fails to conform to any applicable warranty, the user may notify Apple, and Apple will refund the purchase price, if any, for the app. To the maximum extent permitted by law, Apple has no other warranty obligation for the app, and any other claims, losses, liabilities, damages, costs or expenses attributable to a failure to conform to a warranty are our responsibility, to the extent this Agreement does not disclaim them.

B.5 We, not Apple, are responsible for addressing any claim by the user or a third party relating to the app or its possession or use, including product liability claims, claims that the app fails to conform to any legal or regulatory requirement, and claims under consumer protection, privacy or similar laws.

B.6 We, not Apple, are responsible for the investigation, defense, settlement and discharge of any third-party claim that the app or its possession and use infringes that third party's intellectual property rights.

B.7 The user represents that he or she is not located in a country that is subject to a U.S. Government embargo or that has been designated by the U.S. Government as a "terrorist supporting" country, and is not listed on any U.S. Government list of prohibited or restricted parties.

B.8 Questions, complaints or claims about the app should be directed to CyberArmor AI, Inc. at support@cyberarmor.ai.

B.9 The user must comply with applicable third-party terms of agreement when using the app.

B.10 Apple and its subsidiaries are third-party beneficiaries of this Agreement, and on the user's acceptance of it, Apple will have the right, and will be deemed to have accepted the right, to enforce it against the user as a third-party beneficiary.