SaaS Agreements – Data Protection – Safe Harbor Still Adequate

Recently, the Department of Commerce’s International Trade Administration (ITA) – a US government body – published a document confirming that any SaaS suppliers based in the US (and/or SaaS suppliers using a data centre located in the US) who are “safe harbor” registered must be recognised as having an “adequate” level of data protection. The ITA rejected the view that EU data protection authorities can unilaterally refuse to recognise safe harbor certification as a valid means of demonstrating that a SaaS supplier based in the US (and/or SaaS suppliers using a data centre located in the US) has an adequate level of data protection.

Background

Under current EU data protection laws, SaaS suppliers cannot send personal data outside of the EEA (the 28 EU member states plus Norway, Iceland and Liechtenstein) unless adequate protections have been put in place or where the destination country is pre-approved as having adequate data protection. Only the following countries are pre-approved and recognised as having adequate protection: Andorra, Argentina, Canada, Faroe Islands, Guernsey, Israel, Isle of Man, Jersey, New Zealand, Switzerland, Uruguay and Japan.

EU Position

Last year the Article 29 Working Party, a EU privacy body, claimed that SaaS customers based in the EU needed to see actual evidence that US SaaS suppliers (and/or SaaS suppliers using data centres in the US) complied with safe harbor standards. They claimed it was not enough for SaaS customers to simply rely on the fact that a SaaS supplier was registered under the safe harbor scheme.

ITA Position

The ITA disagrees with the above position. The ITA points out that the same rules apply to all SaaS suppliers under EU data protection laws regardless of whether or not they are located within the EEA, an ‘adequate’ country or are safe harbor registered. As the safe harbor framework is binding on all countries within the EEA additional requirements cannot be imposed exclusively on US SaaS suppliers (and/or SaaS supplier using data centres in the US).

Additionally, safe harbor SaaS suppliers (and/or SaaS suppliers using data centres in the US) are not obliged to use the EU model clauses in order to be recognised as adequate, as these are simply for use as an alternative approach to safe harbor. Moreover, they were specifically designed to address the adequacy requirement where safe harbor is not an option.

Additional Requirements

The ITA accepted that US SaaS suppliers (and/or SaaS suppliers using data centres in the US) must enter into a basic processing agreement with SaaS customers (which could form part of the SaaS agreement) but only to ensure that the SaaS supplier has sufficient instructions regarding use of the personal data. This requirement applies to all SaaS suppliers.

Additional requirements could only be imposed if these were required under other applicable laws. For example, under the Markets in Financial Instruments Directive (MiFID) if a US SaaS supplier (and/or SaaS supplier using data centres in the US) enters into a SaaS agreement with a SaaS customer who is providing financial services the terms of the SaaS agreement must guarantee the SaaS customer physical access to the US premises at which data is being processed.

Summary

SaaS suppliers who have SaaS customers querying their “adequacy” and compliance with EU data protection laws can use the ITA document to confirm that safe harbor registration does provide “adequate” protection. Along with the terms of the SaaS agreement, which will include specific data processing obligations, SaaS customers should be satisfied that processing in the US under safe harbor is adequate.

In addition, the European Commission has indicated that safe harbor will continue to be deemed “adequate” in the final version of the new proposed EU Data Protection Regulation.

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 – FAQs – What is a SLA?

SLA is the common abbreviation used for a service level agreement. When providing SaaS services to customers you need to include a SLA in your SaaS agreement, either as part of the main terms of your SaaS agreement or in a specific SLA schedule. A SLA should set out the following support and maintenance services that you will provide to customers to ensure that the SaaS software is made properly available to them.

Availability

The level of availability of the SaaS software should be stated in percentage terms. The basis on which availability is calculated should be included i.e. monthly, annually and any exclusions from the calculation should be clearly stated.

Software Support and Maintenance

Customer support is usually provided to assist customers when problems arise with the availability or functioning of the SaaS software. Customer support provisions should include:

  • A description of the support services to be provided;
  • The times and days on which support will be provided;
  • How support will be provided i.e. online, via telephone;
  • Response and resolution times for dealing with SaaS software problems; and
  • Maintenance times for carrying out updates, repair and maintenance to your SaaS software.

Hardware Maintenance

SaaS providers use servers (hardware) usually located in a third party data centre to host their SaaS software. The provisions to be included in a SLA will be determined by the level of service that the third party data centre provides to the SaaS supplier. The data centre provisions should be reflected in the terms of your SLA but will generally include:

  • A brief description of the security provisions in place at the data centre;
  • A brief description of the technical infrastructure at the data centre;
  • Any applicable disaster recovery provisions;
  • Backups of data.

Commercial Considerations

The way in which you incorporate a SLA into your SaaS agreement and the degree of detail that you provide to SaaS customers will largely depend upon the following:

  • The type of SaaS products and services you are supplying;
  • How much the customer pays for the SaaS product and services;
  • Whether the SaaS product is business critical i.e. online banking;
  • What is standard in that particular business area; and
  • The terms of the hosting agreement with your data centre.

Summary

Due to the unique nature of a SLA you will need to seek specialist legal advice on the content of a SLA whether you are a supplier or a customer to ensure that your rights are adequately protected.

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 – Data Protection – FISA Customer Concerns

SaaS suppliers who use US public cloud providers to store, process or host their SaaS customer’s data as part of their SaaS services may now experience customers raising concerns about the risk of disclosure to, and monitoring of, their data by the US government under the Foreign Intelligence Security Act (FISA).

FISA

FISA (a US law) gives the US government the right to access and monitor the personal data of non-US citizens (who are located outside of the USA) held by US public cloud providers (i.e. Amazon or Google), without a warrant for a period of up to one year, for the purposes of acquiring foreign intelligence information. Public cloud providers must secretly provide all assistance, facilities and information requested by the government. They are not permitted to inform SaaS suppliers that they have disclosed or been asked to disclose personal data or that it is being monitored.

Breach of European Data Protection Laws

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. The provisions of the FISA conflict directly with English and EU data protection laws.

The recent amendment to this US law adds to the concerns raised by the Article 29 Working Party last year in their opinion on cloud computing and data protection. In this opinion, which amongst other things the working party said that EU businesses using cloud services i.e. SaaS customers must ensure that non-EU providers i.e. SaaS suppliers comply with EU data protection laws and that simply relying on a US company’s safe harbor registration was not enough.

FISI is not the only Problem

SaaS customers often falsely believe that their data is “unsafe” due to the fact that SaaS supplier’s use third party data centres to store and process their data. However the risks of personal data being disclosed apply regardless of whether or not data is stored or processed in a SaaS model. Most countries including the UK, France, Spain and Belgium have data disclosure laws that all, not just SaaS suppliers, must comply with. For example in the UK the Regulation of Investigatory Powers Act 2000 (RIPA) requires companies to disclose 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 much wider than FISA.

In addition, in the USA notwithstanding FISA, the US authorities can access customer data 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 Risks

SaaS customer concerns about FISA are valid but these must be considered in light of:

  • The type of data SaaS customer’s are providing;
  • The likelihood of the customer data ever being monitored or 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:

 

SaaS Agreements – Terms and Conditions – The Bribery Act 2010

If your are a SaaS supplier or SaaS customer you should be aware of the provisions of the Bribery Act when negotiating the terms of a SaaS agreement. The Bribery Act 2010 (“Act”) has been in force since July 2011. It aims to distinguish between hospitality (which is permitted) and bribes which are illegal. A breach of the Act can result in an unlimited fine and a maximum prison sentence of 10 years.

Relevance to SaaS Customers

The Act applies directly to SaaS customers. SaaS customers will be liable under the Act for any breaches of the Act caused by their agents or subcontractors i.e. their SaaS suppliers.

In order to protect themselves against such breaches, SaaS customers are increasingly requiring SaaS providers to include anti-bribery provisions in the terms of their SaaS agreements. Such provisions are generally acceptable if they simply state that the SaaS supplier complies with the 6 principles of the Act and has adequate measures in place to ensure compliance.

Relevance to SaaS Suppliers

SaaS suppliers operating mainly in the UK with UK based customers will generally not be affected by the Act, provided that the levels of hospitality that they offer to SaaS customers are proportionate to the SaaS provider’s business, i.e. the reasonable cost of meals out, tickets and travel expenses to events. No definition of excessive hospitality is given in the Act or the guidance to it. It is therefore advisable to keep records of all hospitality entertainment and its purpose so that evidence can be provided at a later date if necessary.

Note that if you are a SaaS supplier operating outside of the UK or you have SaaS customers based in developing countries you should be particularly careful about complying with the Act, as “hospitality” which is usual or acceptable in a developing country such as paying third parties in order to win a contract, could be considered a bribe under the Act.

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 – Data Protection – Cyber Security Issues

SaaS Customers are increasingly raising questions about the security provisions that SaaS suppliers include in their SaaS agreements and insisting on including onerous rights of audit to monitor and check compliance. Under the UK’s Data Protection Act (DPA) SaaS customers (data controllers) are required to take appropriate technical and organisational measures to prevent the:

  • unauthorised or unlawful processing of personal data; and
  • accidental loss, destruction or damage to personal data.

In order to comply with these duties and avoid substantial fines SaaS customers need to ensure that SaaS suppliers have adequate security measures in place to prevent data protection breaches from occurring.

Due Diligence and Auditing

SaaS customers, particularly government departments and/or customers processing sensitive or financial data of customers are commonly carrying out due diligence on a SaaS supplier’s security systems at the pre-contractual stage. This will include ensuring that the SaaS customer has the right to check the SaaS supplier’s security measures and its on-going compliance with the security provisions of the SaaS agreement during the term of the agreement.

Information Security Officer

Both SaaS suppliers and SaaS customers should consider appointing an information security officer to assess their cyber risks. Once appointed the information security officer will be able to deal with any security issues when they arise, at the pre or post contractual stage. Without an information security officer many organisations will lack sufficient knowledge or understanding of actual cyber security risks. SaaS customers will be unable to carry out a proper due diligence and SaaS suppliers will be unable to respond adequately to customer queries. This will result in the customer and supplier spending unnecessary time on the negotiation of the SaaS agreement.

Hackers are increasingly accessing online data (in particular online payment details) and using new methods to do so. An information security officer once appointed could monitor and detect such problems, keep up to date on the latest security countermeasures, deal with queries (not just in the SaaS contracting process but also from concerned data subjects – customers) and report to management on a regular basis.

Notification and Response to Cyber Breaches

Both SaaS suppliers and SaaS customers need to have obligations to inform each other of security breaches (such as hacking) in order for both parties to deal with the issue in a timely manner. If there is a slow rate of detection the potential for the scope of the data breach (and fines) increases. Also, once a party has been notified of the breach, the incident needs to be quickly contained to limit any further potential damage.

Passwords

One of the most common causes of security breaches is the use of inappropriate passwords such as the use of “password”. Both the SaaS supplier and the SaaS customer should have adequate systems in place to monitor and prevent the use of such passwords. Systems and procedures should also be in place for the regular changing of passwords to minimise the risks of a security breach via misuse/use of unsuitable passwords.

Summary

These are just some of the general security issues that SaaS customers and suppliers should consider when entering into a SaaS agreement. There are many other issues which also need to be taken into account depending on the business sector in which the customer operates and the types of data that the SaaS supplier is processing.

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 – FAQs – What is SaaS?

SaaS is the abbreviation for “software as a service”. You may know this under another name, for example ASP services (application service provider), software on demand or software subscription. These names all refer to the same thing – 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 SaaS software may be accessed. This will usually include a service level agreement (SLA).

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 usually receive a physical or installed copy of the software;
  • No ownership in the SaaS software will be transferred to the SaaS customer;
  • The customer ‘s right to use SaaS software will end upon termination of the SaaS agreement.

Is a Service Level Agreement (SLA) a Software Licence?

No. A service level agreement (SLA) sets out the SaaS services being provided in addition to the right to use the SaaS software. These will usually include:

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 supplier or a customer to ensure that your rights are adequately protected.

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 – FAQs – Transferring Data Outside the EEA

When negotiating a SaaS agreement with SaaS customers you will often need to transfer customer data outside of the EEA (European Economic Area). This could be at the request of your SaaS customer or more usually because you have a sub-contractor such as a data centre located outside of the EEA. SaaS suppliers should be aware of the following in order to comply with their duties under the UK Data Protection Act 2018 (DPA) and the GDPR.

The GDPR and the Data Protection Act

The GDPR and the UK Data Protection Act 2018 applies to the processing of personal data, i.e. names, email addresses, dates of birth or national insurance numbers of any living individual. The GDPR and the DPA set out different duties for data controllers and data processors. In a SaaS agreement, the customer is always the data controller and the SaaS supplier is their data processor.

Transfer outside of the EEA

The European Economic Area is the 28 EU member states plus Norway, Iceland and Liechtenstein. If data is transferred to any country outside the EEA the specific consent of each data subject whose data is being transferred must be obtained before the transfer takes place, unless the data is transferred to a country recognised by the EU as having adequate data protection laws.

Countries with Adequate Protection

Currently Andorra, Argentina, Canada, Faroe Islands, Guernsey, Israel, Isle of Man, Jersey, New Zealand, Switzerland, Uruguay and Japan are recognised by the EU data protection authorities as countries with adequate protection. In addition companies registered under the EU-US Privacy Shield regime in the USA are also recognised.

Other ways of Obtaining Consent

Consent can be obtained from data subjects by the SaaS customer including relevant information in its privacy policy and ensuring that its clients actively consent to transfers of their data outside of the EEA when they enter into a contract to use the SaaS customer’s products or services.

Summary

Any transfer of SaaS customer data to any country not set out above will be illegal, unless specific consent has been obtained prior to the data transfer taking place.

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 – 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 – Data Protection – Changes to BCRs

The Article 29 Working Party, which represents the European data protection authorities (DPAs), recently announced that data processors (i.e. SaaS suppliers) can now use binding corporate rules (BCRs) to transfer personal data outside the European Economic Area (EEA). Previously the use of BCRs was limited to data controllers (i.e. SaaS customers).

What are BCRs?

BCRs are a set of rules adopted within a particular company or corporate group that set out legally binding obligations in relation to data processing within a company or group which cover global data transfers of personal data. BCRs include amongst other matters, details of:

  • data protection policies;
  • commitments to data protection training;
  • data protection audits.

BCRs must be approved by a lead national data protection authority (DPA), typically determined by the location of the European headquarters of a SaaS supplier. Once the lead national DPA approves the BCRs they are then responsible for coordinating approval of the BCRs with all other DPAs across Europe.

Current Use of BCRs

Around 30 organisations currently have BCRs in place (e.g. eBay, BP and American Express).  By extending the use of BCRs to data processors SaaS suppliers may wish to review the possibility of using BCRs particularly in light of the proposed new Data Protection Directive.

Advantages for SaaS Suppliers

Under the Data Protection Act personal data cannot be transferred to countries outside of the EEA, unless the receiving country has adequate protection. To date only Andorra, Argentina, Canada, Faroe Islands, Guernsey, Israel, Isle of Man, Jersey, New Zealand, Switzerland, Uruguay and Japan have been deemed “adequate”. Individual companies located in the USA are also accepted as having equivalent protections if they are registered under the Safe Harbor regime. This means that a transfer of data to any other country is not permitted, unless data subjects have given their consent.

The main advantage to SaaS suppliers of using BCRs is that they create a framework under which personal data can be transferred outside of the EEA without the need to negotiate the terms relating to data processing for each SaaS agreement with customers.

If a SaaS supplier has BCRs in place SaaS customers (data controllers) will be able to rely on these BCRs to show that they comply with their duties as a data controller under the Data Protection Act.

Disadvantages for SaaS Suppliers

The major obstacle to the use of BCRs is the time it takes to negotiate and agree their form with the DPAs. Some DPAs still require a permit to be issued before they will allow the transfer of data from that member state. There is also a considerable cost involved in obtaining the approval of the BCRs, as the whole procedure can last a number of years.

Alternatives to BCRs

For the reasons set out above most businesses do not currently use BCRs and choose one of the following options to overcome the obstacles to transferring data outside of the EEA:

  • Safe Harbor arrangement when transferring data to the USA;
  • model contractual clauses with data processors;
  • transfer to a country that is approved by the European Commission as having adequate levels of data protection in place i.e. New Zealand.
  • obtaining specific consent to the transfer from individuals via privacy policies.

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 – Data Protection – Recent ICO Fines

The Information Commissioner’s Office (ICO) has started to issue very high fines to a number of companies and individuals, not just for serious breaches of the Data Protection Act (DPA), but also for breaches of the Privacy and Electronic Communications Regulations (PECR). Below is a summary of the recent fines and the reasons for them being imposed.

Tetrus Telecoms – Fined £440K for sending Illegal Spam Text Messages

Tetrus sent unsolicited text messages to individuals whose numbers they had purchased from lists. Once individuals responded to the spam text, their numbers were then sold on to a third party.

In breach of the PECR, Tetrus were found to be transmitting unsolicited marketing messages (including concealing the identity of the sender). The ICO found that Tetrus was in serious, deliberate and informed breach of the PECR due to the:

  • volume of text messages it sent; and
  • the number of complaints received.

In addition a criminal prosecution is being pursued against the two individuals for breaches of the DPA.

Scottish Council – Fined £250k for failing to Manage Outsourcers

A Scottish council hired a third party to electronically archive its paper employee pension records. Over 600 paper files containing Council employees names, addresses, national insurance numbers, salary and bank account details were dumped in a supermarket’s paper recycling bank once the records had been electronically stored.

The Council was fined for breaching the DPA due to its failure to:

  • have a written contract with the outsourcing company governing the scope of the processing activities; and
  • set out its data security requirements.

In particular, the Council failed to have in place proper technical and organisational security measures governing the processing. It also failed to take reasonable steps to ensure compliance of the third party with these obligations. i.e. that the third party would return or destroy the paper documents after digitally archiving them.

Sony – Fined £250K for Security Lapses

The personal data of millions of UK Sony customers (including names, addresses, email addresses, dates of birth and passwords) was stolen when hackers accessed the Sony PlayStation Network Platform.

The ICO found that in breach of the DPA Sony did not have an appropriate standard of security in place to protect the personal data as it had:

  • failed to take appropriate technical measures (such as cryptographic controls to protect passwords) to prevent the loss of vast amounts of personal data; and
  • stored excessive amounts of personal data.

Sony is currently appealing the decision.

Why these Cases are Important

As a SaaS supplier you will be storing and processing personal data on behalf of your SaaS customers. Under the DPA you are a data processor and you must ensure that you comply with your obligations under the DPA. SaaS customers will often require you to indemnify them for breaches of the DPA in your SaaS agreement i.e. you could become directly liable for ICO fines imposed on your SaaS customers.

How to Avoid Fines

Choose a reputable organisation when outsourcing personal data processing i.e. to a hosting centre.

Have a written contract with the SaaS outsourcer which specifies:

  • that appropriate technical and organisational measures are in place to prevent the unauthorised or unlawful processing of personal data and to protect them against accidental loss, destruction or damage; and
  • that your outsourcer is obliged to report any security breaches or other problems to you.

Note that under the new proposed EU Data Protection Directive (which has not yet been finalised) the ICO will be given the authority to impose much higher fines for breaches of the DPA – up to 2% of a company’s turnover.

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: