GDPR on Websites: How it should work and why it is essential

Learn what GDPR is, how it affects websites, and why compliance is absolutely crucial for security and your customers' trust.

Abstract minimalist representation of data security, privacy shields, and digital compliance with subtle geometric lines and dark professional tones

Every site processes personal data, even if it doesn't sell anything. A contact form, an analytics tool, an embedded video, or a map are enough for the General Data Protection Regulation (GDPR) to apply. The good news is that most of what it requires is common sense and good technical work.

This article is for informational purposes and does not constitute legal advice. For your specific case, speak with a legal professional or your business's Data Protection Officer (DPO).

Why it is essential

  • It's an obligation. GDPR has been applied since 2018 to every business processing people's data in the EU, regardless of size. For cookies, the rules of the ePrivacy Directive also apply, which in Greece have been incorporated via Law 3471/2006.
  • Audits aren't just for the big players. European authorities have also imposed fines on small businesses for cookies without consent, without a reject option, or without proper information.
  • It builds trust. A site that clearly explains what it does with data and doesn't pressure visitors into "accepting all" demonstrates professionalism.

Cookies: how the banner should work

  • It loads nothing prior to consent. Analytics, advertising pixels, and every non-essential tool wait for the visitor's "yes".
  • It has a "Reject" button as easy as "Accept". Same size, same level, no hidden options.
  • It separates categories, without pre-checked boxes: necessary, analytics, advertising.
  • It states who sets what and for how long. The cookie policy mentions whether each cookie is yours or a third party's, and how long it is retained.
  • It allows changing your mind from anywhere. A "Cookie settings" link in the footer is enough.
  • It blocks embedded content. YouTube videos, maps, and social widgets set their own cookies, so they load only after consent or upon clicking.

"By continuing to browse you accept" and "manage cookies from your browser" are not considered valid consent.

Forms and customer data

  • Ask only for what you need. For an inquiry, name, email, and message are enough. The phone number can be optional.
  • State the purpose next to the form, with a link to the privacy policy.
  • Newsletter with separate consent. A quote request does not mean signing up for an email list.
  • Keep data only as long as necessary. Define how long you keep inquiries and delete them afterwards.
  • Be able to respond to requests. Customers have the right to see what you keep about them, correct it, or request deletion. This is much easier when requests live in a system rather than scattered across an inbox.

What every site must have

  1. Privacy policy in plain language: who you are, what you collect, why, to whom you give it, how long you keep it, and how rights are exercised.
  2. Cookie policy with the list of cookies the site actually uses.
  3. HTTPS everywhere, without exceptions.
  4. Contracts with providers who access data: hosting, email, CRM, newsletter, payments.
  5. Caution with non-EU tools. If a tool sends data outside Europe, an appropriate legal basis is required.
  6. Breach plan. If data leaks, notifying the Authority must generally be done within 72 hours.

What's coming: the Digital Omnibus

  • The European Commission has proposed changes to GDPR and cookie rules, aiming for fewer repetitive banners. These changes are still under negotiation and do not apply. Until they are voted on and implemented, current rules apply, and consent remains the basis for non-essential cookies.

Conclusion

Compliance is not a plugin you install once. It is the way the site is built: what it loads, what it collects, and where it sends it. If you design it correctly from the start, GDPR becomes another quality attribute, not a burden.

Sources: Hellenic Data Protection Authority, recommendations for trackers* (2020). Lawspot, [fine by the Spanish Authority for cookies](https://www.lawspot.gr/nomika-nea/cookies-prostimo-9000-eyro-gia-paranomi-egkatastasi-apo-istoselida-stin-ispania/). Osborne Clarke, [Digital Omnibus package](https://www.osborneclarke.com/digital-omnibus-package).*

Is your site ready?

We'll tell you what loads prior to consent.

We check cookies, third-party tools, and forms, and tell you what is technically needed to work correctly.

Contact us