20% off your first year, your own domain name included. See the price
Privacy

Making your website GDPR compliant

Even a small website with a contact form handles personal data. These are the four things you need to arrange, in plain language.

Sophie from Temblit · Updated · 5 min read

The short answer

A website meets the GDPR when you tell visitors what data you collect and why, ask only for what you need, send it securely and keep it no longer than necessary. In practice: a privacy statement, a cookie banner where saying no is as easy as saying yes, short forms and a secure connection. A Temblit website already has that padlock. The privacy statement you write yourself, because only you know what you do with people's data.

What the GDPR asks of a small business

The GDPR is the European privacy law. It applies to anyone who handles personal data of people in the European Union, so also to a plasterer working on his own. A name, a phone number and an email address in a contact form already count as personal data.

That sounds heavy. For an ordinary business website, though, it comes down to a handful of promises to yourself:

  • Say it. Visitors must be able to read what you collect and what for.
  • Do not ask too much. Only what you really need to help someone.
  • Keep it safe. Send it over a secure connection and do not leave it somewhere unguarded.
  • Throw it away. Once you no longer need it, delete it.

A coach who only puts a phone number and an email address on his website has it easy. A dental technician with a form, an online booking calendar and a newsletter has more to sort out. The more you collect, the more you have to explain. That alone is a good reason to look hard at what you really need.

This article helps you get started, but it is not legal advice. Unsure about your own situation, for example because you handle medical data? Ask a lawyer, or check the website of the data protection authority in your country.

A privacy statement people can actually read

Every website that collects data should have a privacy statement. It is an ordinary page, usually linked at the bottom of every page. There are plenty of examples around, but never copy one blindly. A statement full of sentences about web shops and newsletters you do not have is simply wrong.

In your privacy statementWho you are, how to reach youWhat data you ask forWhat you use it forHow long you keep itWhat rights people have
Five parts, in your own words. Short is fine, as long as it is true.

Also write down who you share data with. Use bookkeeping software, a newsletter service or an online calendar? Then data goes to that company. With such companies you sign a data processing agreement. Most big services have one ready; you only need to accept or download it.

With Temblit you add such a page yourself, just like any other page. How to set up and adjust the rest of your website is on the page about your website with Temblit.

A cookie banner with two fair buttons

Cookies are small files a website places on your visitor's phone or computer. Some are needed, or the website will not work properly. For those you need no permission. Others track what someone does, for advertising for example. For those you need permission first.

jouwbedrijf.nlCan we use cookies?We only measure visits if you agree.You can always change this later.DeclineAccept
Decline sits in the same place and is just as big as accept. That is how it should be.

If your website is with Temblit, you put a cookie banner on it yourself. You do that with a snippet of code from a cookie banner provider, which you add to your website. Choose one with two buttons of the same size.

European privacy regulators are clear about this. Saying no must be as easy as saying yes. So no bright button for yes and a grey little link for no. No boxes that are already ticked, and no banner that blocks the whole website until someone agrees.

And then Google Consent Mode

Do you measure visitors with Google Analytics or advertise through Google? Then you will come across the term Google Consent Mode. It is a setting that tells Google what your visitor chose in your cookie banner. If someone says no, Google's measuring codes respect that and do not track that visitor.

Two things to remember. It does not replace your cookie banner, it listens to it. And if you use no Google services on your website, it does not concern you. Preferably let whoever manages your measuring codes set it up.

Forms: ask only for what you need

Say you are a gardener. Someone wants a quote for their garden. What do you need? A name, a phone number or email address, and a short description. Not a date of birth. A house number perhaps only later. Every field you leave out is one you never need to protect or delete.

1Fill inshort form2Useonly for this3Clear outafterwards
A piece of data has a beginning and an end. Decide up front when you will clear it away.

A newsletter only with the visitor's own tick

If you want to send people a newsletter later, let them tick the box themselves. Someone asking for a quote has not yet said he wants mail every month. A box that is ticked in advance does not count as permission.

How long you keep things

There is no fixed period for every piece of data. The rule is: no longer than needed. A request that came to nothing can go after a few months. Customer details you need for your accounts, you keep for as long as your tax office requires. Write your choice down in your privacy statement, so you remember it yourself too.

And never put a form on a website without a secure connection. The padlock in the address bar shows that what someone fills in cannot be read along the way. A Temblit website has that as standard. What else belongs on a new website is in the checklist for a new website.

When someone asks, or when things go wrong

Visitors and customers may ask you what data you hold about them. They may ask you to correct or delete it. Get such a request? Reply within a month. Usually one email settles it.

That goes much faster when you know where everything is. Make a list: your mailbox, your bookkeeping software, your calendar, maybe a folder on your laptop. Officially, such a list is called a record of processing activities. For a small business it can be short: what you keep, why, where and for how long. For most small businesses it need not be more than that.

Something goes wrong, say your laptop with customer details is stolen or someone breaks into your mailbox? Then you may have a data breach. If there is a risk to the people whose data it is, you report it within 72 hours to the data protection authority in your country. Their website explains how.

Many data breaches at small businesses start with a fake email. How to spot one is in the article on recognising phishing.

A website with the padlock on it

Tell us in one sentence what you do. We set up your website with a secure connection, and you see it first for free.

  • Free to try
  • Pay only when you go live on your own domain name

Still have questions? Here are the answers

Unsure about your own situation? Ask a lawyer, or check with the data protection authority in your country.

Do I need a privacy statement as a freelancer?

Yes, as soon as you collect people's data through your website. A contact form or an email address people write to is already enough. It can be short, as long as it matches what you really do.

What should a privacy statement contain?

Who you are and how people reach you, what data you collect, what for, how long you keep it, who you share it with and what rights people have. Also that they can complain to the data protection authority.

Can the button to decline cookies be smaller than the button to accept?

No. Declining must be as easy as accepting. Make the two buttons the same size and just as clear, side by side.

Can I put a contact form on my website?

Yes. Ask only for what you need, make sure the connection is secure and say in your privacy statement what you do with the data and how long you keep it.

How long can I keep data from a contact form?

No longer than needed. A request that did not turn into a job can be deleted after a few months. If someone becomes a customer, you keep what you need for your accounts.

What do I do if customer data has leaked?

Find out what happened and which data is involved. If there is a risk to those people, report it within 72 hours to the data protection authority in your country, and tell the people involved if the risk is high.

Rather just ask?

For questions about your Temblit website, mail service@temblit.com. We answer in English. We do not give legal advice. Or send us a WhatsApp message.