Broker Terms of Use / Partner Addendum

Last Updated: [Date]

These Broker Terms of Use / Partner Addendum (these “Broker Terms”) govern access to and use of H33.ai, Inc.’s cyber-insurance verification workflows, broker enablement tools, Terminal links, dashboards, proof-bundle initiation tools, and related broker-facing services made available in connection with a participating cyber-insurance program.

These Broker Terms are intended to be lightweight broker enablement terms. They do not make Broker a primary purchaser of the H33 platform unless Broker separately enters into an Order Form or other written agreement with H33.

By accessing or using the Broker Tools, initiating a Policyholder verification workflow, distributing a Terminal link, viewing H33-generated status information, or otherwise participating in an H33-supported cyber-insurance workflow, Broker agrees to these Broker Terms.

1. Parties; Program Context

1.1 H33

“H33” means H33.ai, Inc., a Florida corporation.

1.2 Broker

“Broker” means the insurance broker, producer, agent, intermediary, channel partner, or other authorized party that accesses or uses the Broker Tools in connection with a participating cyber-insurance program.

1.3 Program Sponsor / Insurer

“Program Sponsor” means the insurer, managing general agent, program administrator, or other insurance-side entity that has authorized use of H33’s cyber-insurance verification workflows for the applicable program.

1.4 Policyholder

“Policyholder” means an insured, prospective insured, applicant, policyholder, customer, member, account, or other entity invited to authorize system connection, verification, or control-state attestation through an H33-supported workflow.

1.5 Broker Tools

“Broker Tools” means the broker-facing features, links, dashboards, workflows, status views, initiation tools, materials, and other services made available by H33 to support Policyholder verification workflows.

2. Purpose; Broker Role

2.1 Broker as Facilitator

Broker acts only as a facilitator of the applicable insurance placement, renewal, policyholder engagement, verification initiation, or related workflow. Broker does not receive underwriting, pricing, claims, coverage, interpretive, or decision-making authority from H33.

2.2 No Insurance Activity by H33

H33 is a technology provider. H33 does not underwrite, rate, bind, issue, quote, sell, solicit, negotiate, place, market, recommend, adjust, adjudicate, approve, deny, administer, or service insurance products, policies, renewals, applications, endorsements, cancellations, claims, or coverage determinations.

2.3 No Agency Relationship

Broker is not H33’s agent, representative, fiduciary, employee, producer, reseller, sublicensee, or legal representative. Broker has no authority to bind H33, make statements on H33’s behalf, modify H33 materials, or create any obligation, warranty, representation, certification, service level, reliance right, remedy, or duty owed by H33 to any Policyholder, insurer, applicant, insured, claimant, regulator, reinsurer, or third party.

3. Definitions

3.1 Terminal

“Terminal” means an H33-controlled or H33-approved interface, workflow, link, portal, or authorization environment through which a Policyholder, administrator, Broker, or other authorized participant may initiate, authorize, connect, review, or manage an Integration Source or related verification workflow.

3.2 Verification Link

“Verification Link” means a Terminal link, invitation link, workflow link, QR code, embedded flow, or other H33-approved method used to invite a Policyholder or authorized administrator to begin an H33-supported verification workflow.

3.3 Integration Source

“Integration Source” means a third-party system, account, platform, API, cloud environment, endpoint tool, identity provider, backup platform, productivity suite, security tool, log source, or other technology source connected to the H33 workflow by or on behalf of a Policyholder or authorized administrator.

3.4 H33 Output

“H33 Output” means any Proof Bundle, control-state attestation, verification summary, dashboard output, API response, status indicator, technical label, timestamp, log, Claims Event Query result, or related technical output generated by or through H33’s cyber-insurance verification workflows.

3.5 Proof Bundle

“Proof Bundle” means a package, file, report, attestation, log extract, verification summary, timestamped record, cryptographic proof, dashboard output, API response, or related technical output generated by or through H33’s cyber-insurance verification workflows.

4. Permitted Broker Use

Subject to these Broker Terms, any applicable Program Sponsor instructions, H33-approved program materials, and applicable law, Broker may use the Broker Tools solely to:

initiate Policyholder verification workflows;
distribute H33-approved Verification Links to Policyholders or authorized administrators;
assist Policyholders with understanding how to access Terminal or begin an authorization workflow;
view limited workflow status or H33 Outputs to the extent made available to Broker through the applicable program;
support Program Sponsor-approved underwriting, renewal, risk-engineering, policyholder engagement, or claims workflows; and
communicate about H33-supported workflows using H33-approved or Program Sponsor-approved materials that are consistent with H33-approved materials.

Broker may not use the Broker Tools or H33 Outputs for any purpose not expressly permitted by these Broker Terms or the applicable program materials.

5. Broker Responsibilities

Broker will:

use the Broker Tools only for lawful, authorized, business purposes in connection with the applicable cyber-insurance program;
comply with all applicable insurance, producer, broker, privacy, cybersecurity, consumer protection, unfair trade practices, unfair claims settlement practices, anti-discrimination, marketing, and data-use laws;
provide accurate, complete, current, and non-misleading information to H33, the Program Sponsor, and Policyholders;
use only H33-approved descriptions, or Program Sponsor-approved descriptions that are consistent with H33-approved materials, when describing H33, the Broker Tools, H33 Outputs, Terminal, Verification Links, or Policyholder participation;
ensure that Verification Links are sent only to Policyholders or administrators that Broker reasonably believes are authorized to receive and act on them;
not modify, obscure, remove, or contradict H33 role disclosures, authorization language, privacy notices, data authorizations, revocation instructions, disclaimers, or click-through terms;
promptly notify H33 or the Program Sponsor if Broker becomes aware of an incorrect recipient, unauthorized access, disputed authorization, disputed output, policyholder complaint, security concern, or misuse of the Broker Tools; and
cooperate with H33 and the Program Sponsor in investigating suspected misuse, incorrect authorization, inaccurate information, disputed outputs, security concerns, legal requests, or regulatory inquiries relating to the Broker Tools.

6. Prohibited Conduct

Broker will not, and will not permit any third party to:

state or imply that H33 is an insurer, broker, producer, MGA, claims administrator, adjuster, actuarial advisor, cybersecurity advisor, compliance advisor, coverage decision-maker, or fiduciary;
state or imply that H33 underwrites, rates, binds, issues, sells, solicits, adjusts, adjudicates, approves, denies, administers, or services insurance or claims;
state or imply that use of the Broker Tools or H33 Outputs guarantees premium reductions, coverage eligibility, policy issuance, favorable terms, claim payment, claim denial, breach prevention, ransomware prevention, loss reduction, compliance, regulatory approval, or any specific insurance, security, financial, or claims outcome;
use any H33 Output as the sole basis for any recommendation, adverse recommendation, placement decision, coverage statement, premium representation, renewal position, claim statement, or other insurance-related communication;
modify, summarize, interpret, certify, score, or repackage H33 Outputs in a way that misstates their meaning, limitations, source, Verification Window, available telemetry, or technical nature;
represent any H33 score, label, status, flag, tier, exception, dashboard indicator, or summary as an insurance score, credit score, underwriting classification, actuarial classification, rating variable, coverage determination, or claims determination;
distribute Verification Links to unauthorized recipients or use Verification Links for undisclosed, covert, deceptive, or unauthorized monitoring of any Policyholder, administrator, employee, user, system, account, or environment;
access, use, retain, disclose, or share H33 Outputs except as authorized by the applicable program and required for Broker’s lawful insurance facilitation role;
scrape, copy, reverse engineer, decompile, disassemble, benchmark, test, probe, or attempt to derive the underlying source code, algorithms, scoring logic, cryptographic methods, schemas, technical labels, control-signal mappings, or verification logic used by H33;
interfere with, disrupt, overload, misuse, or attempt to bypass access controls, rate limits, security controls, or usage restrictions for the Broker Tools, Terminal, or any H33 system;
use the Broker Tools to build, train, benchmark, or improve a competing product or service; or
create, or purport to create, any obligation, representation, warranty, certification, reliance right, remedy, service level, or duty owed by H33 to any Policyholder, insurer, insured, applicant, claimant, regulator, reinsurer, or other third party.

7. Policyholder Authorization

7.1 Authorization Required

Broker acknowledges that H33-supported workflows may require the Policyholder or its authorized administrator to connect one or more Integration Sources through Terminal, OAuth, API connection, administrator approval, or another H33-approved authorization flow.

7.2 Broker Not Responsible for Technical Authorization Mechanics

Unless otherwise agreed in writing, Broker is not responsible for technically configuring Policyholder systems or Integration Sources. However, Broker is responsible for ensuring that Broker does not knowingly send Verification Links to unauthorized recipients or misrepresent the scope, purpose, recipients, or insurance-related use of the H33 workflow.

7.3 No Circumvention

Broker will not bypass, disable, obscure, alter, or interfere with any H33 authorization flow, click-through term, privacy notice, data authorization, role disclosure, revocation instruction, or other required Policyholder-facing material.

7.4 Revocation and Disputes

If a Policyholder revokes authorization or disputes a Verification Link, Integration Source connection, H33 Output, or related workflow, Broker must promptly follow the applicable Program Sponsor and H33-approved procedures and must not continue to use or distribute the disputed H33 Output except as expressly authorized by the Program Sponsor and permitted by law.

8. H33 Outputs; Limitations

8.1 Technical Inputs Only

H33 Outputs are technical outputs based on available Integration Sources, configured permissions, available telemetry, applicable APIs, and the relevant verification period. H33 Outputs are not insurance decisions, coverage decisions, claims decisions, actuarial conclusions, legal advice, compliance determinations, security guarantees, or complete assessments of a Policyholder’s enterprise security posture.