SaaS Agreements – FAQs – What is SaaS and Essential Terms to include in a SaaS Agreement

SaaS is the abbreviation for “software as a service”. You may know this under another name, for example subscription agreement, SaaS contract, software on demand, software subscription agreement, cloud computing or ASP services (application service provider). These names all refer to the same thing – hosted software being made available via the Internet to users.

What is a SaaS Agreement

A SaaS agreement is simply the name used for the agreement between a SaaS supplier and a SaaS customer which sets out the terms under which the SaaS software may be accessed. This will usually include a service level agreement (SLA) and a data processing agreement (DPA).

Differences between a SaaS Agreement and a Standard Software Licence

A SaaS agreement differs from a standard software licence in that:

  • The SaaS customer will not receive a physical or installed copy of the software;
  • No ownership in the SaaS software will be transferred to the SaaS customer;
  • The SaaS customer‘s right to use SaaS software will end upon termination of the SaaS contract.

Essential Terms to Include in a SaaS Agreement

The following legal issues should be included in any SaaS agreement, whether you are a SaaS supplier or a SaaS customer.

Software Licence

Access to the SaaS software should be limited to the term of the SaaS agreement. Once the SaaS agreement expires or terminates the software licence should automatically terminate.

If the SaaS customer is a global entity, you should specify:

  • Which companies or entities may access the SaaS software;
  • In which territories the software may be used; and
  • The number of authorised users;
  • Identify the specific purposes for which the SaaS software may be accessed; and
  • Name any third parties who will be permitted access to the SaaS software i.e. outsourcing providers or clients of the SaaS customer.

Intellectual Property Rights – IPR

The SaaS supplier should retain ownership of all IPR in the SaaS software and services it provides. The SaaS customer should retain ownership of all IPR in its systems, content and data. You should specifically state that the source code remains owned by the SaaS supplier. The SaaS customer should grant the SaaS supplier the right to use its IPRs for the term of the SaaS agreement i.e. to display the SaaS customer’s logos and copyrighted information.

Applicable Law, Jurisdiction & Language

A SaaS supplier should specify which law applies to the SaaS agreement and which courts will deal with any disputes arising from it. In international SaaS agreements make sure that you specify in which language the dispute will be dealt with, and if the SaaS agreement is in more than one language, which language prevails if there is a discrepancy between the two versions.

Return of Data

At the end of the SaaS agreement the SaaS customer’s data should be returned and to compy with the GDPR and other data protection laws all personal data must be returned and deleted. The format in which the data is to be returned and any payment for this service should be agreed in advance. Additionally, the parties can agree that the SaaS supplier will provide assistance in transferring SaaS customer data to a new supplier – in return for payment for this data migration service.

Data Processing Agreement (DPA)

The SaaS supplier is the data processor and the SaaS customer is the data controller. Under data protection law different rules apply to the data controller and the data processor. In compliance with the General Data Protection Regulation (GDPR) The SaaS supplier is obliged to process data in accordance with the SaaS customer’s written instructions and should protect itself against claims from third parties that such processing was illegal. Likewise, the SaaS customer will also need to protect itself against claims from third parties caused by the SaaS supplier not processing data in accordance with its instructions or the terms of the data processing agreement.

Both the SaaS supplier and the SaaS customer’s data protections obligations must be set out in a written data processing agreement (DPA) which forms a schedule to the SaaS agreement. In addition where any international transfers of EU, UK or Swiss personal data are made, Standard Contractual Clauses must be used and the SaaS customer and SaaS supplier must carry out Schrems II Data Transfer Assessments. The SaaS supplier must also provide a list of the sub-processors that it uses to provide the SaaS services and a security policy.

Service Level Agreement (SLA)

This sets out the hosting, support and maintenance services being provided to the SaaS customer by the SaaS supplier. The SLA should specify where the data centre is located, who is operating it, what security, backup and disaster recovery procedures are in place. Support hours and support services for dealing with hosting problems and software problems should be identified and documented and the procedure for dealing with upgrades and maintenance to the software should be specified. The particular details will depend on the amount being paid for the hosting, support and maintenance and the purpose for which the SaaS software is being used.

Summary

Due to the unique nature of SaaS agreements you will need to seek specialist legal advice on the content of a SaaS agreement whether you are a SaaS supplier or a SaaS customer to ensure that your rights are adequately protected and that you are fully complying with all applicable laws.

Help

Irene Bodle is an IT lawyer specialising in SaaS agreements, GDPR and cloud computing with over 15 years experience in the IT sector. If you require assistance with any SaaS or cloud computing contracts, GDPR or any other IT legal issues please contact me:

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

To register for my newsletter click here

______________________________________________________

Other related articles:

SaaS Agreements – Reseller Agreements – Price Fixing

SaaS suppliers and SaaS resellers should be aware that price fixing is illegal under UK and EU competition law. Often SaaS resellers are not aware that the terms of their SaaS reseller agreement include price fixing clauses. For example: If the SaaS reseller agreement includes clause on resale price maintenance (RPM). This will usually be deemed to be price fixing by the Competition and Markets Authority (CMA) who investigates breaches of competition law in the UK.

What is Price Fixing

Price fixing occurs when competitors agree (i.e. SaaS suppliers or SaaS resellers) what price they will charge SaaS customers for their SaaS services.

Price fixing occurs between a SaaS supplier and a SaaS reseller where a SaaS supplier tries to control the price at which SaaS services can be resold to SaaS customers for example by using RPMs.

What is RPM

An RPM is when a SaaS supplier controls the resale price of the SaaS services to customers, by agreeing with the SaaS reseller that the SaaS services will be resold at, or above, a particular price. RPM can be achieved directly by including this restriction in the terms of the SaaS reseller agreement.

RPM can also be achieved indirectly:

  • By including terms in the SaaS reseller agreement that restrict discounts on prices; or
  • Where financial incentives are offered to the SaaS reseller, to resell at a particular price.

RPM involves parties at different levels of the supply chain i.e. the SaaS supplier and the SaaS reseller.

Why RPM is Price Fixing

RPM is usually deemed to be “price fixing” and illegal because it prevents SaaS resellers from offering lower prices and setting their own independent prices at which they can resell SaaS services to SaaS customers.

Recent Fines

The CMA recently fined a fridge supplier £2.3 million for imposing a minimum advertised price on goods sold by a reseller because this restricted the price that goods could be advertised online by resellers. The supplier threatened to charge resellers “higher cost prices for its products” or to stop supplying products altogether if its resellers advertised fridges below the minimum price. This amounted to price fixing.

In a similar case involving a bathroom fitting company, the CMA imposed a fine of £786,000 for the use of RPMs. The supplier had threatened to penalise online resellers for not pricing its products at, or above, its recommended prices.

It should be noted that fines can be imposed on SaaS suppliers as well as SaaS resellers for breaches of competition law.

How to Avoid Price Fixing

In order to avoid direct or indirect price fixing and the risk of being fined by the CMA,

SaaS Suppliers should, in the terms of the SaaS reseller agreement:

  • Not dictate the price at which SaaS services can be resold, either online or through other sales channels;
  • Not include provisions that set a minimum advertised price for any sales of SaaS services;
  • Not use threats, financial incentives or take any other action, such as withholding supply or offering less favourable terms, to make SaaS resellers stick to recommended resale prices.

SaaS Reseller should in the terms of the SaaS reseller agreement:

  • Ensure that they are entitled to set the price of the SaaS services they resell to SaaS customers, regardless of whether sales are made online or through other sales channels;
  • Ensure that SaaS suppliers cannot dictate the prices at which a SaaS reseller can advertise their products online.

Consequences of Price Fixing

If a SaaS reseller has agreed with a SaaS supplier to resell SaaS services at fixed or minimum prices, both be could be found to be breaking competition law. In addition to both being fined up to 10% of worldwide turnover the SaaS supplier and SaaS reseller could also be:

  • Sued for damages;
  • Sent to prison for up to 5 years;
  • Disqualified from being a company director for up to 15 years.

Help

Irene Bodle is an IT lawyer specialising in SaaS, with over 15 years experience dealing with SaaS, cloud computing matters and IT law issues. If you require assistance with any SaaS agreements, cloud computing matters or any other IT legal issues please contact me at:

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

To register for my newsletter click here

______________________________________________________

Other related articles:

SaaS Agreements – FAQs – Disaster Recovery

Should SaaS suppliers include disaster recovery provisions in a SaaS agreement? If so, what provisions should be included in the SaaS agreement and where.

Disaster Recovery

Disaster recovery sets out the processes and procedures to be followed by a SaaS supplier in the event of its SaaS software and subsequently a SaaS customer’s  data not being accessible. The disaster usually results from a problem with the technology infrastructure on which the SaaS software is being made available, i.e. the SaaS supplier’s data centre or telecommunications provider.

Disasters

The most common disasters are:

  • power failure at the data centre;
  • physical damage at the data centre i.e. flood or fire;
  • physical damage to SaaS customer data i.e. loss, corruption or deletion;
  • insolvency of the data centre or third party telecommunications provider;
  • theft of hardware on which the SaaS software operates.

In any of these circumstances, the disaster usually makes the server on which the SaaS software is running unavailable to the SaaS customer.  As a result, the SaaS customer will not have full access to the software, SaaS services and its data. Where a SaaS customer is operating a live website, the website will cease to function correctly, or possibly at all.

Disaster Recovery Provisions

The following disaster recovery provisions should be set out in the SLA which forms part of the SaaS agreement:

  • the right of a SaaS customer to be informed of the disaster;
  • the obligation of the SaaS supplier to keep the SaaS customer informed of steps being taken to rectify the disaster;
  • the estimated time for restoring servers and SaaS customer data;
  • the right for the SaaS customer to terminate or be given a copy of SaaS customer data in the event of a disaster;
  • details of the SaaS 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 a SaaS supplier will depend upon the level of fees charged for the SaaS services. SaaS suppliers often include the costs of basic disaster recovery within their licence fees. In addition, or as an alternative, they may offer higher levels of disaster recovery for payment of additional fees. The faster and more individual the disaster recovery process is, the higher the fees will be.

Alternatives

If a SaaS supplier does not provide any disaster recovery services, or a SaaS 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 SaaS customer providing online banking services.

Some companies such as the NCC and Iron Mountain offer third party disaster recovery services to SaaS customers directly, whereby they  take over hosting of the SaaS services to ensure continuity of services for the SaaS customer.

Help

Irene Bodle is an IT lawyer specialising in SaaS, with over 15 years experience in dealing with SaaS, cloud computing and IT law issues. If you require assistance with any SaaS agreements, cloud computing concerns or any other IT legal issues please contact me at:

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

To register for my newsletter click here

_________________________________________________

Other related articles:

SaaS Agreements – Terms and Conditions – Limitation Clauses

SaaS suppliers should always include limitation clauses in their the SaaS terms and conditions to attempt to limit or exclude liability for certain types of losses and to cap their financial liability for breaches of contract. However, in order for limitation clauses to be valid, SaaS suppliers must ensure that the wording of the limitation clause is clear and unambiguous, otherwise the whole clause could be ruled void by a court and the SaaS supplier’s liability will then be unlimited.

Dundee City Council v Geddes

In Geddes, a Scottish case, a construction contract contained a limitation clause which attempted to limit the contractor’s liability to a local council for a failure to supply goods of satisfactory quality or reasonably fit for their purpose. The clause stated that a claim for breach must be made in writing within 24 hours of delivery unless there were “special circumstances” to justify delay.

Interpretation by the Court

The court decided that it could be argued in virtually every case that “special circumstances” would apply so the scope of the limitation was uncertain. Accordingly, the court held that the entire clause was invalid for uncertainty. This resulted in the contractor being liable to the council for its failure to supply goods of satisfactory quality or reasonably fit for the purpose.

Court Powers

SaaS suppliers should be aware that if a limitation clause in their SaaS terms and conditions is disputed, in assessing the validity of a limitation clause a court may:

  • simply delete the part of the clause excluding liability and leave the remainder standing;
  • declare the whole clause invalid; or
  • insert wording to amend the clause.

As a court can take any of these options, limitation clauses should be drafted to try to reduce the risk that none of the intended exclusions or restrictions will be valid in the event of a dispute.

Summary

SaaS suppliers should ensure that the language they use in limitation clauses:

  • is not ambiguous;
  • does not contain different types of exclusions in one single clause i.e. financial caps and restrictions on the types of losses that can be claimed should be separated.

Help

Irene Bodle is an IT lawyer specialising in SaaS agreements with over 15 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:

SaaS Agreements – Data Protection – EU US Privacy Shield

The GDPR prohibits SaaS suppliers and SaaS customers from transferring personal data to countries or territories outside the EEA unless they are considered to provide adequate protection. Below is a summary of the current position under the EU-US Privacy Shield which has replaced the safe harbor scheme.

Safe Harbor

Until the 6th of October 2015, SaaS suppliers and SaaS customers relied upon Safe Harbor (a self-certification standard operated by the US Department of Commerce and enforced by the Federal Trade Commission) when transferring personal data to the USA.

Grace Period

Following the invalidation of safe harbor, the Art. 29 Working Party, which is comprised of European Data Protection regulators, (the “Working Party” now known as the EBDP) made clear that no actions would be taken against SaaS suppliers or SaaS customers relying upon on safe harbor until the end of January 2016. This grace period was agreed to allow the Working Party, EU countries and the European Commission time to find a suitable political, legal and technical solution to the problem of transferring personal data from EU countries to the United States in compliance with EU data protection laws.

Interim Enforcements

However, national data protection authorities retain the right to exercise their  powers to protect a data subjects’ rights upon receipt of individual complaints against SaaS suppliers or customers. For example, the German Federal and State Data Protection Commissioners (“the Commissioners”) stated that there would be no grace period and that they would immediately take action against data transfers which were based on Safe Harbor, unlike the UK Information Commissioner’s Office (“ICO”) which made it clear that SaaS suppliers and customers would be given time to adapt.

Interim Options

Accordingly, SaaS suppliers and customers had three options for continuing to lawfully transfer personal data from the EU to the USA:

  • obtain consent from each data subject to the transfer of data to the USA;
  • create and have approved binding corporate rules (“BCRs”) for transatlantic transfers of personal data within a company’s group of companies;
  • enter into EU Model Clauses with US entities to whom personal data was transferred.

Privacy Shield

The grace period has now expired and a new privacy agreement called the Privacy Shield has been agreed by the US and EU to replace the safe harbour scheme. The Privacy Shield is based upon safe harbour but has additional protections, particularly with regard to public authority access to personal data. The Privacy Shield must now be reviewed by the European Commission before it can be relied upon and adopted by SaaS suppliers or customers. The European Commission is currently assessing whether or not the Privacy Shield provides adequate protection in accordance with EU data protection laws. This process is expected to take up to 3 months.

Current Position

The Working Party has confirmed that for the time being EU Model Clauses and BCRs are valid for transfers of personal data from the EU to the USA. Accordingly, Saas suppliers and SaaS customers should continue to us BCRs, consent or EU Model Clauses when transferring personal data to the USA and whilst monitoring the status of the Privacy Shield with their local data protection authorities.

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

Speaker at the Berlin CloudConf 2013.

To register for my newsletter click here

______________________________________________________

Other related articles:

SaaS Agreements – International Agreements – Valid Execution

Where an international SaaS agreement is entered into between a non-UK SaaS customer and a non-UK company of a SaaS supplier the parties should ensure that the SaaS agreement has been properly executed in accordance with the law of the country of incorporation of each company. Even where the SaaS agreement is governed by English law, failure to properly authorise or execute the SaaS agreement in accordance with the local law of each party could result in the SaaS agreement not being binding.

Integral Petroleum SA v SCU – Finanz

Two Swiss companies entered into a supply agreement that was governed by English law. The customer sued the supplier for breach of contract in the English courts and lost because the contract was never validly signed by the supplier in accordance with Swiss law requirements. The UK courts determined that the contract was not legally binding.

The Swiss commercial register stated that the supplier could only enter into a binding contract if two representatives of the supplier company signed the contract together. As only one representative signed the contract he had no authority to bind the supplier and the contract was held to not be legally binding. The customer therefore had no claim for breach of contract, as there was no binding contract.

Overseas Companies Regulations 2009

Regulation 4 of the Overseas Companies (Execution of Documents and Registration of Charges) Regulations 2009 sets out the requirements for the execution of documents by overseas companies under English law.

An overseas company will have validly executed a SaaS agreement if:

  • it has done so in a manner provided for in the regulation i.e. the SaaS agreement is signed by a representative acting under the company’s authority, in accordance with the company’s law of incorporation.

Law of Country of Incorporation

In light of the above, the English courts have clarified that where two non-UK SaaS companies sign a SaaS agreement governed by English law, the law that governs the validity of the execution of the SaaS agreement will depend upon where the companies are incorporated. In the above case as both companies were incorporated in Switzerland, Swiss law applied to the validity of the execution of the SaaS agreement.

Summary

Where a SaaS supplier is dealing with an overseas company, the SaaS supplier should not assume that the execution formalities are the same as in English law, even if the SaaS agreement is governed by English law. The SaaS supplier should check that whoever is signing the SaaS agreement on behalf of the SaaS customer is actually authorised to sign and where possible, seek local advice or a legal opinion for the country or countries in which the parties are located.

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

Speaker at the Berlin CloudConf 2013.

To register for my newsletter click here

______________________________________________________

Other related articles:

SaaS Agreements – International Agreements – Interest on Late Payments

SaaS customers often delay payment of invoices. In order to protect your SaaS business and improve cash flow, SaaS suppliers usually include the right to claim interest on late payments in the terms of their SaaS agreement or rely on the statutory right to interest under the Late Payment of Commercial Debts (Interest) Act 1998 (“Act”). However, following the decision in Martrade Shipping and Transport GmbH v United Enterprises Corporation SaaS suppliers should be aware of the limitations of relying upon the Act, particularly where the SaaS customer or SaaS supplier is a non UK entity.

Contractual Right to Claim Interest

SaaS suppliers can state a specific interest rate in their SaaS agreement terms under which interest for any late payment will be claimed. This can be a number i.e. 5%, or a reference to an index i.e. the European Central Bank base rate, or a combination of both i.e. the Bank of England base rate + 2%. The interest rate specified can be higher or lower than the statutory rate.

Statutory Right to Claim Interest

Alternatively, SaaS suppliers can simply say nothing about interest in the SaaS agreement and rely upon their statutory right to claim interest on late payments from a business customer (BTB) under the Act. The statutory interest rate to be applied is the applicable Bank of England Base Rate plus 8%.

Right to Claim Compensation

In addition to claiming statutory interest from a SaaS customer, under the Act SaaS suppliers can claim a fixed amount of compensation. The amount is based upon the amount of the outstanding invoice:

  • £40 – for debts less than £1,000;
  • £70 – for debts between £1,000 to £9,999; and
  • £100 – for debts over £10,000.

Recovery of Costs

Since the 16th of March 2013 SaaS suppliers have the additional right to claim the difference between the fixed compensation amount and their reasonable costs in recovering the debt e.g. the costs of appointing a debt recovery company or lawyer. However this right only applies to debts accrued after the 16th of March 2013.

Limitation to the Right to Claim Statutory Interest

Following the decision in Martrade in June 2014 the High Court disallowed a claim for interest for late payment under the Act on the basis that the parties had no substantial connection to England. Both parties were non-English entities but the contract was governed by English law and provided for arbitration in London.

The restriction imposed by the court is nothing new, it is included in section 12 of the Act, but many SaaS suppliers are unaware of it. Section 12 of the Act only permits the application of statutory interest to late payments if one or both of two further requirements are fulfilled:

  • There must be a significant connection between the contract and England; or
  • the contract must be one which would be governed by English law apart from the choice of law.

The High Court said that the Act did not apply in this case as by simply including a London arbitration or English court jurisdiction clause in the contract was not a connecting factor, as the decision to have disputes heard in London does not connect the substantive transaction itself to England. This therefore prevented the application of the Act and excluded the parties the right to claim penalty interest under the Act.

Implications for International SaaS Agreements

The above decision does not however mean that the application of the Act will be excluded from all international SaaS agreements. The Act and the high interest rate payable under it will apply if there is a substantial connection between the SaaS agreement and England

A substantial connection could for example be:

  • the SaaS supplier or the SaaS customer being an English entity;
  • England being the place of performance of obligations under the SaaS agreement;
  • where the parties carry out some relevant part of the SaaS services in England; or
  • where the SaaS agreement is governed by English law apart from the choice of English law.

Help

Irene Bodle is an IT lawyer specialising in SaaS agreements with over 15 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

Speaker at the Berlin CloudConf 2013.

To register for my newsletter click here

______________________________________________________

Other related articles:

SaaS Agreements – Heads of Terms – Entire Agreement Clause

Heads of terms are often by SaaS suppliers where the final terms of the SaaS agreement have not yet been fully agreed with the SaaS customer. By using heads of terms the SaaS supplier can start to provide the SaaS services to the SaaS customer. However sometimes the parties are unaware of, or overlook, the legal implications and dangers of using heads of terms prior to finalising the terms of the SaaS agreement.

A recent court case in the UK highlights these problems.

Matchbet Ltd v Openbet Retail Ltd

A software developer claimed damages against a technology supplier for breaching the terms of a development agreement. The development agreement was based on heads of terms but the final signed development agreement contained an entire agreement clause.

Entire Agreement Clause

An entire agreement clause is a clause which states that the terms of the agreement (in this case the development agreement):

  • are the entire agreement and understanding between the parties; and
  • supersede all proposals and prior agreements, arrangements and understandings between the parties.

The purpose of an entire agreement clause is to ensure that all of the rights and obligations of the parties are in one single agreement i.e. the agreement which contains the entire agreement clause, in this case the development agreement.

Relevance of Heads of Terms

As the development agreement contained an entire agreement clause, the heads of terms were irrelevant in determining the intention of the parties, when the court had to interpret the terms of the SaaS agreement. The court had to ignore the heads of terms as they were merely part of the pre-contractual negotiations between the parties and were excluded from the terms of the final SaaS agreement by the entire agreement clause.

Important Note

In light of the above, it is important for SaaS suppliers to understand the interaction between any heads of terms they use prior to signing a final SaaS agreement and the inclusion of an entire agreement clause in the final SaaS agreement.

Where a SaaS supplier wants to ensure that all of the provisions from the heads of terms are included in the final SaaS agreement, the final terms of the SaaS agreement should specifically mirror the provisions of the heads of terms.

Additionally, where the commercial terms have substantially changed between the signing of the heads of terms and the signing of the final SaaS agreement, it is essential that the SaaS agreement includes an entire agreement clause to exclude the out of date heads of terms.

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

Speaker at the Berlin CloudConf 2013.

To register for my newsletter click here

______________________________________________________

Other related articles:

 

SaaS Agreements – Terms and Conditions – Risk Assessment

SaaS customers often complain that the security provisions in SaaS agreements are inadequate and lack transparency. Following a risk assessment, often using external auditors and regulators, SaaS customers often ask SaaS suppliers to add numerous additional terms and warranties to their SaaS terms. By including the security provisions set out below in your standard SaaS agreement, SaaS suppliers can avoid having more rigorous provisions imposed upon them.

Right to Audit

SaaS customers increasingly want, or need, to check a SaaS supplier’s compliance with the security provisions contained in the service level agreement (SLA) for regulatory or data protection reasons. SaaS suppliers should allow SaaS customers (or their authorised third party) limited rights to carry out such security checks. These should be restricted to annual checks where reasonable written notice is given and the audit should take place during business hours.

Certification

Currently there is no harmonised security standard or certification available for SaaS suppliers. The STAR certification programme, backed by the British Standards Institute (BSI), was launched last year. Certification is based upon implementation of ISO 27001 and criteria set by the Cloud Security Alliance (CSA). The certification process provides an independent and technology neutral assessment of a SaaS supplier’s security standards.

SaaS suppliers need to demonstrate that they meet ISO 27001 on security management generally, as well as the criteria contained in the CSA’s Cloud Control Matrix (CCM), which includes:

  • risk management;
  • resiliency and security architecture;
  • facility security;
  • information security; and
  • operations management.

Once certified, SaaS suppliers are listed on the CSA STAR Registry as ‘Star Certified’ and can use the CSA STAR Certification logo.

Reputation

Maintaining a good reputation for data security is essential to a SaaS supplier. If security breaches have taken place in the past and attracted negative publicity, it is unlikely that potential SaaS customers will place any trust in a SaaS supplier’s ability to keep their data secure. SaaS suppliers should have an incident response plan in place before a security breach occurs. This should set out the procedures to be followed in the event of a security breach thus enabling the SaaS supplier to deal with the business impact of the breach and to mitigate any potential damage to reputation.

Insurance

Increasingly SaaS customers are requiring confirmation in the terms of the SaaS agreement that the SaaS supplier has appropriate cyber insurance in place. Such insurance covers the liability of the SaaS supplier to third parties and SaaS customers for claims arising out of the activities and conduct of the SaaS supplier in providing the SaaS services.

Such cyber insurance should cover the following risks:

  • damage to hardware and/or software;
  • loss or damage to data or computer records;
  • infringement of the intellectual property rights of third parties;
  • breaches of data protection law;
  • defects in computer programmes;
  • physical damage to customer property;
  • injury to visitors.

Summary

By obtaining security certification SaaS suppliers will obtain a valuable marketing tool which can be used to differentiate them from competitors. Also by having appropriate cyber insurance in place and an incident response plan SaaS suppliers will be able show SaaS customers the priority that they place on the security of data and that ongoing measures are really being taken to protect Customer data.

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

Speaker at the Berlin CloudConf 2013.

To register for my newsletter click here

________________________________________________

Other related articles:

SaaS Agreements – Legal Requirements – Online SaaS Sales

SaaS suppliers making online sales of SaaS services to business customers in the UK need to ensure that they have the necessary legal documents and information available on their website to comply with English law. Simply having a SaaS agreement online will not cover all legal obligations in the UK when providing SaaS services online. Below is a summary of the documents and information that you should have available on a UK website.

SaaS Agreement

The terms and conditions under which you will be providing SaaS services to customers should be set out in your SaaS agreement. These should as a minimum include:

  • granting SaaS customers a licence to access the SaaS services for the term of the SaaS agreement;
  • retaining ownership in all intellectual property rights in the software and services;
  • return of SaaS customer data on termination of the SaaS agreement;
  • the Customer’s obligations as a data controller under the Data Protection Act 1998.

Service Level Agreement (SLA)

This should set out the hosting, support and maintenance services being provided to the SaaS customer. The SLA should specify:

  • where the data centre is located;
  • who is operating the data centre;
  • what security, backup and disaster recovery procedures are in place;
  • what support services are provided;
  • when and how maintenance will be carried out.

Privacy Statement

When making online SaaS sales you will be collecting and processing the personal data of your SaaS customer. Even if SaaS customers do not have to register in order to use your website you will undoubtedly be using Google analytics or setting other cookies to collect information about visitors to your website. To comply with the Data Protection Act 1998, if you collect, store or process personal data i.e. email addresses you need to have a privacy policy on your website. Your privacy policy must be easy to find and should include the following information:

  • the type of data being collected;
  • why the data is being collected;
  • how the data is used and why;
  • information about any cookies used;
  • if and why personal data will be disclosed to third parties;
  • how and where data is stored;
  • how complaints or queries about personal data will be dealt with.

Registration under the Data Protection Act

If you collect personal data on your website – i.e. email addresses, name or address of a living individual, you will be processing personal data and must register as a data controller under the Data Protection Act. It is a criminal offence not to register.

About Us/Contact Information

SaaS suppliers must provide the following information in an easily accessible position on their website:

  • legal name i.e. XYZ Ltd;
  • geographical address;
  • contact details i.e. telephone number, fax number and email address;
  • which country your business is registered in and the registration number;
  • details of any supervisory body which regulates your business i.e. the FSA;
  • where you are registered for VAT and your VAT number;
  • clear details of prices and whether or not delivery and/or tax is included.

Compliance with other Laws

SaaS supplier’s will also need to consider their compliance with any other applicable laws or rules. These will be industry specific depending on the type of SaaS services being provided.
For example, if you provide email marketing services you will need to comply with applicable email marketing and advertising rules and guidelines such as the CAP Code and the Privacy and Electronic Communications Regulations 2003.

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

Speaker at the Berlin CloudConf 2013.

To register for my newsletter click here

______________________________________________________

Other related articles: