SaaS Agreements – Data Protection – Email Marketing and Consent

As a SaaS supplier you will undoubtedly be sending marketing emails in your own name to existing and potential clients to advertise your own products and services, or possibly as a SaaS service on behalf of a customer. In any event you should be aware that the Information Commissioner’s Office (ICO) has issued new guidance on direct marketing, with regard to complying with the Data Protection Act (DPA) and the Privacy and Electronic Communications Regulations (PECR) both of which apply to sending direct marketing to consumers (BTC).

Consent

SaaS suppliers must obtain “extremely clear and specific” consent from individuals in order to conduct direct marketing via email or through any other form of electronic marketing i.e. text or via the telephone. SaaS suppliers cannot simply rely upon implied consent unless this is adequate.

Implied consent will not be adequate if:

  • it is obtained via acceptance of a privacy policy which is hard to find, difficult to understand, lengthy, or rarely read;
  • it must be given in order to subscribe to a service;
  • it is not freely given;
  • the individual is not specifically informed about what they are consenting to; and
  • it does not involve a positive action indicating agreement.

Specific Consent

A SaaS supplier must obtain specific consent to the type of communication in question.  For example, if an individual has consented to receive marketing texts a SaaS supplier is not permitted to send marketing emails and vice versa. Also, although a general statement of consent to receive marketing might be valid for email marketing, it will not cover telephone calls or texts as additional rules apply to these forms of marketing under the PECR.

Email Marketing Lists

The ICO guidance specifically refers to the issue of obtaining consent in relation to the use of third party email marketing lists. Often marketing lists are sold to a SaaS supplier or a SaaS customer where the seller claims to have obtained relevant consents from individuals. However, such third party consent cannot be relied upon by the SaaS supplier or the SaaS customer – unless the individual intended their consent to be passed on to the SaaS customer or SaaS supplier (whoever is actually doing the marketing).

SaaS suppliers should also be aware that other regulatory bodies have rules that apply to social media and digital advertising that must also be complied with. For example the Advertising Standards Agency (ASA), the Digital Marketing Association (DMA) and the Office of Fair Trading (OFT) have their own rules.

How to Obtain Consent

SaaS suppliers should use opt-in boxes in order to obtain explicit consent to direct marketing from individuals. Clear records should be kept of all consents, showing when and how such consent was obtained. These records can then be used as evidence if a complaint is made.

On-going Marketing

The context in which consent is obtained will determine whether SaaS suppliers can rely on consent to all future direct marketing via electronic messaging. For example, consent for a one-off message, or consent that is clearly only intended to cover a short period of time or a particular context, will not count as on-going consent for all future marketing messages.

Fines for Breach

The ICO can fine SaaS suppliers up to £500,000 for serious breaches of the DPA or PECR i.e. for sending unsolicited marketing emails, texts or live and automated marketing phone calls.

Therefore if you are a SaaS supplier offering SaaS services to consumers or you have a SaaS customer who uses your SaaS services to send marketing emails to consumers, you need to ensure that you follow the ICO guidance on direct marketing.

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 learn more about SaaS and cloud computing join me at the Berlin CloudConf 2013 on 5th of December.

To register for my newsletter click here

______________________________________________________

Other related articles:

SaaS Agreements – Data Protection – Prism and US Laws

SaaS suppliers should be aware of relevant US laws when outsourcing SaaS services (data storage and hosting) to US companies or companies located in the USA. SaaS customers are becoming increasingly concerned about outsourcing in the USA following media reports about “Prism”. Namely, that the National Security Agency (NSA) accesses personal data stored on the servers of Microsoft, Apple, Google, Yahoo, Facebook and a few other major US public companies. Below is a summary of the most relevant US laws that SaaS suppliers should be aware of.

FISA

If you outsource any SaaS services to a US public company the US government can access SaaS customer data pursuant to the Foreign Intelligence Security Act (FISA).

FISA allows the US government to access and monitor the personal data of non-US citizens (located outside of the USA) held by US public cloud providers (i.e. Amazon or Google). Public cloud providers must secretly provide all assistance, facilities and information requested by the government if they request access to SaaS customer data. The public entity is not permitted to inform the SaaS supplier that it has disclosed or been asked to disclose personal data, nor that the data is being monitored.

The Patriot Act

If you are a SaaS supplier owned by a US parent company or you outsource any SaaS services to a US located data centre or a US based company, US law enforcers can access SaaS customer data pursuant to the Patriot Act.

The Patriot Act gives US law enforcement authorities the right to access personal data held by SaaS suppliers, regardless of where in the world the data is stored. The Act also gives US law enforcers the right to prevent SaaS suppliers from informing their customers that they have handed over personal data. The Act applies not just to SaaS suppliers owned by a US company but also to any SaaS suppliers using the services of a US subsidiary for data processing i.e. a US data centre.

HIPAA

If you are a SaaS supplier providing SaaS services to a US customer who is a health care provider you, and your sub-contractors, must comply with the security and privacy obligations of the Health Insurance Portability and Accountability Act 1996 (“HIPAA”).

HIPAA applies to any SaaS supplier who creates, receives, maintains, or transmits protected health information (“PHI”), regardless of whether or not the SaaS supplier actually views the data. HIPAA applies even if the SaaS supplier is not located in the USA. Any subcontractors a SaaS supplier uses i.e. a data centre will also need to comply with HIPAA.

SaaS Suppliers must include the privacy and security obligations set out in HIPAA in their SaaS agreements with US health care provider customers. SaaS suppliers are directly liable for breaches of the HIPAA security and privacy rules, which includes failing to cooperate with DHHS investigations of HIPAA breaches. Liability is strict i.e. a SaaS supplier will be liable regardless of intent. The penalties for breach are severe and a SaaS supplier can be fined up to 1.5 million US dollars for all breaches in any calendar year.

Summary

Under the provisions of the US Patriot Act and FISA the personal data of SaaS customers based in the EU must be shared with US law enforcers without the customer being informed, even though this conflicts with English and EU data protection law. Under HIPAA SaaS suppliers must comply with detailed privacy and security provisions of a US law applicable to the health care industry or face severe fines.

It is therefore important that SaaS suppliers ensure they are aware of the extent of any US laws they will be subject to when:

  • contracting with US SaaS customers; or
  • outsourcing SaaS services to companies linked to or based in the USA; or
  • if they have a parent company based in the USA.

SaaS suppliers should have procedures and measures in place to deal with any applicable US laws. These procedures need to be set out clearly in the terms of the SaaS agreement with the Customer, bearing in mind mandatory obligations to comply with US laws.

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:

Other related articles:

SaaS Agreements – Terms and Conditions – Need for an Arbitration Clause

SaaS customers and suppliers entering into business to business (BTB) contracts are increasingly using arbitration clauses in their SaaS agreements to avoid going to court to resolve disputes. If you do not already have an arbitration clause in your SaaS agreement it is worth considering adding one for the following reasons.

Costs of Litigation

Court fees charged by the UK courts for dealing with commercial disputes have been substantially increased in the last few years. In addition to court fees, you will need to pay solicitors and barristers to represent you in court. Legal fees for defending a SaaS dispute can easily run into millions of pounds in a large intellectual property dispute. Also, the English law principle of the “loser pays” will add substantially to the costs of the losing party.

Speed

Litigating a dispute is not a fast process. It can take months to prepare a claim before court proceedings are even issued. Following the issuing of the court proceedings, it could then take a couple of years for the SaaS dispute to be decided at trial. Thereafter the parties may be able to dispute the court’s decision, thus making the process even longer, unlike an arbitration decision which is final and can only be disputed in very limited circumstances.

Confidentiality

Court proceedings are open to the public (i.e. your competitors) who will have access to details about the operation of your SaaS business, prices and products. Such information is confidential information but may have to be disclosed in litigation. Arbitration proceedings are held in private and details about the existence of the dispute or any of your confidential information revealed in the process can usually remain confidential.

Brussels I Exemption

Currently arbitration proceedings can be delayed, blocked or disputed by one of the parties simply issuing court proceedings in their own courts (due to the application of Regulation (EC) 44/2001 on the jurisdiction and the recognition and enforcement of judgments). Once the Regulation is revised and in force it will specifically exclude arbitration from its scope and the aforementioned tactic will no longer be of any practical use.

Summary

Whether or not you decide to include an arbitration clause in your SaaS agreement will depend upon the importance of the above factors to your SaaS business and the types of matters that you envisage being disputed. Also bear in mind that you should carefully consider the type of expert to be used in the arbitration process and how the costs of the arbitrator should be allocated between the parties to the dispute.

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:

 

SaaS Agreements – Terms and Conditions – Limitation of Liability

The terms of a SaaS agreement should always include a clause limiting the SaaS supplier’s liability to the customer. The specific details of the liability clause will depend upon the type of SaaS software being supplied, the value of the SaaS agreement and what is usual in the business sector in which the parties operate.

The following issues should be covered by the limitation of liability clause in most SaaS agreements.

Amount of Liability

If you do not cap the amount of your monetary liability to SaaS customers in your SaaS agreement you will be liable for an unlimited amount. You can specify whatever financial cap you choose for all liabilities or specific liabilities, provided that you do not place any cap on your financial liability for:

  • death or personal injury arising out of negligence; and
  • fraud or fraudulent misrepresentation;

Under English law you cannot limit your liability for these issues and any attempt to do so will be invalid and could make all of your limitation of liability clauses invalid.

Type of Damage Covered

In addition to limiting the amount of your liability you should also limit the types of damages and losses for which you will be liable. Generally in SaaS agreements, liability is excluded for indirect, consequential and economic losses. If there are any particular losses that you do not want to be liable for it is prudent to specifically state these in order to ensure that they are included in your restriction. For example, the non-functioning of the SaaS software due to the Internet being unavailable.

Liquidated Damages

In some circumstances you may want to specify a fixed amount that the parties agree in advance is a fair sum to be paid for particular breaches of the SaaS agreement. Usually liquidated damages (service credits) will be specified in your service level agreement (SLA) for availability problems. Remember that if you include liquidated damages in your SaaS agreement you should ensure that no other types of damages can be claimed in addition for the same breach.

Validity of the Limitation

In order for your limitation of liability clauses to be valid they must:

  • be reasonable;
  • be incorporated into the terms of the SaaS Agreement; and
  • be clearly worded.

There are different rules concerning the reasonableness of your limitation of liability depending upon whether you are operating business to business (BTB) or business to customer (BTC).

Any limitation clause should be included in your standard terms and conditions and the wording should be clear. Remember that any uncertainty or contradiction in the wording will be construed in favour of your SaaS customer. For example, specifically state that indemnities are included in the financial cap on liability.

Foreign Laws

If you supply SaaS services outside of the UK SaaS customers often request that you change the law that applies to the SaaS agreement to their local law. Be careful when agreeing to this, as your limitation of liability clauses could be invalid under the SaaS customer’s local law and you will then have unlimited liability for all claims.

Alternatively, if your SaaS agreement is currently subject to a law other than English law and you wish to change the applicable law to English, you should have the agreement checked by an English lawyer, as you will probably be able to restrict your potential liabilities to a greater extent under English law.

General

In view of the above it may be worth reviewing your SaaS agreement to ensure that it covers the above issues in order to limit your liability for potential claims.

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:

 

SaaS Agreements – Terms and Conditions – Subcontractors and Outsourcing

The terms of your SaaS agreement must include the right to use sub-contractors as 99% of SaaS suppliers use at least one sub-contractor – a third party data centre – to host their SaaS software. SaaS customers often try to prohibit the use of sub-contractors or place severe restrictions on their use by insisting that they must give prior consent to each sub-contractor. This is not acceptable for practical reasons as often numerous sub-contractors are used in providing the SaaS services and these sub-contractors will change over time.

Types of Sub-Contractors

The type, nature and number of sub-contractors that a SaaS supplier will use depends upon the SaaS software being used and the business sector in which you operate. However, generally the following sub-contractors are commonly used.

Hosting Centre

All SaaS suppliers will host data in a data centre which is in 99% of cases owned and operated by a third party. It is therefore essential that you specifically include the right to host customer data and process it in your third party data centre and you should reserve the right to be able to change the data centre without requiring prior consent from the SaaS customer.

Backups and Disaster Recovery

Many SaaS suppliers use online third party providers to backup data remotely and/or to provide disaster recovery services. If SaaS customers want to restrict your right to sub-contract, do not forget to include these sub-contractors in the list of approved sub-contractors, again reserving the right to change them without requiring the prior consent of the SaaS customer.

Consultants

Many SaaS suppliers use third party software developers or offshore IT outsourcing centres to develop source code for their SaaS applications. If you do so, it is essential that you have the right to sub-contract included in the terms of your SaaS agreement. Also where professional services are provided to SaaS customers, third party consultants are often used and you will also need to have the right to use such sub-contractors. In such cases many SaaS customers will then require you to carry out security and background checks on such individuals (as if they were employees).

Liability

A SaaS customer’s main objection to the use of sub-contractors, is that they will have no recourse against the sub-contractor directly if there is a breach of contract caused by an act or omission of the sub-contractor i.e. the data centre is flooded and the SaaS service goes offline. It is common practice for SaaS suppliers to state in the SaaS agreement that any breach by a sub-contractor of the SaaS agreement will be treated as if the breach had been caused by the supplier itself. The customer should then agree to the use of sub-contractors as the aforementioned risk has been minimised.

Data Protection

In addition, SaaS customers often try to prevent the use of sub-contractors due to their obligations to comply with the provisions of the Data Protection Act 1998. SaaS customers often require the SaaS supplier to confirm that the data centre is bound by written obligations similar to those that the SaaS supplier gives to the customer in the SaaS agreement before it will agree to the sub-processing of data by the third party data centre. It is becoming increasingly common for SaaS customers to require SaaS suppliers to sign separate data processing agreements, particularly where the customer is a local authority.

Summary

By including appropriate provisions in your SaaS terms and conditions which cover the usual concerns raised by SaaS customers and address the risks of using sub-contractors, SaaS supplier’s should be able to avoid protracted discussions on their contractual right to use sub-contractors.

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:

 

SaaS Agreements – SLA – Proposed EU Model Terms

The European Commission has recently released a paper on cloud computing stating that it will develop model terms for SaaS agreements which should be available for use in service level agreements (SLAs) by the end of 2013.

Need for Model Terms

An SLA determines the relationship between a cloud provider (SaaS supplier) and a cloud user (SaaS customer). During the negotiation process the terms of the SLA often form, or destroy, the basis of trust that SaaS customers have in a SaaS supplier’s ability to deliver the SaaS services. SaaS customers often complain that SLAs:

  • are too complex;
  • contain extensive disclaimers;
  • impose a choice of applicable law; and
  • exclude liability for data integrity, confidentiality and service continuity.

The Commission claims that SaaS agreements will be made fairer and safer by using model clauses. It argues that SaaS customers are currently “locked in” to agreements with SaaS suppliers making it difficult for customers to change their supplier due to non-interoperability and data portability issues.

Common European Sales Law and Model Terms

Within the context of the Commission’s on-going work on developing a common European sales law, it is now also preparing model terms specifically designed for cloud computing. These will cover issues such as:

  • subcontracting;
  • data preservation after termination of the SaaS agreement;
  • data disclosure and integrity;
  • data location and transfer;
  • direct and indirect liability; and
  • ownership of the data.

The proposed new model terms are being designed for use by SaaS suppliers in SaaS agreements with consumers and small businesses.

Voluntary Certification and Audit

In addition to developing model terms, the Commission wants to develop new EU-wide voluntary certification schemes and independent compliance mechanisms to promote trust in cloud computing. Such schemes would include independent certification:

  • of a SaaS supplier’s IT systems’ compliance with legal and audit requirements;
  • that a SaaS supplier’s applications and systems are interoperable and secure; and
  • that data is reversible and portable.

Changes to Current Model Clauses

As part of the above process, the Commission will also review the existing model contract clauses. These can be used in SaaS agreements where personal data is transferred from the EU to non-EU countries to ensure compliance with EU data protection laws. The Commission intends to adapt these model contract clauses to “fit” with cloud services.

Summary

Currently the Commission is working with stakeholders to prepare the new model terms and to develop systems for the voluntary certification and audit of SaaS suppliers. In late 2013 when the drafts are available, SaaS suppliers should review their SaaS agreements and SLAs to check their compliance with/divergence from the proposals.

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:

SaaS Agreements – The Advantages of using English Law

If you are a SaaS supplier who often deals with customers located outside of the UK, you will have experienced customers insisting on their local law applying to your SaaS agreement. Many SaaS suppliers agree to this by simply removing “English law” from the SaaS agreement and replacing it with, for example, “German law” unaware of the consequences this will have upon their SaaS terms and conditions.

Law and Jurisdiction

There is an important difference between applicable law and applicable jurisdiction. Applicable law specifies the country’s laws that will apply to your SaaS agreement, if there is a dispute. Jurisdiction specifies which courts will have authority to deal with a dispute. Usually your SaaS agreement will specify England and Wales as the applicable law and the courts of England as the jurisdiction.

Therefore, if you change the applicable law in your SaaS agreement you may also want to consider changing the country in which the courts are located that will deal with any disputes.

Language

Do not forget to specify in the SaaS agreement in which language disputes should be dealt with. If you do not speak or understand the local language of your customer, you should state that all disputes must be dealt with in English, particularly if you have agreed to your SaaS agreement being translated into your customer’s local language. You should also state that the English version of the SaaS agreement will prevail if there is a discrepancy between the two versions.

Limitation of Liability

By agreeing to a change of the law applicable to your SaaS agreement you could automatically be invalidating many of the limitations on liability contained in your SaaS agreement. For example, in France and Germany you cannot limit your liability for gross negligence, wilful misconduct, breach of material obligations or some types of force majeure.

Damages Available

By agreeing to a change of the law applicable to your SaaS agreement you may also become liable for types of damages that you claim to exclude in your SaaS agreement, i.e. direct damages, indirect damages, typically foreseeable damages, punitive damages, as in some countries liability cannot be limited for these types of damages or the local understanding of what types of losses fall within these areas may differ from English law.

Consumer or Business

By agreeing to a change of the law applicable to your SaaS agreement you could become liable to local laws that apply to consumer contracts, even though you are contracting with a business. For example, in France if you enter into a SaaS agreement with a business which does not operate in your business sector – the customer will be considered to be a consumer and will be protected by local consumer protection laws.

Extra Rights

By agreeing to a change of the law applicable to your SaaS agreement you may grant customers new rights that do not exist under English law. For example, in Germany under mandatory German law a customer can lower the price it pays for the SaaS services if the service is defective.

General

For the above reasons English law is often the law of choice used in international SaaS agreements. Suppliers can more easily avoid “hidden” mandatory laws which can invalidate your carefully drafted supplier terms and conditions and English law allows you more freedom to draft terms free from mandatory legal restrictions.

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:

SaaS Agreements – Agency Agreements – Commercial Agents Regulations

SaaS suppliers often use partners to find prospects, refer leads, assist with the sales process or to conclude sales with SaaS customers on their behalf. Many SaaS suppliers are not aware that the terms of the Commercial Agents Regulations 1993 may apply to the terms of the agreement between the SaaS supplier and its commercial agent.

What is a Commercial Agent?

A commercial agent is a person or company who acts on behalf of a SaaS supplier to find leads and/or assist with sales of the supplier’s SaaS software. SaaS suppliers usually use agents where they need to find customers outside of their territory or business sector.  The agent has no legal relationship with the customer – the contract with the customer is made with the SaaS supplier.

Commercial Agents Regulations 1993

These Regulations apply to all agency agreements made with a commercial agent based in the EU in relation to goods. If you are a SaaS supplier who only supplies services and no goods then the Regulations will not apply. The rules apply regardless of where the SaaS supplier is based. For example if you are a SaaS supplier located in the USA using an agent in the UK, the Regulations will still apply to your agency agreement.

The Regulations include mandatory rules on notice periods that have to be given to agents, payment terms and compensation or indemnities payable to the agent if the agency agreement is terminated.

Mandatory Payments on Termination

If the agent is located in the EU, the SaaS supplier must pay commission for up to a year after termination of the agency agreement (regardless of the reason for termination) or an indemnity. Compensation will be paid unless the agency agreement states than an indemnity should be paid.

Indemnity

If an indemnity is specified in the agency agreement, the amount payable is limited by the Regulations to a maximum of 1 year’s gross commission. This will be based on the average commission paid to the agent over the last 5 years. In calculating the amount of an indemnity, unless the parties have agreed otherwise, the benefits accruing to the SaaS supplier’s corporate group are not considered to be benefits of the SaaS supplier and can be ignored.

Compensation

If the agency agreement is silent or the SaaS supplier specifies the payment of compensation, a court will determine how much compensation the agent is entitled to. There is no cap on the amount that can be awarded to an agent. In McQuillan v McCormick 2010 the High Court identified the following factors which should be considered when determining how much compensation an agent should be paid on termination:

  • loss of value of the agency relationship;
  • state of the market;
  • no cap on the amount;
  • future possible income stream to the SaaS supplier after termination;
  • whether the agreement is exclusive or non-exclusive.

In this case the agent received approximately one year’s commission from the court.

Limitation Period for Claims

Agents lose the right to claim compensation or an indemnity if they fail to serve notice of their intention to make a claim within one year of termination of the agency agreement.

Notice Period and Termination

If the agency agreement is for an indefinite period it can be terminated by either party giving notice. This also applies where a fixed term agency agreement is converted into an indefinite agreement.

Mandatory minimum notice periods are specified under the Regulations. These are:

  • one month for the first year;
  • two months for the second year; and
  • three months for any third or subsequent years.

The parties may agree longer notice periods, but the notice provisions imposed on the agent must be no longer than those which the supplier has to give.

What if the Agency Agreement is not Governed by English law

Often agency agreements state that the laws of a non-EU country e.g. USA or Canada apply to the agreement or that disputes should be referred to arbitration outside of the EU.  Usually the Courts in a country outside the EU will not recognise a claim for compensation or an indemnity under the Regulations.  However, if you have an agreement with an agent based in the UK, the fact that your agreement is subject to the law of a non-EU country does not mean that the Regulations do not apply to the agency agreement.

For example, the right of the agent to claim compensation or an indemnity on termination under the Regulations cannot be excluded.   Even though your agency agreement may be governed by non-EU laws, an agent located in the UK will still be entitled to bring a claim in the English Courts for compensation or an indemnity under the Regulations. If the agent is located in another EU country, then the local law version of the Regulations applicable to that EU country will apply.

How to Avoid Paying Compensation after Termination

The SaaS supplier is not required to pay compensation if the agent has terminated the agency agreement “because of default attributable to the commercial agent which would justify immediate termination of the agency agreement”. For example if the agent has committed a serious breach of contract, such as ignoring an exclusivity provision. However, such exclusions are very limited.

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:

SaaS Agreements – Patriot Act – Renewed Customer Concerns

Recently SaaS suppliers have seen a marked increase in EU customers raising concerns about disclosure of their data to US law enforcement authorities under the Patriot Act – an American anti-terrorism law – particularly where the SaaS supplier has a parent company in the USA or data is being hosted or processed in the USA.

High Profile Cases

Microsoft recently admitted that United States law enforcement authorities can access their European customer data without having to obtain a court order, ask for consent or even inform data subjects of the disclosure under the terms of the Patriot Act. To add to SaaS suppliers worries it is believed that BAE recently withdrew from contract negations for a Microsoft SaaS product due to fears that defence secrets could be accessed by the US authorities under the Act.

The recent publication of the new proposed EU data protection regulation has also added to customer fears that data is not safe from disclosure under the Patriot Act. The new regulation attempts to counter the application of the US Patriot Act by stating that non-EU companies will have to comply with EU data protection rules when accessing EU citizen data.

The Patriot Act v European Data Protection Laws

The provisions of the Patriot Act conflict directly with English and EU data protection laws.

The Patriot Act gives US law enforcement authorities the right to access personal data held by SaaS suppliers, regardless of where in the world the data is stored. The Act also gives US law enforcers the right to prevent SaaS suppliers from informing their customers that they have had to hand over their personal data.

Data protection laws in the 27 countries of the EU all prohibit the disclosure of personal data without a data subject’s consent or knowledge.

Therefore if a EU company is faced with a Patriot Act disclosure request it is impossible to comply with both the US law and the EU company’s local data protection laws. In practice the US law usually prevails. Some of the largest global software and search engine companies have admitted that EU customer data has already been disclosed by them as a consequence of requests under the Patriot Act.

The Cloud is not the Problem

SaaS customers often falsely believe that their data is not safe from disclosure due to the cross-border nature of cloud computing. However this problem applies to all data whether or not it is stored or processed in a SaaS model. Most countries (the UK, France, Spain and Belgium to name a few) have laws similar to the Patriot Act that all, not just SaaS suppliers must comply with i.e. in the UK the Regulation of Investigatory Powers Act 2000 (RIPA) requires disclosure of the content of communications to police forces.

Also data stored or processed anywhere outside of the EEA, in a country which does not have equivalent protection will be subject to all local disclosure laws i.e. in China and India, and such local laws may be less restrictive than the Patriot Act with regard to the type of data that must be disclosed.

In any event, regardless of whether or not the Patriot Act applies to customer data, the US authorities can access customer data even when it is hosted outside of the USA and there is no company presence in the USA under Mutual Assistance Legal Treaties (MLAT)

Assessing the Actual Risk of Disclosure

SaaS customer concerns about the Patriot Act are valid but these must be considered in light of:

  • The type of data covered by a request for disclosure under the Patriot Act;
  • The likelihood of the customer data ever being requested; and
  • The fact that customer data is already subject to similar disclosure obligations to the UK government and foreign governments under other existing laws.

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: