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.
Risk Summary
A concise snapshot of key risks, their impact, and priority concerns.
Insurance
Insurance requirements
- SailPoint is not required to carry any form of insurance
Summary
Liability cap
- SailPoint's liability is capped at 12 months' fees
- There is no secondary cap on SailPoint'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 SailPoint's liability
- Claims related to fraud or willful misconduct are excluded from the cap on SailPoint's liability
- Indemnification obligations relating to IP infringement are excluded from the cap on SailPoint's liability
- Claims related to payment obligations by Customer are excluded from the cap on Customer's liability
- Claims related to violations of SailPoint's IP rights are excluded from the cap on Customer'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 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
- Indemnification obligations relating to data are excluded from the cap on Customer's liability
Excluded damages
- One or more forms of indirect damages are excluded from SailPoint's liability
- One or more forms of indirect damages are excluded from Customer's liability
Exceptions to excluded damages
- The damages excluded from SailPoint's liability do not include claims related to violations of Customer's IP rights
- The damages excluded from SailPoint's liability do not include claims related to gross negligence or recklessness
- The damages excluded from SailPoint's liability do not include claims related to fraud or willful misconduct
- 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 violation of SailPoint's intellectual property rights
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 SailPoint
Claims
- SailPoint indemnifies Customer for claims based on third-party IP infringement
- Customer indemnifies SailPoint for claims based on Customer's content, data, and/or materials
- Customer indemnifies SailPoint for claims arising from violation of any third party rights (other than IP infringement)
Scope of obligations
- SailPoint's IP indemnification covers all types of IP
- SailPoint's indemnification obligations are the exclusive remedy for indemnified claims
- SailPoint's indemnification includes the obligation to provide a defense
- SailPoint'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 the exclusive remedy for indemnifiable claims
- Customer's indemnification includes the obligation to provide a defense
- Customer's indemnification does not include the obligation to hold harmless
Limitations, conditions, or exclusions
- Obligations include conditions regarding Customer's cooperation or SailPoint's control of the defense
- Obligations include conditions regarding Customer's use of the services in breach of the contract
- SailPoint's IP indemnity does not cover claims resulting from modifications, combinations, or use of an outdated version of the service
- SailPoint's indemnity obligations include conditions regarding settlements
- There are time constraints on when Customer must notify SailPoint of an indemnifiable claim
- Obligations include conditions regarding SailPoint's cooperation or SailPoint's control of the defense
- Customer's indemnity obligations include conditions regarding settlements
- There are time constraints on when SailPoint must notify Customer of an indemnifiable claim
Warranties Offered
SLAs
- SailPoint offers an SLA regarding uptime
- The specified remedy for SailPoint's violation of the uptime SLAs is credit or refunds
- The specified remedy for SailPoint's violation of an uptime SLA is the exclusive remedy
- SailPoint offers some other form of SLA
- There is no specified remedy for SailPoint's violation of the other form of SLA
Other warranties
- SailPoint warrants that the services will meet specified standards of care or conduct
Implied warranties
- SailPoint disclaims some or all implied warranties
Data Rights
Data provided by Customer
- SailPoint does not claim ownership of any data provided by Customer
- SailPoint does not receive usage rights in any data provided by Customer beyond what is necessary to improve or provide the services
Data Security
Subprocessor obligations
- The contract lists or references a list of some subprocessors
- SailPoint is required to ensure that subprocessors are bound by data or privacy requirements similar to those in this contract
Security commitments
- SailPoint makes contractually binding data security commitments
Third party audits, standards, or certifications
- SailPoint commits to comply with at least one third-party data security audit, standard, or certification
- SailPoint commits to ISO 27001 standards and/or certification
- SailPoint commits to Data Privacy Framework (DPF) standards and/or certification
- SailPoint commits to some other audits, standards, or certifications which TermScout was unable to classify - see citation
- There are qualifications and/or limitations to SailPoint's commitments to comply with third-party data security audits, standards, or certifications
Data breach notification policy
- SailPoint commits to notifying Customer of a security breach impacting Customer's data
Summary
Vendor's confidential information
- Customer must provide some protection of SailPoint's confidential information
Customer's confidential information
- SailPoint must provide some protection of Customer's confidential information
- SailPoint explicitly commits not to disclose Customer's confidential information, except as necessary to provide the services
- SailPoint 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
- SailPoint warrants that the services will comply with certain documentation and/or specifications, but the warranty has some conditions or qualifications
Payment Terms
Late payment penalties
- There are penalties for late payments
Payments due
- Customer has at least 30 days to pay
Vendor's expenses
- SailPoint reserves the right to bill Customer for one or more types of expenses incurred by SailPoint
- SailPoint reserves the right to bill Customer for expenses beyond the collection of unpaid fees
Summary
Customer's termination rights
- Customer has certain rights to terminate for cause
- Customer has certain rights to terminate for convenience
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
- SailPoint does not receive the right to terminate the contract for convenience
- Customer has between 11 and 30 days to cure a breach before SailPoint can terminate for cause
- SailPoint may suspend Customer's access to the service for payment-related issues
- SailPoint may suspend Customer's access to the service for violation of SailPoint's policies and/or guidelines
- SailPoint may suspend Customer's access in order to prevent material harm
Customer's IP
Licenses to Customer IP
- SailPoint receives a right to Customer's suggestions and/or feedback
- SailPoint receives the right to use Customer's name and/or marks publicly
Publicity rights
- SailPoint's use of Customer's name and/or marks is subject to Customer's guidelines
Assignment of Customer IP or work product
- Customer does not assign any work product or other IP to SailPoint
Warranties Offered
Other warranties
- SailPoint 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
- SailPoint is allowed to assign in the event of a merger or acquisition
- SailPoint is allowed to assign in the event of a corporate reorganization
- There are consent requirements restricting SailPoint'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 SailPoint's ability to assign the contract
- There are no restrictions or conditions on SailPoint'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 SailPoint
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 Framework Customer Agreement ("FCA") for SailPoint 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 FCA for SailPoint and any documents specifically listed under 'Scope of Review'. For purposes of this report, "Customer" means the party contracting with SailPoint and "Vendor" means SailPoint.
References herein to the "Agreement" are to the following documents:
- The Primary Document: Framework Customer Agreement ("FCA")
- The following Secondary Document(s) expressly incorporated by reference into the Primary Document and reviewed by TermScout as part of this analysis:
- Support Policy ("SP")
- Data Processing Addendum ("DPA")
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.
Enterprise buyers frequently challenge agreements that require customers to absorb broad operational or third-party risks while limiting the vendor’s responsibility for security failures, infringement claims, or data incidents. Contracts often attract additional scrutiny when indemnity obligations appear one-sided or exclude the vendor’s core service risks from meaningful coverage. Buyers generally expect security vendors to accept proportional accountability for incidents directly connected to the systems and controls they manage.
Indemnity provisions often influence multiple internal stakeholders simultaneously, including legal, security, compliance, procurement, and insurance teams. Review complexity increases when the agreement creates unclear boundaries around breach response obligations, defense control rights, or financial exposure following a security event. Enterprise buyers may escalate negotiations when contractual language could shift downstream operational costs onto the customer without corresponding governance protections or remediation commitments.
Buyers often react cautiously when agreements narrowly define covered incidents, exclude common operational failure scenarios, or reserve broad vendor discretion over remediation decisions. Additional concern arises when vendors disclaim responsibility for subcontractors or shared infrastructure dependencies while simultaneously limiting customer audit or oversight rights. These patterns can signal that the contractual framework is not fully aligned with the operational role the vendor will play inside the enterprise environment.
Buyers generally compare indemnity obligations against vendors handling similar categories of infrastructure access, sensitive information, and operational responsibility. Agreements tend to appear more market aligned when indemnity structures reflect the vendor’s actual control over security-related outcomes and include workable cooperation procedures during incident response. Contracts become harder to approve when indemnity language appears disproportionately vendor-protective relative to the level of operational dependency created by the service.
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