A plain language, highly structured agreement for buying and selling cloud services and SaaS. Use instead of an MSA or SaaS sales contract.
Everything you need to get your agreement sent and signed today:
Templates -> Proposals -> Negotiations -> Approvals -> Esignature -> Recordkeeping
Common Paper agreements help you get on the same page, faster.
Written by a committee of experienced attorneys so you can start negotiations on the same, reasonable terms every time.
Highly-structured format makes dealing with commonly negotiated terms faster and simpler for both parties.
You shouldn’t need to start a new agreement from square one each time. Our CSA is available for anyone to use and modify.
The Common Paper CSA consists of a Cover Page, plus the Standard Terms that are hosted online and incorporated by reference. Creating and executing an agreement is easy:
Use this document to describe the terms of the products and services being sold in the Order Form section, plus the legal details of the agreement in the Key Terms section.
Once both parties have agreed on the terms, send the Cover Page for signature.
The Common Paper CSA was created by a committee of dozens of attorneys representing technology vendors, procurement teams, boutique firms, and Big Law.
The CSA was created specifically to help companies sell cloud services and SaaS. It addresses core legal and business terms like indemnification, fees, payment terms, and intellectual property, as well as SaaS-specific topics like customer data usage and privacy. Many Master Service Agreements are built for any type of commercial transaction and include terms that aren’t applicable to cloud services and SaaS (making them harder and slower to customize for your particular transaction). If an MSA can also be used for renting event space or catering, it’s not going to be as relevant to software. While the name of an agreement doesn’t solely determine its applicability, starting with a contract built for SaaS companies speeds up legal review and the sales cycle.
The CSA was built to be extensible via other commonly used agreements such as a Business Associate Agreement, Data Processing Agreement, or Service Level Agreement. You can incorporate these standard agreements or custom agreements and documents that you or your attorney have created.
The latest version of the CSA is 2.0, and it will remain unchanged and hosted at commonpaper.com/standards/cloud-service-agreement/2.0. We expect future changes to occur infrequently, and they will be posted as a new version when they happen. New versions will not change or otherwise impact agreements that incorporate prior versions, and you can see the full list of all CSA versions here.
CSA v2 adds expanded support for product trials/pilots, more flexibility for defining payment terms, language covering the use of data for training AI models, and many other improvements. You can see a summary of changes along with a redline on the version history page at: commonpaper.com/standards/cloud-service-agreement/versions
Yes, older versions of standards will remain posted under their version number. You can access all prior versions on a standard’s version history page.
To execute an agreement using the Common Paper CSA, first download a copy of the Cover Page in your preferred format. Then fill out the business terms of your agreement, like fees and subscription period, and the legal terms like the governing law of your contract. Finally, sign your Cover Page with your counterparty via the signing process of your choice. The Cover Page incorporates the Standard Terms by reference, completing the executed agreement.
You can also download the full version of the agreement here and include the Standard Terms in the agreement itself.
Yes, some concepts in the Cover Page are optional, like whether your agreement includes SLAs. When you download the Cover Page, you’ll see notes explaining which fields are optional. If you omit a definition from the Cover Page, the meaning will default to “none” or “not applicable” when the capitalized word is used in the Standard Terms.
Yes, you can feel free to change the Cover Page any way you like. Many companies decide to add their company branding or logo and edit some of the text. The only thing you are required to keep is the license information and link to the Standard Terms.
All modifications to the Standard Terms should be made by addendum on the Cover Page. Incorporating the Standard Terms by reference from the Common Paper website gives both sides assurance that all key details and modifications are explicitly called out in the Cover Page.
Common Paper agreements are free to use and modify under CC BY 4.0.
This agreement is free to use or modify under CC BY 4.0. The agreement is available in the following formats.
Set up this agreement by answering a few questions.
Generate your free CSAEverything you need to get your agreement sent and signed today:
Templates -> Proposals -> Negotiations -> Approvals -> Esignature -> Recordkeeping
The key business terms of this Order Form are as follows:
Framework TermsThis Order Form incorporates and is governed by the Framework Terms included below . If there is any inconsistency between this Order Form and the Framework Terms, this Order Form will control for this Agreement.
Cloud ServiceThe Cloud Service available under this Order Form is [ description of the product ].
Order Date The date access to the Cloud Service starts( x ) Date of last signature on this Order Form
( ) [ Fill in custom start date ]
Subscription details PilotCustomer may access the Cloud Service for a limited [ fill in length of pilot/trial, e.g. 3 months ] trial (“Pilot Period“). The Subscription Period will automatically start following the Pilot Period.
( ) Fee for Pilot Period: [ fill in $ amount ]
[ ] Modifications to the Agreement that apply only to the Pilot Period: [ – Sections 6.3 (Representations & Warranties from Provider), 6.4 (Provider Warranty Remedy), and 9 (Indemnification) do not apply during the Pilot Period.
– There are no Increased Claims or Unlimited Claims during the Pilot Period.
– The General Cap Amount is $1,000 for all claims that arise during the Pilot Period.
– Either party may immediately terminate the Agreement during the Pilot Period for any or no reason by giving notice to the other party. ]
[ Fill in length of access, e.g. 12 months ]
Cloud Service Fees[ ] [ fill in $ amount ] per [ year, month, Subscription Period, User, gigabyte, etc. ]
[ ] Other fee structure: [ fill in ]
[ ] Fees may increase up to [ # ]% per renewal.
[ ] Fees will increase [ # ]% per renewal.
[ ] Modifying Section 4.1 of the Standard Terms, Fees are inclusive of taxes.
Payment ProcessProvider will invoice Customer [ monthly | quarterly | annually | once per Subscription Period ] .
Customer will pay each invoice within [ # ] days from [ Customer’s receipt of invoice | the invoice date ] .
Customer authorizes Provider to bill and charge Customer’s payment method on file [ monthly | quarterly | annually | once per Subscription Period ] for immediate payment or deduction without further approval.
Auto-renewal( x ) Non-Renewal Notice Date: At least [ fill in number ] days before the end of the current Subscription Period
( ) Modifying Section 5.1 of the Standard Terms, this Order Form does not automatically renew and will expire at the end of the Subscription Period.
Use Limitations[ Describe Use Limitations, such as geographic restrictions, system requirements, etc. ]
Technical Support[ Describe included support and/or how Customer can receive support ]
Additions and Modifications SLA Service Level Agreement[ Provider will use commercially reasonable efforts to provide and maintain the Cloud Service without excessive errors and interruptions. If Provider does not meet the SLA in two consecutive months or over three months in any 12-month period, then Customer may, as its only remedy, terminate this Order Form upon notice and receive a prorated refund of prepaid Fees for the remainder of the Subscription Period. ]
Professional Services[ ] Provider will provide professional services according to the [ attached SOW or reference PSA ].
[ ] Provider will provide the following professional services: [ description of professional services, including any fees that may be assessed ]
[ ] Payment Process for these services: [ describe how services fees will be billed, for example “Invoices for these services will be sent monthly.” ]
Customer will reasonably cooperate with Provider to allow the performance of the services described above, including providing Customer Content as needed. Provider is not responsible for any inability to perform these services if Customer does not cooperate as reasonably requested.
Other Changes to Standard Terms Changes that apply for this Order Form onlyBy signing this Order Form, each party agrees to enter into this Order Form.
PROVIDER: [official company name] CUSTOMER: [official company name] Signature Print Name Title Notice Address Use email or postal address DateThe Framework Terms have 2 parts: (1) the Key Terms below (including any attached or referenced policies and documents) and (2) the Common Paper Cloud Service Standard Terms Version 2.0 posted at commonpaper.com/standards/cloud-service-agreement/2.0 , which are incorporated by reference . If there is any inconsistency between the parts of the Framework Terms, the Key Terms will control over the Standard Terms. Capitalized words have the meanings or descriptions given in the Cover Page or Standard Terms. A copy of the Standard Terms is attached for convenience only.
The key legal terms of this Agreement are as follows:
Effective Date The date the Framework Terms start( x ) Date of last Cover Page signature
( ) [ Fill in custom Effective Date ]
Governing LawThe laws of [ fill in state, province, and/or country ]
Chosen Courts Jurisdiction or where disputes are filedThe courts (whether state, federal, or otherwise) located in [ fill in state, province, and/or county ]
Covered Claims Claims covered by indemnity obligations[ x ] Provider Covered Claims: [ Any action, proceeding, or claim that the Cloud Service, when used by Customer according to the terms of the Agreement, violates, misappropriates, or otherwise infringes upon anyone else’s intellectual property or other proprietary rights. ]
[ x ] Customer Covered Claims: [ Any action, proceeding, or claim that (1) the Customer Content, when used according to the terms of the Agreement, violates, misappropriates, or otherwise infringes upon anyone else’s intellectual property or other proprietary rights; or (2) results from Customer’s breach or alleged breach of Section 2.1 (Restrictions on Customer). ]
General Cap Amount Limitation of liability amount for most claims[ x ] [ Fill in a number ]x the Fees paid or payable by Customer to Provider in the 12 month period immediately before the claim
[ ] $[ Fill in dollar amount ]
[ ] The greater of $[ fill in dollar amount ] or [ fill in a number ]x the Fees paid or payable by Customer to Provider in the 12 month period immediately before the claim
Increased Claims Specific claims covered by the Increased Cap Amount[ x ] Breach of Section 3 (Privacy & Security)
[ x ] Breach of Section 10 (Confidentiality) (however, excluding any data or security breaches)
[ ] An Indemnifying Party’s indemnification obligation
[ ] Breach of Section 3 (Privacy & Security) resulting from gross negligence or willful misconduct
[ ] Breach of Section 10 (Confidentiality) resulting from gross negligence or willful misconduct (however, excluding any data or security breaches)
Increased Cap Amount Higher limitation of liability amount for Increased Claims, often called a supercap
[ x ] [ Fill in a number other than 1 ]x the Fees paid or payable by Customer to Provider in the 12 month period immediately before the claim
[ ] $[ Fill in dollar amount ]
[ ] The greater of $[ fill in dollar amount ] or [ fill in a number other than 1 ]x the Fees paid or payable by Customer to Provider in the 12 month period immediately before the claim
Unlimited Claims Specific claims covered by the Increased Cap Amount[ x ] An Indemnifying Party’s indemnification obligation
[ ] Breach of Section 3 (Privacy & Security) resulting from gross negligence or willful misconduct
[ ] Breach of Section 10 (Confidentiality) resulting from gross negligence or willful misconduct (however, excluding any data or security breaches)
[ ] Breach of Section 3 (Privacy & Security)
[ ] Breach of Section 10 (Confidentiality) (however, excluding any data or security breaches)
Additional Warranties[ ] By Provider: [ fill in ]
[ ] By Customer: [ fill in ]
Attachments, Supplements & Modifications DPA Data Processing Agreement[ Attach or describe where to find. ]
Security Policy[ x ] Provider will use commercially reasonable efforts to secure the Cloud Service from unauthorized access, alteration, or use and other unlawful tampering.
[ ] Provider will comply with the Security Policy available at [describe where to find].
[ ] Provider will maintain annually updated reports or annual certifications of compliance with the following:
Insurance MinimumsDuring the Subscription Period and for six months after, Provider will carry commercial insurance policies with coverage limits that meet the Insurance Minimums below:
[ ] Commercial general liability with a minimum limit for each occurrence of at least $[ dollar amount ] and at least $[ dollar amount ] in the aggregate
[ ] Workers’ compensation or employers’ liability insurance as required by Applicable Laws
[ ] Errors and omissions or professional liability with a minimum limit for each occurrence of at least $[ dollar amount ] and at least $[ dollar amount ] in the aggregate
[ ] Cyber liability insurance with a minimum limit for each occurrence of at least $[ dollar amount ] and at least $[ dollar amount ] in the aggregate
Upon request, Provider will give Customer a certificate of insurance evidencing its insurance policies that meet the Insurance Minimums. Provider’s insurance policies will not be considered as evidence of Provider’s liability.
[ ] The following of Provider’s policies will cover Customer as additional insured:
[ ] Commercial general liability
[ ] Errors and omissions or professional liability
Other Changes to Standard Terms List specific changes to the Standard TermsProvider and Customer have not changed the Standard Terms except for the details in the Key Terms above. By signing this Cover Page, each party agrees to enter into the Framework Terms.
PROVIDER: [official company name] CUSTOMER: [official company name] Signature Print Name Title Notice Address Use email or postal address DateCommon Paper Cloud Service Agreement (Version 2.0) free to use under CC BY 4.0 .
The Order Form contains the business details that you can customize from deal to deal.
The Order Form is contained in a Cover Page. Learn about how standard agreements work in our anatomy of a contract blog post.
The Framework Terms operate as an overarching governing document between two organizations, similar to a “master agreement”. Framework Terms can apply to one or many Order Forms. When you combine an Order Form with Framework Terms, you get the Agreement or overall contract.
If the Framework Terms are not included as Key Terms in this same document, you can replace this first sentence with “This Order Form incorporates and is governed by the Framework Terms dated [ enter Effective Date of Key Terms ] between [ enter name of Provider ] and [ enter name of Customer ].”
The Order Date is distinct from the Effective Date, which is the date the Framework Terms start and is defined below the Key Terms. They are often, but not always, the same date.
Choices pre-marked with an “x” show the default selection. You can use the “x” to mark off your choice, or keep the text for your choice and delete the text for the other options.
Parentheses with blank space indicate a choice you need to make where one option must be chosen, but not more than one should be selected.
Square brackets with text indicate a field you can fill in or customize before sending the agreement.
For this one, if the Order Date is different from the date of signature, then set the Order Date here.
This is an optional field. Use it to include a pilot or trial period that is in addition to the full Subscription Period. If there is no pilot period, delete this entire row.
This clarifies that the Pilot Period is in addition to the Subscription Period.
Square brackets with blank space indicate choices that are optional. You can pick none, one, or more than one. Indicate selections by checking the box for those you wish to include and/or deleting the unused options.
Use this area to make modifications that only apply during the Pilot Period. Shown are some common modifications that occur for pilots and trials, which can be changed to suit your needs.
From the Benchmark : The majority (70%) of CSAs have a Subscription Period of one year. The next most common length is one month, accounting for 19% of CSAs.
This is optional and may be deleted if not applicable. It permits a Fee increase upon renewal, but would require notifying the customer about an increase before it happens.
From the Benchmark : 29% of CSAs include the ability to increase fees upon renewal, typically in the range of a 5-8% increase.
This is optional and may be deleted if not applicable. It authorizes an automatic Fee increase upon renewal, without the requirement to notify the customer.
This is optional and may be deleted if not applicable. It is for situations where the prices listed include applicable taxes, such as in regions that use a VAT-inclusive model.
Use Payment Process to clarify how billing and payments will work for your customer.
This option requires the provider to send invoices in order for your customer to pay.
If using this option, set how frequently the provider must send invoices. Although this time frame is often the same as the Subscription Period, it can be different. For example, you can have a 1 year subscription period that is invoiced monthly in 12 equal increments.
From the Benchmark : 48% of CSAs use monthly invoices, while 46% send annual invoices.
Together, these two fields set how long a customer has to pay each invoice. Finance teams often refer to this time period in “NET terms” such as “NET-30 days”.
From the Benchmark : “30 days from Customer’s receipt of invoice” is the most common payment period, making up 62% of CSAs.
This option requires the customer to keep a credit card or other payment method on file that the provider automatically charges on the agreed-upon cadence.
If using this option, set how frequently the provider will charge the customer’s payment method. Although this time frame is often the same as the Subscription Period, it can be different. For example, you can have a 1 year subscription period that is charged monthly in 12 equal increments.
The Standard Terms set a default of automatic renewal for contracts. However, automatic renewal doesn’t mean the contract cannot end. At baseline, either side can cancel renewal by giving sufficient notice, the time period for which is set here.
From the Benchmark : The vast majority (90%) of CSAs retain automatic renewal.
From the Benchmark : The majority (84%) of automatically renewing CSAs require 30 days prior notice to cancel renewal.
Select this option if the contract will not automatically renew when it ends. In these situations, both sides will need to explicitly opt in to the renewal by signing a new Order Form.
Including use limitations is optional. If no limitations apply, delete this entire row.
Including technical support is optional. If no technical support is included, delete this entire row.
All sections in the Additions and Modifications section are optional. Delete any rows that do not apply.
From the Benchmark : SLAs are included in 39% of CSAs.
This is a very basic and lightweight example of SLA language. Modify it to your situation, incorporate your own, or use the Common Paper SLA.
If including professional services, use this option to incorporate an existing SOW or professional services agreement, which will govern the services.
If including professional services, use this option to describe the services directly on this Order Form. Without a separate professional services agreement, the CSA will govern the services.
If only using the CSA to describe the services and fees, describe how the fees will be billed and paid. If referencing an SOW or professional services agreement that already includes fees and payment terms, including those details here isn’t necessary.
Including Other Changes is optional. Examples of how to use this section can be found in the Language Library.
All Common Paper agreements are released under the Creative Commons CC BY 4.0 license, which enables you to use the agreements in any way, as long as you leave in the attribution.
The Framework Terms operate as an overarching governing document between two organizations. Framework Terms can apply to one or many Order Forms. The Framework Terms are made up of the Key Terms + the Standard Terms. When you combine an Order Form with Framework Terms, you get the Agreement or overall contract.
CSA v2 incorporates the Standard Terms by reference, with a link to commonpaper.com/standards/cloud-service-agreement/2.0. Each version of the Standard Terms will remain unchanged and posted our website, and updates will get posted as new versions.
Incorporating the Standard Terms by reference ensures there are no hidden changes in the Standard Terms.
This allows including a copy of the text of the Standard Terms for convenience. You can find a version without the standard terms attached on the cloud service agreement page.
The Key Terms contains the key legal details of each specific contract.
The Effective Date is when the Framework Terms start. If the Effective Date is different than the Order Date, then things like confidentiality obligations start on the Effective Date, while the customer’s access to the product won’t start until the Order Date.
Governing Law identifies the set of laws under which the contract will be interpreted.
From the Benchmark: 71% of CSAs set Governing Law to Delaware. California is the next most common choice.
Chosen Courts identifies where a lawsuit related to the contract can be filed in the event of a dispute.
From the Benchmark: 71% of CSAs set Chosen Courts to Delaware. California is the next most common choice.
Including Covered Claims is optional. Use this Variable to set which claims the provider and/or customer will be responsible for under an indemnity obligation.
Section 9 of the Standard Terms includes the full language around indemnities and Covered Claims, including narrowing the obligation to claims brought by entities other than the provider, customer, end users, or their affiliates (i.e., third party claims).
If there are no Covered Claims, delete the entire row.
This reflects a default for Provider Covered Claims (i.e., what indemnification obligations the provider has) set by the Committee. You can modify it in any way to address your particular situation.
From the Benchmark: 76% of CSAs keep this default.
This reflects a default for Customer Covered Claims (i.e., what indemnification obligations the customer has) set by the Committee. You can modify it in any way to address your particular situation.
From the Benchmark: 76% of CSAs keep this default.
The General Cap Amount is the maximum dollar amount a party to the contract could be responsible for in the event of a legal dispute over the contract. It applies to all contract claims, except for Increased Claims (below), Unlimited Claims (below), and claims that cannot be limited as a matter of law.
Deleting the General Cap Amount does not set it to $0. Instead, it would mean there is no monetary limitation of liability that applies to the contract, and either party could be responsible for an unlimited amount of monetary damages in the event of a legal dispute over the contract.
This option sets a variable liability cap amount that fluctuates with the cost of the contract. It is expressed as a multiple of fees, for example 1x or 2x. This option sets the time period for calculating the fees to the 12 months before the claim.
From the Benchmark: 85% of CSAs select this option and sets the amount to 1x.
Including fees that are “paid or payable” (but potentially unpaid) helps balance the incentives between a provider and customer. If the liability cap is set to the fees paid but does not include payable but unpaid fees, a customer could pay a fraction of the cost they agreed to and limit their liability to that lower amount.
This option sets a fixed liability cap amount. It is expressed as a monetary amount, for example $1,000,000.
In general, a $0 liability cap would be unenforceable.
This option sets a hybrid liability cap amount. It combines the two above options.
This is set to “greater” rather than “lesser” to avoid situations creating a $0 liability cap, for example where there are zero fees due.
Including Increased Claims is optional. If using this Variable, it will define certain claims that are not subject to the General Cap Amount, but are instead subject to the Increased Cap Amount (below). In addition, Increased Claims are not subject to the damages waiver in Section 8.2.
If there are no Increased Claims, delete the entire row.
From the Benchmark: Only 13% of CSAs include Increased Claims.
Including an Increased Cap Amount is optional, but it must be set if you are including Increased Claims. If there are no Increased Claims, delete the entire row.
Including Unlimited Claims is optional. If using this Variable, it will define certain claims that are not subject to any monetary liability cap.
From the Benchmark: Unlimited Claims are rare, appearing in roughly 1% of CSAs.
Because Section 8.4 excludes breaches of confidentiality from the damages waiver, selecting this option as an Unlimited Claim would mean these types of claims are not confined by any limitation of liability, whether by types of damages or monetary amounts.
Because Section 8.4 excludes breaches of confidentiality from the damages waiver, selecting this option as an Unlimited Claim would mean these types of claims are not confined by any limitation of liability, whether by types of damages or monetary amounts.
Including Additional Warranties is optional. If there are no Additional Warranties, delete the entire row.
In situations where the customer is requesting the provider to provide an intellectual property representation and warranty, you could add the following language: “the Product, when used as authorized by the Agreement, does not and will not infringe or misappropriate anyone else’s copyright, trademark, trade secret, [[U.S.] patent], or right of publicity”.
“U.S.” and “patent” are in brackets, because this type of representation can be tricky for many companies, as it is possible to infringe a patent without necessarily knowing about the patent.
All sections in the Attachments, Supplements & Modifications section are optional. Delete any rows that do not apply.
A Data Processing Agreement is commonly used by companies that need to comply with the GDPR. GDPR is the legal regulation that protects an individual’s personal data in Europe (EU) and the European Economic Area (EEA). It restricts what companies can and cannot do with the personal data of EU/EEA individuals.
From the Benchmark: Although 37% of CSAs include a security policy, requiring some type of security policy becomes more and more likely as customers become larger enterprises.
From the Benchmark: Only 9% of CSAs include corporate insurance requirements.
Including Other Changes is optional. Examples of how to use this section can be found in the Language Library.
This includes the ability for customers to use any included documentation or incidental software, such as a local client.
Affiliates of a customer are able to enter their own Order Form with the provider without having to renegotiate the Framework Terms.
Many customers bristle at seeing an assignment in SaaS contracts. This is a lightweight approach to clarify that a provider may use any and all feedback that’s given. If you prefer to be more explicit about intellectual property ownership over Feedback, you could use the Other Changes to the Standard Terms section on the Cover Page to add an assignment for Feedback.
In light of the rapid rise in the use of AI to supplement products and services, the Committee opted to include a default clause to permit basic training of AI and machine learning models.
If you prefer to remove the AI training language, you could use the Other Changes to the Standard Terms section on the Cover Page.
Due to the nature of the issues listed in this section, provider has the ability to suspend customer’s access regardless of the materiality of the violation. However, the Committee saw this as a fairly reasonable risk allocation because it is not permanent termination and the customer has the ability to remove the suspension by resolving the underlying issue.
You can incorporate your own DPA or use the Common Paper DPA.
You can add a BAA to authorize sharing patient, medical, or other protected health information regulated by HIPAA, which would otherwise be prohibited by this clause.
CSA v2 supports 2 methods of payment: invoicing with an obligation to pay within a set time (Section 4.2), or automatic payment with a credit card or other payment method (Section 4.3). The details of when payment must be made or how frequently an account is charged are all set in the Payment Process Variable on the Cover Page.
This standard intentionally does not include fines for late payments. In the experience of Committee members, payment disputes were more often an oversight by the customer rather than an intentionally bad act. Moreover, the time and expense of enforcing late payment fines tend to be more than what a provider recoups; not to mention the strained customer relationship these actions can create.
If adding a late payment penalty is important for you, you could use the Other Changes to the Standard Terms section on the Cover Page to do so.
As a default, contracts will auto-renew unless someone affirmatively notifies the other company that they wish to not renew. That notice of non-renewal must be given before the Non-Renewal Notice Date, which is on the Order Form and expressed as a set time period before the renewal date (e.g., 30 days before the end of the Subscription Period).
If you do not want a deal to auto-renew, you can change this in the Auto-renewal section of the Order Form.
The Framework Terms serve as an overarching umbrella agreement. To better facilitate multiple Order Forms, such as one Order Form for an introductory time period like 6 months, followed by a longer term engagement, the Framework Terms will last for at least 1 year. This allows two companies to issue new Order Forms without needing to renegotiate the Framework Terms. It is also helpful if the initial Order Form expires before the two companies have signed the longer term Order Form because it preserves the Framework Terms during that gap in time between the Order Forms.
There is no termination for convenience, as that is uncommon in SaaS subscription agreements.
In some situations, a customer may want the ability to terminate for convenience after a set time period. This could be because the deal is for a longer time, or because the customer is wary of purchasing a product that is still unproven. If this type of termination right is needed for your deal, you could use the Other Changes to the Standard Terms section on the Cover Page.
Under Section 5.5, terminating the Framework Terms will end all Order Forms under the terminated terms. However, terminating an Order Form would not affect other Order Forms nor the Framework Terms.
Termination under this clause would not terminate unaffected Order Forms nor the overarching Framework Terms.
Neither the General Cap Amount nor the Increased Cap Amount apply to Unlimited Claims. However, the damages waiver in Section 8.2 still applies to Unlimited Claims. The one exception is if Breach of Section 12 (Confidentiality) is an Unlimited Claim, in which case no cap amount and no damages waiver would apply.
The liability provisions are set this way because the trend in SaaS companies has been to use an Increased Cap Amount, or supercap, for higher risk concerns such as personal data issues. In addition, having fully uncapped and unlimited claims has come to be seen as a risk that is hard to justify. As a result, companies have more and more relied on the damages waiver to have some measure of risk mitigation when they do remove a liability cap on certain claims.
This excludes claims by the customer, its affiliates, or Users so that provider is not responsible for first party claims. In other words, a customer could not sue the provider and then seek indemnification coverage for the lawsuit they filed.
This excludes claims by the provider or its affiliates, so that the customer is not responsible for first party claims. In other words, a provider could not sue the customer and then seek indemnification coverage for the lawsuit they filed.
It is very common for indemnification obligations to be the sole and exclusive remedy for claims that are subject to indemnity. This is important in situations where there is overlap between other contractual obligations or commitments (such as representations and warranties) and claims that are subject to indemnity.
Common Paper standard agreements were created with the laws of the United States in mind by a committee of US-based attorneys.
Some companies prefer arbitration for speed and confidentiality reasons. You could use the Other Changes to the Standard Terms section on the Cover Page to add mandatory arbitration.
Alternatively, you could use the Other Changes to the Standard Terms section on the Cover Page to permit assignment to any Affiliate, or to prohibit all assignment.
With CSA v2, the default is to allow providers to use customer’s name and logo to identify the customer as a user of the product, for example on a customer list webpage.
Some customers prefer to remove the grant of any logo rights, which you could do by using the Other Changes to the Standard Terms section on the Cover Page.
Some Variables are optional. When optional Variables are removed from the Cover Page, the related clauses will not apply to the contract.
All Common Paper agreements are released under the Creative Commons CC BY 4.0 license, which enables you to use the agreements in any way, as long as you leave in the attribution.