Blunom Inc. Terms of Service

1.01. Parties and Scope: These Terms of Service ("Terms") are entered into by and between Blunom Inc. ("Blunom," "we," "us," or "our") and the entity or individual accessing our systems ("Customer," "you," or "your"). These Terms govern your access to and use of the website located at https://blunom.ai, our waitlist, and our secure sovereign AI orchestration control plane, policy engines, and low-code studio interfaces, collectively referred to as the "Service."

1.02. Authority and Age Limit: If you accept these Terms on behalf of a company or other legal entity, you represent and warrant that you possess the full legal authority to bind that entity and its Affiliates to these conditions. "Affiliate" means any entity that controls, is controlled by, or is under common control with a party, where "control" means ownership of more than 50% of the voting equity. The Service is intended strictly for users 18 years of age or older.

1.03. Procurement Channels: These Terms govern your use of the Service regardless of whether you procure the platform directly from Blunom via a Blunom-executed commercial document, each referred to as an "Order Form," or indirectly through an authorized reseller, distributor, system integrator, or managed service provider, each referred to as an "Authorized Partner."

2.01. General Service Definition: Blunom provides an AI orchestration platform allowing users to securely govern, deploy, monitor, and track the token resource performance, referred to as "TokenOps," of AI agents.

2.02. SaaS Multi-Tenant Deployment: Depending on the explicit configuration selected within the applicable Order Form or Authorized Partner agreement, Blunom may provide the Service on a shared cloud infrastructure architecture hosted, managed, secured, and maintained by Blunom.

2.03. SaaS Single-Tenant Deployment: Depending on the explicit configuration selected within the applicable Order Form or Authorized Partner agreement, Blunom may provide the Service on dedicated, structurally isolated cloud infrastructure provisions allocated exclusively to Customer, hosted and managed by Blunom.

2.04. Customer/Partner Self-Hosted Deployment: Depending on the explicit configuration selected within the applicable Order Form or Authorized Partner agreement, Blunom may license the Service to Customer or partner for direct installation, operation, and execution within Customer's own Virtual Private Cloud (VPC), segregated local endpoints, or private cloud infrastructure.

2.05. Organization ID & Licensing Anchoring: Regardless of the chosen Deployment Option, and irrespective of whether the platform is sold, implemented, or configured directly by Blunom or indirectly via an Authorized Partner, every unique Customer tenant environment strictly requires the provisioning of a unique, Blunom-issued corporate organization identifier, referred to as an "Organization ID." All active software licenses, seat entitlements, feature permissions, and TokenOps financial metrics are tied unalterably to this unique Organization ID. Customer shall not attempt to duplicate, mask, split, alter, or circumvent an Organization ID to deploy un-entitled platform instances or bypass verified licensing thresholds.

2.06. Anti-Reselling & Multi-Tenant Pooling Restrictions: Each provisioned Organization ID is strictly single-entity, localized, and non-transferable. Customer is expressly prohibited from utilizing a single Organization ID to host, pool, segment, lease, sub-license, or otherwise resell the Service's capabilities to distinct external third-party customers, separate commercial entities, or un-affiliated organizations. Any downstream customer, external client, or distinct legal entity requiring the governance, orchestration, or utilization of Blunom’s orchestration plane must be provisioned with its own separate, independent Organization ID through an authorized Blunom procurement channel.

2.07. Evaluation Frameworks: We may designate certain features, modules, or early-access deployment paths as "Public Preview," "Beta," or "Evaluation Services." Notwithstanding anything to the contrary in these Terms, all Evaluation Services are provided strictly "as-is" and "as-available" without any express or implied warranties, service level agreements (SLAs), uptime commitments, or indemnities of any kind. Blunom reserves the right to modify, suspend, or terminate evaluation paths at any time in its sole discretion without liability.

2.08. Tenant Infrastructure & Telemetry Obligations: For all SaaS Single-Tenant and Customer Self-Hosted Deployments: (a) Customer remains solely responsible for procuring, configuration-hardening, and funding any underlying cloud hosting environments, databases, or compute resource frameworks specified as customer-managed, (b) Customer shall grant Blunom secure, automated, non-invasive cryptographic back-channels or API endpoints solely to transmit encrypted licensing verification data, active user seat counts, core system error metrics, and TokenOps utilization data attached to Customer's unique Organization ID, and (c) for Customer Self-Hosted Deployments, upon expiration or termination of these Terms, Customer shall immediately delete, un-install, and completely purge all binaries, software keys, containers, and deployed instances of the Blunom platform from its private tenants.

3.01. Authentication Requirements: To access the platform's orchestration engines, you must authenticate securely via approved federated identity single sign-on (SSO) solutions, such as Google OAuth.

3.02. Authorized Users: Customer will limit access to the Service strictly to its and its Affiliates' employees, designated consultants, and independent contractors acting solely on Customer's behalf, referred to as "Authorized Users."

3.03. Services Partners (SIs/MSPs): If Customer authorizes a third-party system integrator, global system integrator (GSI), or managed service provider (MSP) to access, configure, manage, or deploy agents within Customer's workspace, such third party shall be legally deemed an Authorized User hereunder. Customer remains fully liable and responsible for all actions, prompt injections, routing configurations, policy overrides, or resource costs executed by such third parties within Customer's environment.

3.04. Account Liability: Customer is entirely responsible for maintaining the strict confidentiality of access credentials, API keys, and workspace routes, and remains fully liable for all automated and human executions occurring within its workspace. Customer will notify Blunom immediately at security@blunom.ai upon discovery of any credential compromise or unauthorized access paths.

4.01. Customer Input: Customer retains all right, title, and ownership interest in any proprietary data, documentation, systems logic, or institutional knowledge assets ingested or submitted into the Service, referred to as "Input." Customer grants Blunom a limited, worldwide, non-exclusive, royalty-free license to host, process, and transmit Input solely to provide, secure, maintain, and troubleshoot the Service for Customer's active workspaces.

4.02. Agent Output: As between the parties, and subject to Customer's full compliance with these Terms, Customer owns all execution paths, structured workflow charts, configurations, and logs generated specifically for Customer by autonomous agents via the platform, referred to as "Output." Customer acknowledges that due to the structural nature of generative AI, Outputs may not be structurally unique across the platform, and other users may generate similar routing charts or system behaviors.

4.03. Platform Proprietary Rights: Blunom and its licensors retain all right, title, and interest in and to our proprietary orchestration architecture, low-code studio interfaces, core software frameworks, Policy Engines, underlying routing algorithms, and all associated intellectual property. No implied licenses are granted hereunder.

4.04. Aggregated Data & Telemetry Limits: Customer explicitly grants Blunom the right to compile, anonymize, and aggregate structural system telemetry, latency metrics, orchestration error paths, and resource usage statistics derived from the platform's operations to generate "Aggregated Data." Blunom may use Aggregated Data exclusively to develop, test, optimize, and maintain its orchestration routing logic, security layers, and platform features. For the avoidance of doubt, Aggregated Data shall strictly consist of operational metadata and shall never contain, include, or expose the underlying text, semantic payloads, source code, or proprietary content of any Customer Input or Agent Output.

4.05. Feedback Assignment & Innovation Safeguards: If Customer, its Affiliates, or any Authorized Users transmit, submit, or otherwise provide Blunom with any operational suggestions, feature requests, structural ideas, optimization methodologies, or performance enhancement feedback regarding the Service, referred to as "Feedback," Customer hereby irrevocably assigns to Blunom all right, title, and intellectual property interest worldwide in and to such Feedback. This assignment universally applies to all Feedback derived from any individual, relationship, association, or commercial entity whatsoever, including without limitation, partners, design partners, system integrators, global system integrators, managed service providers, distributors, cloud service providers, hardware providers, and infrastructure providers. Blunom shall possess the absolute, perpetual, and unrestricted right to use, implement, modify, commercialize, and fully exploit such Feedback in any manner it deems appropriate, including but not limited to integration within Blunom's core orchestration architecture, low-code studio interfaces, Policy Engines, and TokenOps cost-management metrics, without any restriction, accounting, or financial compensation to Customer. Blunom will treat all received Feedback as strictly non-confidential and non-proprietary.

5.01. Prohibited Platform Usage: Customer represents and warrants that it will not use Blunom's control plane to build, host, or orchestrate autonomous agents designed to, or engage in activities that: (a) Violate local, national, or global laws, regulations, or international trade compliance paradigms, (b) Harvest, redact, or process personally identifiable information (PII) or sensitive biometric identifiers without valid legal authorization, (c) Deploy malicious scripts, automated vulnerability scanning networks, or digital denial-of-service (DDoS) pathways, (d) Infringe upon the intellectual property, trade secrets, or data sovereignty parameters of any third party, or (e) Circumvent financial optimization guardrails or intentionally run counter to configured TokenOps budget thresholds.

5.02. Architectural and Competitive Restrictions: Customer and its Authorized Users shall not modify, translate, decompile, reverse engineer, or attempt to extract the source code or underlying logic of the Blunom orchestration engine. Customer and its Authorized Users shall not use the Service, Input, or Output to build, train, optimize, or improve a product or service that competes directly or indirectly with Blunom.

5.03. Guardrail Evasion and Prompt Exploits: Customer and its Authorized Users shall not attempt to bypass safety filters, manipulate agent instructions to override enterprise platform policies, or execute prompt-injection attacks designed to undermine the platform's native security guardrails.

5.04. High-Risk Automated Decisions: Customer and its Authorized Users shall not deploy autonomous agents to execute unmonitored automated decision-making processes carrying critical legal or material impacts, such as financial credit scoring, automated employment screening, or live professional legal or medical advice, without explicit human-in-the-loop review and verification to maintain alignment with global AI regulatory standards, including the EU AI Act.

6.01. External Provider Limitations: The platform natively coordinates with third-party application programming interfaces (APIs), hosted model providers, and foundational Language Models (LLMs) managed under separate agreements between Customer and those respective providers. Blunom exercises no control over, and assumes no liability for, the availability, uptime, data compliance, or structural performance variations of any external third-party endpoints.

6.02. Downstream Blockage & Emergency Suspension: Customer acknowledges that the Service relies fundamentally on interoperability with external foundational model providers. If Customer’s or its Services Partner’s operational utilization of autonomous agents generates system behavior that violates a downstream provider's acceptable use policies, or otherwise threatens to cause the suspension, throttling, or termination of Blunom’s master API credentials or platform access infrastructure, Blunom retains the absolute right to immediately suspend Customer's workspace access without prior notice and without liability, pending a technical audit of the agentic routing paths.

6.03. AI Technology Accuracy Warning: Evolving AI technologies and autonomous agents are fundamentally subject to hallucinations, reasoning errors, and algorithmic biases. Blunom does not warrant or guarantee the accuracy, completeness, or real-world factuality of any agent Output. Customer must exercise independent judgment and maintain rigorous human oversight to monitor and verify all agent-driven behaviors and outcomes.

6.04. High-Risk Deployments Disclaimer: The Service is not engineered for use in high-risk environments where system failures or erroneous agent actions could directly result in death, personal injury, structural physical damage, or catastrophic environmental ruin.

7.01. Decoupling of Commercial Terms: If Customer procures access to the Service through an Authorized Partner, such as a GSI, MSP, reseller, or distributor, the commercial billing, pricing, payment structure, and tax reconciliation terms set forth in Section 8 of these Terms shall not apply directly to Customer. Instead, Customer's payment obligations, billing frequencies, and pricing tiers shall be exclusively governed by the separate commercial agreement executed between Customer and the applicable Authorized Partner.

7.02. Partner Default & Workspace Suspension: Customer acknowledges and agrees that Blunom’s provision of the platform to Customer is strictly contingent upon Blunom receiving timely, full, and uninterrupted payment of the corresponding platform fees from the Authorized Partner. If the Authorized Partner fails to pay Blunom for any reason, Blunom retains the absolute right, in its sole discretion and without liability to Customer, to suspend or terminate platform access for Customer's workspaces upon written notice. Customer's sole recourse in such an event shall be directly against the defaulting Authorized Partner.

7.03. No Modification of Terms: Customer explicitly agrees that no Authorized Partner possesses the legal authority, agency, or capacity to alter, amend, expand, or delete any provision of these Terms. No representation, custom service level commitment, specialized liability expansion, or supplemental product warranty provided to Customer by an Authorized Partner shall be binding upon Blunom.

8.01. Billing & Taxes: If Customer purchases paid subscriptions or enterprise tiers directly from Blunom via a Blunom-executed Order Form, Customer will maintain accurate billing details and payment methods. All stated fees are exclusive of sales, use, value-added (VAT), or withholding taxes, which are the sole responsibility of Customer.

8.02. Late Fees: All payment obligations are non-cancelable and fees paid are non-refundable. Past due balances shall accrue interest at a rate of one and one-half percent (1.5%) per month, or the maximum rate permitted by law, whichever is lower, calculated from the original due date until settled in full.

8.03. Price Adjustments: Blunom may adjust platform pricing for any upcoming Renewal Term by providing written notice to Customer at least 30 days prior to the expiration of the then-current term.

9.01. By Blunom: Blunom will defend Customer against third-party legal claims alleging that the production-ready Service directly infringes a valid United States copyright or misappropriates a trade secret, paying all court-awarded damages or settled liabilities. This obligation does not apply if the claim arises from: (a) modification of the platform by parties other than Blunom, (b) combination of the platform with external software or data where the platform alone would not infringe, or (c) use of the platform in violation of these Terms.

9.02. By Customer: Customer will defend, indemnify, and hold harmless Blunom and its officers, directors, and employees from any third-party claims, liabilities, losses, and legal costs arising out of: (a) Customer Data or Input, (b) Customer's deployment or operational utilization of agent Outputs, (c) breach of the Acceptable Use guidelines in Section 5, or (d) acts, omissions, or configurations executed by any corporate Affiliate or designated third-party Services Partner.

10.01. Exclusion of Consequential Damages: Except for liability arising from a party's breach of Confidentiality (Section 13) or Customer's violation of Acceptable Use (Section 5), in no event shall either party be liable for any indirect, special, incidental, exemplary, punitive, or consequential damages, including loss of profits, enterprise data corruption, system downtime, or runaway resource or token costs, even if advised of the possibility of such damages.

10.02. Aggregate Liability Cap: Except for Customer's direct payment obligations or a party's explicit indemnification duties under Section 9, each party's total cumulative liability for all claims arising under or relating to these Terms shall be limited to the aggregate fees paid or payable by Customer to Blunom, or to the Authorized Partner on Blunom's behalf, during the 12 months immediately preceding the event giving rise to the claim.

10.03. Contractual Claim Time-Bar: YOU AGREE THAT ANY CAUSE OF ACTION OR LEGAL CLAIM ARISING OUT OF OR RELATING TO THE SERVICE OR THESE TERMS MUST BE COMMENCED WITHIN ONE (1) YEAR AFTER THE CAUSE OF ACTION ACCRUES. OTHERWISE, SUCH CAUSE OF ACTION IS PERMANENTLY BARRED.

11.01. Informal Meet-and-Confer: Before initiating formal legal action, the parties agree to attempt to resolve disputes informally. A written notice of dispute must be sent to hello@blunom.ai, and executive representatives from both parties must meet and confer in good faith to reach a resolution within 45 days.

11.02. Mandatory Binding Arbitration: If informal resolution fails, any remaining dispute, controversy, or claim shall be finally and exclusively settled by binding arbitration administered by JAMS in accordance with its Streamlined Arbitration Rules. The arbitration shall take place on a strictly confidential basis.

11.03. Class Action & Jury Waiver: THE PARTIES WAIVE ALL CONSTITUTIONAL OR STATUTORY RIGHTS TO A TRIAL BY JUDGE OR JURY IN COGNIZABLE COURTS. ALL CLAIMS MUST BE BROUGHT IN A PARTY'S INDIVIDUAL CAPACITY, AND NOT AS A PLAINTIFF OR CLASS MEMBER IN ANY PURPORTED CLASS, COLLECTIVE, CONSOLIDATED, OR REPRESENTATIVE PROCEEDING.

12.01. Data Protection Addendum: To the extent that Blunom processes any regulated Personal Data, as defined under GDPR, CCPA, or applicable data privacy frameworks, on Customer's behalf within the Input, the parties agree that Blunom's Data Protection Addendum ("DPA"), available at https://blunom.ai/legal/dpa, is hereby incorporated into these Terms by reference.

12.02. Security & Audit Program Standards: Blunom shall maintain a formal, documented information security program containing administrative, physical, and technical safeguards designed to protect Customer workspaces. Blunom undergoes independent structural validation of its internal control frameworks, including, but not limited to, SOC 2 Type II audit tracking procedures. Upon written request, which may not be submitted more than once per rolling 12-month period, Blunom shall provide Customer or its executing Authorized Partner with its most recent independent third-party security audit documentation, subject to the execution of an appropriate mutual confidentiality agreement.

13.01. Scope of Confidential Information: "Confidential Information" refers to any proprietary information disclosed by one party ("Discloser") to the other ("Recipient") that is marked as confidential or should reasonably be understood to be confidential given its context. Blunom's engineering strategies, custom pricing models, and architectural routing configurations, alongside Customer's proprietary tenant configurations, constitute Confidential Information.

13.02. Obligations of Protection: Recipient will use at least a reasonable standard of care to protect the Discloser's Confidential Information, restricting access solely to employees, contractors, or professional advisers who require access to execute rights under these Terms and who are bound by matching confidentiality duties. Confidential Information excludes information that becomes publicly known through no fault of the Recipient.

14.01. Delaware Jurisdiction: These Terms, along with any transactional or tort claims arising out of platform functionality, shall be governed by and construed under the laws of the State of Delaware, without regard to its conflict of laws principles.

14.02. Export Compliance: Customer agrees to comply with all applicable U.S. export control regulations, ensuring no technical data or software assets are exported or re-exported in violation of federal restrictions or agency embargoes.

15.01. Term & Subscription Renewal: These Terms remain effective for the duration of any active platform use or subscription period set forth in an Order Form or Partner purchase agreement. Subscriptions automatically renew for matching terms unless either party provides written notice of non-renewal at least 30 days prior to the expiration of the then-current term.

15.02. Amendments to Text: Blunom reserves the right to amend these Terms at any time by posting an updated text to https://blunom.ai/terms. We will notify Customer of material modifications via workspace pop-up notifications, system dashboards, or direct email. Continued platform access following the effective date of an update constitutes binding acceptance.

15.03. Termination for Cause: Either party may terminate these Terms immediately if the other party materially breaches its obligations and fails to cure such breach within 30 days of receiving descriptive written notice. Upon termination, all platform access rights cease, and Customer must immediately settle all outstanding financial balances.

15.04. Survival Clauses: Sections 4, 5, 6, 7, 9, 10, 11, 12, 13, and 14 shall survive any expiration or termination of these Terms.

16.01. Notices Point of Contact: To request clear workspace closure procedures, report acceptable use violations, or submit DMCA copyright infringement notifications, please contact our team at: hello@blunom.ai.