NODEFOX END USER LICENSE AGREEMENT

Version 1.0 | Effective Date: April 8, 2026 | Last Updated: April 8, 2026

Beta Status Notice: NodeFox is currently provided in beta. Features, behavior, documentation, and controls may change without notice. You must independently validate suitability for your use case and maintain your own safeguards.

© 2025–2026 NodeFox LLC. All rights reserved.

---

IMPORTANT — READ CAREFULLY BEFORE INSTALLING OR USING THE APPLICATION

THIS END USER LICENSE AGREEMENT ("EULA" OR "AGREEMENT") IS A LEGALLY BINDING CONTRACT BETWEEN YOU AND NODEFOX LLC ("NODEFOX," "COMPANY," "LICENSOR," "WE," "US," OR "OUR") GOVERNING YOUR USE OF THE NODEFOX DESKTOP APPLICATION AND RELATED SOFTWARE (THE "APPLICATION").

BY DOWNLOADING, INSTALLING, COPYING, OR OTHERWISE USING THE APPLICATION, YOU AGREE TO BE BOUND BY THIS EULA. IF YOU DO NOT AGREE, DO NOT DOWNLOAD, INSTALL, OR USE THE APPLICATION.

IF YOU ARE ACCEPTING ON BEHALF OF AN ENTITY, YOU REPRESENT THAT YOU HAVE AUTHORITY TO BIND THAT ENTITY.

THE APPLICATION IS IN BETA. IT MAY CONTAIN BUGS, ERRORS, OR INCOMPLETE FEATURES. DATA LOSS MAY OCCUR. USE AT YOUR OWN RISK.

THIS EULA CONTAINS IMPORTANT PROVISIONS REGARDING:

• DISCLAIMER OF WARRANTIES (Section 22)
• LIMITATION OF LIABILITY (Section 23)
• INDEMNIFICATION (Section 24)
• BINDING ARBITRATION AND CLASS ACTION WAIVER (Section 35)
• AUTOMATIC UPDATES (Section 12)
• DATA COLLECTION AND TELEMETRY (Section 14)
• LOCAL DATA STORAGE AND SECURITY (Section 15)
• AI FEATURES AND AUTONOMOUS ACTIONS (Section 17)
• HUMAN DEPLOYER ACCOUNTABILITY (Section 17.11)
• RUNAWAY EXECUTION AND COST RESPONSIBILITY (Section 17.13)
• EXECUTION SEMANTICS (Section 18.8)

---

RELATIONSHIP TO TERMS OF SERVICE

This EULA governs your use of the Application specifically. Your use is also subject to the NodeFox Terms of Service at /legal/terms (the "Terms of Service"), which are incorporated by reference.

Scope of EULA control. This EULA controls for matters specific to the Application: installation, local storage, desktop-only execution, updates, telemetry, license mechanics, and desktop-specific features.

Controlling regime for liability, arbitration, and limitation period. The Terms of Service control for liability limitations, indemnification, dispute resolution (arbitration), and limitation periods, including for Application-related disputes. In the event of any conflict between this EULA and the Terms of Service on those matters, the Terms of Service prevail. For all matters within the EULA's scope as defined above, this EULA controls. Capitalized terms not defined here have the meanings given in the Terms of Service.

---

KEY TERMS SUMMARY

This summary is for convenience only and creates no independent obligations or warranties. The full EULA controls.

---

EXECUTION SEMANTICS NOTICE

WORKFLOW EXECUTIONS MAY BE RETRIED, DUPLICATED, REORDERED, PARTIALLY EXECUTED, OR TIME OUT. STOP/PAUSE IS BEST-EFFORT AND MAY NOT HALT IMMEDIATELY. ACTIONS ALREADY DISPATCHED TO THIRD-PARTY SERVICES MAY COMPLETE EVEN AFTER A STOP REQUEST. YOU ARE RESPONSIBLE FOR DESIGNING WORKFLOWS WITH APPROPRIATE IDEMPOTENCY, ERROR HANDLING, AND COST CONTROLS.

---

PART I: DEFINITIONS AND LICENSE GRANT

SECTION 1. DEFINITIONS

1.1 "Account" — your NodeFox user account.

1.2 "Application" — the NodeFox desktop application software, including all components, modules, plugins, extensions, updates, patches, new versions, modifications, and associated documentation, files, libraries, installers, and resources.

1.3 "Application Data" — data created, stored, or cached by the Application on your Authorized Device (configuration files, preferences, cached content, local databases, logs, temporary files).

1.4 "Authorized Device" — a computer or device meeting System Requirements, owned or controlled by you, on which the Application is installed per this EULA.

1.5 "Background Processes" — Application processes running in the background (update checkers, sync services, schedulers, notification handlers).

1.6 "Documentation" — user guides, help files, release notes, API documentation, tutorials, and other materials describing the Application, including system requirements published at https://www.nodefox.ai.

1.7 "Execution Logs" — records of Workflow executions (timestamps, status, duration, errors, metadata).

1.8 "Feedback" — suggestions, ideas, enhancement requests, bug reports, or other feedback regarding the Application.

1.9 "In-flight Actions" — actions already dispatched to Third-Party Services or external systems that may complete regardless of whether you issue a stop/pause command or the Application terminates.

1.10 "License" — the license granted under Section 2.

1.11 "Local Storage" — data storage on your Authorized Device (databases, caches, configuration files).

1.12 "NodeFox Parties" — NodeFox LLC, its Affiliates, officers, directors, employees, agents, contractors, licensors, suppliers, successors, and assigns.

1.13 "NodeFox Platform Fees" — fees paid directly to NodeFox for platform access (subscriptions, premium features), expressly excluding all Third-Party Fees, payment processor fees, taxes, and pass-through costs.

1.14 "Outbound Request" — any HTTP request, API call, webhook, fetch, or network connection initiated by or through the Application or Workflows, whether to Third-Party Services, external endpoints, or internal/local addresses.

1.15 "Runaway Execution" — any Workflow execution that loops, recurses, self-triggers, fans out, retries, or otherwise continues beyond intended scope, potentially consuming unbounded resources or generating unbounded Third-Party Fees.

1.16 "Sandbox" — the execution environment in which User Code runs, which may include Web Workers, WASM containers, or other isolation mechanisms. No sandbox provides perfect isolation.

1.17 "Secrets Exposure Event" — any event in which User Secrets are or may have been exposed, whether through logs, crash reports, exports, shared workspaces, prompts, screen sharing, diagnostic bundles, or any other means.

1.18 "Services" — the NodeFox cloud platform, APIs, Marketplace, and related online services accessed through or in connection with the Application.

1.19 "Subscription" — a paid subscription plan.

1.20 "System Requirements" — the minimum hardware, software, and operating system specifications for the Application, as published in the Documentation and subject to change.

1.21 "Telemetry" — usage data, analytics, and diagnostic information collected by the Application.

1.22 "Third-Party Components" — software, libraries, frameworks, SDKs, or components developed by third parties incorporated into or distributed with the Application.

1.23 "Third-Party Fees" — any fees for Third-Party Services, including AI provider API fees, cloud costs, payment processing fees, and any costs not paid directly to NodeFox.

1.24 "Third-Party Services" — third-party websites, platforms, APIs, AI providers, or services accessed through or connected to the Application.

1.25 "Update" — any update, upgrade, patch, hotfix, security fix, new version, or modification to the Application.

1.26 "User Code" — custom JavaScript, DSL, scripts, or other code written by you for execution within the Application, including code executed in Code nodes, Script nodes, or made available to AI models as callable tools.

1.27 "User Content" — any content, data, workflows, files, configurations, or materials you create, upload, import, or process using the Application.

1.28 "User Secrets" — API keys, credentials, tokens, passwords, certificates, or other secrets you provide, whether entered directly, embedded in configurations, prompts, logs, DSL, environment variables, or otherwise present in Workflows or Application Data.

1.29 "Workflow" — any automated process, sequence, logic flow, node configuration, network, trigger, action, or orchestration created using the Application.

1.30 "Workflow Files" — files containing Workflow definitions, configurations, and related data, stored in NodeFox's proprietary format (which may change without notice).

1.31 "Workspace" — a logical container within the Application or Services holding Workflows, nodes, functions, schemas, files, and settings.

---

SECTION 2. LICENSE GRANT

2.1 Grant. Subject to your compliance with this EULA, the Terms of Service, the AUP, and applicable third-party provider terms, and subject to payment of applicable fees, NodeFox grants you a limited, non-exclusive, non-transferable, non-sublicensable, revocable license to download, install, and use the Application on Authorized Devices solely for your personal or internal business purposes.

2.2 License, Not Sale. The Application is licensed, not sold. NodeFox retains all ownership rights. No title or ownership transfers to you.

2.3 Revocability. The License is revocable at any time, for any reason, with or without notice, subject to the termination provisions herein.

2.4 Reservation. All rights not expressly granted are reserved.

2.5 Conditions. The License is conditioned on compliance with this EULA, the Terms of Service, and the AUP. The License may be automatically suspended during suspected abuse or security incidents without prior notice.

2.6 No Service Bureau. You may not use the Application to provide services to third parties on a service bureau, outsourcing, managed service, application service provider, access-brokering, or similar basis without NodeFox's prior written consent.

---

SECTION 3. PERMITTED USES

3.1 The License permits you to: download and install from authorized sources; install on Authorized Devices you own or control; make a reasonable number of backup copies for archival purposes only (backups must include proprietary notices and may not be redistributed); use for personal or internal business purposes; create, edit, test, and execute Workflows; connect to your Account and Third-Party Services using your own credentials; sync with the Services; use AI Features through third-party providers you configure; and share or publish Workflows subject to your Subscription and Marketplace Terms.

3.2 You may install on multiple Authorized Devices subject to Subscription limits. You are responsible for all use under your Account.

3.3 No Reliance for Critical Use. You agree not to rely on the Application for production or mission-critical workloads (unless you accept full responsibility), regulated or compliance-critical decisions, uses where errors could cause significant harm, or purposes requiring guaranteed correctness, determinism, availability, or security.

---

SECTION 4. LICENSE RESTRICTIONS

4.1 Prohibited Activities. You may not, and may not permit or assist any third party to:

(a) Modification: Modify, adapt, alter, translate, or create derivative works, except as permitted by applicable law or as necessary for normal use per the Documentation.

(b) Reverse Engineering: Reverse engineer, disassemble, decompile, decode, or attempt to derive source code, algorithms, data structures, file formats, non-public APIs, prompts, tool schemas, routing logic, safety policies, system configurations, or other internal logic, except as expressly permitted by applicable law that cannot be waived.

(c) Circumvention: Circumvent, disable, or interfere with any license verification, copy protection, DRM, access control, usage restriction, security feature, kill switch, rate limit, safety mechanism, or technical protection measure, including by modifying hosts files, local DNS, or network routing to selectively block NodeFox licensing, telemetry, or update servers.

(d) Distribution: Distribute, publish, sublicense, sell, resell, lease, rent, loan, or transfer the Application or rights therein.

(e) Commercial Exploitation: Use the Application to provide services to third parties without NodeFox's consent; charge others for access; or include the Application in a commercial product or service.

(f) Competitive Use: Use for competitive analysis, benchmarking, feature comparison, reverse engineering of business logic, or to develop or improve a competing product.

(g) Unauthorized Access: Access features or functionality not included in your License or Subscription; use others' credentials; or share credentials or License Keys.

(h) Proprietary Notices: Remove, obscure, or modify any proprietary notices, labels, watermarks, or branding.

(i) Malicious Use: Create, store, or transmit malware; attack or disrupt systems; or engage in any harmful activity. This includes using the Application or Workflows to generate or deploy malicious code, exploit payloads, or conduct unauthorized scanning or penetration testing.

(j) Illegal Use: Use in violation of any law, regulation, or third-party rights, or in any manner prohibited by the Terms of Service or AUP.

(k) Credential Abuse: Use the Application or Workflows for credential stuffing, token replay, session hijacking, secret harvesting, phishing, or any form of unauthorized credential acquisition or use, including via Outbound Requests.

(l) Runaway Execution: Create Workflows designed for or reasonably likely to cause unbounded loops, recursive self-triggering, fan-out amplification, retry storms, or other patterns generating runaway spend or infrastructure overload.

(m) Network Abuse: Use the Application to conduct SSRF attacks; probe localhost, link-local (169.254.x.x), RFC 1918 addresses, or cloud metadata endpoints (169.254.169.254); perform port scanning, service enumeration, or vulnerability probing; or operate as a proxy, tunnel, relay, VPN, or anonymization bridge.

(n) Hardware Obfuscation: Use HWID spoofers, MAC address changers, or hypervisor masking to evade device bans, reset trial periods, or circumvent licensing.

(o) Protocol Emulation: Intercept, emulate, or replicate NodeFox API protocols to build substitute servers intended to spoof NodeFox Services or evade Subscription verification.

(p) Copyleft Injection: Dynamically link, inject, or hook third-party code governed by a viral open-source license (such as GPL) into the Application's runtime in any manner that would subject NodeFox's proprietary IP to open-source disclosure obligations.

(q) Extraction: Extract, separate, or isolate Application components for standalone use, or use debuggers, memory dumpers, or packet sniffers on Application processes to extract decrypted secrets, bypass DRM, or reverse-engineer proprietary execution logic.

4.2 Technical Enforcement. NodeFox may implement technical measures to prevent, detect, or respond to violations, including license verification, usage monitoring, feature disabling, throttling, execution termination, and remote deactivation — all without liability. NodeFox does not guarantee immediate stoppage or detection of any violation.

4.3 Injunctive Relief. Violation of this Section may cause irreparable harm for which monetary damages are inadequate. NodeFox may seek injunctive relief without bond.

---

PART II: INTELLECTUAL PROPERTY

SECTION 5. INTELLECTUAL PROPERTY RIGHTS

5.1 NodeFox and its licensors own all right, title, and interest in the Application (software, source code, object code, algorithms, data structures, APIs, protocols, interfaces, designs, documentation) and all IP rights therein. No ownership transfers.

5.2 "NodeFox" and related marks are trademarks of NodeFox LLC. No use without written permission except factual reference.

5.3 The Application is protected by copyright, trademark, patent, trade secret, and other IP laws. You agree to maintain confidentiality of trade secrets, except where disclosure is compelled by law (with reasonable advance notice where permitted).

5.4 The Application may be protected by patents. No patent license is granted except as necessary for use expressly permitted herein.

5.5 No implied licenses. Except for the express License in Section 2, no right in any NodeFox IP is granted or implied.

---

SECTION 6. USER CONTENT AND OUTPUTS

6.1 As between you and NodeFox, you retain ownership of User Content. NodeFox does not claim ownership.

6.2 License to NodeFox. You grant NodeFox a limited license to access, process, display, and transmit User Content solely as necessary to provide Application functionality, enable sync, and comply with legal obligations. NodeFox has no obligation to provide support, and support may require access to content/logs at your direction.

6.3 Output Ownership. Subject to third-party rights and AI provider terms, you own Outputs generated through the Application. Outputs may be non-copyrightable under applicable law, may be similar or identical to outputs generated for other users, and third-party AI provider terms may impose additional restrictions. You are responsible for ensuring Outputs do not infringe third-party rights.

6.4 Workflow Files use NodeFox's proprietary format, which may change without notice. Export is available in supported formats as provided by the Application; compatibility across versions or with third-party tools is not guaranteed.

---

SECTION 7. NO AI MODEL TRAINING

7.1 NodeFox does not use User Content, Input Data, Outputs, Workflows, or Workflow Files to train, fine-tune, or develop general-purpose AI/ML models. This applies regardless of Subscription Tier.

7.2 Limited Exceptions. NodeFox may use limited processing strictly necessary for security, threat detection, abuse prevention, fraud detection, anomaly detection, and operational integrity. Such processing does not involve training general-purpose AI models.

7.3 Third-party AI providers have their own data practices and may use your data to train their models unless you configure opt-outs under their terms. NodeFox cannot configure opt-outs on your behalf.

7.4 NodeFox may use aggregated, de-identified operational data (feature usage statistics, error rates) that does not include substantive Workflow or Output content.

---

SECTION 8. FEEDBACK

8.1 If you provide Feedback, you grant NodeFox a perpetual, irrevocable, worldwide, royalty-free, sublicensable, transferable license to use Feedback for any purpose without attribution or compensation.

8.2 To the extent permitted by law, you waive moral rights in Feedback. You represent that Feedback does not contain confidential information (yours or third parties'), User Secrets, regulated data, or Personal Data.

8.3 NodeFox has no obligation to use, implement, respond to, or maintain Feedback in confidence.

---

PART III: SYSTEM REQUIREMENTS AND INSTALLATION

SECTION 9. SYSTEM REQUIREMENTS

9.1 Supported platforms, minimum hardware, and software requirements are published in the Documentation at https://www.nodefox.ai and may change with Updates.

9.2 You are responsible for ensuring your Authorized Device meets requirements. The Application may not function properly on unsupported configurations. NodeFox is not responsible for performance issues, instability, or data loss on unsupported configurations.

9.3 System Requirements may change with Updates. NodeFox has no obligation to maintain compatibility with older hardware, operating systems, or software.

9.4 Hardware Resources. The Application may consume significant CPU, GPU, memory, and disk resources during intensive Workflow executions. NodeFox disclaims all liability for hardware degradation, battery wear, thermal events, or component failure resulting from resource-intensive use.

9.5 OS Updates. Operating system updates may render the Application unstable or inoperable. NodeFox is not liable for interruptions caused by your OS upgrades prior to availability of a compatible Application Update.

---

SECTION 10. INSTALLATION AND ACTIVATION

10.1 Sources. Download the Application only from the official NodeFox website (https://www.nodefox.ai/download) or authorized distribution channels. NodeFox is not responsible for Applications from unauthorized sources.

10.2 Installation. By installing, you authorize the Application to: install files and resources; create application data directories; register file associations and URL protocol handlers; create shortcuts; install and configure Background Processes; bind to local network ports; and store credentials in OS credential storage — in each case, to the extent necessary for operation. Specific behaviors vary by OS. You are responsible for granting necessary OS permissions. NodeFox is not liable for failures caused by denied permissions.

10.3 Installation may require administrator privileges. Some features may require administrator privileges.

10.4 Code Signing. The Application is digitally signed. If your OS blocks installation due to signature verification, you may need to adjust security settings. If you bypass OS security warnings (including macOS Gatekeeper, Windows SmartScreen, or similar) to install the Application, you assume all resulting security and system integrity risks. NodeFox is not liable for compromise occurring while OS security features are bypassed or disabled.

10.5 Activation. The Application requires activation through your Account. Some features may be unavailable until activation. The Application may periodically verify your License by connecting to NodeFox servers. If verification fails, features may be disabled or the Application may cease to function.

10.6 Immutable License Verification. The Application contains license verification and security telemetry that cannot be disabled. The Application may transmit device identifiers and License status to NodeFox servers. Attempts to block this traffic may result in Application deactivation.

10.7 Constructive Acceptance. If the Application is installed on your device via silent installation, MDM, or centralized deployment, your subsequent access or use constitutes acceptance of this EULA regardless of whether you clicked an acceptance button.

---

SECTION 11. ACCOUNT AND AUTHENTICATION

11.1 A NodeFox Account is required for full functionality. Create one at https://www.nodefox.ai if needed.

11.2 The Application supports authentication via email/password, third-party OAuth, and other methods as may be added.

11.3 Sessions may expire after inactivity, be terminated for security reasons, or be remotely terminated by NodeFox. You are responsible for maintaining credential security, logging out on shared devices, enabling MFA, and notifying NodeFox immediately of unauthorized access at security@nodefox.ai.

11.4 Authentication tokens are stored in OS credential storage (Keychain, Credential Manager, or equivalent). These tokens provide Account access and must be protected.

---

PART IV: UPDATES AND VERSIONS

SECTION 12. UPDATES

12.1 Automatic Updates. By default, the Application automatically checks for, downloads, and installs Updates without your action. You consent to automatic Updates to the extent permitted by law. You may disable automatic Updates in settings, but doing so may expose you to vulnerabilities, cause compatibility issues, and degrade performance.

12.2 Updates may include bug fixes, security patches, new features, feature modifications or removal, performance changes, UI changes, compatibility updates, dependency changes, changes to default settings, and changes to execution semantics or DSL behavior.

12.3 Mandatory Updates. Some Updates are mandatory for security, compatibility, or functionality. Mandatory Updates may install automatically, be required before continued use, and may not be declined.

12.4 Breaking Changes. Updates may break Workflows, change file schemas, alter execution behavior, render locally saved Workflow Files incompatible, or require re-authentication. NodeFox is not liable for data loss, Workflow breakage, or business interruption caused by Updates, including background automatic Updates.

12.5 No Obligation. NodeFox has no obligation to: provide Updates; maintain backward compatibility; continue supporting older versions; provide migration tools; maintain any particular feature; or patch vulnerabilities within any timeframe.

---

SECTION 13. VERSION MANAGEMENT

13.1 The Application may offer Update Channels (Stable, Beta, Nightly/Development). Beta and development channels are highly unstable and used at your own risk. NodeFox disclaims all liability for data loss, system instability, or other harm from non-stable channels.

13.2 Version numbering generally follows semantic conventions but this is not guaranteed and does not constitute an operational commitment.

13.3 NodeFox may discontinue older versions at any time. Discontinued versions may cease to function, become incompatible, or lose security updates.

13.4 Downgrading is unsupported and may cause data incompatibility, corruption, or loss. Intentionally rolling back to exploit patched vulnerabilities, bypass licensing, or evade feature restrictions is a material breach.

---

PART V: DATA, TELEMETRY, AND SECRETS

SECTION 14. DATA COLLECTION AND TELEMETRY

14.1 Data collection is governed by the Privacy Policy (/legal/privacy), incorporated by reference.

14.2 Data Collected. The Application may collect: Account and License identifiers; device identifiers; activation status; features used and frequency; session duration; Workflow execution counts; node types used; performance metrics; OS type and version; hardware configuration; Application version; error logs; crash reports (including stack traces, system state, and memory snapshots); and approximate location (country/region from IP).

14.3 Incidental Data Capture. Crash reports and diagnostic data may incidentally capture fragments of User Content, User Secrets, prompts, file paths, or other data that was in active memory at the time of failure. You should avoid embedding secrets in prompts, logs, configurations, or any location from which they may be captured. By opting in to automatic crash reporting, you consent to the secure transmission of such data for debugging purposes.

14.4 What We Do Not Intentionally Collect. For general telemetry purposes, the Application does not intentionally collect the substantive content of your Workflows, prompts, or Outputs, or your User Secrets. This does not apply to: (a) crash reports or diagnostic data, which may incidentally contain such information; (b) data you voluntarily submit via support requests or feedback; or (c) license verification and security telemetry.

14.5 Controls. You may limit certain optional telemetry in settings. License verification, security telemetry, and DRM cannot be disabled. The user is solely responsible for redacting secrets, Personal Data, or confidential information before sharing logs, crash reports, diagnostic bundles, or workspaces with anyone (including NodeFox).

14.6 Telemetry is not used to train general-purpose AI models.

---

SECTION 15. LOCAL STORAGE AND SECURITY

15.1 The Application stores data in OS-appropriate locations (application data, cache, credential storage). Specific paths may vary by OS and version and are described in the Documentation.

15.2 Encryption. User Secrets and credentials may be stored using your OS's secure credential storage. Workflow Files and database files may be encrypted at rest using available encryption mechanisms. No encryption or security measure is perfect, and none is warranted. NodeFox does not guarantee the effectiveness of any encryption, especially in beta software.

15.3 Encryption Limitations. Encryption does not protect against: malware with session access; physical access to unlocked devices; users with administrator privileges; or OS vulnerabilities.

15.4 Your Responsibility. You are responsible for device security, full-disk encryption, strong passwords, OS updates, and malware protection.

15.5 Backup. YOU ARE SOLELY RESPONSIBLE FOR BACKING UP LOCAL DATA. NodeFox is not responsible for data loss, corruption, partial writes, or workspace corruption. Backup, export, and import features are provided "as available," may be incomplete, may be incompatible across versions, and may fail. You are responsible for verifying restores independently.

15.6 Data Portability. The Application may provide export in supported formats. Exported data may or may not be importable depending on formats, versions, and tools. No interoperability is guaranteed.

15.7 Local File Corruption. The Application may cause local file corruption, workspace corruption, partial writes, or data loss, particularly during crashes, power failures, or concurrent access. NodeFox disclaims all liability for local data integrity.

---

SECTION 16. USER SECRETS AND CREDENTIALS

16.1 You may store User Secrets in the Application. User Secrets are stored using available OS credential storage, associated with your user profile, and are not intentionally transmitted to NodeFox servers except: (a) as necessary to execute Workflows you configure; (b) in support bundles you voluntarily submit; or (c) incidentally in crash reports.

16.2 NodeFox implements security measures appropriate to beta software. These are not warranted.

16.3 User Secrets are transmitted to Third-Party Services only when you execute Workflows requiring them, via TLS/HTTPS where available.

16.4 Your Responsibility. You are solely responsible for: security and confidentiality of User Secrets; regular credential rotation; revoking compromised credentials immediately; compliance with Third-Party Service terms; and not storing credentials for unauthorized services.

16.5 Secrets Hygiene. You must not embed User Secrets in prompts, Workflow configurations, logs, DSL, templates, shared workspaces, export bundles, or any location from which they may be captured, shared, or transmitted. Upon any Secrets Exposure Event, you must immediately rotate all potentially affected credentials. NodeFox is not liable for User Secrets exposure resulting from your actions or configurations.

16.6 NodeFox is not responsible for: Third-Party Service actions using your credentials; Third-Party Fees; data processed by Third-Party Services; or Third-Party Service security practices.

16.7 If your device is compromised, lost, or stolen, immediately revoke and rotate all User Secrets.

---

PART VI: AI FEATURES AND AUTONOMOUS ACTIONS

SECTION 17. AI FEATURES AND AUTONOMOUS ACTIONS

17.1 AI Features. The Application enables integration with third-party AI providers (such as OpenAI, Anthropic, Google, and others) and may include NodeFox's own AI-assisted features (Suggest, DSL generation, AI-generated Networks, code completion, and similar). NodeFox is a workflow orchestration platform, not an AI provider.

17.2 Your API Keys. To use third-party AI Features, you must provide your own API keys. You are responsible for obtaining keys in compliance with provider terms, paying all usage fees, configuring limits, securing keys, and complying with provider terms.

17.3 Data Transmission. When Workflows execute AI Features, your Input Data is transmitted to the third-party AI provider or processed by NodeFox AI features. Data roles and responsibilities are governed by the Privacy Policy and DPA.

17.4 Third-party AI providers may use your data to train their models unless you configure opt-outs under their terms. NodeFox cannot configure opt-outs on your behalf.

17.5 AI Outputs may be inaccurate, incomplete, biased, offensive, harmful, factually incorrect, hallucinated, or fabricated. NodeFox does not warrant accuracy, quality, safety, legality, or fitness. You are solely responsible for reviewing and validating all Outputs.

17.6 Autonomous Actions. The Application allows Workflows to take autonomous actions: executing code, making API calls, sending messages, modifying files or databases, initiating transactions, and interacting with external systems.

17.7 Autonomous actions execute without per-action human approval. Errors or unexpected behavior may cause unintended consequences, financial loss, data corruption, system damage, or harm to third parties.

17.8 You are solely responsible for: safe Workflow design; implementing safeguards; testing before use; monitoring autonomous actions; all consequences; and compliance with applicable laws.

17.9 Recommended Safeguards. For autonomous actions, you should implement: human-in-the-loop approval for high-risk actions; rate limits and spending caps; comprehensive logging; rollback capabilities; sandbox testing; and monitoring. These are recommendations; their adequacy is your responsibility.

17.10 Logging and Traceability. The Application may provide logging capabilities. NodeFox does not guarantee versioning, audit trails, or traceability. If your use case requires traceability for regulatory compliance, you are solely responsible for enabling logging, preserving logs for required retention periods, implementing tamper-evident storage, and maintaining compliance documentation.

17.11 Human Deployer Accountability. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, YOU ACKNOWLEDGE THAT YOU, AS THE HUMAN DEPLOYER OF ANY WORKFLOW OR AI SYSTEM, BEAR FULL LEGAL ACCOUNTABILITY FOR ALL OUTCOMES AS IF YOU PERSONALLY PERFORMED EACH ACTION. YOU MAY NOT ASSERT AI AUTONOMY, AGENT INDEPENDENCE, EMERGENT BEHAVIOR, UNFORESEEABLE AI DECISIONS, OR LACK OF HUMAN CONTROL AS A DEFENSE.

17.12 Watermarking Compliance. Where AI-generated content includes watermarks, provenance indicators, content credentials, or authenticity markers as required by applicable law, you must maintain them. Failure is a material breach. NodeFox may suspend or revoke access; NodeFox may, but is not obligated to, allow a cure period.

17.13 Runaway Execution and Cost — CRITICAL. Workflows may self-trigger, retry, branch, loop, fan out, or otherwise execute beyond intended scope. NodeFox does not guarantee detection of unbounded loops, the ability to stop executions immediately, or prevention of Third-Party charges once requests are dispatched or queued. YOU ARE SOLELY RESPONSIBLE FOR ALL THIRD-PARTY FEES, INCLUDING FEES INCURRED AFTER A STOP REQUEST (due to In-flight Actions, queued work, or delayed termination). NodeFox may throttle or terminate executions without liability, but has no obligation to do so. Implement your own spending caps, iteration limits, timeouts, backoff, and circuit breakers.

17.14 User Code and Sandbox. If the Application supports code execution (Code nodes, Script nodes, DSL), NodeFox does not review, audit, scan, or validate User Code. No sandbox provides a security guarantee. NodeFox does not warrant isolation and is not liable for escape, exfiltration, SSRF, or other security failures originating from User Code. NodeFox may disable scripting, networking, or execution features remotely without liability.

17.15 Outbound Requests. User Code and Workflows may make Outbound Requests. You are solely responsible for endpoints, authentication, scopes, payloads, headers, and legality. NodeFox does not sanitize, validate, or restrict Outbound Requests (except as may be provided by optional platform controls).

---

PART VII: WORKFLOW EXECUTION AND CONNECTIVITY

SECTION 18. WORKFLOW EXECUTION

18.1 Local Execution. Workflows may execute locally using your device's resources (CPU, memory, disk, GPU). Local execution may interact with your local environment (PATH, development tools, package managers, system binaries). NodeFox is not liable for corruption, modification, or disruption of your local software, development environments, or system configuration.

18.2 Cloud Execution. Workflows may execute on NodeFox cloud infrastructure (requiring connectivity, subject to Subscription limits).

18.3 Hybrid. Workflows may combine local and cloud execution.

18.4 Resource Consumption. Resource-intensive Workflows may slow your device, consume memory, use disk space, and impact other applications.

18.5 Execution Limits. Subscription Tiers may impose limits on execution count, concurrency, duration, resources, and API calls.

18.6 Scheduled and Background Execution. Scheduled Workflows require the Application to be running. Background Workflows continue when the main window is closed, may be affected by power settings, and may be interrupted by system events. Cloud-dispatched executions may continue even if the desktop UI closes.

18.7 Throttling and Termination. NodeFox may throttle, queue, or terminate Workflow executions at any time without liability. There is no guarantee of completion. NodeFox has no obligation to restore interrupted executions.

18.8 Execution Semantics. Workflow executions may be retried, duplicated, executed out of order, partially executed, or time out. Stop/pause commands are best-effort and may not halt immediately. In-flight Actions may complete. Queued work may execute after the UI closes or crashes. Charges may accrue after a stop request. You are responsible for idempotency, error handling, monitoring, and cost controls. NodeFox does not guarantee exactly-once execution, atomicity across nodes, or deterministic timing.

---

SECTION 19. CONNECTIVITY AND OFFLINE

19.1 Network connectivity is required for: Account authentication, License verification, sync, cloud execution, AI Features, Updates, and Marketplace access.

19.2 When offline: you may edit local Workflows, execute local-only Workflows, view cached content, and access local data. You cannot sync, use cloud features, use AI Features, verify License, or receive Updates.

19.3 Grace Period. If connectivity is unavailable, the Application may continue with reduced capabilities for a discretionary grace period. No specific grace period duration is guaranteed.

19.4 Sync. Changes made offline are queued for sync when connectivity restores. Sync conflicts may be resolved under then-current conflict policies, which may result in overwrites or data loss. NodeFox disclaims all liability for data destruction caused by sync resolutions.

19.5 Local Port Binding. The Application may bind to local network ports or launch local servers. This may trigger corporate firewalls, antivirus, or IDS. You are responsible for configuring your local network to accommodate the Application. NodeFox disclaims liability for unauthorized access originating from other devices exploiting local ports.

---

SECTION 20. INTEGRATION WITH SERVICES

20.1 The Application integrates with NodeFox cloud Services (Account, sync, cloud execution, Marketplace, collaboration, usage tracking).

20.2 When sync is enabled, data may be synchronized to the cloud. NodeFox does not warrant encryption of synced data; see Privacy Policy. You may disable sync, in which case data exists only locally.

20.3 Use of integrated Services is subject to the Terms of Service. Marketplace access is subject to Marketplace Terms.

---

PART VIII: THIRD-PARTY COMPONENTS AND DISCLAIMERS

SECTION 21. THIRD-PARTY COMPONENTS

21.1 The Application includes Third-Party Components licensed under their own terms. Your use is subject to those terms. Where third-party terms grant additional rights or impose obligations conflicting with this EULA, those terms control solely for the relevant component.

21.2 Attribution notices are in the Application's "About" dialog, Documentation, or accompanying files. Source code for components requiring availability is available upon written request to legal@nodefox.ai for three years from the date you obtained the Application, for a nominal distribution fee.

21.3 Third-Party Components are provided "AS IS" without warranty from NodeFox. NodeFox does not provide support for them, does not guarantee security patches within any timeframe, and is not liable for bugs, security vulnerabilities, supply-chain compromises, or incompatibilities.

21.4 The Application may render web content, frames, or embedded media from external sources. Such content may include trackers, malicious scripts, or other harmful elements. NodeFox does not sanitize third-party content. You assume risk for content you load.

---

SECTION 22. DISCLAIMER OF WARRANTIES

22.1 THE APPLICATION IS PROVIDED "AS IS" AND "AS AVAILABLE" WITHOUT WARRANTIES OF ANY KIND. TO THE FULLEST EXTENT PERMITTED BY LAW, NODEFOX DISCLAIMS ALL WARRANTIES, INCLUDING MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, NON-INFRINGEMENT, ACCURACY, QUALITY, RESULTS, UNINTERRUPTED OPERATION, ERROR-FREE PERFORMANCE, SECURITY, COMPATIBILITY, DATA INTEGRITY, AND VIRUS/MALWARE-FREE OPERATION.

22.2 THE APPLICATION IS IN BETA AND MAY CONTAIN BUGS, ERRORS, INCOMPLETE FEATURES, OR INSTABILITIES. BETA SOFTWARE IS PROVIDED WITHOUT WARRANTY. THE BETA STATUS MAY CONTINUE INDEFINITELY. YOU USE THE APPLICATION AT YOUR OWN RISK.

22.3 AI OUTPUTS MAY BE INACCURATE, INCOMPLETE, BIASED, MISLEADING, OFFENSIVE, HARMFUL, OR FABRICATED. NO WARRANTY REGARDING ACCURACY, QUALITY, SAFETY, LEGALITY, OR FITNESS.

22.4 IF YOU CONFIGURE AUTONOMOUS ACTIONS, YOU DO SO AT YOUR OWN RISK. NODEFOX IS NOT RESPONSIBLE FOR UNINTENDED CONSEQUENCES.

22.5 NODEFOX DISCLAIMS LIABILITY FOR THIRD-PARTY COMPONENTS, THIRD-PARTY SERVICES, AND THIRD-PARTY AI PROVIDERS.

22.6 THE APPLICATION MAY CAUSE DATA LOSS, CORRUPTION, OR UNAVAILABILITY. YOU ARE RESPONSIBLE FOR BACKUPS.

22.7 NODEFOX DOES NOT WARRANT NETWORK RELIABILITY OR AVAILABILITY.

22.8 NODEFOX DOES NOT WARRANT THAT THE SANDBOX, ENCRYPTION, LOCAL STORAGE, OR ANY SECURITY MECHANISM IS EFFECTIVE AGAINST ANY PARTICULAR THREAT.

22.9 NODEFOX IS NOT AN ESCROW AGENT, CUSTODIAN, OR FIDUCIARY OF YOUR DATA, CREDENTIALS, FUNDS, OR RECORDS. THE APPLICATION IS A TOOL THAT TRANSMITS AND PROCESSES DATA AT YOUR DIRECTION.

22.10 SOME JURISDICTIONS DO NOT ALLOW DISCLAIMER OF CERTAIN WARRANTIES. IN SUCH JURISDICTIONS, WARRANTIES ARE LIMITED TO THE MAXIMUM EXTENT PERMITTED BY LAW. IF YOU ARE A CONSUMER IN AUSTRALIA, THE APPLICATION COMES WITH GUARANTEES THAT CANNOT BE EXCLUDED UNDER THE AUSTRALIAN CONSUMER LAW.

---

SECTION 23. LIMITATION OF LIABILITY

23.1 The Terms of Service (Section 40) contain the controlling limitation of liability provisions, which apply to Application-related claims. To the extent the Terms of Service limitation of liability applies, it is incorporated here by reference and governs.

23.2 Without limiting the foregoing: TO THE FULLEST EXTENT PERMITTED BY LAW, THE NODEFOX PARTIES SHALL NOT BE LIABLE FOR ANY INDIRECT, INCIDENTAL, CONSEQUENTIAL, SPECIAL, EXEMPLARY, OR PUNITIVE DAMAGES, INCLUDING LOST PROFITS, LOSS OF DATA, BUSINESS INTERRUPTION, COST OF SUBSTITUTES, DAMAGES FROM AUTONOMOUS ACTIONS OR AI OUTPUTS, DAMAGES FROM THIRD-PARTY COMPONENTS OR SERVICES, OR DAMAGES BEYOND NODEFOX'S REASONABLE CONTROL, REGARDLESS OF THEORY AND EVEN IF ADVISED OF THE POSSIBILITY.

23.3 TOTAL AGGREGATE LIABILITY SHALL NOT EXCEED NODEFOX PLATFORM FEES PAID IN THE TWELVE (12) MONTHS PRECEDING THE CLAIM. FOR FREE/TRIAL USERS: ZERO DOLLARS ($0).

23.4 NODEFOX IS NOT LIABLE FOR THIRD-PARTY FEES.

23.5 THESE LIMITATIONS APPLY EVEN IF ANY LIMITED REMEDY FAILS OF ITS ESSENTIAL PURPOSE AND REFLECT A REASONABLE ALLOCATION OF RISK FUNDAMENTAL TO THE BARGAIN.

23.6 Exceptions. Limitations do not apply to: NodeFox's gross negligence or willful misconduct; death or personal injury from NodeFox's negligence; fraud; your payment obligations; your indemnification obligations; or liability that cannot be limited under mandatory law.

23.7 Sole Remedy. Except as provided in Section 23.6, your sole and exclusive remedy for any claim is limited to the damages recoverable under Section 23.3.

---

SECTION 24. INDEMNIFICATION

24.1 You agree to indemnify, defend, and hold harmless NodeFox and the NodeFox Parties from claims arising from: (a) your use of the Application; (b) User Content and Outputs; (c) violation of this EULA, Terms of Service, or law; (d) violation of third-party AI provider terms; (e) AI Outputs; (f) autonomous Workflow actions; (g) use of Third-Party Services; (h) User Secrets and credentials; (i) your negligence, misconduct, or fraud; (j) IP claims regarding your content; (k) failure to implement required human oversight; (l) failure to maintain required watermarks; (m) User Code that causes harm to NodeFox, other users, or third parties; (n) data protection violations; (o) regulatory inquiries caused by your conduct; and (p) incident response costs incurred due to your actions or configurations.

24.2 Procedure. NodeFox may provide notice of claims (failure to provide notice does not relieve your obligation except to the extent materially prejudiced). NodeFox may assume exclusive control of defense and settlement at your expense. You will cooperate fully. No settlement admitting NodeFox liability without consent.

24.3 Indemnification survives termination and is not subject to the liability caps in Section 23, except where unlimited indemnification is prohibited under mandatory applicable law.

---

PART IX: BETA AND SUPPORT

SECTION 25. BETA STATUS

25.1 The Application is beta software under active development. The beta period may continue indefinitely.

25.2 The Application may: contain bugs; crash unexpectedly; cause data loss; have performance issues; change significantly between versions; have features added/modified/removed without notice; have incomplete documentation; and have compatibility issues.

25.3 You acknowledge the inherent risks of beta software.

25.4 Not suitable for: production workloads; mission-critical applications; situations where failure could cause harm; environments requiring guaranteed reliability; or use cases requiring certified software.

25.5 Any ambiguity regarding capabilities, performance, reliability, or fitness shall be interpreted against any expectation of production-grade software.

---

SECTION 26. SUPPORT

26.1 NodeFox may provide support at its discretion. No support is guaranteed for any Subscription Tier.

26.2 Free Tier users receive no guaranteed support. Self-service documentation may be available at https://docs.nodefox.ai.

26.3 Paid Subscriptions may include access to additional support channels as described in plan details. No SLA, response time, resolution time, or outcome is guaranteed.

26.4 Enterprise support requires a separate Enterprise Agreement.

26.5 Support, where provided, does not cover Third-Party Components, Third-Party Services, modified Application versions, unsupported platforms, on-site support, training, consulting, or custom development.

26.6 Statements by support personnel do not constitute binding commitments, EULA modifications, product roadmap representations, or professional advice.

26.7 No statement regarding Updates, support, security patches, or feature maintenance implies an obligation to provide any of these within any timeframe.

---

PART X: TERM AND TERMINATION

SECTION 27. TERM AND TERMINATION

27.1 This EULA is effective from first download, installation, or use and continues until terminated.

27.2 By You. Terminate by uninstalling, destroying all copies, ceasing use, and deleting backups.

27.3 By NodeFox. NodeFox may terminate at any time, with or without notice, for: EULA or Terms of Service violation; Application discontinuation; legal requirement; Account suspension or termination; Subscription expiration; security risk; suspected fraud or abuse; or any business reason.

27.4 Automatic. This EULA automatically terminates if you violate Section 4, the Terms of Service, or become subject to sanctions or export restrictions.

---

SECTION 28. EFFECT OF TERMINATION

28.1 Upon termination: all licenses terminate immediately; you must cease use and uninstall; you must delete backups; obligations incurred before termination survive; NodeFox may remotely disable the Application.

28.2 Local Application Data remains on your device until you delete it. You may export Workflow Files before uninstalling (in supported formats). Cloud data is subject to the Terms of Service and Privacy Policy and may be deleted per retention policies. NodeFox has no obligation to provide post-termination access or export windows for EULA-terminated users; post-termination data export rights are governed by the Terms of Service.

28.3 Survival. License Restrictions (§4), IP (§5), Ownership (§6), No AI Training (§7), Feedback (§8), Disclaimers (§22), Limitation of Liability (§23), Indemnification (§24), Export Compliance (§32), Governing Law/Disputes (§§34–36), and any provisions that by nature should survive.

28.4 NodeFox is not liable for termination.

---

SECTION 29. UNINSTALLATION

29.1 Standard uninstallation removes Application files, shortcuts, file associations, and stops Background Processes.

29.2 Standard uninstallation may not remove all data. Application Data directories, cached content, log files, credential storage entries, and registry/preference files may remain. You acknowledge this and waive claims based on residual files remaining after uninstallation.

29.3 For complete removal: uninstall; manually delete Application Data directories (see Documentation for paths); remove credentials from OS credential storage; and clear any associated browser data.

29.4 Uninstallation does not delete cloud-synced data. Cloud data deletion is governed by the Terms of Service and Privacy Policy.

---

PART XI: SUBSCRIPTION AND DEPLOYMENT

SECTION 30. SUBSCRIPTION TIERS

30.1 Features vary by Subscription Tier. NodeFox may modify tier features at any time, including adding, modifying, removing features, or changing limits.

30.2 Downgrading may cause loss of access to features and data exceeding lower-tier limits.

---

SECTION 31. ENTERPRISE DEPLOYMENT

31.1 Enterprise customers may, where available and as agreed in a separate Enterprise Agreement, have access to deployment options such as silent installation, enterprise packages, MDM support, centralized configuration, and license management. All enterprise deployment features are available only to the extent expressly agreed in the Enterprise Agreement. No feature list here constitutes a delivery obligation.

31.2 Enterprise administrators may deploy, configure, and manage the Application on managed devices per the Enterprise Agreement.

---

SECTION 32. VIRTUAL MACHINES AND REMOTE ACCESS

32.1 You may install in VM environments subject to this EULA. Each VM installation counts toward limits. VMs must meet System Requirements. Performance may vary. You may not clone or snapshot active session tokens or License Keys across multiple VM instances; you are responsible for duplicate seat costs from mass-deployment of activated states.

32.2 The Application is not designed for containerized deployment (Docker). Container use is unsupported.

32.3 You may access via remote desktop for your own use. Multi-user terminal services or cloud desktop use requires appropriate licensing (contact sales@nodefox.ai).

32.4 Portable Media. The Application is designed for installation on secure, persistent local drives. Use from removable media on shared or untrusted devices is at your own risk. NodeFox is not liable for credential theft or data capture by untrusted host devices.

---

SECTION 33. AUDIT

33.1 NodeFox may audit compliance through license verification mechanisms, usage data, and information requests.

33.2 Upon reasonable request, you agree to provide accurate information regarding installations, users, Subscription Tier, and feature use.

33.3 If an audit reveals unauthorized use, you must cure within the timeframe specified by NodeFox, pay for additional licenses owed, and reimburse NodeFox's reasonable audit costs for material violations.

---

PART XII: COMPLIANCE

SECTION 34. EXPORT COMPLIANCE

34.1 The Application may be subject to U.S. export control laws (EAR, OFAC sanctions) and other jurisdictions' export laws.

34.2 You may not download, install, export, re-export, or transfer the Application to: any comprehensively sanctioned jurisdiction (as designated by OFAC from time to time); any person on any restricted party list; any prohibited end-use (including WMD development); or for any purpose prohibited by export law. This applies to physical travel: you may not transport devices containing the Application into sanctioned jurisdictions.

34.3 You represent that you are not located in a sanctioned country, not on any restricted party list, and not acting on behalf of a prohibited person.

34.4 NodeFox may restrict access from sanctioned jurisdictions and may immediately terminate Accounts transmitting from sanctioned IP addresses to comply with law. NodeFox is not liable for data loss from compliance-driven termination.

---

SECTION 35. DISPUTE RESOLUTION

35.1 The Terms of Service (Sections 47–51) contain the controlling dispute resolution, arbitration, governing law, and limitation period provisions, which apply to disputes arising from or related to this EULA and the Application. Those provisions are incorporated by reference and govern.

35.2 Governing Law. Delaware law governs. The CISG does not apply. Consumer protection savings clauses in the Terms of Service apply.

35.3 Equitable Relief. NodeFox may seek injunctive relief in any court for IP or confidentiality matters without bond.

---

SECTION 36. GOVERNMENT USERS

36.1 The Application is a "commercial item" under 48 C.F.R. § 2.101. Government users receive only the rights in this EULA, consistent with applicable FAR and DFARS provisions.

---

PART XIII: GENERAL PROVISIONS

SECTION 37. LOCAL ENVIRONMENT AND DEVICE DISCLAIMERS

37.1 Corporate Controls. Corporate device controls (MDM, EDR, antivirus, DLP, browser policies, group policies, OS-level restrictions) may block, alter, or break Application functionality. NodeFox has no liability for failures, data loss, or degraded performance caused by your or your organization's device management policies.

37.2 Third-Party Software Conflicts. The Application may conflict with other software on your device. NodeFox is not liable for conflicts, crashes, or data loss arising from software interactions on your device.

---

SECTION 38. FORCE MAJEURE

38.1 The force majeure provisions in the Terms of Service (Section 40.8) apply to this EULA and are incorporated by reference. Neither party is liable for failure due to causes beyond reasonable control.

---

SECTION 39. ASSIGNMENT

39.1 You may not assign, transfer, delegate, or sublicense this EULA without NodeFox's prior written consent. Unauthorized assignment is void.

39.2 NodeFox may freely assign, including in connection with mergers, acquisitions, or asset sales, without notice or consent.

---

SECTION 40. SEVERABILITY

40.1 If any provision is held invalid, it shall be modified to the minimum extent necessary or severed. Remaining provisions continue in full force.

---

SECTION 41. NO WAIVER

41.1 Failure to enforce any provision does not waive it. Waivers must be written. Remedies are cumulative.

---

SECTION 42. NOTICES

42.1 To NodeFox. Legal notices to: NodeFox LLC, PO Box 1667, Ross, CA 94957, United States. Email: legal@nodefox.ai. Notices are effective upon receipt.

42.2 To You. Via email to your Account address, posting on the website, or through the Application. Email notices are deemed effective when sent. Application/website notices are effective upon posting. To the extent permitted by law, you bear the risk of delivery failures to outdated contact information.

---

SECTION 43. MODIFICATIONS TO EULA

43.1 NodeFox may modify this EULA at any time. For material changes, NodeFox will require affirmative in-app acceptance before continued use where technically feasible, or provide notice via email or prominent Application notice. Continued use after modifications become effective constitutes acceptance. If you disagree, stop using the Application.

---

SECTION 44. ENTIRE AGREEMENT

44.1 This EULA, the Terms of Service, Privacy Policy, and incorporated policies constitute the entire agreement regarding the Application. Enterprise Agreements control to the extent of conflict. No course of dealing modifies this EULA.

---

SECTION 45. CONSTRUCTION

45.1 Headings are for convenience. "Including" means "without limitation." "May" is permissive; "must" and "shall" are mandatory. "Days" means calendar days. No drafting presumption applies.

---

SECTION 46. ACCESSIBILITY

46.1 NodeFox endeavors to follow accessibility guidelines where practicable. No compliance with any accessibility standard is warranted. Contact accessibility@nodefox.ai with feedback.

---

SECTION 47. CONTACT

Mailing Address: NodeFox LLC, PO Box 1667, Ross, CA 94957, United States

Website: https://www.nodefox.ai

---

SECTION 48. ACKNOWLEDGMENT

BY DOWNLOADING, INSTALLING, OR USING THE APPLICATION, YOU ACKNOWLEDGE THAT:

(A) YOU HAVE READ AND UNDERSTOOD THIS EULA; (B) YOU AGREE TO BE BOUND BY ALL TERMS; (C) YOU HAVE AUTHORITY TO ACCEPT (FOR YOURSELF OR YOUR ORGANIZATION); (D) THE APPLICATION IS IN BETA AND MAY CONTAIN BUGS OR INCOMPLETE FEATURES; (E) DATA LOSS MAY OCCUR AND YOU ARE RESPONSIBLE FOR BACKUPS; (F) YOU UNDERSTAND THE RISKS OF AI FEATURES AND AUTONOMOUS ACTIONS; (G) YOU BEAR FULL LEGAL ACCOUNTABILITY AS HUMAN DEPLOYER; (H) STOP/PAUSE IS BEST-EFFORT AND CHARGES MAY ACCRUE AFTER STOP REQUESTS; (I) YOU HAVE READ THE ARBITRATION AGREEMENT AND CLASS ACTION WAIVER IN THE TERMS OF SERVICE; (J) YOU HAVE HAD THE OPPORTUNITY TO CONSULT LEGAL COUNSEL; AND (K) THIS IS A BINDING LEGAL AGREEMENT.

---

THIRD-PARTY COMPONENT NOTICES

The Application includes Third-Party Components under various licenses. Attribution notices are in the Application's "About" dialog, Documentation, or accompanying files. Conflicting third-party license terms control solely for the relevant component. Source code requiring availability is available upon written request to legal@nodefox.ai for three years, for a nominal distribution fee.

---

END OF END USER LICENSE AGREEMENT

© 2025–2026 NodeFox LLC. All rights reserved.

NodeFox LLC | PO Box 1667, Ross, CA 94957, United States | https://www.nodefox.ai