Fuse Beta General Service Agreement

Version: 2026-09-15
Reference: A21-FUSE-GSA-2026-09-15
Agreement URL: https://dpq3723ss5vok.cloudfront.net/gsa
Archived version: https://dpq3723ss5vok.cloudfront.net/agreements/A21-FUSE-GSA-2026-09-15.html
Effective date: The date on which Customer accepts this Agreement

This Fuse Beta General Service Agreement (the “Agreement”) is between NeuralSoft Private Limited, CIN U62090DL2024PTC427960, doing business as a21.ai, with its U.S. business and legal-notice address at 651 N Broad St, Suite 201, Middletown, New Castle County, Delaware 19709, United States (“a21.ai,” “Provider,” “we,” “us,” or “our”), and the organization on whose behalf an authorized individual activates Fuse for the connected HubSpot portal (“Customer,” “you,” or “your”).

By selecting the acceptance checkbox and activating Fuse, the individual accepting this Agreement confirms: “I confirm that I am authorized to bind this organization and accept the a21.ai General Service Agreement on its behalf.” If that individual is not authorized, they must not accept this Agreement or activate Fuse. The parties agree that electronic acceptance and records have the same effect as a handwritten signature and paper records to the extent permitted by law.

1. Fuse Beta Service

“Fuse” is a beta software service that connects one Customer-authorized HubSpot portal to one Customer-authorized AWS Partner Central seller environment. Each HubSpot portal installation is treated as an independent tenant.

Fuse may provide configuration, initial synchronization, bidirectional synchronization of supported opportunity data, reconciliation, administrative controls, tenant-authorized exports, and optional AI-assisted features. Only HubSpot Deals that Customer or its authorized users classify for AWS workflows are eligible for outbound Partner Central processing; ordinary non-AWS Deals remain outside that workflow. HubSpot remains Customer’s CRM, and AWS Partner Central remains the applicable co-sell system of record.

Fuse does not provide payment collection, private-offer execution, legal or tax advice, or automatic submission of funding claims. Beta features may be incomplete, changed, suspended, or removed as the service is developed.

2. Thirty-Day Trial and Paid Access

Acceptance starts one 30-day beta trial for the authorized installation, covering the beta features Provider makes available during the trial. FuseAI remains subject to the separate opt-in described in Section 6. The trial is provided without charge unless Customer and Provider sign a separate written order stating otherwise. Each HubSpot portal may receive only one trial; disconnecting, uninstalling, or reinstalling Fuse does not restart it.

The trial does not automatically renew, convert to a paid service, or authorize billing. Continued or annual access requires a separate written order or other express written agreement identifying the term, fees, payment terms, and included services. If an order conflicts with this Agreement, the order controls only for the subject matter it expressly addresses.

3. Accounts, Authority, and Customer Responsibilities

Customer authorizes Provider to access and process Customer’s connected systems and Customer Data only as reasonably necessary to provide, secure, support, maintain, and recover Fuse, carry out Customer’s instructions, and comply with applicable law.

Customer is responsible for:

1. maintaining lawful control of its HubSpot and AWS accounts and the permissions required to use them;
2. ensuring that an authorized HubSpot administrator with the required permissions installs and activates Fuse and grants the requested OAuth permissions;
3. deploying and maintaining any Customer-side AWS role, external ID, or other configuration required for Partner Central connectivity;
4. ensuring that Customer and its authorized users have the right to provide and process the information submitted through Fuse;
5. keeping account access secure and promptly removing or reporting unauthorized users or credentials;
6. reviewing synchronization decisions, mappings, exports, AI-assisted content, and proposed actions; and
7. complying with applicable law and the terms and policies governing HubSpot, AWS, and AWS Partner Central.

Customer remains responsible for the accuracy and lawfulness of its CRM and Partner Central data and for any submission or write that an authorized user confirms.

4. Acceptable Use

Customer must not use Fuse to violate law or third-party rights; introduce malicious code; probe or circumvent security, tenancy, authorization, rate, or usage controls; interfere with the service; misrepresent AWS eligibility or approval; or access another tenant’s data.

Unless Provider expressly agrees in writing, Customer must not place payment-card data, authentication secrets, government identification numbers, protected health information, children’s data, or special-category or similarly sensitive personal data in Deal fields, FuseAI prompts, notes, uploads, or other general-content fields. This restriction does not prohibit authorization material transmitted through Fuse’s designated secure OAuth or AWS authorization flows. Ordinary business contact, company, Deal, and opportunity information required for the supported workflows is permitted when Customer has a lawful basis to process it.

Customer must not reverse engineer, circumvent security or usage controls, resell, sublicense, scrape, or provide Fuse as a service bureau; use Fuse to develop or benchmark a competing service for publication; or interfere with its operation, except where applicable law expressly prohibits such restrictions.

5. Customer Data and Service Data

“Customer Data” means data submitted to, retrieved from, or generated from Customer’s connected environments for Customer, including supported HubSpot, company, contact, Deal, AWS account, and opportunity information. Customer retains all rights in Customer Data.

Customer grants Provider a limited, non-exclusive right to host, copy, transmit, validate, transform, and otherwise process Customer Data solely for the purposes stated in Section 3. Provider will not sell Customer Data.

“Service Data” means security, audit, configuration, performance, and usage information generated by operating Fuse that does not contain Customer-provided content except where narrowly required for support, security, recovery, or audit evidence. Provider may use aggregated and de-identified Service Data to operate and improve Fuse only where it cannot reasonably identify Customer or an individual and is not used to reconstruct Customer Data.

Customer may request an export of supported retained Customer Data through the available Fuse controls. Export links are time-limited and must be protected by Customer.

6. FuseAI and Human Review

FuseAI is optional, disabled by default, and requires a separate affirmative opt-in by an authorized tenant administrator. FuseAI may generate summaries, classifications, recommendations, drafts, and guidance. Its output may be incomplete, inaccurate, or unsuitable, and Customer must independently review it before relying on or using it.

FuseAI does not guarantee AWS eligibility, funding, approval, co-sell acceptance, or any commercial outcome. The supported confirmed-action flow will not create a HubSpot note or task unless an authorized user separately reviews and confirms that specific action. Other drafts remain copy-only unless the product clearly presents and Customer authorizes a supported write.

Subject to this Agreement and applicable law, Customer may use FuseAI outputs for its internal business purposes. Outputs may not be unique, and Provider does not guarantee that an output is accurate, protectable, owned exclusively by Customer, or non-infringing. Customer is responsible for reviewing outputs and determining whether and how to use them.

For the beta, FuseAI uses Amazon Bedrock in the AWS us-east-1 Region. Bedrock text prompt and output invocation logging is disabled in Provider’s account. Certain AWS Partner Central assistant context may be retained by the applicable AWS service for up to 48 hours. This Agreement does not make any broader claim about third-party model training, storage, or residency beyond the applicable third-party terms and verified service configuration.

7. Third-Party Services

Fuse depends on services supplied by third parties, including HubSpot and Amazon Web Services. Customer’s use of those services remains governed by Customer’s agreements with the relevant provider.

a21.ai does not control and is not responsible for third-party availability, security, policy changes, API behavior, data accuracy, account restrictions, or program decisions. Third-party changes or outages may limit or interrupt Fuse.

Neither Fuse nor a21.ai represents or guarantees that Customer will qualify for, receive, or retain any AWS program status, opportunity validation, co-sell benefit, promotional credit, incentive, reimbursement, funding, approval, or commercial outcome. Those decisions are made independently by AWS or the relevant third party.

8. Security and Confidentiality

Each party will use the other party’s non-public information only for purposes of this Agreement and will protect it using at least reasonable care. Confidential information excludes information that the receiving party can demonstrate was lawfully known without restriction, independently developed without use of the other party’s information, lawfully received from another source, or made public without breach of this Agreement.

Provider will maintain reasonable administrative, technical, and organizational safeguards appropriate to the beta service. As applicable to a workflow, these may include tenant-scoped authorization, encryption, restricted credentials, least-privilege access, and redacted operational logging. These controls reduce risk but do not make any system completely secure.

A party may disclose confidential information to its personnel, professional advisers, and service providers who need it for this Agreement and are bound by confidentiality obligations at least as protective as this Section. A party may also disclose confidential information when legally required, provided it gives advance notice where legally permitted and reasonably cooperates in seeking protective treatment. Provider will notify Customer without undue delay after confirming a security incident affecting Customer Data when notice is required by applicable law. These confidentiality obligations continue for three years after termination, and for trade secrets for so long as they remain trade secrets under applicable law.

9. Data Retention and Deletion

New access and normal synchronization are disabled when the applicable installation is disconnected, uninstalled, revoked, suspended, or expired. Items already queued or in flight may complete, be suppressed, or expire under the applicable workflow and third-party controls. Different data categories have different lifecycle controls:

1. raw analytics events become eligible for lifecycle deletion after 30 days;
2. live analytics projections become eligible for lifecycle deletion after 90 days;
3. FuseAI records are configured to become eligible for lifecycle deletion after 30 days;
4. encrypted recovery copies associated with the analytics and recovery chain may become eligible for expiration as late as 365 days after the applicable live-data eligibility point; and
5. the configured 456-day figure is the lifecycle horizon for that analytics and recovery chain, including UTC-bucket rounding. It is an eligibility schedule, not a guaranteed maximum retention or physical-erasure deadline, and it is not a universal retention period for every category of Customer Data.

“Eligible for deletion” and “eligible for expiration” do not mean immediate physical erasure. AWS, HubSpot, and other providers may apply asynchronous deletion, replication, backup rotation, or service-specific grace periods. Operational records may remain recovery-gated while Provider verifies that deletion will not compromise security, audit evidence, disaster recovery, or tenant isolation. Provider therefore does not promise deletion from every physical copy on a particular calendar day.

Primary Deal and opportunity data, tenant configuration, authorization material, exports, queued records, and other operational Customer Data follow service-specific controls rather than the analytics schedule above. After access ends, Provider restricts and deletes or expires those Provider-held copies when they are no longer reasonably necessary to complete authorized in-flight work, secure and recover the service, preserve required audit or acceptance evidence, comply with law, resolve disputes, or honor a valid legal hold. Operational tenant deletion may remain pending until Provider’s recovery-copy safety gate is satisfied. When a retention basis no longer applies, the applicable lifecycle process resumes.

Ending Fuse does not delete or change source records that remain in Customer’s HubSpot or AWS environments. Customer controls those source systems under its agreements with HubSpot and AWS.

10. Intellectual Property and Feedback

Provider and its licensors retain all rights in Fuse, its software, documentation, workflows, designs, and improvements. Subject to this Agreement, Provider grants Customer a limited, non-exclusive, non-transferable, non-sublicensable, revocable right to use the beta internally during the applicable term.

Customer may provide suggestions or feedback. Customer grants Provider a perpetual, worldwide, royalty-free right to use that feedback without identifying Customer or disclosing Customer’s confidential information.

Nothing in this Agreement transfers ownership of Customer Data to Provider or ownership of Fuse to Customer.

Neither party may use the other party’s name, trademarks, logos, testimonials, participation in the beta, or the existence of the relationship in publicity, marketing, case studies, or announcements without prior written consent, except where disclosure is required by law. Acceptance of this Agreement is not publicity consent.

11. Support, Availability, and Beta Changes

Beta support is available through support@a21.ai. Unless a separate written order states otherwise, the beta has no service-level agreement, guaranteed uptime, response-time commitment, service credits, or guaranteed support hours.

Provider may modify beta functionality and limits, perform maintenance, or suspend features where reasonably necessary for security, legal compliance, third-party changes, or service operation. Provider will use reasonable efforts to avoid materially reducing the beta during the active trial without notice, but no roadmap or future feature is promised.

12. Warranties and Disclaimers

Each party represents that the person accepting or signing this Agreement for it has authority to do so.

TO THE MAXIMUM EXTENT PERMITTED BY LAW, THE BETA IS PROVIDED “AS IS” AND “AS AVAILABLE.” PROVIDER DISCLAIMS ALL EXPRESS, IMPLIED, STATUTORY, AND OTHER WARRANTIES, INCLUDING MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, NON-INFRINGEMENT, ACCURACY, AVAILABILITY, AND ERROR-FREE OPERATION.

Nothing in this Agreement excludes any warranty, remedy, or right that applicable law does not permit the parties to exclude.

13. Indemnification

Customer will defend and indemnify Provider and its personnel against third-party claims arising from Customer Data, Customer’s unlawful or unauthorized use of Fuse, or Customer’s breach of Section 3 or 4, except to the extent caused by Provider’s breach of this Agreement.

The party seeking indemnification must promptly notify the indemnifying party, reasonably cooperate, and allow the indemnifying party to control the defense and settlement, provided no settlement admits fault by or imposes non-monetary obligations on the protected party without its consent.

14. Limitation of Liability

TO THE MAXIMUM EXTENT PERMITTED BY LAW, NEITHER PARTY WILL BE LIABLE FOR INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, PUNITIVE, OR CONSEQUENTIAL DAMAGES, OR FOR LOST PROFITS, REVENUE, GOODWILL, BUSINESS OPPORTUNITIES, OR DATA, EVEN IF ADVISED THAT SUCH LOSS WAS POSSIBLE.

EXCEPT FOR CUSTOMER’S PAYMENT OBLIGATIONS, CUSTOMER’S BREACH OF SECTION 4, CUSTOMER’S INDEMNIFICATION OBLIGATIONS, A PARTY’S FRAUD OR WILFUL MISCONDUCT, AND LIABILITY THAT CANNOT BE LIMITED BY LAW, EACH PARTY’S TOTAL AGGREGATE LIABILITY ARISING OUT OF OR RELATING TO THIS AGREEMENT WILL NOT EXCEED THE GREATER OF INR 100,000 OR THE FEES PAID OR PAYABLE UNDER THE APPLICABLE ORDER DURING THE 12 MONTHS PRECEDING THE EVENT GIVING RISE TO LIABILITY.

These limitations apply across all theories of liability and do not apply where prohibited by law.

15. Suspension, Term, and Termination

This Agreement begins when Customer accepts it and continues during the 30-day trial and any later service term established by a written order, unless terminated earlier under this Agreement or the applicable order.

Customer may end the beta at any time by disconnecting Fuse or sending written notice. Provider may suspend or terminate access where reasonably necessary to address a security risk, unlawful use, material breach, non-payment under an applicable order, threats to connected systems, or third-party restrictions. Either party may otherwise terminate the beta on written notice.

Upon expiration or termination, Customer’s right to use Fuse ends, Provider may disconnect the integrations, and retained data enters the lifecycle described in Section 9. Provisions that by their nature should survive—including confidentiality, intellectual property, disclaimers, indemnification, liability limitations, and general terms—will survive.

16. Compliance

Each party will comply with laws applicable to its performance under this Agreement. Customer will not use Fuse in violation of anti-bribery, sanctions, or export-control laws, or applicable HubSpot or AWS program rules.

If applicable privacy law requires additional data-processing or international-transfer terms for Customer’s use of Fuse, Customer will notify Provider before submitting data subject to those requirements and the parties will execute the required terms. A signed data processing addendum controls over this Agreement for conflicts concerning personal-data processing.

17. Agreement Version and Changes

Acceptance applies to version 2026-09-15, reference A21-FUSE-GSA-2026-09-15. Provider will retain an immutable archived copy of the exact accepted text at the archived-version URL shown above. The archived accepted artifact will not be edited.

A future page at https://fuse.a21.ai/gsa may reproduce, redirect to, or link to this version. Moving or copying the display page does not change the terms already accepted. Any material amendment requires a new version and affirmative acceptance in writing or through a supported acceptance process; it does not apply retroactively.

18. General Terms

This Agreement and any expressly incorporated written order or data processing addendum are the entire agreement concerning the beta and supersede prior discussions on that subject. If there is a conflict, a data processing addendum controls for personal-data processing, an order controls for its expressly addressed commercial terms, and this Agreement controls otherwise.

Neither party may assign this Agreement without the other party’s written consent, except in connection with a merger, reorganization, or sale of substantially all relevant assets where the assignee assumes this Agreement. Neither party is liable for delay caused by events beyond its reasonable control. The parties are independent contractors; this Agreement creates no partnership, agency, fiduciary relationship, or third-party beneficiary.

If any provision is unenforceable, it will be modified only to the minimum extent necessary, and the remaining provisions remain effective. A waiver must be in writing and applies only to the specific instance. Headings are for convenience only.

This Agreement is governed by the laws of India, without regard to conflict-of-law principles. The courts located in New Delhi, India will have exclusive jurisdiction, unless applicable law requires otherwise. Before filing a claim, the parties will attempt in good faith for 30 days to resolve it through authorized business representatives, except where urgent injunctive relief is reasonably necessary.

Notices to Provider must be sent to support@a21.ai and 651 N Broad St, Suite 201, Middletown, New Castle County, Delaware 19709, United States. Notices to Customer may be sent to the business email supplied during activation or another contact designated by Customer.

Schedule 1 — Data Processing Summary

This Schedule summarizes the beta’s current processing and does not replace a data processing addendum where one is legally required.

Acceptance Statement

I confirm that I am authorized to bind this organization and accept the a21.ai General Service Agreement on its behalf.