• info@build100k.com

How A Privacy Policy Should Be Written

How A Privacy Policy Should Be Written

How A Privacy Policy Should Be Written

Sharing is caring!

A privacy policy is an important part of any website. If you are not sure if you need a privacy policy, there is a simple question to answer if you should have one. ‘Does your website collect any personal data from the users?’ This does include email. If you answered yes, then you need a privacy policy.

In most countries, you legally need a privacy policy if you collect any kind of data from a user. Once you know you need one, how do you write one?

How To Write A Privacy Policy?

A privacy policy needs to be understood by everyone who visits your website. English is the best option, but if your website is in another language, you should have the privacy policy in that language. When you are writing the policy, you should aim for a 9th-grade reading level. This is a reading level that most people have and allows them to understand what is being said.

You should explain the information that you are gathering and why you are collecting the data. Emails and cookies are very common information to track, so there are a lot of great examples out there. If you are gathering information for any sketchy reasons, you should stop these practices instead of trying to explain it to your visitors.

The important information that you should include is if you are sharing information with anyone. This is a huge part because you need to inform the users where their information is going. In most areas, you do not need to list the exact company, but you do have state clearly that the information gathered is being shared or sold.

You should also have information about the laws and initiatives that you are complying with. Having this information is legally required in some areas, and you can face fines if this information is missing.

Depending on the information that you are collecting and what it is being used for, you should include information about how the users can opt out. Most email collections will have this information at the bottom of every e-mail, and somewhere on the host website.

If you are using Google or Apple products, you will need to include information about their services and about their privacy policy. In most areas, you can just post a link to Google’s or Apple’s privacy policy in your policy to be covered.

These are the common elements that a privacy policy should have:

Who is the site/app owner?
What data is being collected? How is that data being collected?
For which purposes is the data collected? Analytics? Email Marketing?
What third parties will have access to the information? Will any third party collect data through widgets (e.g. social buttons) and integrations (e.g. Facebook connect)?
What rights do users have? Can they request to see the data you have on them, can they request to rectify, erase or block their data (under European regulations most of this is mandatory)?
Description of process for notifying users and visitors of material changes to the privacy policy
Effective date of the privacy policy

Do you have a privacy policy for your site?

Writing a privacy policy does not need to be hard, and you do not even need to write your own. There are tools like terms feed and iubenda that will make a privacy policy for you in minutes, and you can add it to your website.

generate your privacy policy

jay kang

Translate »