Ranking
The vendor's agreements were benchmarked against thousands of vendor forms and are in the top 5% for customer favorability.
80% customer favorability, based on 750 plus contract signals powered by Certify.
Indicates balanced, low-risk terms favorable to the customer.
Top 5% IT contract. No structural blockers. Procurement-ready.
Risk Summary
A concise snapshot of key risks, their impact, and priority concerns.
Insurance
Insurance requirements
- ReliaQuest must carry general liability insurance
- ReliaQuest must carry workers' compensation insurance
- ReliaQuest must carry automobile insurance
- ReliaQuest must carry professional liability insurance
- ReliaQuest must carry errors and omissions insurance
- ReliaQuest must carry data related insurance
- ReliaQuest must carry some other form of insurance TermScout was unable to classify - see citation
Summary
Liability cap
- ReliaQuest's liability is capped at 12 months' fees
- There is no secondary cap on ReliaQuest's liability
- Customer's liability is capped at 12 months' fees
- There is no secondary liability cap on Customer's liability
Exceptions to the liability cap
- There are no exceptions to ReliaQuest's liability cap
- There are no exceptions to Customer's liability cap
Excluded damages
- One or more forms of indirect damages are excluded from ReliaQuest's liability
- One or more forms of indirect damages are excluded from Customer's liability
Exceptions to excluded damages
- The damages excluded from ReliaQuest's liability do not include claims related to fraud or willful misconduct
- The damages excluded from ReliaQuest's liability do not include indemnification obligations relating to IP infringement
- The damages excluded from Customer's liability do not include claims related to fraud and/or willful misconduct
Timing of claims
- Claims against ReliaQuest must be brought by Customer in less than or equal to 18 months
- There are no limits on when claims must be brought by ReliaQuest
Claims
- ReliaQuest indemnifies Customer for claims based on third-party IP infringement
- Customer does not indemnify ReliaQuest for any claims
Scope of obligations
- ReliaQuest's IP indemnification covers all types of IP
- ReliaQuest's indemnification obligations are the exclusive remedy for indemnified claims
- ReliaQuest's indemnification includes the obligation to provide a defense
- ReliaQuest's indemnification does not include the obligation to hold harmless
Limitations, conditions, or exclusions
- Obligations include conditions regarding Customer's cooperation or ReliaQuest's control of the defense
- Obligations include conditions regarding Customer's use of the services in breach of the contract
- ReliaQuest's IP indemnity does not cover claims resulting from modifications, combinations, or use of an outdated version of the service
- ReliaQuest's indemnity obligations include conditions regarding settlements
- There are time constraints on when Customer must notify ReliaQuest of an indemnifiable claim
- Conditions or exclusions to ReliaQuest's indemnification obligations that TermScout was unable to classify - see citation
Warranties Offered
SLAs
- ReliaQuest does not offer an SLA regarding uptime
- ReliaQuest does not offer any other form of SLA
Other warranties
- ReliaQuest warrants that the services will meet specified standards of care or conduct
Implied warranties
- ReliaQuest disclaims some or all implied warranties
Data Rights
Data provided by Customer
- ReliaQuest does not claim ownership of any data provided by Customer
- ReliaQuest receives rights to use data provided by Customer to the extent it is anonymized
Data Security
Subprocessor obligations
- The contract lists or references a list of some subprocessors
- ReliaQuest is required to ensure that subprocessors are bound by data or privacy requirements similar to those in this contract
Security commitments
- ReliaQuest makes contractually binding data security commitments
Third party audits, standards, or certifications
- ReliaQuest commits to comply with at least one third-party data security audit, standard, or certification
- ReliaQuest commits to Soc 2 audits
- ReliaQuest commits to ISO 27001 standards and/or certification
- ReliaQuest commits to some other audits, standards, or certifications which TermScout was unable to classify - see citation
- There are no qualifications and/or limitations to ReliaQuest's commitments to comply with third-party data security audits, standards, or certifications
Data breach notification policy
- ReliaQuest commits to notifying Customer of a security breach impacting Customer's data
Summary
Vendor's confidential information
- Customer must provide some protection of ReliaQuest's confidential information
Customer's confidential information
- ReliaQuest must provide some protection of Customer's confidential information
- ReliaQuest explicitly commits not to disclose Customer's confidential information, except as necessary to provide the services
- ReliaQuest explicitly commits not to use Customer's confidential information, except as necessary to provide the services
Mutuality
- All commitments concerning confidential information are mutual
Residuals clause
- There is no residuals clause
Warranties Offered
Compliance with documentation/specifications
- ReliaQuest warrants that the services will comply with certain documentation and/or specifications, but the warranty has some conditions or qualifications
Other warranties
- ReliaQuest provides warranties regarding malware, malicious code, spyware, viruses, or similar
Payment Terms
Late payment penalties
- There are no penalties for late payments
Payments due
- Customer's payment terms are either less than 30 days or not specified in the Agreement
Vendor's expenses
- ReliaQuest does not reserve the right to bill Customer for any expenses incurred by ReliaQuest
Summary
Customer's termination rights
- Customer has certain rights to terminate for cause
Refunds
- Customer's termination rights include the right to a refund
Auto-renewal
- The contract and/or any order under it does not auto-renew
Vendor's termination and suspension rights
- ReliaQuest does not receive the right to terminate the contract for convenience
- Customer has greater than 30 days to cure a breach before ReliaQuest can terminate for cause
- ReliaQuest may suspend Customer's access to the service for material breach of the contract
- ReliaQuest may suspend Customer's access to the service for payment-related issues
- ReliaQuest may suspend Customer's access to the service for violation of ReliaQuest's policies and/or guidelines
- ReliaQuest may suspend Customer's access in order to prevent material harm
Customer's IP
Licenses to Customer IP
- ReliaQuest receives a right to Customer's suggestions and/or feedback
Assignment of Customer IP or work product
- Customer does not assign any work product or other IP to ReliaQuest
Summary
Non-compete
- There are no restrictions on Customer's right to compete with ReliaQuest
Non-solicit
- There are no restrictions on Customer's right to solicit
Exclusivity
- There are no restrictions on Customer's ability to procure similar products or services from other vendors
Vendor's assignment rights
- ReliaQuest is allowed to assign in the event of a merger or acquisition
- ReliaQuest is allowed to assign in the event of a corporate reorganization
- There are consent requirements restricting ReliaQuest's ability to assign the contract
- Consent requirements do not apply in the event of a merger or acquisition
- Consent requirements do not apply in the event of a corporate reorganization
- There are no notice requirements restricting ReliaQuest's ability to assign the contract
- There are no restrictions or conditions on ReliaQuest's right to assign to a competitor of Customer
Customer's assignment rights
- Customer is allowed to assign in the event of a merger or acquisition
- Customer is allowed to assign in the event of a corporate reorganization
- There are consent requirements restricting Customer's ability to assign the contract
- Consent requirements do not apply in the event of a merger or acquisition
- Consent requirements do not apply in the event of a corporate reorganization
- There are no notice requirements restricting Customer's ability to assign the contract
- There are no restrictions or conditions on Customer's right to assign to a competitor of ReliaQuest
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 Platform and Support Agreement - 01/2026 ("PSA") for ReliaQuest, LLC. 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.
In order to qualify for Certification, a contract must meet the following criteria:
- Achieve a TermScout rating of Balanced or Customer Favorable, and
- Be free of all designated Deal Breaker clauses.
The difference between certified Balanced and certified Customer Favorable is the TermScout favorability rating achieved by the contract. Each of these criteria is more fully described below.
A contract is balanced when it allocates risks between the parties in a roughly equal manner, as determined by TermScout's two-step, data-driven analysis. First, we use our proprietary AI to abstract over 750 defined data points from each contract we analyze. Then, we use an algorithm to objectively score that data. Because TermScout looks at the exact same set of data points and uses the exact same scoring algorithm in every contract analysis we conduct, you can now compare contracts on an apples-to-apples basis. (You can read more about the data points that TermScout analyzes in every IT contract here.)
This enables us to objectively rate contracts at both the agreement level and by key topic area (e.g., limitations of liability, indemnification, warranties, etc.) and show you which contracts are vendor favorable, which are customer favorable, and which are balanced.
Not all risks are created equal. Even if a contract shifts only a single risk to the buyer, the contract still may not merit certification if that risk is material enough. Examples of these types of Deal Breakers include exclusivity, complete disclaimers of liability, etc. Accordingly, TermScout will not certify a contract if it contains any of the following Deal Breaker clauses,² which TermScout identified by reference to market data and input from prominent buy-side and sell-side legal experts from TermScout's Innovation Advisory Council:
This makes it nearly impossible for a customer to recover from a vendor, no matter what goes wrong - even if the vendor violates other provisions of the contract.
Signing non-competes means contractually promising not to engage in a certain line of business. This is something most businesses want to avoid where possible.
Agreeing not to solicit a vendor's employees, customers, or vendors sounds reasonable, but it places challenging burdens on the customer to ensure they comply.
Agreeing not to procure similar services from other companies can severely hinder a company's ability to do business.
Privacy laws require companies to follow strict rules with respect to how they handle certain types of data. This clause presents major risks to a company's ability to comply with such laws.
It's extremely rare for a customer to need to assign IP rights to an IT vendor. Doing so can materially jeopardize a company's rights in its own IP.
Since most IT services today are delivered "as a service", customers often upload wide varieties of information onto vendors' servers. Confidentiality commitments are expected by most customers.
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.
- Comparable Contracts: We'll show a list of contracts sorted by favorability ratings and allow for the comparison of similar contracts based on position, industry, and contract type.
- 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.
Certified Contract Reports contain only a subset of the above data. To access all of the data available, create a free account here and search for the desired contract in Triage.
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 PSA for ReliaQuest and any documents specifically listed under 'Scope of Review'. For purposes of this report, "Customer" means the party contracting with ReliaQuest and "Vendor" means ReliaQuest.
References herein to the "Agreement" are to the following documents:
- The Primary Document: Platform and Support Agreement - 01/2026 ("PSA")
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.
Documents that do not form part of the Agreement:
TermScout could not find any clear language stating that these documents are incorporated by reference into the Primary Document. Documents that are not incorporated into a contract by reference may not be contractually binding; therefore, they were not reviewed by TermScout.
The TermScout review does not include the Beta Terms.
Frequently Asked Questions
Find quick answers to the most common questions about our platform, process, and agreements.
IT and procurement teams frequently escalate agreements when the contractual security obligations do not match the operational assurances presented during the sales or security assessment process. Escalation is common when contracts lack measurable commitments around incident response, vulnerability management, access controls, or subprocessor oversight. Enterprise buyers increasingly expect the negotiated agreement itself to reinforce the vendor’s stated security posture rather than relying solely on external policies or certifications.
Procurement delays often occur when agreements allow vendors broad discretion to change security practices without customer notice or when core operational obligations are fragmented across multiple external documents. Buyers also react cautiously to contracts that narrowly define breach notification obligations, limit audit cooperation, or disclaim responsibility for subcontracted environments. These issues can complicate internal governance reviews because the operational risk becomes difficult to evaluate consistently across legal, security, and procurement stakeholders.
Buyers typically compare contractual commitments against the sensitivity of the systems, data, and workflows involved. Agreements tend to appear more market aligned when they include clear operational standards, transparent escalation procedures, reasonable audit support, and enforceable incident response obligations. Contracts become harder to approve when critical security responsibilities are described vaguely or reserved entirely to vendor discretion. Consistency between contractual terms and actual operational practices is often treated as a key trust signal.
Enterprise review teams often flag agreements that disclaim meaningful accountability for security failures while simultaneously restricting customer oversight rights. Additional concern arises when vendors reserve broad rights to modify controls, limit breach disclosures, or avoid commitments tied to remediation timelines. Buyers may also interpret fragmented or heavily conditional security obligations as indicators of governance immaturity. Agreements that shift operational uncertainty onto the customer typically generate more negotiation friction and slower approval cycles.
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