Legal Clauses to Include in a SaaS Sales Proposal

SaaS suppliers often prepare sales proposals in order to win business from prospective clients. A few basic legal clauses should be included in the sales proposal to protect your business if you win the sale, but more importantly, if you don’t.

Prices

There can be a substantial time delay between sending a client a proposal and actually negotiating the terms of the SaaS agreement. The proposal may also include pricing for optional additional functionality, that the client may want to  order a later stage. The proposal should state dates for the validity of the various prices quoted, otherwise you could be obliged to provide functionality in 2012 for 2010 prices.

SaaS Agreement Terms and Conditions

The proposal should state that the software and services will be sold subject to the supplier’s standard terms and conditions. This is particularly important for SaaS applications. Often client’s – who are usually not software suppliers and who supply physical goods – will want to use their own standard terms and conditions. These will not work for a SaaS agreement as the software is not a physical good (and for many other reasons which will not be elaborated here). If the client’s terms and conditions are used – a situation which should be strongly resisted – they will need to be substantially amended, which will waste time and expense. If you already have suitable terms and conditions in place then it makes commercial sense for both parties to use these as the basis of the SaaS agreement.

More importantly – always specifically state in the proposal that your SLA (service level agreement) will apply. This sets out the hosting, maintenance and support services that you will be providing to the client. As you will usually be using a third party hosting centre to provide the majority of these services, the SLA must reflect the level of services that you yourself receive from the hosting centre. It makes no commercial sense to use an SLA provided by the customer, as you will not be able to comply with this.

Confidentiality

It is imperative that you obtain the client’s undertaking to treat all information provided to them by you during the sales process  – including any documents referred to in the proposal – as confidential.  You will probably have given the client copies of your price lists,  functional descriptions of your software and other internal documents which you do not want third parties to see. This is particularly important if the proposal does not lead to a sale and the client is speaking to your competitors… The client should agree to keep all information confidential and to return all of your confidential information immediately, if no sale is agreed.

No Obligation to Supply

The proposal should state that it is not legally binding and does not create any obligation on your part to provide the software or services to the client. Often between the proposal stage and the actual terms of the SaaS agreement being negotiated, your client’s requirements will have changed. You do not want to be bound by the terms and prices, in the proposal if the client has changed the basic scope of the services or the functionality.

Help

Irene Bodle is an IT lawyer specialising in SaaS agreements with over 10 years experience in the IT sector. If you require assistance with any SaaS, ASP, software on demand contracts or any other IT legal issues contact me:

irene.bodle@bodlelaw.com
www.bodlelaw.com

To register for my newsletter click here

______________________________________________________

Other related articles:

Benefits of SaaS and Cloud Computing

The benefits of SaaS (software as a service) applications to customers are numerous. They include:

  • customer collaboration
  • access anytime/anywhere,
  • no need to install programmes and updates,
  • number of users can be increased or decreased easily
  • more functions and modules can be quickly and easily added
  • reduced need for internal IT
  • saving in professional time

Customer Collaboration

Often customer portals are included in the SaaS application which enables the customer to share information with its clients.

Access Anytime, Anywhere

SaaS applications are usually hosted on the software supplier’s servers. This enables the customer to be able to log in and work with the software application and customer data from work, home, other computers or whilst travelling, via mobile devices.

Reduced need for Internal IT Resources

Small and mid-sized firms, unlike large firms do not usually have large internal IT expertise.  By using SaaS applications the need to install, reinstall, update and generally deal with ever changing technological issues is avoided. The supplier automatically deals with all of these issues on your behalf. This saves the customer time and the expense of troubleshooting themselves or hiring external assistance.

Help

Irene Bodle is an IT lawyer specialising in SaaS agreements with over 10 years experience in the IT sector. If you require assistance with any SaaS, ASP, software on demand contracts or any other IT legal issues contact me:

irene.bodle@bodlelaw.com
www.bodlelaw.com

To register for my newsletter click here

______________________________________________________

Other related articles:

Cloud based Software, Cloud based Technologies, Cloud based Services

What is Cloud based Software

Applications that live in the cloud, are also known as SaaS (Software as a Service), on demand, hosted or online applications. Such cloud based services are proving to be useful tools for businesses looking to save money and ease the burden on IT. An increasing number of organisations are entering into SaaS Agreements for their customer relationship, email, financial, recruitment and talent management.

Advantages of Cloud Based Software

In contrast to the traditional, installed software model, SaaS solutions can reduce the administrative burden on IT, personnel and the strain on physical resources caused by supporting and maintaining traditional software. Upfront capital expenditure can also be reduced, as SaaS software is rented on a monthly basis, rather than being purchased outright for a large upfront fee.

The appeal of cloud based software is clear. Businesses are no longer responsible for purchasing, configuring, loading, and maintaining applications onto their own hardware. In very simple terms all that is needed is an Internet connection.

Avoiding Problems

However, due to the unique nature of SaaS applications it is important to obtain specialist legal advice on the terms of the SaaS agreement to ensure that it covers the requirements of your organisation. For example is disaster recovery included, what are the provisions for return of customer data, have you seen a copy of the SLA (service level agreement), are the data protection and security provisions adequate, will the source code be held in escrow by a third party?

If things go wrong, your data is lost and your customers start to move to your competitors –  making a claim for breach of contract will not repair the damage already sustained to your finances and business reputation. These issues should be dealt with upfront, as part of the commercial negotiation process, with the assistance of an experienced specialist SaaS lawyer. Thereby your interests can be adequately covered to minimise the risks of the above scenario occurring.

Help

Irene Bodle is an IT lawyer specialising in SaaS agreements with over 10 years experience in the IT sector. If you require assistance with any SaaS, ASP, software on demand contracts or any other IT legal issues contact me:

irene.bodle@bodlelaw.com
www.bodlelaw.com

To register for my newsletter click here

______________________________________________________

Other related articles:

Cloud Computing and the Legal Cloud

Everyone is talking about “cloud computing” but what is it?

What is Cloud Computing

Cloud computing is a new and rapidly expanding delivery model, often used to supply IT services to customers via the Internet. Cloud computing involves the sharing of resources, software and information on the Internet for users to use on their computers and other devices, on-demand.

Other Related Terms

Where software is supplied using the cloud you will hear people refer to SaaS, software as a service, ASP services and software on demand to describe the provision of the services.

Why refer to a “cloud”

The term “cloud” is used as a metaphor for the Internet, based on the cloud drawing used in the past to represent the telephone network, and later to depict the Internet. Typical cloud computing providers deliver business software applications online which are accessed from another web service or software i.e. a web browser while the software and customer data are stored on servers, hosted by the service provider.

The Legal Cloud

Most cloud computing infrastructures consists of services delivered through hosting centres. The service provided to users are usually set out in a service level agreement (SLA) and the software licence for use of the services and software will be set out in a SaaS agreement.

Help

For assistance with cloud computing matters, SaaS, ASP, software on demand contracts or any other IT legal issues contact:

irene.bodle@bodlelaw.com
www.bodlelaw.com

To register for my newsletter click here

______________________________________________________

Other related articles:

SaaS, ASP Agreements – Transfer of Personal Data outside of the EEA

There are no restrictions on transferring personal data within the EEA.  However, due to the global nature of SaaS agreements personal data often needs to be  transferred outside of the EEA, for example to an IT outsourcing provider in India, a subsidiary of your company in China or a data centre or software development centre in Vietnam.

Restrictions on Export of Data Outside of the EEA

Under the Data Protection Act 2018 and the GDPR before any personal data may be exported to any country outside of the EEA, you must ensure that there are adequate levels of protection in place. The European Economic Area consists of the 28 EU member states plus Norway, Iceland and Liechtenstein. There are four ways in which adequate levels of protection can be achieved:

  • consent
  • equivalent protection/ safe harbor
  • use of the EU model contract clauses
  • binding corporate rules

Consent

The easiest method of compliance is to obtain specific consent from the data subject before the transfer takes place. If the data subject consents to the transfer, you will comply with the Data Protection Act and the GDPR. Consent is usually obtained by having a data subject agree to the transfer of its personal data outside of the EEA and full details about the transfer itself should be set out in your privacy policy.

Equivalent Protection and Safe Harbor

Alternatively, the transfer is permitted if the non-EEA country to which the personal data is being transferred has equivalent data protection legislation. Currently only Andorra, Argentina, Canada, Faroe Islands, Guernsey, Israel, Isle of Man, Jersey, New Zealand, Switzerland, Uruguay and Japan are recognised as having adequate protection. Certain companies in the USA are also recognised under the EU-US Privacy Shield, provided that the company to which the personal data is being transferred has an up to date Privacy Shield registration.

EU Model Clauses

The European Commission has issued its own model clauses to cover transfers of personal data outside of the EEA. If these model clauses  are used in the SaaS agreement with the data subject and the agreement with the third party IT outsourcer, data centre or software developer to whom the data is being transferred, there will be adequate protection. However, these clauses are not ideal due to the different legal responsibilities of the data processor and the data controller which still remain unclear in the situation where there is a sub-processor.

Binding Corporate Rules

BCRs are designed to cover transfers of personal data within multi-national companies where they have subsidiaries based in many countries. These rules only permit the inter-company transfer of personal data and do not cover transfers to third parties such as IT outsourcing providers or data centres. To date very few companies have adopted binding corporate rules due to the expense and time it takes for the rules to be recognised within the EU.

Help

For assistance with transfers of personal data within or outside the EEA, SaaS, ASP, software on demand contract  or any other IT legal issues contact:

irene.bodle@bodlelaw.com
www.bodlelaw.com

To register for my newsletter click here

______________________________________________________

Other related articles:

SaaS, ASP Agreements – FAQs – Disaster Recovery

Do I need disaster recovery provisions in a SaaS agreement?

Disaster Recovery

Disaster recovery sets out the processes and procedures to be followed in the event of SaaS software, or customer data, no longer being accessible due to a problem with the technology infrastructure at the supplier’s data centre.

For example if there is a power cut, flood or fire at the data centre, the server on which the software is running will no longer function and the customer will no longer have full access to the software and its data. If the customer is using the software for a live website, the website will cease to function correctly, or possibly at all.

Supplier Obligations

The disaster recovery provisions of a SaaS agreement should be set out in the SLA and should as a minimum, include the following supplier obligations in the event of a disaster:

  • customers must be notified of the disaster;
  • any third parties used for disaster recovery should be identified;
  • the estimated time for restoring the servers and access to the software and services should be specified; and
  • details should be given about the supplier’s testing procedures i.e. how often its disaster recovery processes are tested.

Costs

The extent and speed of the disaster recovery offered by the supplier will depend upon the fee charged for this service. Suppliers often include the costs of basic disaster recovery in their licence fees. In addition, or as an alternative, they may offer higher levels of disaster recovery for additional fees. The faster and more individual the disaster recovery process is, the higher the fees.

If the supplier does not provide any disaster recovery services, or the customer is not satisfied with the disaster recovery offered, it should consider setting up its own disaster recovery procedure with a third party, particularly if a disaster would be business critical i.e. for a customer providing online banking services.

Avoiding Disasters

The most common disaster recovery risks are power failure, physical damage to the data centre or data and insolvency.

Power Failure

To minimise the risk of a power failure causing the servers to fail, ensure that the data centre has a continuous power supply (UPS) and power regulators to prevent fluctuations or interruptions in the power supply.

Backups

If the SaaS agreement includes backup of customer data, the regularity, media used for backups and storage should be set out in the SLA.  Backups should not be stored at the same physical location as the servers on which the data is being processed.

Encryption

The media on which customer data is backed up should be encrypted. Particularly, if backups are to be physically sent to the customer, or moved to another data centre in the event of a disaster.

Access to Data

In the event that the data centre or a third party making backups of customer data becomes insolvent, the customer usually has no right to access its data and backups. Provisions should be included in the SLA to give the customer the right to access its data and backups in such circumstances.

Help

For assistance with any disaster recover issues, SLA, SaaS, ASP, software on demand contracts or any other IT legal issues contact me at:

irene.bodle@bodlelaw.com
www.bodlelaw.com

To register for my newsletter click here

______________________________________________________

Other related articles:

 

SaaS, ASP Agreements – FAQs – Confidential Information

What confidentiality provisions need to be included in a SaaS agreement?

Define Confidential Information

Parties will obtain and have access to the business critical information of each other as a result of entering into a  SaaS Agreement. For example, they may have access to customer lists, banking information, IPR, source code and object code or business secrets and processes. Confidential information should be defined in the SaaS agreement to make clear what is, and what is not, confidential. Do not simply refer to documents which are “marked as confidential” or “which should be treated as confidential”. Not all confidential information exists in a physical format, particularly in a SaaS scenario – so do not restrict your definition to just documents.

Restrictions on Disclosure

Confidential information should not be passed on to third parties or used by either party for any purpose other than performing their duties under the SaaS agreement. However, under certain circumstance parties may be legally required to disclose confidential information to a third party and such disclosure must be permitted. Additionally, employees and agents of the parties (accountants, sub-contractors) may need access to the confidential information for the purposes of the SaaS agreement. Such disclosure should be permitted, but must be restricted to named or defined groups of sub-contractors i.e. the supplier’s hosting provider or the customer’s named IT outsourcing providers. Disclosure to competitors of either party should be specifically prohibited. If any third parties are to have access to a party’s confidential information they must be bound by the same confidentiality duties as the party disclosing the information to them.

Return or Destruction of Data

Once the SaaS agreement is terminated, or expires, all confidential information of each party should be returned or destroyed. Confirmation of destruction of data should be required in writing. This is particularly important in relation to any personal data, as under the Data Protection Act 1998 no personal data should be kept longer than necessary. The length for which such personal data may be stored will depend upon the type of data and the purposes for which it was collected and stored.

Freedom of Information Request – FOI

If the customer is a public authority or another body subject to FOIs, both the supplier and the customer will need to comply with any requests for releases of information within strict time limits. Provisions should be added to the SaaS agreement to give the supplier control over what is, and what is not, released to prevent third parties having access to its confidential information pursuant to such requests.

Subject Access Request – SAR

Similar provisions are contained in the Data Protection Act 1998 which allow data subjects to request a copy of the personal data held on them which the supplier is processing on behalf of the customer. The request is made to the customer, who will need to ensure that there are provisions in the SaaS agreement obliging the supplier to release appropriate data.

Audit Rights

Sometimes customer’s will have a regulatory duty (i.e. under the FSA) to check the supplier’s security structures and data storage systems. Any third parties used by the customer during the audit should be bound by the confidentiality provisions of the SaaS agreement before being permitted access to any confidential information.  This can be easily achieved by having the third party sign a non-disclosure agreement.

Help

For assistance with any confidentiality issues, SaaS, ASP, software on demand contracts or any other IT legal issues contact me at:

irene.bodle@bodlelaw.com
www.bodlelaw.com

To register for my newsletter click here

______________________________________________________

Other related articles:

 

SaaS, ASP Agreements – FAQs – Security

What data security provisions need to be included in a SaaS agreement?

Customer’s Security Obligations

These should be set out in the software licence. Access to the software and services should not be permitted to third parties without prior authorisation from the supplier. The customer should provide the following warranties:

  • existence of adequate security measure to ensure access to the software and services does not breach the terms of the SaaS agreement
  • relevant confidentiality provisions relating to the use and access to passwords required for accessing the software and services
  • the obligation to notify the supplier of all security breaches, unauthorised access to the software and services and misuse of passwords
  • provision of indemnities for breaches of the above warranties

Supplier’s Security Obligations

These should be set out in the software licence and in the service level agreement (SLA). The supplier’s obligations will be more extensive than the customer’s obligations due to the nature of a SaaS agreement and the inherent risks of operating over the Internet. The following provisions should be included:

  • details of the firewalls and cryptology used
  • obligation of the supplier to notify the customer of security breaches or data loss
  • details of the data centre security structure
  • restrictions on access to passwords
  • information about virus protection mechanisms

Additionally the supplier should reserve the right to suspend access to the software and services if there is a security breach in order to ensure the integrity or security of the software and services.

Audit Rights

Sometimes customer’s will have a regulatory duty (i.e. under the FSA) to check the supplier’s security structures and systems and that the supplier is complying with its contractual security obligations. If an audit right is granted the following issues should be covered in the SaaS agreement:

  • frequency of the audits
  • payment for the supplier’s time and assistance with audits
  • the supplier’s right to be given copies of audit reports
  • confidentiality provisions relating to access to the supplier’s IPRs, data and infrastructures and disclosure of such to third parties
  • whether or not the supplier has any obligation to make changes to the software and services following an audit

Help

For assistance with any security issues, SaaS, ASP, software on demand contracts or any other IT legal issues contact me at:

irene.bodle@bodlelaw.com
www.bodlelaw.com

To register for my newsletter click here

______________________________________________________

Other related articles:

 

SaaS, ASP Agreements – FAQs – Software Licence

The software licence to be included in a SaaS agreement is very different from the standard software licence found in non-SaaS agreements for the following reasons.

Term

Access to the software is provided together with support and maintenance services. Without support and maintenance there can be no licence and vice versa. This is because  the  customer has no copy (physical or intangible) of the source code or object code. The software is installed on the supplier’s server and accessed by the customer via the Internet.

The customer therefore does not own any software licence. The customer simply has the right to access the software and the services together for the term of the SaaS agreement. Unlike a standard software licence, no perpetual licence is granted. The term of the licence is the same as the term of the support and maintenance services and both cease to exist when the SaaS agreement is terminated or expires.

NB/It is possible to have  perpetual licence in a more complicated SaaS agreement but this is the exception rather than the norm, and is not dealt with here.

Use of the Software

The software should only be used for the specific purposes set out in the SaaS agreement. Issues such as territory, number of users, who the users are (i.e. the customer, the customer’s users, the customer’s subsidiaries and identified third parties).  No right to copy, distribute, resell or lease the software should be granted to the customer.

Intellectual Property Rights – IPR

The customer needs to be granted the right to use the software for the term, however no rights in the software, source code or support and maintenance services  should be transferred to the customer. No rights in any developed or customised software should , or can be transferred to the customer – as there will be no developed or customised software created in a standard SaaS agreement.

Copyright

No right to copy, decompile or create derivative works from the software should be granted to the customer. However, under the Copyright, Designs and Patents Act 1988 the customer has a mandatory right to decompile the software in limited circumstances, which should be referred to in the SaaS agreement, as such rights cannot be contractually excluded.

Escrow

If you are providing business critical software to customers (i.e. online banking) it is usual to offer customers the possibility of entering into an escrow agreement to hold the source code, or data in escrow. However, if the software is not business critical (to your customers) this should be an optional clause that can be added to the SaaS agreement later at the request of the customer, as most customers will not want to incur the additional cost of an escrow agent.

Help

For assistance with any software licence matters, in particular SaaS, ASP, software on demand contracts or any other IT legal issues contact me at:

irene.bodle@bodlelaw.com
www.bodlelaw.com

To register for my newsletter click here

______________________________________________________

Other related articles:

 

SaaS, ASP Agreements – FAQs – Escrow

When negotiating a SaaS agreement you may come across the term escrow. What is  escrow and is an escrow agreement necessary?

SaaS and Escrow

Under the terms of a SaaS agreement you do not own and only have very limited rights to use the software (which includes the source code) that you are accessing. This is usually not an issue until technical problems arise, i.e. unexpected service interruptions, downtime, loss of application functionality and loss of data. Such problems can add significant costs to your business and you are dependent upon the supplier to resolve these issues, unless you have an escrow agreement in place.

Escrow Agreement

An escrow agreement sets out the terms on which the  software source code will be held by a third party – an escrow agent – on behalf of the customer and the supplier. The escrow agent stores a copy of the software source code and will release this to the customer if any of the events set out in the escrow agreement occur (e.g. the supplier fails to maintain the software, there is a transfer of intellectual property rights in the software or the supplier becomes insolvent). Thus the customer has the right to continue to use the software if the supplier is in default. However, having the right to use the software and actually being able to use the source code are very different.

Limitations of Escrow Agreements

The following should be considered by customers before entering into an escrow agreement:

  • is the software business critical, if not, do you really need an escrow agreement?
  • the cost of setting up the escrow agreement and the ongoing renewal fees;
  • do you have the technical know-how to understand and use the source code in the event of an escrow release?
  • do you have programmers who can in the long term update and enhance the software to stop it becoming outdated?
  • will you need to engage a specialist software consultant to deal with the source code?
  • is there alternative SaaS software which could simply be used instead?

There is no point having access to the source code if you cannot actually use  and understand it, as access alone will not ensure business continuity.

Types of Escrow Agreement

If you decide to enter into an escrow agreement you will need to choose between a multi-licence or a single licence agreement.

Many suppliers have multi-licence escrow agreements for their source code already in place with recognised escrow agents. The customer can quickly be added to pre-existing agreement as a licensee. The advantage of multi-licence agreements is that they are relatively inexpensive (compared to a single licence agreement). The customer simply pays a fee to join the existing multi-licence agreement and usually an annual renewal fee. The disadvantage of a multi-licence agreement is that only the basic source code will be held in escrow, no customisations will be stored.

If the customer has any source code customisation that they are accessing it is worth considering having a single licence escrow agreement. This will ensure that the customer’s source code version is held in escrow. The disadvantage of this is that the single licence agreement will need to be set up and the fees are much higher.

Help

For assistance with any escrow matters, SaaS, ASP, software on demand contracts or any other IT legal issues contact me at:

irene.bodle@bodlelaw.com
www.bodlelaw.com

To register for my newsletter click here

______________________________________________________

Other related articles: