SaaS Agreements – FAQs – Cookies

What is a Cookie?

Cookies are small text files placed on a user’s hardware device, such as a computer, tablet or mobile phone which record online activity. The majority of websites use cookies to measure visits and the use of websites (analytics cookies). Cookies are often also used to save user names, passwords and user preferences to make repeated use of a website more comfortable for the user. However, increasingly cookies are being used to collect information about users for the purposes of targeted marketing, tracking and other non essential purposes.

Opt In Consent Required

It is unlawful to use cookies to collect user data without first obtaining consent. There is an exception when a cookie is strictly necessary for a service which a user has requested i.e. where a user places an item in an online shopping basket and there is the need to ensure that payment is for the goods actually purchased.

Compliance and Fines

The UK Information Commissioners Office (ICO) investigates and prosecutes companies for breaches of the Privacy and Electronic Communications (Amendment) Regulations and the GDPR. These two laws set out the obligations of website operators to provide users with information about cookies and any other similar techonlogy that track use of a website and the need to obtain obtain a user’s consent to the use of cookies. Failure to comply with the rules can result in GDPR fines.

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

SaaS Agreements – Data Protection – Direct Marketing Rules

In September 2013 the Information Commissioner’s Office (ICO) published a lengthy guide to Direct Marketing. The guide covers compliance with the Data Protection Act 1998 (DPA) and the Privacy and Electronic Communications Regulations 2003 (PECR) in relation to the sending of unsolicited marketing. SaaS suppliers who are sending unsolicited marketing to SaaS customers and prospective customers should check their compliance with the guidance. Additionally, the Direct Marketing Association (DMA) has also published its own further supplemental guide which provides detailed guidance on how and when to obtain consent to marketing from individuals.

Marketing and the DPA

The DPA applies to marketing where a SaaS supplier is using personal data. For example: if a SaaS supplier is sending marketing emails to a named person i.e. peter.smith@microsoft.com. When sends marketing emails to a named person a SaaS supplier must comply with the 8 data protection principles. In particular, the SaaS supplier must give the individual the right to object to any direct marketing (in writing).

Marketing and the PECR

The PECR complements the DPA. It sets out more detailed rules on electronic marketing i.e. email, text messages, fax and telephone calls.  Unlike the DPA, the rules apply even if the SaaS supplier does not know the name of the person it is contacting i.e. admin@microsoft.com.

The rules under the PECR also vary depending on whether the marketing is sent to a consumer (B2C) or to a business (B2B).

Obtaining Consent

Both the DPA and the PECR require that the recipient consents to being sent direct marketing. Such consent must be informed and must be freely and specifically given. Consent is only valid if:

  • it is not a condition to subscribing to a service or completing a transaction;
  • the information given is clear, prominent and not difficult to find (so that individuals understand what they are consenting to);
  • it is relevant to the type of marketing being sent; and
  • there is a positive indication of the recipient’s agreement to receive direct marketing.

This means as a general rule that pre-ticked “opt-in” boxes should not be used to obtain consent.

Marketing Emails and Texts

Where marketing messages are sent by email or text additional rules apply. Consent must be:

  • notified; and
  • specific to the type of communication.

No express consent is required where:

  • a recipient’s details are obtained in the course of a sale (or negotiation of a sale) of a product or service of the SaaS supplier to that individual;
  • the SaaS supplier is only marketing their own similar products or services; and
  • the recipient had the option to refuse or “opt-out” of the marketing at the time their details were collected, and in every subsequent email.

In order to demonstrate compliance with the rules on consent, SaaS suppliers should keep clear records of:

  • what, when and how consent was collected;
  • who gave the consent; and
  • the information provided to the individual about the consent being given.

Marketing Calls

In the UK SaaS suppliers must not make unsolicited marketing calls to numbers registered with:

  • the Telephone Preference Service (TPS) in relation to individual B2C subscribers; or
  • the Corporate Telephone Preference Service (CTPS) in relation to B2B subscribers.

Automated marketing calls can only be made to individuals who have specifically consented to receiving such calls.

Fines for Breach

Breaches of the DPA or PECR can result in a SaaS supplier receiving an enforcement notice from the ICO requiring remedial steps to be taken. Failure to comply with such a notice is a criminal offence.  In addition, the ICO can also impose a fine of up to £500,000 for serious breaches.

Summary

The above is a general summary of the complicated rules applicable to direct marketing. Before launching any direct marketing campaign, specific legal advice should be taken, in order to check full compliance with the above laws and rules to reduce the risks of substantial fines being imposed for breaches.

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 – 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:

Website Legal Requirements – Privacy Policy – Basics for your Website

If you are operating a website and require users to register in order to use your website or you are simply using Google analytics on your website then you are collecting and processing personal data. Under the Data Protection Act 1998, if you collect, store or process personal data you must provide specific information to the persons whose personal data you are using. This information is usually provided to users in a privacy policy which should be published on your website.

The following basic issues should be covered in your privacy policy.

Personal Data Practices

Your privacy statement should reflect your personal data practices. For example, it should include details of:

  • The type of data being collected;
  • Why the data is collected;
  • How the data is used and why;
  • 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.

Cookies

Cookies are small text files placed on a user’s computer which record online activity. Virtually all websites use cookies. Most use analytics cookies to measure visits and use of websites. Performance and functionality cookies are used to make repeated use of a website more comfortable for the user and advertising cookies are increasingly used to collect information about users for targeted marketing.

In your privacy policy you must provide users with clear and comprehensive information about the type of cookies being used on your website and the purposes for which the information is collected.

Where should the Privacy Policy Appear on my Website

The privacy policy should be easy to find on your home page and/or at the point where you obtain consent to the collection of the personal data i.e. where a user registers on your website. It is advisable to have links between the privacy policy and all references made to it on your website. For example, if you are providing online recruitment services you should place your privacy policy on your home page and also have a link to it when users register to use your website or services. In addition you should have a process for the user to confirm acceptance of your privacy policy i.e. by actively clicking an acceptance box or a double opt-in email process.

Compliance with other Laws

You will need to consider your compliance with any other applicable laws or rules, which will apply in relation to the collection of a user’s personal data. Which other laws apply will depend upon a number of factors. For example if you are selling or providing services to children (persons under the age of 18) you must have additional safeguards in place on your website. For example, you will need to obtain parental consent before you collect any personal data for children of certain ages. Or if you are providing services to children which include advertising or marketing you will need to comply with the CAP Code.

The type of products or services that you are offering online and the countries in which you are making these available will also be relevant – as this will determine whether national, EU and/or international laws will also apply to your website. Depending on the business sector in which you operate, the rules of self-regulatory schemes may also apply. For example, if you are providing email marketing services to users you will need to comply with applicable email marketing and advertising rules.

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: