Archive for the 'Contract Law' Category



“Congratulations” to record companies as “Cliff Richard’s law” is passed

The European Union’s Term of Protection Directive has been ratified, extending the term of copyright protection in the EU for sound recordings and performers’ rights from 50 years to 70. The directive is expected to be implemented by EU member states by 2014.

Copyrights in sound recordings currently run for 50 years from the year of recording, or 50 years from date of release if released outwith that year, and usually lie with the “producer” who has made the arrangements for the recording – typically the record company. Performers’ rights in sound recordings entitles them to contractual royalties on the sale and other exploitation of the recordings, and statutory remuneration from the copyright owner each time their work is played in public (though in practice most performers have relatively complicated contractual relationships, requiring their royalties from exploitation of recordings to be paid to their record company).

This traditional 50-year term of protection for sound recordings and performers’ rights was based on the principle that authors, such as music composers, should be entitled to a longer term of protection for their works (the life of the author plus 70 years) because their rights are linked to their personality and creative contribution, whereas the sound recording and performers’ rights typically arise from economic investment, and are usually owned by corporate bodies (the record companies).

The result of the 50-year term was that record companies became increasingly agitated during the noughties, as digital piracy led to plummeting revenue from record sales, whilst, simultaneously, valuable copyrights in classic 1960s recordings edged towards expiry.

The 2004 European Commission Staff Working Paper, the UK’s Gowers Review of 2006, and the European Community-commissioned IVIR Report of 2006 all considered the question of an extension, reaching the same conclusion: that it was undesirable on both economic and theoretical grounds, and that the extension would benefit record companies far more than the performers. For example, if the extension was solely to benefit performers during their lifetime, then why was an extension of up to 95 years being proposed? Why also were performers’ rights not an unalienable right of the performer? And why did the extension have to apply to the sound recordings at all? This year’s UK Hargreaves Report (which we blogged about in May) also noted scepticism about claims that the extension would spur creativity, noting drily that “no one has yet discovered a mechanism for incentivising the deceased”.

In recent years however this evidence-based approach to the debate, founded on economic reasoning, has been obscured by increasingly desperate and emotive arguments. Lobbyists representing record companies have sought to supplant the rather unappealing spectacle of big business protecting lucrative assets with an image which has been calculated to attract greater public sympathy: the beloved yet unrewarded music performer.

A major participant in the campaign for extension has been Sir Cliff Richard, whose performer’s rights in his string of breakthrough hits had either expired or were very close to doing so. The participation of artists such as Sir Cliff has clouded the issues. The Gowers Review noted that even in the most favourable scenario of additional revenue, the performing artists would receive only 1 percent or less of it, and in a highly uneven distribution favouring very few already very successful musicians. If the goal of the proposed reform was genuinely about helping a large number of artists, noted Gowers, then overhauling the relevant contract law would be much more effective.

It seems curious that someone as wealthy as Cliff Richard would bother to get involved with this issue. Of course, over the last decade he has become obsessed with getting a final No. 1 record, a quest which reached its’ nadir with the horrendous 21st Century Christmas. Should we expect a single sometime in the near future from a trendy chart-topping young buck like Tinie Tempah or Pixie Lott, prominently featuring a sample from a Cliff performance? If so, “Congratulations” would be the obvious candidate!

Advertising standards and Groupon

Earlier this year, in response to the changing nature of online marketing, the Committee of Advertising Practice extended its Code (the “CAP Code”) to cover “advertisers’ own marketing communications on their own websites and in other non-paid-for space online under their control”.

This means that the Advertising Standards Authority (“ASA”) (the independent, one-stop-shop that investigates alleged breaches of advertising codes, including the CAP code), is now able enforce the withdrawal of all online marketing messages that don’t meet the CAP Code, including those which are on companies own Twitter or Facebook profiles, and also those which are contained in companies’ own promotional emails.  (Of course, the ASA is an advertising industry body – so don’t expect too much from it – you may recall my blog about its remarkably permissive Bodyform adjudication in March.)

Nevertheless, a high-profile consequence of the extension of its powers is that the ASA appears to be considering complaints against emails sent by “deal of the day” websites, and has already upheld 2 such complaints against the biggest “deal of the day” website in the world, Groupon.  The adjudications can be read here and here.

I treat the Groupon offers as more or less “advertising puffs” – that is, unenforceable advertising claims that no reasonable consumer would take seriously. I expect a discount to be involved, but not on the sensational “90% off” sort of scale routinely indicated. 

Perhaps this indifference is because I have viewed Groupon as a passing fad, like those ghastly rubber charity wristbands that everybody used to wear, or MySpace. My hunch is that the business model doesn’t have legs.  (Douglas says that once I get married I may feel differently - I have referred him to the European Financial Review, which backs up my hunch with all sorts of fancy analysis - and Douglas has, in turn, referred me to his wife’s monthly 3-figure Groupon spend…)

However, if lots of less cynical folk than myself (like Douglas’s wife, and, admittedly, my fiancee) are giving Groupon their money, then it’s a good thing that the ASA is regulating it (even if the only punishment which the ASA can at present enforce is the withdrawal of the unlawful communication).  Groupon should also beware of the Unfair Trading Regulations 2008, and their general ban on unfair commercial practices – various parties entitled to enforce the Unfair Trading Regs may not decide to look upon Groupon’s advertising as benevolently as I do.

Overall this blog post is a decent reminder that businesses shouldn’t get too carried away when stating the brilliance of their product or service, even if it’s just words contained in a throwaway tweet or blog. With that in mind, I’ll let the Law Society of Scotland Journal boast about Brodies LLP on our behalf.

Using e-signatures to sign contracts – what are the legal issues?

Adobe yesterday announced that it had acquired electronic signature provider Echosign. Adobe’s intention is to integrate Echosign’s products and tools into Adobe’s PDF format/Acrobat products. Echosign’s tools allow users to electronically sign a document, or apply a traditional (inked) signature that is scanned and then incorporated into a PDF of the “signed” document.

Douglas has blogged previously about exchanging PDFs of inked signature pages, but I thought it might be worthwhile to look at the use of so called electronic signing.

Signing documents electronically
We have a number of clients that use tools similar to Echosign to allow contracts to be signed electronically. There are a number of advantages to these products – signing documents is quicker and easier, and avoids the need for physically delivering and retaining a “wet” signature page.

For standard commercial contracts, using products like Echosign generally doesn’t cause any problems from a legal perspective, but there are some things to watch out for:

Who has actually signed?
An electronic signature is generally appended by a user receiving an email that then takes the user to a website that allows the user to “sign” the document (perhaps using a unique signature key). Whilst the e-sign tool will provide evidence of the signature being appended, if the e-mail is accessed by a third party (eg someone who has access to that e-mail account) it would be open to one party to say that he/she had not signed the contract; it had been signed by someone else/someone who did not have authority. The e-sign tool does not provide evidence of who signed the contract.

In one sense, this is no different from the use of “real” signatures in the offline world where it is definitely possible for someone to say that their signature had been forged. In each case, the onus on proving that the document had been signed by the person whose signature it purports to be will fall on the person who is trying to allege that there is a valid contract. Evidentially, however, this is probably easier to do when comparing inked signatures.

Many organisations using e-sign services will take comfort from the fact that once the parties begin performing their obligations (for example, providing services and paying invoices) it will be harder for a party to argue that it was not bound by the contract because it had not signed it.

Data Protection
Many of the companies providing e-sign services are based in the US, and will host your contracts (and data about signatories) on their servers. Data protection laws contain specific rules in relation to the transfer of personal data outside the EEA. Generally, the US is not considered to provide an adequate level of protection of personal data for the purposes of European data protection legislation. Any organisation that decides to adopt such a system for signing its standard customer contracts should highlight to its customers that the data they submit may be held in the US and held by the e-sign provider subject to the terms of its privacy policy.

If the contracts contain personal data (for example, about employees) then this will be more problematic.

Confidentiality and liability of the e-sign provider
More generally, organisations may also wish to consider whether they are comfortable with commercially sensitive contracts (or contracts containing personal data) being hosted in a third party repository, and whether the service provider has in place appropriate information security controls.

In particular, you may find that the e-sign provider’s standard terms are weighted heavily in the e-sign provider’s favour. I have seen standard terms foir e-sign services that contain no confidentiality obligation by the e-sign provider in favour of the user. This will cause particular concerns where copies of contracts are being held/hosted by the e-sign provider.

Data ransom
Finally, remember also that these services are generally delivered using the software as a service model. If you decide to stop using the service, can you get access to your archive of contracts and associated data? Is it in a useable form? Again, Douglas has blogged on this.

Soutwark v. IBM – New Article in Supply Management

I have an article about the recent Southwark v. IBM case in this month’s edition of Supply Management. Its good reading if you ever buy or sell software (especially in relation to the public sector).

Here is a link to the on-line version. http://www.supplymanagement.com/law/analysis/2011/quality-questions/

Supply Management is the journal of the Chartered institute of Purchase and Supply (CIPS) – it is typically read by procurement professionals (and the odd lawyer).

By the way I much prefer the five-year old photo below to the much newer photo used by Supply Management. Time and tide has not been that kind to me, and yes it was me who ate all the pies.

Happy reading.

Cloud Computing and the risk of Data Ransom

There have been lots of articles about cloud computing by lawyers. Most of them: i) have a dodgy pun in the title; and ii) bang on about data protection and the risk that your data is outside Europe.

That is not what I am going to write about. Partly because it’s been done to death, and partly because I think DP law is dull (sorry Grant and other data law lovers).

I am going to talk about data ransom in a cloud or hosted environment. That is the risk that your supplier goes bust and you have to buy your data from an administrator/receiver, or that you get into a commercial dispute with your supplier and they either turn off your service or ransom your data.  Both are possible scenarios.

Remember that administrators are legally bound recover as much money as possible for the creditors. They are also not too bothered what your contract with the insolvent company says.  These facts can make them quite interesting to deal with!

On the commercial dispute side it is traditional for purchasers to manage suppliers by withholding payment on invoices or similar. But with cloud or hosted apps the power has shifted – if the purchaser withholds payment then the supplier can probably turn off the service. Gulp!  Worse imagine you have decided not to renew the contract, and your supplier starts being “sticky” about handing over your data to the new supplier. Remember “sticky” could include giving the new supplier all your data, but in an incomprehensible format.

So what do you do ?

Contractually

  • Have an obligation to get a weekly or daily back-up of your data delivered to you in a format you could decode.
  • In fact why not take advantage of virtualisation technology and get a virtual copy of “your environment” and related rights to run it on your servers. (I have been putting this in contract for about a year – so far I have not seen anyone else do this).
  • Have strong exit management provisions (preventing the supplier mucking you around on exit).
  • Have a source code escrow agreement.  Note from a “self-help” basis these are probably useless (partly) because you may not have the object code; but having the right to get the source code will give you bargaining position against an administrator/receiver *.

Practically

  • Actually Enforce any of the contractual rights described above (it is probably too late to start enforcing them once the “ransom” starts).
  • Make sure your lawyer really understands concepts such as cloud, source code and virtualisation (this is an undercover sales pitch).

Not one dodgy pun!

*  I find a lot of lawyers still ask for source code escrow in a hosted app environment (where the client doesn’t even have the object code) not because of the reasons I have outlined but simply because the turnkey contract they are using as a style has an escrow clause in it. This strikes me as fairly dumb. Rant over.

Bribery Act 2010 – have you reviewed your policies and procedures?

When the Bribery Act finally comes into force on 1 July 2011 it will be the most substantial change to the UK’s corruption laws since 1916. The Bribery Act creates a new offence for commercial organisations. This is a key development for companies and other commercial organisations as an organisation will be guilty of an offence where a person “associated” with it bribes another person to obtain business or a business advantage.

Why is the new Act relevant to procurement?
The new Act is relevant not just to the “sales” side of businesses, but also to procurement, where those involved in tendering, purchasing, and procurement need to be aware of what might constitute the receipt of a bribe (and therefore an offence) under the new legislation.

Importantly, the commercial organisation will be presumed guilty if they do not have “adequate procedures” in place designed to prevent bribery.

What should we be doing?
Businesses should put in place “adequate procedures” now to minimise the risk of criminal prosecution when the Act comes into force. Your adequate procedures should set out clearly your company’s approach to, amongst other things, the giving and receiving of corporate hospitality and the rules governing your procurement processes (which may need to be updated to reflect the new laws).

How can Brodies help?
Our Regulatory Compliance team can help your organisation to plan for the Bribery Act, for example by assisting with the development of internal policies and providing training to help ensure your business is protected when the Act comes into force. If you would like to discuss this further then please send me an email or get in touch with your usual TIO Group contact.

For more information, see my colleague Susheela Math’s blog post over on Brodies’ PublicLawBlog, or our Regulatory Compliance team’s recent legal update.

Interim report on the banking industry published

This week’s interim report by the Independent Commission on Banking caught the headlines in terms of the economic and regulatory implications of its recommendations and conclusions.

Beyond these headlines, though, there were some interesting views regarding the structuring of operational services for banking groups which, if adopted, will require careful thought and planning for banking operations and those dealing with them. This includes reviewing the sourcing arrangements and contracting structures currently used by banking groups for outsourcing and procurement of services, intra-group arrangements, and the way in which they hold and process data.

You can read more about this in our Legal Update.

Entire Agreement clause ineffective to exclude implied terms or misrepresentations

In the recent case AXA Sun Life Services plc v Campbell Martin Ltd and others [2011] EWCA Civ 133 case the English Court of appeal considered the following entire agreement clause.

“This Agreement and the Schedules and documents referred to herein constitute the entire agreement and understanding between you and us in relation to the subject matter thereof. Without prejudice to any variation as provided in clause 1.1, this Agreement shall supersede any prior promises, agreements, representations, undertakings or implications whether made orally or in writing between you and us relating to the subject matter of this Agreement but this will not affect any obligations in any such prior agreement  which are expressed to continue after termination.”

The Court decided that the clause didn’t exclude any remedies in respect of pre contractual misrepresentations. This decision is consistent with the Sky v. EDS judgement of last year. So to put it plainly if you want to exclude liability for any misreps you have to be very clear (and remembering that you can’t exclude liability for fraudulent misreps).

Second, the court stated the clause did not exclude any implied terms, such as the implied warranty of reasonable skill and care in a service contract. (This is something I have often wondered about – and now I have an answer). 

Of course most agreements have an exclusion of implied warranties at the end of the warranties clause – but that may not exclude all implied terms – so I often beef up that exclusion to exclude all “implied warranties, implied conditions*, implied licences and/or implied terms”.

This is another anti-supplier judgement. Am I detecting a trend here?

* For the law geeks out there the exclusion of implied conditions is technically only relevant for Scots law contracts. However, I tend to include it even in English law contracts.

Douglas on Radio Scotland talking about iPods and digital music rights

I was on Radio Scotland last week talking to Fred MacAulay about downloaded music,  iPods, iTunes and other Apple “iPayTooMuch” products.

Here is a link to an mp3 recording of the piece – its about 10 minutes long.

Douglas on Radio Scotland re iPods

Some Key Points (that weren’t fully made in the interview):-

1. When you “buy” a music download you are actually buying a contractual right (licence right) to do certain specified things with that dowload. 

2, The contract (licence) will set out what you can do, e.g. listen to it in private, burn it to up to 5 devices etc.

3. If what you are doing is not expressley permitted under the contract (licence) then you are infringing copyright. 

4. So for example using your iPod to run a karoke event at your place of work would likely be a copyright infringement.

5. This is not a new model, the same rules applied to LPs. (Remember those? – I still listen to mine.) 

6. The iTunes contract is subject to California law, California Courts, and allows Apple to unilaterally change your rights to use the download.  Nice for them, not so good for you.  (To be fair the other on-line music stores are not much better).

7. Format shifting is not legal in the UK (it’s copyright infringement), but it’s low risk.

Happy listening.

Apple, iTunes and iPod are all registered trade marks of Apple Inc. “iPayTooMuch” is a lifestyle choice by our Martin.

HOLLYWOOD HACKING: WIKILEAKS

“Hollywood Hacking” is the trusty cinema cliche whereby a geek with a laptop hits lots of buttons on his keyboard very quickly, says “we’re in” (or something similarly breezy), and gains access to the military system/bank account of his choosing. While Hollywood Hacking is usually very silly and completely unrealistic, the current Wikileaks saga is actually happening right now, in real life, and there’s more than a touch of unbelievable Hollywood Hacking about the whole tale.

As you’ll probably be aware, Wikileaks is the whistleblowing website that last week made available for download more than 250,000 confidential U.S. diplomatic cables. The cables contain correspondence between American embassies throughout the world and the U.S. State Department, and their contents are proving to be highly embarrassing for the U.S. Government and its allies.

Wikileaks founder Julian Assange has been placed on Interpol’s Most Wanted list (for “sex crimes” being investigated by the Swedish authorities, although the US government is also investigating if espionage laws were broken), and the Wikileaks website is under continuous heavy attack from unidentified and mysterious “internet hackers”.

These hackers are bombarding the site, or more accurately, the computer servers which hold or “host” its content, with “Distributed Denial of Service” (“DDoS”) attacks of unprecedented ferocity. (In DDoS attacks incoming messages flood the target system and force it to shut down, thereby denying service to the system to legitimate users).

In an attempt to defend itself, Wikileaks moved last week from smaller internet providers to a larger one whose servers would be more likely to withstand a DDoS assault. Wikileaks provider of choice was Amazon.com and its’ much-vaunted EC2 cloud computing system, which operates on vast banks of computers, meaning that network capacity can be quickly scaled up or down to meet surges in traffic. The tactic was working well for Wikileaks until Amazon.com decided on Thursday to kick them out.

In a blogpost, Amazon.com denied that it was acting under pressure from politicians, saying WikiLeaks had breached its terms by not owning the rights to the content it was publishing. (I imagine Amazon.com might also have been a bit nervous about potential liability for the illegally sourced cables.)

The wikileaks.org web address was then withdrawn from Wikileaks because its domain name service provider EveryDNS.net claimed that WikiLeaks had violated part of its Acceptable Use Policy, which requires members not to “interfere with another member’s use and enjoyment of the service or another entity’s use and enjoyment of similar services. WikiLeaks had interfered with other members’ service because, said EveryDNS, “wikileaks.org has become the target of multiple DDoS attacks. These attacks have, and future attacks would, threaten the stability of the EveryDNS.net infrastructure, which enables access to almost 500,000 other websites.”

Wikileaks solution has been to move to Switzerland, with a new domain wikileaks.ch.  The domain name is registered by the Pirate Party of Switzerland, associated with an IP address in Sweden, and points to a web address in France (where the Wikileaks documents are actually believed to be hosted).  If wikileaks.ch is also withdrawn, Wikileaks has announced that content will still be accessible by bypassing the DNS look-up and typing in Wikileaks’ actual IP address: http://88.80.13.160/.

Over the weekend online payment service provider PayPal cut off the WikiLeaks account, eliminating one of the easiest means for donors to send money to the organisation. It’s simply impossible to tell what’s going to happen next!   The latest development is that Julian Assange is under arrest, having voluntarily reported to a police station in central London this morning.

Who said Tech Law was boring? Hopefully in the inevitable Hollywood dramatisation of the saga there will at least be a cheeky cameo of yours truly writing this blog.

« Previous PageNext Page »


Twitter: @BrodiesTechBlog feed

 

February 2012
M T W T F S S
« Jan    
 12345
6789101112
13141516171819
20212223242526
272829  

Follow

Get every new post delivered to your Inbox.

Join 135 other followers