Establishing secure connection…Loading editor…Preparing document…

Malwarebytes Software Add-on

This template is fully customizable. Edit the text, fill out the fields, and send it for signature. Give it a try!

MALWAREBYTES SOFTWARE ADD-ON AGREEMENT

Parties and Recitals

Provider Name:

Client Name:

WHEREAS, Provider and Client are parties to a Master Software License Agreement, Agreement Date: , Agreement No.: (the "Master Agreement");

WHEREAS, Provider offers a Malwarebytes-compatible software add-on product that extends the Master Agreement functionality, including enhanced threat detection, integration modules, and support services;

WHEREAS, the parties desire to amend the Master Agreement to incorporate the add-on features, fees, and service obligations set forth in this Add-On Agreement (the "Add-On").

Scope of Work

The Provider will deliver the add-on in accordance with the acceptance criteria set forth above and will make commercially reasonable efforts to ensure compatibility with the Client's specified Malwarebytes product version(s). Target delivery milestone:

Payment Terms

Unpaid amounts shall accrue interest at or the maximum permitted by law, whichever is less. The Client shall also reimburse Provider for collection costs, including reasonable attorneys' fees.

Term and Termination

Effective Date: . Term End Date: .

Either party may terminate this Add-On for material breach by the other party if the breach remains uncured for a period of days following written notice. Either party may terminate for convenience upon days' prior written notice.

Upon termination, Client will pay Provider for all work performed and non-cancellable commitments incurred through the effective termination date. License rights granted hereunder shall survive termination only to the extent expressly set forth in this Add-On or the Master Agreement.

Confidentiality

Each party (the "Receiving Party") shall maintain in confidence all non-public, proprietary, or business information disclosed by the other party (the "Disclosing Party") that is designated confidential or that reasonably should be understood to be confidential ("Confidential Information"). Confidential Information does not include information that the Receiving Party can demonstrate: (a) is or becomes generally available to the public other than by a breach of this Add-On; (b) was in its possession prior to receipt from the Disclosing Party without restriction; (c) is rightfully received from a third party without breach of any obligation of confidentiality; or (d) is independently developed by employees who did not have access to the Disclosing Party's Confidential Information.

The Receiving Party shall use Confidential Information solely to perform its obligations under this Add-On and shall use at least the same degree of care to protect the Confidential Information as it uses to protect its own confidential information, but in no event less than reasonable care. Disclosure is permitted to the extent required by law, provided the Receiving Party gives prompt notice to the Disclosing Party and cooperates in any reasonable protection of confidentiality.

Intellectual Property and License

All intellectual property rights in the Add-On, including modifications and derivative works, remain exclusively with Provider except as expressly granted in the Master Agreement. Provider grants Client a non-exclusive, non-transferable license to use the Add-On solely in accordance with the terms of the Master Agreement and this Add-On. Client shall not reverse engineer, decompile, or otherwise attempt to derive source code from the Add-On except to the extent permitted by applicable law.

Representations, Warranties and Liability

Provider represents that it has the right to grant the rights herein and that the Add-On will materially conform to the specifications in the Scope of Work for a period of days from delivery. EXCEPT AS EXPRESSLY PROVIDED HEREIN, THE ADD-ON IS PROVIDED "AS IS" AND PROVIDER DISCLAIMS ALL OTHER WARRANTIES, WHETHER EXPRESS, IMPLIED, STATUTORY OR OTHERWISE, INCLUDING MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.

Provider's aggregate liability for breach of this Add-On shall not exceed the amounts paid by Client to Provider under this Add-On during the month period preceding the claim. Neither party shall be liable for indirect, incidental, special, or consequential damages.

Notices

Governing Law; Dispute Resolution

This Add-On shall be governed by and construed in accordance with the laws of the State of , without regard to its conflicts of law principles. The parties agree to attempt in good faith to resolve disputes through negotiation prior to pursuing any formal remedy; if unresolved, the parties submit to the exclusive jurisdiction of the state and federal courts located within the chosen jurisdiction.

Entire Agreement

This Add-On, together with the Master Agreement, constitutes the entire agreement between the parties with respect to the subject matter hereof and supersedes all prior and contemporaneous agreements, representations, and understandings of the parties. Any amendment must be in writing and signed by authorized representatives of both parties.

Additional Provisions

Assignment: Neither party may assign its rights or delegate its obligations under this Add-On without the prior written consent of the other party, except that Provider may assign to an affiliate or in connection with a sale of substantially all of its assets.

Compliance with Laws: Each party shall comply with all applicable laws and regulations in performing its obligations under this Add-On, including export control and data protection laws.

Provider:

By:

Date:

Client:

By:

Date:

Enter text✕

What the Malwarebytes Software Add-on Is

The Malwarebytes Software Add-on is a supplemental agreement or licensing amendment that extends or modifies an existing Malwarebytes product subscription. It typically defines additional modules, updated scope of protection, permitted users, pricing adjustments, and any special support or deployment terms. Organizations use an add-on when they acquire extra features, move to a new licensing tier, or formalize volume or partner discounts. The add-on becomes part of the governing contract and should be executed and retained with the primary license agreement to preserve auditability and evidence of agreed changes.

Why a Formal Software Add-on Matters

A written Malwarebytes Software Add-on clarifies scope, billing, and responsibilities, reduces disputes, and documents consent to additional processing or data uses while supporting audit, compliance, and procurement controls.

Why a Formal Software Add-on Matters

Typical parties involved

The add-on is completed by stakeholders across security, procurement, and legal who need clear licensing and data handling terms.

  • IT/security teams: choose modules, confirm deployment, and verify technical compatibility with existing endpoints.
  • Procurement/finance: confirm pricing, billing cycles, and budgetary approvals for the expanded license.
  • Legal/compliance: review data processing, indemnities, and any regulatory language tied to the add-on.

Final execution often requires signatures from both an authorized purchasing officer and the vendor representative to bind the amendment to the master agreement.

Step-by-step: completing an add-on

Follow a consistent sequence to avoid delays and to preserve an audit trail for approvals and compliance.

  • 01
    Upload Document: Attach the signed master agreement and the proposed add-on version.
  • 02
    Fill Fields: Complete legal names, effective date, scope, and pricing precisely.
  • 03
    Review Parties: Have procurement and legal confirm financial terms and liability language.
  • 04
    Execute: Collect signatures and store the executed add-on with the primary contract.

Suggested digital workflow settings

Configure the online workflow to match your approval and authentication needs before sending for signature.

Field Configuration
Signer Authentication Email + SMS OTP or KBA where required
Signing Order Sequential: legal then procurement then vendor
Reminders Auto-reminders at 3 and 7 days
Access Control Restrict downloads to signed parties

Where the executed add-on goes next

After signature, route the executed add-on to legal, procurement, and the security operations team for implementation and recordkeeping.

  • Legal Repository: Store the executed add-on alongside the master agreement and change log.
  • Finance: Send copy for billing updates and purchase order reconciliation.
  • IT/Security: Provide implementation notes, activation keys, and scope details.
  • Vendor Records: Ensure the vendor retains a signed copy linked to your account record.

Technical formats and integrations to plan for

Confirm acceptable file formats and any integrations needed for procurement or ticketing systems.

  • File Types: PDF and DOCX supported for signature and archival
  • Integrations: Salesforce, NetSuite, Microsoft 365, or Procore connectors common
  • Export Options: Download signed PDF with audit trail attached

Key elements to include in a professional add-on

Ensure the document is complete, precise, and matches the master agreement to minimize later disputes or misinterpretation.

Scope

Define modules, endpoint counts, user seats, and geographic or subsidiary limitations so both parties share a clear operational baseline.

Pricing

Show per-unit pricing, discounts, billing frequency, and any one-time activation fees to prevent billing disagreements after deployment.

Term and Renewal

State the add-on term, auto-renewal terms, and termination notice windows to avoid unintended renewals or lapses in protection.

Data Handling

Describe data collection, processing locations, retention, and whether a BAA or similar addendum is required for healthcare data.

Support and SLA

List support tiers, response times, and escalation paths tied to the added modules to align operational expectations.

Liability and Indemnity

Clarify limits of liability, indemnity obligations, and any exclusivity clauses introduced by the add-on.

Security and compliance checkpoints

Encryption: TLS 1.2/1.3 in transit; AES-256 at rest
Audit Trail: Time-stamped events and IP attribution
HIPAA BAA: BAA required for PHI handling
21 CFR Part 11: Compliant where required
Access Controls: Role-based signer and admin rights
Accessibility: WCAG 2.0 Level AA support

Common preparation challenges

  • Using an informal email or memorandum instead of an executed add-on, which leaves scope and billing ambiguous and complicates enforcement.
  • Failing to match the licensee legal name exactly to corporate records, triggering vendor refusal or delayed activation.
  • Omitting the effective date or using inconsistent date formats, creating disputes about billing start and service windows.
  • Not including a signature block with titles and dates, which can prevent the document from being accepted by procurement or audit teams.

Consequences of an incorrect or incomplete add-on

Contract Dispute: Ambiguous scope invites disagreement and potential litigation
Billing Errors: Incorrect pricing fields lead to invoice disputes
Data Liability: Improper data terms may cause HIPAA or privacy exposure
Compliance Failures: Missing BAA or controls can block deployments in regulated sectors
Operational Delay: Incomplete add-ons delay provisioning and risk coverage
Revocation Risk: Lack of authorization may allow vendor to refuse execution

Key dates and timing considerations

Document timing affects billing, coverage, renewals, and termination rights—capture each date in a standardized format.

Effective Date:

Use MM/DD/YYYY; this starts billing and service obligations

Signature Deadline:

Set a clear cutoff to lock pricing and deployment schedules

Renewal Notice:

Specify notice period, commonly 30 days before term end

Payment Due Date:

Align invoices with the effective date and stated payment terms

Implementation Window:

Document any agreed deployment milestones and acceptance tests

Comparing eSignature vendors for add-on execution

Common selection criteria for signing and routing an add-on include price model, bulk send, audit trail, HIPAA support, and any envelope or session caps.

signNow DocuSign Adobe Sign PandaDoc HelloSign
Starting Price $8/user/mo $15/user/mo $14/user/mo $19/user/mo $15/user/mo
Free Trial 7-day trial Varies Varies Varies Varies
Bulk Send Yes Yes Yes Yes No
Audit Trail Yes Yes Yes Yes Yes
HIPAA Compliant Yes Yes Yes No No
Envelope Cap No cap 100 envelopes/user/year Varies Varies Varies

Industry examples of add-on use

Real-world situations show how add-ons close capability or compliance gaps without replacing the master agreement.

Optica Ventures

A VC-backed portfolio needed endpoint telemetry expanded

  • added 2,000 seats for portfolio firms
  • the add-on documented pricing, activation schedule, and a 12-month support SLA, enabling rapid rollout without renegotiating the master agreement.

Fertility Centers

A healthcare provider added advanced threat protection

  • required HIPAA BAA and data-processing specifics
  • the executed add-on included a BAA and breach-notice timeline, which preserved compliance with patient privacy rules during onboarding.

FAQs and troubleshooting for add-on execution

Answers to frequent questions about signing, authentication, and integration choices when completing a Malwarebytes Software Add-on.


Need help? Contact support

be ready to get more
Join over 28 million airSlate SignNow users