| You really should have a Privacy Policy page if | | | | this article. |
| you collect data from visitors to your website in | | | | However, as a general minimum guideline, your |
| any way. This data could be something as simple | | | | Privacy Policy should cover the following: |
| as an email address - for instance if you invite | | | | How information is collected. |
| someone to add themselves to your mailing list. | | | | The types of information collected. |
| Or it could be more detailed information, such as | | | | How and for what ends it is shared with |
| what you might obtain via a contact form. | | | | others (or not). |
| Nowadays, web users are very conscious of | | | | How information can be updated by users. |
| privacy and safety issues online. So for individuals | | | | Information should also be available to users at |
| and small businesses, it helps potential customers | | | | any time, and they should be able to contest its |
| build confidence in you as a supplier of products | | | | accuracy and completeness. |
| or services. In fact it's a good idea to link to your | | | | The use of cookies, particularly by third |
| Privacy Policy from your contact page or | | | | parties, such as analytics providers. |
| anywhere you ask someone to submit | | | | The tracking of online activities, for example |
| information, such as when subscribing to a | | | | by a search engine paid ads service. |
| newsletter. That way you're likely to get more | | | | Any changes to tracking activities should be |
| response and fewer forms abandoned before | | | | notified well in advance. |
| completion. | | | | What information, if any, is passed on to third |
| By the same token, don't go overboard with | | | | parties, and the nature of these third parties. |
| finding out information on your contact forms - | | | | The secure holding of all information, with |
| the more questions you have and the more | | | | reasonable steps taken to prevent unauthorized |
| intrusive a contact form appears to be, the less | | | | access. |
| likely it is to be completed and submitted. | | | | The clearer and more succinct you can make |
| Larger companies will often actively look for a | | | | your Privacy Policy the better. The average Policy |
| Privacy Policy. They may insist that you have one | | | | is around 2,500 words, which is long for a web |
| in place before doing business with you, or they | | | | page. |
| may simply not contact you in the first place, if | | | | Don't expect many people to read it in full, but |
| they can't see a Privacy policy on your website. | | | | anyone accessing the page will likely scan it for |
| Your Privacy Policy should clearly explain what | | | | key points. Any mistakes will stand out, so ensure |
| information you will be collecting and how you | | | | that the grammar, spelling, and punctuation is as |
| intend to use it. If you intend to make it available | | | | good as that on the rest of your site. |
| to other companies, you should clearly say so. If | | | | For small businesses which hire a freelance |
| you don't, you should also say so clearly. Most | | | | copywriter, there's always the temptation to do |
| people are uneasy about information being | | | | the 'less important' pages yourself and save |
| forwarded, even if it is to 'carefully selected | | | | money. However, a poorly written Privacy Policy |
| partners' - so if you guarantee not to pass | | | | or badly-worded contact page could end up |
| anything on, you should say so. | | | | costing you dearly. |
| The content of a privacy policy is open to | | | | Finally, bear in mind that while a Privacy Policy |
| interpretation, and privacy policies vary from | | | | should be in place, it doesn't have to be highly |
| jurisdiction to jurisdiction. Both the United States | | | | visible. It's not worth making it part of your main |
| and the European Union have developed privacy | | | | menu, for instance. Instead, have it as the small |
| policy guidelines, as well as an extensive legal | | | | print at the bottom, next to your Terms & |
| framework, as have other jurisdictions, and these | | | | Conditions. This is also where anyone looking for it |
| are updated over time. Comprehensive | | | | would expect to see it. |
| frameworks are therefore beyond the scope of | | | | |