Global opinion, news alerts and updates on laws, regulations, standards and good practice for online business.
Friday, July 18, 2014
The 10 Commandments For Digital Life | E RADAR
The 10 Commandments For Digital Life | E RADAR A great summary on how to protect yourself when interacting with others online
Wednesday, July 9, 2014
Wednesday, June 11, 2014
Are You On Twitter? Are You A Twitter Twat?
I recently read an article by Janet Street Porter about the shortcomings of Twitter. She wasn’t nice.
But then you don’t expect anything less from the ‘thinking man’s nemesis’? She’s my ideal fifth dinner guest to join Leonardo (that’s DaVinci, not DiCaprio), Nelson Mandela, Henry VIII and Pharaoh Khufu for an evening of good old fashioned chit chat. Her outspoken, no-nonsense remarks cut to the chase like a northern Cheshire cat looking to devour the three blind mice. That icy stare would turn Medusa into stone.
Can you imagine sitting Janet between Bluff King Hal and Pharaoh Khufu to discuss the benefits of sixteenth century wife disposal and the symbolic architectural intricacies of the Great Pyramid? Or between DaVinci and Mandela where intellectual contortion meets political prowess? Assuming, of course, that they can stand – let alone understand – each other. Forget the translator. Janet’s distinctive Brentford twang alone can cut a conversation like a fly sliding down a razor blade on its reproductive what nots!
So, Janet’s recent attack upon the inflated egos on Twitter who send endless self-gratifying rubbish to their followers hit the nail on the head – a real ‘Bercow moment’ if you get my drift.
And she’s right, of course. Who cares if you’ve just burnt your toast – don’t be sending us banal tweets when you should be paying more attention to that burning smell! And please, we really don’t want to know about your baby’s regurgitation habits, especially when she’s 27, drunk, and ought to know better!
Clever bird
The Twitter Bird, her brothers and sisters all champion ‘freedom of speech’. But social media and networking sites are a headache for governments used to managing information. We’ve seen the strange case of John Inman lookalike Julian Assange and his Wikileaks, Edward Snowden revelations about US government secrets that we’ve all suspected for years, and Google’s recent ‘right to be forgotten’ where we can all suddenly disappear from view.
Are you on Twitter?
There are 140 million worldwide users on Twitter, that’s 140 million egos all communicating with each other. And I’m one of them. Like most Twitter users I’m ego in its purest sense – I think therefore I am. I want to be part of this super cyber phenomenon, inquisitive about what its technology can do, interested in what others are saying, how they are using Twitter and looking to apply those features and benefits to my own everyday world.
The Twitter bird is clever. She connects at every intellectual level: Twits write anything, Twitterers just sell and Tweeters have strategically got it. With Twitter you can’t suffer from verbal diarrhea with a message limit of only 140 characters. Either you will spout rubbish or be succinct and precise. There’s nothing in between.
Except the Twitter Twat!
The blockhead who abuses the bird. The troll who thinks it funny to send vile messages. The law breaker who creates the illusion that Internet anonymity will let them get away with everything. The opinionated who just won’t accept they’re wrong. They’re all on there looking for that 15 minutes of fame.
Social media is all or nothing. It shows us everything we need to know about the good, bad and the ugly in the world today. But Janet Street Porter misses one vital point. People have a need to talk to others. And so long as others are listening, social media is the ‘mouthpiece’ for us to express all the human emotions we need to, as we choose. The world is a better place when once-distant people can now communicate with each other.
Ego
Thursday, May 15, 2014
What's in a web developer contract?
Many websites are now developed using open source software, for example WordPress. This allows independent developers to create additional functionality such as website templates and plugins. Most of these are free to use but may have premium modules attached for extra functionality. Both customers and web designers need to determine what functionality is allowed free commercially and what’s not.
Web developer contracts are made up of three separate documents which you need to assemble carefully. Otherwise, you might find yourself being charged extra to update your website plus becoming liable for things you hadn’t even considered!
These are:
- A Form of Agreement;
- Terms of Business; and
- a Works Schedule which has job-specific details relating to the work.
In this article we set out the key elements in the web developer contract for your to consider plus some helpful tips…
Form of agreement
This is the document to be signed by both parties. In addition to filling in the full names and address of each party, the fees and estimated completion date also need to be completed. Clearly, the Form of Agreement needs to be tailored to your particular circumstances.
When it’s signed – and there should be two copies – one signed by each party – the Terms of Business and the Works Schedule with the job-specific details should be attached.
Terms of business
1. Definitions and Interpretation
This clause may contain a few defined terms which are used throughout the agreement. The description of the artwork to be provided is to be included in a separate schedule which will form part of the agreement.
2. Services of the Developer
This briefly describes the work of the developer. If there’s to be a deadline within which the design work is to be carried out, this can be inserted in the Schedule but our wording is designed to ensure that dates are estimated and not guaranteed.
Generally, it is sensible in a relationship such as this for the developer and client to have a clear understanding before any contract is signed regarding the scope of work that is required and the type of designs to be prepared. From the developer’s point of view, there will usually be a fixed fee and the designer doesn’t want to find that he/she is regularly being required to revise the designs to meet the client’s requirements. Equally, from the client’s perspective, he/she doesn’t know whether or not the designs will be suitable until an initial draft is produced, but he/she needs to be happy with the choice of the designer at the start of the contract.
The final paragraph 2.3 dealing with extra fees is meant to give the web developer some protection against major changes to the brief.
3. Fees and Payment
There will usually be a lump sum fee, but that isn’t always the case. Occasionally the fee will be related to the time spent on the project and sometimes there will be a mixture – e.g. a fixed sum plus £X per hour/day if more than a budgeted amount of work has to be performed.
Details relating to the fee will go into the Schedule. This section deals with the invoicing and payment terms.
If the designer is registered for VAT, then a VAT Invoice or VAT receipt will need to be issued in respect of each payment.
Under this section, the web developer is entitled to claim interest on late payment. The interest rate in this clause is, in fact, lower than the rate which would apply if the agreement is made in England: the “Interest on Late Payments Act” gives a party to a contract a right to claim interest at quite a high rate – currently 8% p.a. – even if there’s nothing in the contract to this effect. A slightly lower interest rate is usually more commercially acceptable and the fact that such a clause is incorporated gives greater weight to any claim by the designer for late payment.
The final paragraph 3.6 gives the developer the opportunity to charge for extra services. Where the designer has an hourly or daily rate, this will go into the Schedule. Otherwise, the designer should provide an estimate before starting on any extra work. Sometimes it could be worth having a statement in the Schedule to describe the expected time to be spent on the project by the designer – so any serious deviation from this caused by the client may trigger a claim for extra payment.
4. Cancellation
Designers may wish to delete this section altogether. However, it caters for the possibility of an initial design being prepared and the client then deciding not to proceed. In those circumstances, the cancellation clause will make it clear that the designer is entitled to be paid at least a portion of the original fee, even if the assignment doesn’t go through to completion.
Where a client does cancel, it’s sensible to require, as here, that the artwork already handed over should be returned and to make it clear that the client doesn’t have any right to use any of the designer’s work unless the full fee is paid.
5. Intellectual Property
There are two alternative sections – one of which should be deleted before these Terms are given to a client. Alternative A gives all ownership of copyright etc to the client, subject to him paying the fees due. Alternative B leaves the copyright with the designer and the client has a licence to use the artwork in his business.
Copyright
A designer will, in the absence of any agreement to the contrary, own the copyright in the artwork that he prepares. Where a design is being commissioned by a client for a particular purpose – e.g. the design of a logo for a company – the client will usually want to ensure that it owns the copyright and that the designer doesn’t have any residual rights to use those designs somewhere else. In order to achieve this, a clause such as Alternative A is needed, under which copyright and any other intellectual property rights in the design transfer to the client. However, this transfer (or “assignment”) will only take effect once the full price has been paid. This is clearly important from the designer’s point of view.
Occasionally, the designer will retain copyright in which case Alternative B should be used. An architect, for example, will usually want to retain copyright in his designs for a building and in that case the client will be given an irrevocable licence to use those designs for the purposes the building for which they were commissioned, but not for any other purpose.
Moral Rights
Under European law relating to intellectual property, the “author” – i.e. in this case, the designer – has a right to be named as the author in any document which contains that work. For reasons already discussed in relation to copyright, it’s usual for a client to have all rights in relation to the design without having to refer to the designer/developer, and in order to achieve this legally, appropriate wording is required in Alternative A.
In those circumstances where the designer/developer wishes to assert his/her moral rights, e.g. the designer of the dust-jacket of a book, would usually be identified in all published copies – the wording in Alternative B may be used. Sometimes a designer/developer may want to go further and say:
“The Client shall ensure that the following notice will appear on every document which includes the Artwork:
“The right of [name of designer/developer] to be identified as the author of [description of Artwork] has been asserted in accordance with the Copyright, Designs & Patents Act 1988“.
It is the responsibility of the Client to ensure that this obligation is imposed on any assignee or licensee of the Client.
6. Designer/Developer Warranties
It isn’t uncommon for a client to want a written assurance that the designs he is paying for are indeed the designs of the person selling them and not some third-party. This section is meant to achieve this and to give the client comfort that no third-party rights are being infringed.
7. Client Obligations
Under the first paragraph, the Client is required to respond promptly to requests from the designer/developer.
Under the next two paragraphs, whilst not always considered necessary, it’s no harm to establish the reasons why the designs are required and to obtain a provision that the client won’t use the artwork for some illegal or pornographic purpose (this clause would obviously not be appropriate if the designer/developer is preparing illustrations for a pornographic magazine!).
Where the copyright is transferred to the client, the designer/developer will no longer have any rights – hence the wording which reserves for the designer/developer the right to make use of the artwork in his publicity material.
8. Termination
If either party becomes insolvent or commits a material breach of the agreement then it’s sensible to give the other party the right to terminate.
9. Confidentiality
It is usual to have a confidentiality clause so that any trade secrets or confidential information which either party receives as a result of their dealings is kept confidential and not made available to anyone else.
10. Assignment
The issue of assignment of copyright has already been dealt with. This Clause concerns the right of either party to transfer/assign any rights or obligations under the agreement to someone else. Since a Design Agreement (Contract) trends to be somewhat personal in nature, assignment is prohibited by this clause.
11. Notices
It is usual to have a clause such as this, stating that notices must be given in writing and specifying the method of giving notice – in this case by hand, by fax or by.
12. Law and Disputes
Hopefully no disputes will arise, but it’s important to specify the courts and laws of the country which governs the agreement – usually that of the country which both parties are resident – and also to say how disputes will be resolved if they do arise. Remember that the United Kingdom has different legal systems: England and Wales, Scotland and Northern Ireland.
You might also wish to require the parties to try mediation in the event of a dispute, with recourse to the Court as the final option.
For more on mediation, visit CEDR
Works schedule
The Works Schedule should be written to suit the particular circumstances. In addition to the overall brief of the work to be done, the Works Schedule may contain dates for delivery, details of any expenses which can be reimbursed and hourly or daily rates that may apply.
General considerations
The documents should address the following issues:
(a) the agreed website specification (or a procedure to arrive at an agreed specification before development commences).
(b) the date by which the website must be delivered, together with key milestone dates that must be achieved in order to achieve that objective.
(c) the agreed fees for the design and/or development.
(d) the term of the contract
(e) there must be a written assignment of all copyright and other intellectual property in the website, including underlying software (or right to use a third party’s software) from the contractor to the organisation.
Ownership
You need to pay particular attention to ensure your company owns its own domain name and is the legal account holder for other online services, such as connectivity, hosting and security. You need to have control over access to these accounts.
Exclusivity and bargaining power
The web designer/developer will want to re-use some technical work from your website on websites for other customers. You should get as much exclusivity on their work as possible to give your business a competitive advantage.
The parties’ bargaining power, perception of the deal & the project’s price will contribute towards resolving any issues. The division of rights in a wholly bespoke, exclusive project may be very different from the division in one in which the customer is obtaining a customised version of a standard site.
Top 10 tips for project managers
Project managers with practical experience of web design and development have written our Top 10 Tips in this section. They should be considered by both designer/developer as well as the client.
1. Scope of Services
Start off with the most important aspect of the entire project. What exactly is the designer/developer going to do for the client? Write a general 3-5 sentence summary of the scope of service. Will the designer/developer be responsible for the design and programming? How will the website be updated? Who will be responsible for the marketing at the end of the project? Who will host the website when the project is done?
2. Price and Payments
This is the area where the designer/developer is upfront and states the exact price payment and terms of the payment is split up into installments. Is the project quoted at a fixed rate? Is it an hourly rate and how is this documented and tracked? Will the payments be made with a certain percentage up front as a down payment and then a monthly billing cycle, or is it a milestone related payment system?
3. Term and Termination
How long will this agreement contract be enforceable? If the client does not want to pursue the project ¾ of the way through the project how can he get out? What are the penalties and timeframe they can exit the contract? This is crucial especially to web development agreements with entrepreneurs and startups that many times have a great idea, some type of outline or business plan for what they wish to do, but for some reason never finish through with the project. The designer/developer must have certain rights. Do they keep all of the code that has been developed? Can they finish it and retain intellectual property to it? Many factors can go in this area, but it protects both the client and the developer in case a designer/developer is never able to complete a project or continues to be late on deliverables and the client wishes to terminate the relationship.
4. Ownership of Intellectual Property
One aspect that needs to be addressed is who will retain the intellectual property to the project? Typically the client retains all intellectual property. This area highlights all of the intellectual property covered such as the source code, all digital files, documentation, etc. Intellectual property is very important to any and all web design and development projects.
For further information visit Websites and Intellectual Property
5. Confidential Information
Many clients wish to keep all information that is exchanged within a project to the developer as highly confidential and cannot be disclosed whatsoever. The extent to which information can be disclosed must be addressed in the agreement. Can the designer/developer mention that they are working for the client during the course of the project to other prospects or potential clients? Many designers/developers use their portfolio of clients as sales tools for other clients. This area must represent exactly what is disclosed and for how long. What period of time is the information kept confidential? And so on.
6. Warranty and Disclaimer
Having a warranty on the work that is developed is standard in most web projects. Typically a 30-90 day warranty is given on all work to be functional and bug free. This is the area that small details such as the client having access to the server and by mistake entering the files and making changes that affect the functionality within the terms. Think of the label on products that the designer/developer purchases such as furniture and mattresses. It says that the warranty is void if you tear the label off. This is what the designer/developer can address in this area. They will provide warranty on certain terms and conditions with specific disclaimers as well.
7. Limitation of Liability
This is the area in which the designer/developer discloses that they are not liable for any losses of money for the developer or other economic losses directly or indirectly associated with the development of the website. Some less experiences clients will turn around to the designer/developer as the source of their website not succeeding online. Avoid issues in the future if something does not succeed that the client thought would, especially things that the designer/developer cannot control once the website is launched. Also, during the project itself, if for whatever reason there is a financial loss, it protects the designer/developer.
8. Relation of Parties
Make sure that the client and designer/developer understand what their relationship is. Is the relationship a development partnership? Is it strictly a work-for-hire type relationship? Is it a client and vendor relationship? This is the area where this needs to be highlighted to make sure the business relationship is understood.
9. Employee Solicitation / Hiring
Many designer/developers never think twice about this, but there have been cases where clients have lured employees or freelancers of the developer during or after the project was completed. Of course this has huge negative aspects associated to it if this happens. That is why this area is also extremely crucial to lay out the fact that the client can not solicited the developer’s employees in any way when it comes to potential hiring or additional perks. Specify a certain amount of time for this as well. Typically this time from is between 2-5 years.
10. Entire Agreement
This is the ending of the document that basically should say that the entire document and its attributes fall under the entire contract and that nothing will supersede it. Also, this is the area the will have the client and developers key representative who will sign it, date it, and post their roles within the company. Make sure that any and all modifications after signature are signed with initials of both parties next to the change.
E RADAR IT contract templates
You can purchase a selection of IT contract templates from E RADAR’s web shop. Members can download all the legal templates as part of their membership package.
What's in a web developer contract?
Monday, March 17, 2014
Looking for someone in the US
Search over 1 billion US records to find debtors, do due diligence and check backgrounds of new staff!
22 e-contract legal and security risks
A contract is the defining document for cementing the relationship between the business and customer. Not only does it establish the parties’ intentions and expectations on what goods and services have been offered and accepted, the contract should also set out the road map to resolve difficulties if something were to go wrong, for whatever reason.
It goes without saying that the contract must have integrity and be enforceable, if necessary.
This includes e-contracts.
E-contracts – contracts signed electronically- still have the same legal requirements (an offer, acceptable, consideration, intention… etc) as their paper cousins; they are simply a little bit more complicated to define because of the use of technology to create and deliver them.
So, if you are considering using e-contracts in your business here’s my top 22 legal and security risks you need to discuss with your board directors, project teams and lawyers.
Unenforceable e-contracts?
- 1. The time that an e-contract has been formed may be uncertain;
- 2. The place where an e-contract has been formed may be uncertain;
- 3. The authority of an individual to enter into a contract on behalf of another person or entity may be uncertain.
- 4. Electronic communications may not satisfy statutory requirements for certain contracts to be in writing;
- 5. Electronic communications may not satisfy statutory requirements for certain contracts to be signed.
- 6. Depending on the terms of a contract, it may be uncertain whether electronic communications are effective to amend the contract.
- 7. Depending on the terms of a contract, it may be uncertain whether electronic notices are valid.
- 8. Disruptions to the availability of a project collaboration system may cause interference with the project.
- 9.Incompatible technology may be used by the various contracting parties.
- 10. Disputes may arise between the provider of an online collaboration system and the contracting parties in relation to the use of the system.
- 11. Disputes may arise between the contracting parties regarding the use of the system.
- 12. Disputes may arise in relation to the ownership of intellectual property associated with the project.
- 13. The confidentiality of electronic records may be compromised during communication or retention.
- 14. Electronic records created and maintained by a system may not be admissible in court as evidence in the event of a dispute.
- 15. Electronic records created and maintained by a system may not be given the same evidential weight as paper records.
- 16. There may be difficulty proving the time at which an electronic record has been communicated.
- 17. The identity of the contracting parties may not be able to be authenticated.
- 18. The process of disclosing relevant documents in the event of a dispute may be unmanageable as a result of multiple communication and record-keeping methods.
- 19. Parties may be in breach of their duty to preserve evidence if electronic records are not preserved.
- 20. Parties may be in breach of their statutory obligations to maintain records if electronic records are not archived appropriately.
- 21. Where a third party service provider is used, the contracting parties may not have access to electronic records after completion of the project.
- 22. There is a risk that the statutory record-keeping obligations of government agencies may be breached by using an online collaboration system.
Want to find out more?
Subscribe to E RADAR to discover more resources on e-contracts. Or visit our E Adoption Risk Ladder page.
22 e-contract legal and security risks
Saturday, March 15, 2014
53 Essential IT Security Tips For Your Digital Business
As IT and the Internet matures we are all becoming much wiser about many of the online threats facing us personally and the organisations where we work.
However, cyber criminals are becoming cleverer and more sophisticated too! New threats, different ways of attacking network and information systems, and more sophisticated malware demand that we keep alert at all times.
Ongoing training for all members of staff across the organisation is your first line of defence. You need to keep them informed about the latest threats and what they should and shouldn’t do when working online.
Having policies in place to deal with staff use of business communications and the Internet whilst they are at work is also a priority. Staff policies should be linked to the contract of employment so that you can instigate disciplinary proceedings should a member of staff deliberately abuse the policy.
IT security tips
We’ve listed 53 essential IT security tips for you to consider. We can also provide general training courses in Information Security for staff throughout the year with our network of qualified IT security specialists.
Threat - virus and other software attacks
- Tip 1 – Introduce virus-checking software.
- Tip 2 – Use a properly-configured firewall between your systems and the Internet.
- Tip 3 – Do not open suspect emails or attachments.
- Tip 4 – Only enable preview panes once you have removed all suspect emails.
Threat – theft of laptops, personal devices and other hardware
- Tip 5 – Maintain a list of your equipment (including serial numbers) and check your physical security.
- Tip 6 – Control access to business premises and computer systems.
- Tip 7 – Encrypt sensitive data.
- Tip 8 – Password protect your hard drive and data.
- Tip 9 – Mark your postcode on all hardware with an ultra-violet pen.
- Tip 10 – Regularly back-up essential files and store copies in a secure place, away from the premises where the computers are used.
Threat – theft of Intellectual Property / copying of information
- Tip 11 – Make safe your customer or prospect lists, ideas and designs, and correspondence.
- Tip 12 – Check who has access to your systems and log usage.
- Tip 13 – Check physical security of computers and back-up files.
- Tip 14 – Make sure all your security staff are adequately vetted.
Threat – mishandling of personal information
- Tip 15 – Notify the Information Commissioner that you process personal information.
- Tip 16 – Ensure you understand the 8 Data Protection Principles.
- Tip 17 – Don’t allow your computer screens to be viewed from the street.
Threat – financial fraud and theft on-line
- Tip 18 – Understand the risks associated with different types of ‘card not present’ transactions, including cardholder not receiving goods, or goods sent to another address.
- Tip 19 – Validate new customers and suppliers using published information from trusted sources.
- Tip 20 – Obtain an online credit status report and electronic identity check.
- Tip 21 – Report fraud or attempted fraud to your local Police.
Threat – unauthorised email access/misuse/abuse
- Tip 22 – Protect email systems against accidental misuse.
- Tip 23 – Ensure workers know about policies on sending or publishing illegal or offensive materials via email or on a website.
- Tip 24 – Check that the policies are lawful and enforceable.
- Tip 25 – Always ‘inform’ users that you may monitor their communications.
Threat – unauthorised Internet browsing
- Tip 26 – Protect website against accidental misuse.
- Tip 27 – Ensure workers know about policies on viewing non-work related websites or visiting offensive or illegal websites.
- Tip 28 – Check that the policies are lawful and enforceable.
- Tip 29 – Always ‘inform’ users that you may monitor their communications.
Threat – sabotage of data
- Tip 30 – Protect against unauthorised amendment or deletion of records to disrupt the business or for financial gain.
- Tip 31 – Ensure that regular back-up copies are securely stored.
- Tip 32 – Check data regularly for changes in nature or size.
- Tip 33 – Adopt vetting procedures for workers doing tasks deemed higher risk.
Threat – identity theft
- Tip 34 – Protect against impersonation and developed identities.
- Tip 35 – Do not provide personal information without validating the identity of the organisation making the request.
- Tip 36 – Implement security measures to prevent theft of business records for use in identity theft.
- Tip 37 – Use identity authentication and credit status checking services.
Threat – spoofing attacks/passing off
- Tip 38 – Protect against impersonation of the business.
- Tip 39 – Forward email to sender’s ISP for action and adjust your filters to block unwanted email.
Threat – denial of service attack
- Tip 40 – Protect against attempts to prevent legitimate users of a service from accessing or using the service, including ‘flooding’ a network with mass e-mail and disrupting connections between machines.
- Tip 41 – Contact your ISP if you suspect an attack.
Regularly practice restoring files onto your systems
- Tip 42 – Draw up a set of comprehensive computer/information security policies for yourself and your staff.
- Tip 43 – Maintain a list of your equipment (including serial numbers) and check your physical security.
- Tip 44 – Introduce virus-checking software.
- Tip 45 – Use a properly configured firewall between your systems and the internet.
- Tip 46 – Do not open suspect emails or attachments.
- Tip 47 – Only enable preview panes once you have removed all suspected emails.
- Tip 48 – Control access to business premises and computer systems.
- Tip 49 – Password protect your hard drive and data.
- Tip 50 – Mark your postcode on all hardware with an ultra-violet pen.
You’ll notice that some of these tips are repeats. It’s deliberate in order to get you into the regular cycle of IT security management: Plan Do Check Act, Plan Do Check Act, Plan Do…. you know what I’m saying.
And for those of you who were expecting 53 tips instead of just 50… for the time it took you to read to the end of this article 3 more people in the UK became victims of identity theft.
Just goes to show that 3 is a magic number!
Related articles
53 Essential IT Security Tips For Your Digital Business
Subscribe to:
Posts (Atom)