Addendum to Master Services Agreement

Effective Date: 2/27/26 | Last Updated: February 26, 2026

This AI Terms and Conditions Addendum (“Addendum”) supplements the Master Services Agreement (“MSA”), Data Processing Addendum (“DPA”), and Privacy Policy between Revenue, Inc. (doing business as “Revenue.io”) and the Customer (collectively referred to as “Parties”). This Addendum outlines the terms and conditions governing the use of artificial intelligence (“AI”) technologies and services provided by Revenue.io.

1. Definitions

Capitalized terms used but not defined in this Addendum shall have the meanings given to them in the MSA.

“AI Subprocessors”: Listed at https://www.revenue.io/subprocessors as in effect from time to time.

“Revenue AI”: Any feature(s) or functionality utilizing machine learning and generative artificial intelligence, including but not limited to prompts, suggestions, guidelines, queries, weights or parameters that Revenue.io provides or incorporates into its products or services, but solely to the extent made available by Revenue.io to Customer. Revenue AI shall be deemed a Revenue Product as defined by the MSA, but there is no obligation on Revenue.io to make any Revenue AI available to Customer absent Revenue.io’s written agreement to do so.

“Input”: Customer-submitted and Customer-generated information, including Customer Data, for processing by Revenue AI. For clarity, any information that Customer submits as a prompt or query is only an Input to the extent that the Customer generates that prompt or query. Any prompts, suggestions, guidelines, queries, weights or parameters that Revenue.io provides or incorporates into its products or services or that are presented to or available to Customer to modify or supplement does not constitute an Input.

“Output”: Responses generated by Revenue AI in response to an Input. For clarity, any guidelines, weights or parameters that are incorporated into or used by Revenue AI to generate Output does not constitute Output.

“Google API Data”: As defined in the MSA, means any data accessed, received, or processed through Google APIs, including Gmail data and Google Calendar data, as authorized by the user through Google’s OAuth 2.0 consent framework. Google API Data is subject to the Google API Services User Data Policy, including the Limited Use requirements.

“GPAI Models”: Third-party general-purpose AI models provided by Revenue.io’s AI Subprocessors.

2. Purpose and Scope of AI Usage

Revenue.io utilizes machine learning and generative AI technologies, including conversation analysis, scorecards, opportunity insights, automated coaching, email generation and sentiment analysis, to enhance its products and services. Some AI functionalities are supported by AI Subprocessors as described in Section 8 below.

Google API Data Exclusion: Google Workspace data obtained via Google APIs (“Google API Data”) is not used as input to, processed by, analyzed by, or incorporated into Revenue AI or any other artificial intelligence, machine learning model, large language model, or automated decision-making system operated by or on behalf of Revenue.io. This exclusion applies to all AI functionalities described in this Addendum, in compliance with the Google API Services User Data Policy and the Limited Use requirements.

3. Data and Output Responsibilities

Output generated by Revenue AI constitutes Customer Data. The Customer is solely responsible for its Inputs, Customer Data, and use of Outputs. Customer warrants that its Customer Data will not violate applicable laws, this Addendum, or third-party rights. Customer confirms it has all necessary rights to provide Input to Revenue AI.

4. Participation and Termination

Use of Revenue AI is voluntary. All use of Revenue AI is subject to Customer’s compliance with the MSA and paying any fees due for the use of Revenue AI. Revenue.io may modify Revenue AI or this Addendum at any time with or without notice at its discretion. Customer’s continued use of Revenue AI following changes constitutes acceptance. Revenue.io may restrict access, suspend, discontinue or impose limits on Customer’s use of Revenue AI without liability.

4.1 Right to Opt Out of AI Features

Consistent with Revenue.io’s Global Privacy Policy, users have the right to opt out of AI-driven features and profiling. To exercise this right, users may:

• Adjust AI feature settings within the Revenue.io platform, where available
• Contact Revenue.io at privacy@revenue.io to request that AI-driven processing be disabled for their account
• Submit a request through Revenue.io’s Data Subject Access Request Form

Opting out of AI-driven features will not affect the user’s ability to use the core functionality of the Revenue Products.

5. Risks and Limitations

Customer acknowledges the inherent risks of AI, including potential inaccuracies, biases, and harmful outputs. Customer is responsible for establishing appropriate use policies, obtaining consents, and providing human oversight in the use of all Revenue AI. Revenue.io is not responsible for any inaccuracies in Output that Revenue AI generates or Customer’s failure to comply with applicable law in the use of Revenue AI.

6. Use Restrictions

Customer agrees not to provide sensitive data (e.g., health information, government IDs, financial data) as Customer Data or an Input or use Revenue AI to create competing models, mislead users, generate inappropriate content, and to adhere to Revenue.io’s policies and procedures regarding use of Revenue AI as they may be in effect from time to time and provided to Customer. Customer may not use Revenue AI to:

• (i) make automated decisions that may have a detrimental impact on individual rights without appropriate human supervision
• (ii) copy, create, offer, train, or sell any competing AI technology system, product, service, or offering with the same or similar functionality as the Revenue AI during the term of the MSA
• (iii) use the Revenue AI or Output to generate content that violates or promotes violence, hate speech, or harassment; or insults or demeans a person; or contravenes any regulatory safety policies
• (iv) mislead any person that the Revenue AI or Output is solely human-generated
• (v) modify, manipulate, or use Revenue AI in a way that contradicts Revenue.io’s ethical guidelines or applicable legal requirements

Customer will provide all disclosures regarding its use of Revenue AI as required by law and to comply with legal and industry practices regarding transparency.

7. AI Output Attribution and Watermarking

To the extent required by applicable law, the Customer shall ensure that end-users or third parties are informed when content or material has been generated using Revenue AI. Revenue.io may implement watermarking, cryptographic provenance indicators, metadata tagging, or similar technical measures to comply with transparency, traceability, and provenance requirements under the EU AI Act or any other applicable regulation.

8. EU AI Act Compliance

Revenue.io is an AI deployer under the EU Artificial Intelligence Act (“EU AI Act”) and does not develop or train AI models. Revenue.io uses third-party GPAI Models provided by its AI Subprocessors. All Revenue AI features are classified by Revenue.io as “Limited-Risk AI Systems” under the EU AI Act. Revenue.io will meet all deployer obligations for Limited-Risk AI Systems, including required transparency, monitoring, and human oversight. Revenue.io does not permit any use of Revenue AI by Customer that would reclassify Revenue AI as a High-Risk, Unacceptable-Risk, or otherwise prohibited system under the EU AI Act.

The Customer may not use Revenue AI for any High-Risk domains listed in Annex III of the EU AI Act — such as employment decisions, public-service eligibility, credit or insurance determinations, or biometric categorization — unless the Customer completes all legally required assessments, maintains human oversight, and receives Revenue.io’s prior written approval.

9. Synthetic Data

Revenue.io may generate or use synthetic data for evaluation, validation, testing, red-teaming, and performance assurance of Revenue AI. Synthetic data used or created by Revenue.io shall not contain identifiable Customer Data. The Customer acknowledges that synthetic data and synthetic Outputs are not inherently factual and shall not rely on such data or Outputs for regulatory, legal, or accuracy-sensitive use cases without conducting independent verification.

10. Data Collection and Use

Revenue.io shall make commercially reasonable efforts to collect and process specific categories of personal data only as strictly necessary for the operation and functionality of its Revenue AI. This includes, for example, summaries of voice calls, video meetings, SMS messages, and voice/video for conversation analysis, automated coaching, scorecards, opportunity analysis, sentiment analysis, and speech-to-text conversion summaries, as well as metadata such as timestamps, user identifiers, session IDs, and IP addresses to support AI processing and service optimization. Revenue.io will use this data to provide, maintain, enhance, and develop AI functionalities within its products and services, in compliance with applicable data protection laws.

By using Revenue AI, Customer expressly consents to this data collection and processing and confirms that all necessary consents from end-users or data subjects have been obtained in accordance with this Addendum and applicable laws.

Customer agrees that Revenue.io may use the Customer Data in aggregated and de-identified form and the Output to train, develop, enhance, and improve the Revenue AI.

Google API Data Carve-Out: Notwithstanding the foregoing, Google API Data is expressly excluded from any aggregated, de-identified, or anonymized data sets used for AI training, development, enhancement, or improvement. Google API Data shall not be used as Input to Revenue AI, shall not be incorporated into any training data set, and shall not be processed by any AI or machine learning system operated by or on behalf of Revenue.io. This exclusion is required by the Google API Services User Data Policy, including the Limited Use requirements, and is consistent with Section 2.6 of the MSA and Section 2 of Revenue.io’s Global Privacy Policy.

11. Training Data Sources, Model Provenance, and Lineage

Revenue.io does not use identifiable Customer Data to train or fine-tune any machine learning model. Revenue.io may use aggregated, de-identified, anonymized, or synthetic data derived from Customer Data solely for internal evaluation, testing, optimization, quality assurance, or improvement of Revenue AI. All training and foundational capabilities used within Revenue AI are derived from GPAI Models provided by Revenue.io’s AI Subprocessors, which maintain their own lawful data provenance, licensing, and model governance practices.

For avoidance of doubt, Google API Data is not included in any aggregated, de-identified, anonymized, or synthetic data derived from Customer Data for any purpose described in this Section.

Revenue.io maintains documentation describing the origin, provider, versioning, and operational characteristics of all GPAI Models used for inference, including model lineage, updates, configuration parameters, and evaluation methodologies (“Model Lineage Documentation”). Revenue.io will provide the then-current version of such documentation to the Customer upon reasonable written request.

12. Subprocessors and Third-Party Involvement

Revenue AI uses AI Subprocessors to provide certain AI functionalities. The AI Subprocessors operate under their own policies in compliance with industry privacy, security, and ethical standards, aligned with Revenue.io’s commitments.

A current list of AI Subprocessors is maintained at: https://www.revenue.io/subprocessors

13. User Consent and Transparency

To the extent required by applicable law, Revenue.io will provide transparency regarding the source of datasets used to train Revenue AI, types of data collected, the purposes of processing, and the involvement of AI Subprocessors.

For full details on Revenue.io’s data practices, users may refer to Revenue.io’s Global Privacy Policy, which includes detailed disclosures regarding AI model usage, opt-out mechanisms, and data subject rights. Data subject access requests may be submitted through Revenue.io’s DSAR Form or by contacting privacy@revenue.io.

14. Customer Regulatory Obligations

The Customer is solely responsible for ensuring compliance with all applicable AI, privacy, data protection, and automated decision-making laws arising from its use of Revenue AI, including but not limited to conducting Data Protection Impact Assessments (DPIAs), AI Impact Assessments (AIAs), establishing human oversight mechanisms, maintaining audit trails, providing all required notices to data subjects, and ensuring appropriate transparency for AI-generated content.

The Customer acknowledges that synthetic data and Outputs (whether derived from synthetic data or otherwise) are not inherently factual. Customer must independently validate all synthetic data and all Outputs and shall not rely on such synthetic data or any Outputs for regulatory, legal, employment, financial, compliance, safety-critical processes or accuracy-sensitive use cases without conducting independent verification. The Customer shall not rely upon Outputs as the exclusive basis for decisions that produce legal, employment or similarly significant effects on individuals.

15. Ethics, Compliance, and Acceptable Use

Customer agrees not to use Revenue AI for any unlawful purposes or in any manner that may violate applicable laws, regulations, or ethical standards. Revenue.io will use commercially reasonable measures to monitor the AI models provided by its AI Subprocessors to mitigate potential biases and ensure fairness. Customer shall not modify, manipulate, or use Revenue AI in a way that contradicts Revenue.io’s ethical guidelines or applicable legal requirements. Both Parties shall cooperate to address any issues related to ethics and compliance.

16. Model Governance, Safety Evaluation, and Risk Management

Revenue.io maintains an AI Governance Program aligned with ISO/IEC 42001, the NIST AI Risk Management Framework, and applicable regulatory and industry standards. Revenue.io performs ongoing safety, quality, and reliability assessments of the Revenue AI system and the GPAI Models it integrates, including testing for bias, hallucinations, toxicity, model drift, adversarial vulnerabilities, and misuse potential.

Revenue.io conducts periodic red-teaming, adversarial testing, technical guardrail evaluations, and Output analysis to identify and mitigate harmful or unsafe behavior. All material model updates, behavioral changes, and Subprocessor-driven modifications are reviewed by Revenue.io’s AI Governance Board prior to deployment into the Revenue AI environment.

17. Termination Rights and Recourse

Either Party may terminate the use of Revenue AI upon written notice if the other Party materially breaches this Addendum or applicable data protection regulations and fails to cure such breach within thirty (30) days of receiving written notice of the breach. In the event of termination due to an uncured breach by Revenue.io, Customer shall have the right to seek recourse through mediation or other legal remedies as specified in the MSA. Conversely, if termination results from a breach by the Customer, Revenue.io reserves the right to suspend or terminate access to the AI services and seek any applicable remedies under the MSA and applicable law.

18. Model Versioning and Change Management

Revenue.io may update, replace, or reconfigure Revenue AI models, model architectures, guardrail mechanisms, or AI Subprocessors at any time. Revenue.io shall notify the Customer of any material change that materially modifies the performance profile, behavior, safety characteristics, or risk posture of Revenue AI. Revenue.io will maintain comprehensive versioning documentation for the Revenue AI system, including GPAI Model version history, configuration changes, and safety evaluation summaries, and shall make such documentation available to the Customer upon reasonable request.

Where legally required, or where a material change imposes a new compliance obligation on the Customer, the Customer may request exclusion from newly introduced AI functionality in Revenue AI. Revenue.io will, subject to applicable technical limitations, restrict and exclude Customer’s access to such new AI functionality until Customer requests that such restriction and exclusion be terminated.

19. Feedback, Updates, and Continuous Improvement

Revenue.io is committed to the continuous improvement of its AI technologies and welcomes feedback from the Customer. Feedback may be reviewed by Revenue.io’s AI Governance Board to identify opportunities for enhancement. This Addendum may be reviewed and updated annually or as required to reflect changes in AI practices, legal requirements, or industry standards. Updates will be communicated to the Customer in a timely manner. By continuing to use the Revenue AI, Customer accepts all updates to this Addendum.

20. AI Incident Reporting

Revenue.io shall notify the Customer without undue delay upon becoming aware of any AI-related incident that results in materially harmful, unsafe, or anomalous Outputs; materially compromises the safety, robustness, or expected behavior of Revenue AI; results from misuse of Revenue AI; or materially impacts the confidentiality, integrity, or availability of Customer Data processed through Revenue AI.

The Customer shall promptly notify Revenue.io of any suspected harmful Outputs, unusual behavior, or regulatory concerns arising from its use of Revenue AI. The Parties shall cooperate in good faith to assess, mitigate, and remediate any AI incidents.

21. AI Safety Contact

Revenue.io shall maintain a designated AI Safety and Compliance contact point for escalation of AI-related safety concerns, Output anomalies, regulatory inquiries, or model behavior issues. Revenue.io’s current contact for AI safety matters is: privacy@revenue.io. Revenue.io will provide and update contact information as necessary.

22. Privacy and Related Policies

This Addendum shall be read in conjunction with Revenue.io’s Global Privacy Policy, Master Services Agreement, and DPA. For more information on how Revenue.io handles data and its commitment to privacy, please refer to our Global Privacy Policy, Cookie Notice, Master Services Agreement, and our Data Processing Addendum.

Google API Services Compliance: For detailed terms governing Revenue.io’s access to, use of, storage of, and sharing of Google Workspace data obtained via Google APIs, including the Limited Use disclosure, please refer to Section 2.6 of the MSA and Section 2 of the Global Privacy Policy. The restrictions on Google API Data described in this Addendum are required by and consistent with the Google API Services User Data Policy.

23. Intellectual Property

Revenue.io owns all rights to Revenue AI features and functionality and all intellectual property rights therein. Customer owns all Inputs and Outputs. No other rights are granted except as specified herein and no rights are implied or granted by estoppel.

24. Indemnification

In addition to Customer’s indemnity obligations set forth in the MSA, Customer shall indemnify, defend and hold harmless Revenue.io from and against any and all claims, costs, damages, losses, liabilities and expenses (including reasonable attorneys’ fees and costs) arising out of or in connection with any claim brought against Revenue.io by a third party:

• (a) alleging that Customer, or any of its employees, agents or subcontractors, infringes such third party’s copyright, patent, trademark or trade secret rights in providing any Input
• (b) that arises out of or relates to access or use of, or inability to access or use, the Revenue AI by Customer or any of its employees, agents and subcontractors
• (c) Customer’s use of the Revenue AI for any High Risk Use or Unacceptable Risk Use
• (d) Customer’s failure to comply with this Addendum
• (e) arising from claims that could have been avoided if Customer had independently validated synthetic data and Outputs
• (f) Customer’s reliance on synthetic data or Outputs for regulatory, legal, employment, financial, compliance, safety-critical processes or accuracy-sensitive use cases without conducting independent verification
• (g) Customer’s reliance on Outputs as the exclusive basis for decisions that produce legal, employment or similarly significant effects on individuals

“High Risk Use” means any uses of Revenue AI that could or does: (i) significantly and negatively impact Revenue.io’s operations or reputation; (ii) significantly and negatively impact intellectual property protections or data security or privacy; (iii) impact the work and lives of Customer’s employees, users, partners, clients, and members of the public; or (iv) present novel or significant legal, compliance, or enterprise risks.

“Unacceptable Risk Use” means any use of Revenue AI that: (i) could have or actually has an effect on the access of an individual to employment or in a manner that could affect an individual’s rights under applicable AI laws; (ii) could lead or cause bias or discrimination; or (iii) lead to errors, omissions or other risks that have the potential to impact safety, fundamental rights of natural persons or affect the safety of tangible or physical property. This includes prohibited uses as defined under the EU AI Act.

25. Disclaimer

Revenue.io does not guarantee, and does not and is not obligated to verify, authenticate, monitor or edit Customer Data, including the Inputs, or any other Customer Data into or stored in the Revenue AI for completeness, integrity, quality, accuracy or otherwise. Customer shall be responsible and liable for the completeness, integrity, quality and accuracy of Input into Revenue AI.

Customer is solely responsible to ensure that all Output is checked and validated, that they are fit for Customer’s purpose and that they are in compliance with applicable laws prior to their use. Further, due to the nature of AI, the Output may not be unique across users and the Revenue AI services may generate or return the same or similar Output to other customers or a third party. If Customer provides Revenue.io with written notice or otherwise decides that Customer no longer desires to use Revenue AI, Revenue.io is not required to retain any Inputs or Outputs used or otherwise processed in connection with the Revenue AI service.

IN ADDITION TO THE WARRANTY DISCLAIMERS IN THE MSA, REVENUE.IO DOES NOT MAKE, AND HEREBY DISCLAIMS, ANY AND ALL OTHER EXPRESS, STATUTORY AND IMPLIED REPRESENTATIONS AND WARRANTIES, INCLUDING, BUT NOT LIMITED TO, WARRANTIES OF QUALITY, SUITABILITY, OPERABILITY, CONDITION, SYSTEM INTEGRATION, NON-INTERFERENCE, WORKMANSHIP, TRUTH, ACCURACY (OF DATA OR ANY OTHER INFORMATION OR CONTENT), ABSENCE OF DEFECTS, WHETHER LATENT OR PATENT, AND ANY WARRANTIES ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE. CUSTOMER UNDERSTANDS AND AGREES THAT ANY SUCH INFORMATION OBTAINED THROUGH USING REVENUE AI IS AT CUSTOMER’S SOLE RISK. CUSTOMER MUST NOT RELY ON FACTUAL ASSERTIONS IN OUTPUT WITHOUT INDEPENDENT FACT-CHECKING, AND CUSTOMER MUST NOT RELY ON WORKFLOWS/PROCESSES OR WORK INSTRUCTIONS IN OUTPUT WITHOUT INDEPENDENT REVIEW OF FUNCTIONALITY AND SUITABILITY FOR CUSTOMER’S NEEDS. NO SUCH INFORMATION, SUGGESTIONS, OR OUTPUT, OBTAINED BY CUSTOMER FROM THE REVENUE AI SERVICE SHALL CREATE ANY WARRANTY NOT EXPRESSLY MADE HEREIN.

26. Export Controls

Revenue AI and any associated technologies, including Outputs derived from the use of third-party GPAI Models, may be subject to U.S. export control laws, EU dual-use regulations, and other international restrictions. The Customer shall not export, re-export, transfer, or make available Revenue AI or any Output in violation of applicable export control, sanctions, or national security laws. The Customer remains solely responsible for compliance with all cross-border restrictions arising from its deployment or use of Revenue AI.

27. Governing Law and Jurisdiction

This Addendum shall be governed by and construed in accordance with the laws specified in the MSA. Any disputes arising out of or in connection with this Addendum shall be subject to the exclusive jurisdiction of the courts stipulated in the MSA.

© Revenue, Inc. (Revenue.io). All rights reserved.