Ranking
The vendor's agreements were benchmarked against thousands of vendor forms and are in the top 10% 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 10% IT contract. No structural blockers. Procurement-ready.
Contract Performance
Start with a quick risk summary, then compare this agreement to similar contracts.
Insurance
Insurance requirements
- Bitsight must carry general liability insurance
- Bitsight must carry workers' compensation insurance
- Bitsight must carry automobile insurance
- Bitsight must carry professional liability insurance
- Bitsight must carry errors and omissions insurance
- Bitsight must carry umbrella liability insurance
- Bitsight must carry data related insurance
Summary
Liability cap
- Bitsight's liability is capped at 12 months' fees
- There is no secondary cap on Bitsight'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
- Claims related to gross negligence or recklessness are excluded from the cap on Bitsight's liability
- Claims related to fraud or willful misconduct are excluded from the cap on Bitsight's liability
- Claims related to violations of obligations relating to confidential information are excluded from the cap on Bitsight's liability
- Indemnification obligations relating to IP infringement are excluded from the cap on Bitsight's liability
- Claims related to gross negligence and/or recklessness are excluded from the cap on Customer's liability
- Claims related to fraud and/or willful misconduct are excluded from the cap on Customer's liability
- Claims related to violations of obligations relating to confidential information are excluded from the cap on Customer's liability
- Claims related to Customer's use of the service, violations of an acceptable use policy or other restrictions or responsibilities are excluded from the cap on Customer's liability
- At least some indemnification obligations (other than relating to data or IP infringement) are excluded from the cap on Customer's liability
Excluded damages
- One or more forms of indirect damages are excluded from Bitsight's liability
- One or more forms of indirect damages are excluded from Customer's liability
Exceptions to excluded damages
- The damages excluded from Bitsight's liability do not include claims related to gross negligence or recklessness
- The damages excluded from Bitsight's liability do not include claims related to fraud or willful misconduct
- The damages excluded from Bitsight's liability do not include claims related to violations of obligations relating to confidential information
- The damages excluded from Bitsight's liability do not include indemnification obligations relating to IP infringement
- The damages excluded from Customer's liability do not include claims related to gross negligence or recklessness
- The damages excluded from Customer's liability do not include claims related to fraud and/or willful misconduct
- The damages excluded from Customer's liability do not include claims related to violations of obligations relating to confidential information
- The damages excluded from Customer's liability do not include claims related to Customer's use of the service, violations of an acceptable use policy or other restrictions or responsibilities
- The damages excluded from Customer's liability do not include at least some indemnification obligations (other than relating to data or IP infringement)
Timing of claims
- There are no limits on when claims must be brought by Customer
- There are no limits on when claims must be brought by Bitsight
Claims
- Bitsight indemnifies Customer for claims based on third-party IP infringement
- Customer indemnifies Bitsight for claims arising from violation of laws
Scope of obligations
- Bitsight's IP indemnification covers all types of IP
- Bitsight's indemnification obligations are the exclusive remedy for indemnified claims
- Bitsight's indemnification includes the obligation to provide a defense
- Bitsight's indemnification does not include the obligation to hold harmless
- Customer's indemnification obligations are limited to third-party claims
- Customer's indemnification obligations are not the exclusive remedy for indemnifiable claims
- Customer's indemnification includes the obligation to provide a defense
- Customer's indemnification includes the obligation to hold harmless
Limitations, conditions, or exclusions
- Obligations include conditions regarding Customer's cooperation or Bitsight's control of the defense
- Obligations include conditions regarding Customer's use of the services in breach of the contract
- Bitsight's IP indemnity does not cover claims resulting from modifications, combinations, or use of an outdated version of the service
- Bitsight's indemnity obligations include conditions regarding settlements
- There are time constraints on when Customer must notify Bitsight of an indemnifiable claim
- Customer's indemnification obligations are not subject to conditions and/or exclusions
Warranties Offered
SLAs
- Bitsight offers an SLA regarding uptime
- The specified remedy for Bitsight's violation of the uptime SLAs is credit or refunds
- The specified remedy for Bitsight's violation of an uptime SLA is the exclusive remedy
- Bitsight offers some other form of SLA
- There is no specified remedy for Bitsight's violation of the other form of SLA
Implied warranties
- Bitsight disclaims some or all implied warranties
Data Rights
Data provided by Customer
- Bitsight does not claim ownership of any data provided by Customer
- Bitsight receives rights to use data provided by Customer for its internal business purposes
- Bitsight receives rights to use data provided by Customer to comply with applicable law
- Bitsight receives rights to use data provided by Customer to the extent it is anonymized
- Bitsight receives rights to share data provided by Customer with third parties who may only use it to provide or improve the services
- Bitsight receives rights to use data provided by Customer for marketing purposes
Data Security
Subprocessor obligations
- The contract lists or references a list of some subprocessors
- Bitsight is required to ensure that subprocessors are bound by data or privacy requirements similar to those in this contract
Security commitments
- Bitsight makes contractually binding data security commitments
Third party audits, standards, or certifications
- Bitsight commits to comply with at least one third-party data security audit, standard, or certification
- Bitsight commits to Soc 2 audits
- Bitsight commits to ISO 27001 standards and/or certification
- Bitsight commits to complying with one or more NIST frameworks
- There are no qualifications and/or limitations to Bitsight's commitments to comply with third-party data security audits, standards, or certifications
Data breach notification policy
- Bitsight commits to notifying Customer of a security breach impacting Customer's data
Summary
Vendor's confidential information
- Customer must provide some protection of Bitsight's confidential information
Customer's confidential information
- Bitsight must provide some protection of Customer's confidential information
- Bitsight explicitly commits not to disclose Customer's confidential information, except as necessary to provide the services
- Bitsight 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
- Bitsight warrants that the services will comply with certain documentation and/or specifications, but the warranty has some conditions or qualifications
Other warranties
- Bitsight 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
- Bitsight does not reserve the right to bill Customer for any expenses incurred by Bitsight
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 has auto-renew language, but Customer may opt out
- The contract has auto-renewal language and Customer may opt out by giving less than or equal to 45 days' notice
Vendor's termination and suspension rights
- Bitsight does not receive the right to terminate the contract for convenience
- Customer has between 11 and 30 days to cure a breach before Bitsight can terminate for cause
- Bitsight may suspend Customer's access to the service for reasons TermScout was unable to classify - see citation
Customer's IP
Licenses to Customer IP
- Bitsight receives a right to Customer's suggestions and/or feedback
- Bitsight receives the right to use Customer's name and/or marks publicly
Publicity rights
- Bitsight's use of Customer's name and/or marks is not subject to Customer's guidelines
Assignment of Customer IP or work product
- Customer does not assign any work product or other IP to Bitsight
Warranties Offered
Other warranties
- Bitsight provides warranties regarding its authority to enter into this contract and/or the validity of this contract
Summary
Non-compete
- There are no restrictions on Customer's ability to compete as long as Customer doesn’t violate the agreement or use the services to compete
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
- Bitsight is allowed to assign in the event of a merger or acquisition
- Bitsight is allowed to assign in the event of a corporate reorganization
- There are consent requirements restricting Bitsight's ability to assign the contract
- Consent requirements do not apply in the event of a merger or acquisition
- Consent requirements apply to Bitsight's assignment rights in the event of a corporate reorganization
- There are no notice requirements restricting Bitsight's ability to assign the contract
- There are no restrictions or conditions on Bitsight'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 apply to Customer's assignment rights 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 Bitsight
Access the complete methodology and detailed breakdown by
downloading the full report for in depth insights
Frequently Asked Questions
Find quick answers to the most common questions about our platform, process, and agreements.
Legal teams often escalate agreements when confidentiality obligations contain broad operational exceptions, weak restrictions on internal sharing, or unclear protections for security-related telemetry and incident data. Additional scrutiny is common when vendors reserve expansive rights to disclose customer information for service improvement, analytics, or subcontractor support purposes. Enterprise buyers increasingly expect confidentiality frameworks to align with the operational sensitivity of the environments the vendor will access.
Buyers generally evaluate confidentiality language against the vendor’s level of infrastructure access, handling of sensitive information, and operational role within the customer environment. Agreements tend to appear more market aligned when restrictions on use, disclosure, retention, and downstream access are clearly defined and operationally enforceable. Contracts may create friction when confidentiality protections rely heavily on discretionary vendor policies rather than negotiated contractual commitments.
Approval delays frequently occur when confidentiality provisions conflict with broader data usage rights, audit limitations, or incident reporting obligations elsewhere in the agreement. Legal and security teams also pay close attention to whether the vendor can reuse operational information across shared systems or affiliated services. Inconsistent drafting across the master agreement, DPA, and security documentation often signals governance complexity that requires additional internal review before approval.
Confidentiality terms increasingly affect incident response coordination, access management, vendor oversight, regulatory exposure, and long-term trust management. Enterprise buyers therefore assess whether the agreement creates a workable operational framework for handling sensitive business and security information over time. Contracts that narrowly define obligations or leave critical handling practices ambiguous can create uncertainty around accountability after deployment, especially in complex enterprise environments involving multiple vendors and subprocessors.
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 Main Subscription Terms and Conditions ("TAC") for BITSIGHT TECHNOLOGIES, 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.
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 TAC for Bitsight and any documents specifically listed under 'Scope of Review'. For purposes of this report, "Customer" means the party contracting with Bitsight and "Vendor" means Bitsight.
References herein to the "Agreement" are to the following documents:
- The Primary Document: Main Subscription Terms and Conditions ("TAC")
- The following Secondary Document(s) expressly incorporated by reference into the Primary Document and reviewed by TermScout as part of this analysis:
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.
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