Ranking
The vendor's agreements were benchmarked against thousands of vendor forms and are in the top 33% for customer favorability.
70% customer favorability, based on 750 plus contract signals powered by Certify.
Indicates balanced, low-risk terms favorable to the customer.
Top 33% DPA contract. No structural blockers. Procurement-ready.
Risk Summary
A concise snapshot of key risks, their impact, and priority concerns.
Data Handling
Data ownership
- Moody's does not claim any ownership of any data provided by Customer
Data usage
- Moody's does not anonymize or pseudonymize personal data that is used beyond what is necessary to provide services to Customer
- Moody's commits to processing data solely as specified in the DPA, underlying agreement and/or on documented instructions from Customer
Data transfer frequency
- The frequency of the data transfer is not addressed in the contract
Data accuracy
- Moody's is not required to ensure accuracy of Customer data
- Moody's is not required to notify Customer of inaccurate data
Subprocessors
Subprocessor obligations
- There is a list of subprocessors included in the contract
- Moody's commits to ensuring that its subprocessors will be bound to the same or substantially similar data or privacy requirements as those contained in the contract
- Moody's is responsible for the acts or omissions of its subprocessors
Subprocessor authorization
- The DPA does not allow for general subprocessor authorization
Subprocessor objection
- The contract allows for the Customer to object to new subprocessors
- Customer has the option to terminate the contract if the parties cannot resolve a subprocessor objection
Summary
Data types
- The processing of sensitive data is explicitly excluded in the contract
- Individual identifiers may be processed under the contract
- Customer records may be processed under the contract
- Electronic network information may be processed under the contract
- Professional or employment related information may be processed under the contract
Data subjects
- Employees are present as data subjects in the contract
- Some other category is present as data subjects in the contract that TermScout was unable to identify - see citation
Incorporated documents
- The DPA is incorporated into the master agreement by reference
Transfer and Use Restrictions
Cross-Border details
- It is not required for data to stay in one or more defined country
- Moody's is not restricted from transferring the data to certain countries or regions
- Moody's does not commit to only allowing employees or personnel to access or process data in one or more specified countries
Selling information
- Moody's explicitly commits to not sell personal information
Retaining information
- Moody's is prohibited from retaining, using, or disclosing personal information except for the defined purpose
Combining information
- Moody's is not prohibited from combining Customer's personal information with other businesses' personal information
Requirements to anonymize
- There is no requirement that Moody's must take reasonable measures to ensure that de-identified information cannot be used to identify a specific individual or Customer
- Moody's does not commit to not re-identify personal information
Audit Rights
Customer's rights
- Customer's audit rights do not include access to Moody's' systems
Audit payment
- The contract does not address who is responsible for costs of the audit
Compliance with Laws
Supplier's commitments
- Moody's commits to complying with laws that TermScout is unable to classify - see citation
- Moody's commits to complying with the GDPR
- Moody's commits to complying with the CCPA
- Moody's commits to complying with some data privacy law TermScout is unable to classify - see citation
- Moody's commits to aiding Customer in complying with applicable laws
Customer's commitments
- Customer commits to complying with the GDPR
- Customer commits to complying with data and/or privacy laws that TermScout is unable to classify - see citation
Notifications and Third-Party Requests
Third party request requirements
- Moody's will notify Customer more than 72 hours from a request for data from third parties
- Moody's is not only required to respond to a request for data from third-parties if they find it to be valid and binding
- If Moody's is prohibited by law from providing notice to Customer of a request for data Moody's is not required seek an injunction and/or leave to notify Customer
- There is not a requirement that Moody's act in good faith to ensure confidentiality is afforded to any data they are compelled to share, and that they limit the scope of sharing
Data subject request requirements
- Moody's is required to assist Customer in responding to data subject requests
- There is not a requirement that assistance provided in responding to data subject requests be at Customer's expense
- There is explicit language prohibiting Moody's from responding to a data subject request unless agreed to or requested by Customer
Complaint requirements
- Moody's is required to notify Customer of a third-party complaint regarding the processing of personal information
- Moody's is not required to assist Customer in responding to third-party complaints
Compliance notification
- Moody's is required to notify Customer if there is reason to believe it will no longer be able to comply with any of its obligations under the contract
Summary
Safeguards
- Moody's commits to safeguards for the protection of Customer's data in the contract
- Moody's commits to technical controls
- Moody's commits to organizational controls
- Moody's commits to use controls
- Moody's commits to distribution controls
- Moody's commits to administrative controls
- Moody's commits to physical controls
- Moody's commits to personnel training safeguards
Return or destruction obligations
- Data must be returned or destroyed upon termination
- Customer has the right to elect return or destruction of the data
Retention policies
- The data retention period is not described in the contract
Standards
- Moody's commits to comply with at least one third party data security audit, standard, or certification
- Moody's commits to Soc 1 audits
- Moody's commits to Soc 2 audits
- Moody's commits to some other audits, standards, or certifications which TermScout was unable to classify - see citation
Data breach
- Moody's must notify Customer of a data breach in a time frame TermScout was unable to classify - see citation
- Moody's is required to assist Customer in responding to a data breach
- The assistance provided by Moody's in the event of a data breach will not be at Customer's expense
- Moody's is required to assist Customer with data protection impact assessments, privacy questionnaires or assessments, and/or consultations with relevant authorities
Summary
SCC
- As it relates to the Standard Contractual Clauses, it is not possible to ascertain which party is the data importer and which is the data exporter
- No flowdown clauses are referenced in the DPA
Indemnification
Customer's indemnification obligations
- Customer does not offer any indemnities to Moody's
Supplier's indemnification obligations
- Moody's does not offer any indemnities to Customer
Limitation of Liability
Supplier's liability
- The DPA does not reference a limit on Moody's' liability
- The DPA does not reference a limit on Moody's' liability
Customer's liability
- The DPA does not reference a limit on Customer's liability
- The DPA does not reference a limit on Customer's liability
Summary
Supplier's termination rights
- Moody's does not have termination rights
Customer's termination rights
- Customer can terminate for cause
Termination rights
- Moody's is required to continue its data protection/confidentiality obligations beyond expiration or termination of an agreement for so long as Customer data is retained
Data processing term
- The duration of the data processing is the duration of the provision of the services
Access the complete methodology and detailed breakdown by
downloading the full report for in depth insights
Why this Matters
See value, risks, and position at a glance for better decisions.
How TrustMark™ Works?
Data Extraction
Scans and converts legal text into structured data.
Objective Scoring
Clauses benchmarked against market data.
Deal Breakers
Risks and non-negotiables flagged early.
Benchmarking
Compares your contract to market standards.
Certification
Contract validated after meeting risk and score thresholds.
Based on 750 plus contract signals benchmarked against market data.
Certified Contract Reports, Explained
Verified™ contract reviews are reviews of contracts that have been carefully checked by contract experts. This review is designed to help users understand the rights and obligations associated with the Data Processing Schedule ("DPS") for Moody’s Analytics, Inc.. We looked at the issues found in 'Term Sheets' and did not look for any other issues.
For more information on TermScout's contract review process, visit our methodology page.
Not all data protection and compliance risks are created equal. Even a single provision in a Data Processing Agreement that materially increases regulatory, security, or liability risk for either party may render the agreement ineligible for certification. TermScout evaluates DPAs against objective standards intended to reflect widely accepted Controller-Processor practices and prevailing data protection requirements. Accordingly, TermScout will not certify a DPA if it contains any provision that fails to meet the following standards. Any DPA that reflects the inverse of one of these standards will be treated as a Deal Breaker:
Failing to require breach notification prevents the Customer from meeting legal obligations to regulators and data subjects. Without timely notice, the Customer may face regulatory penalties, reputational harm, and an inability to respond appropriately to a security incident.
Without a clear description of the nature and purpose of processing, the Vendor may process data in ways the Customer did not intend or authorize. This increases regulatory risk and undermines the Customer's ability to demonstrate lawful and limited processing.
Allowing a Vendor to claim ownership over Customer data creates significant legal and compliance risks. Customers are typically required by law to retain control over personal data, and ownership claims can conflict with privacy, security, and data subject rights obligations.
If a Vendor is permitted to process data outside documented Customer instructions, the Customer loses control over how personal data is used. This can lead to unauthorized processing and regulatory violations for which the Customer remains responsible.
Without explicit commitments to security safeguards, the Customer has limited assurance that personal data will be adequately protected. This increases the risk of data breaches and may prevent the Customer from complying with security requirements under applicable privacy laws.
If the Vendor can disclose data to third parties without notifying the Customer, the Customer may be unable to challenge or respond to those requests. This undermines transparency and can result in unlawful disclosures of personal data.
Failing to notify the Customer of data subject requests prevents the Customer from meeting statutory response obligations. This can lead to missed deadlines, regulatory penalties, and violations of data subject rights.
If audit rights are restricted or prohibited, Customers lack a meaningful way to verify compliance with data protection obligations. This limits oversight and weakens accountability, particularly where the Vendor processes sensitive or regulated data.
Allowing subprocessors to operate under weaker standards exposes Customer data to uncontrolled risk. Customers remain responsible for downstream processing, and inconsistent obligations can result in compliance failures outside the Customer's direct control.
The goal of TermScout's reports is to provide users with the data necessary to make an informed decision about whether they can accept the terms. The data provided in TermScout's reports includes:
- Term Sheet: A full report of the key rights and obligations contained in the agreement.
- Overall Ratings: TermScout's overall impression of the favorability of the contract vis a vis the parties. These ratings are algorithmic approximations of favorability that are based on market data and the subject views of contract experts with experience in the specific type of contract.
- Rare Clause Radar: TermScout identifies and surfaces a list of the most rare and material clauses that favor your counterparty.
- Playbooks: Playbooks are a way of programming into TermScout's software a specific set of acceptance criteria for a contract type. All accounts have access to sample Playbooks for select templates, and Pro accounts have the ability to build custom Playbooks.
- Market Data: Any right or obligation in a contract can be compared to market data for similar contract types, including data from TermScout's Contract Market Database™ of thousands of public contracts and anonymized and aggregated data from hundreds of negotiated contracts.
Please note that this report focuses on the identification of terms from the contract documents listed under 'Scope of Review' and compares them against a defined set of criteria. Certain services may be subject to additional terms not available to TermScout, such as purchase orders and other deal-specific documents. You should always review the terms associated with the specific service you are using and know that TermScout's ratings generally do not cover (a) services purchased through a reseller, (b) offline variants of any of the Agreements, (c) service-specific terms that override any of the terms discussed here, or (d) free services. You also should consult your legal counsel if you have any questions about the meaning, significance or assessment of any agreement or provision.
TermScout prepared this report with an average use-case customer in mind and operated under the assumptions listed below (the "Key Assumptions"). To the extent that provisions in a contract vary based on specific circumstances that differ from the Key Assumptions, TermScout ignores those variations. Additional contract-level assumptions, if any, are disclosed in 'Notes to Customer'.
Key Assumptions
- Customer is an average "end user" of the service (i.e. not a partner, distributor, or developer).
- Customer is not a government entity.
- Customer is a US-based company and is using the service in the US.
- Customer is a paying user (i.e. not a user of free services).
- Customer is not using beta services.
- Unless otherwise noted, service-specific terms that may override or supersede the terms of the Agreement are not reviewed by TermScout.
We reviewed the Data Processing Schedule for Moody’s Analytics, Inc.. "Customer" means the party acting as Data Controller, and "Supplier" means the party acting as Data Processor.
References herein to the "Agreement" are to the following documents:
- The Primary Document: Data Processing Schedule ("DPS")
- The following Secondary Document(s) expressly incorporated by reference into the Primary Document and reviewed by TermScout as part of this analysis:
- Descriptions of Processing Data ("DPD")
- Privacy Policy ("PP")
- Information Security Standards Schedule ("ISS")
TermScout did not review any documents other than those listed above. If other documents form part of this Agreement, the answers provided by TermScout may be incomplete or incorrect. TermScout's accuracy commitments only cover documents specifically identified in this section.
No additional notes to customer for this report.
Frequently Asked Questions
Find quick answers to the most common questions about our platform, process, and agreements.
Security and compliance teams often escalate fintech agreements when data processing language does not clearly explain how transaction data, customer financial information, or payment-related records are stored, shared, or retained. Additional scrutiny is common when vendors reserve broad rights to use operational data for analytics or service optimization without clear governance boundaries. Enterprise buyers increasingly expect fintech privacy obligations to align closely with regulatory requirements and internal financial-control frameworks.
Procurement delays frequently occur when agreements contain vague cross-border transfer rights, loosely defined subprocessor permissions, or inconsistent breach-notification obligations. Buyers also react cautiously when DPAs rely heavily on external policies that vendors can modify without customer review. Friction increases when contractual commitments appear weaker than the operational sensitivity of the financial workflows supported by the platform.
Buyers generally compare privacy obligations against the vendor’s operational access to payment information, financial reporting systems, and regulated customer data. Agreements tend to appear more market aligned when they clearly define processing scope, deletion obligations, incident cooperation procedures, and operational accountability across third-party environments. Contracts may attract additional review when data rights remain overly broad or governance responsibilities are operationally unclear.
Enterprise review teams often flag agreements that permit extensive internal reuse of transaction-related data, limit audit visibility into processing environments, or reserve unilateral authority to modify data-handling practices after onboarding. Additional concern arises when contracts narrowly define vendor obligations following privacy incidents or fail to distinguish clearly between operational processing and broader analytics activities. These patterns frequently signal elevated governance and operational risk during enterprise review.
Check If Your Contract
Qualifies for Certification
See how your terms compare to market standards and uncover opportunities to build buyer trust and close deals faster.
Get your Certification Score Now