Contents · 11
- What Actually Counts as Personal Data on a Website
- The Privacy Policy - What Must Be in It
- Cookies and Consent - How to Do It Properly
- Forms - the Information Clause and Consents
- External Tools - the Silent Problem
- Processing Agreements and Providers
- Technical Security as Part of GDPR
- People's Rights - How to Handle Requests
- The Most Common Mistakes on Polish Business Websites
- A Checklist to Print
- How to Approach It in Practice
Most business owners treat GDPR on a website like a tax on other people's ideas: something they were once told to have, so they pasted a ready-made privacy policy from the internet and forgot about it. The problem is that a website changes faster than a document. An analytics tool was added, someone embedded a map, a new field appeared in the form, and the policy still describes the state of affairs from three years ago.
The good news: making a website GDPR compliant is not a gigantic project. It is a list of about twenty things you can check in a single afternoon. This article is exactly such a list - ordered by what is usually broken first.
An important disclaimer: this is a practical write-up, not legal advice. For more complex cases (sensitive data, selling to consumers in several countries, profiling) it is worth consulting a lawyer or a data protection officer.
4%
30 days
72 h
What Actually Counts as Personal Data on a Website
Let us start with what surprises the most people. Personal data is not only a first and last name. It is any information that allows a person to be identified - directly or indirectly. On a business website these are:
- the email address and phone number from a form,
- the visitor's IP address,
- identifiers in cookies and similar technologies,
- data from a customer account in a shop,
- the content of a message sent through a chat,
- session recordings and click maps, if you use such tools.
Since an IP address is personal data, the mere presence of a site on a server that keeps logs means processing data. So there is no such thing as a site "without GDPR". There are only sites that have it under control and those that do not know they are processing anything.
In practice a three-layer split is used: data you collect deliberately (forms, accounts), data collected by tools on the site (analytics, ads), and data collected by infrastructure providers (hosting, CDN, server logs). Only once you have drawn up such a map do you know what needs to be described and with whom to sign agreements.
The Privacy Policy - What Must Be in It
A privacy policy is the document that fulfils the information obligation under Articles 13 and 14 of the GDPR. The most common mistake: the document is correct as text but does not match the site.
Minimum content:
- The data controller - the full company name, address and contact details. If you run a sole-trader business, you are the controller.
- Purposes and legal bases - separately for each purpose: replying to an enquiry, fulfilling an order, accounting, marketing, analytics, establishing and defending claims. Each purpose has its own basis under Article 6 of the GDPR.
- Recipients of the data - providers of hosting, email, CRM, analytics tools, the accounting office.
- Retention periods - specific ones, not "as long as necessary".
- User rights - access, rectification, erasure, restriction, portability, objection and the right to lodge a complaint with the supervisory authority (in Poland, the President of UODO).
- Transfers outside the EEA - if you use tools from outside Europe, state the basis for the transfer.
- Cookies and similar technologies - a list of categories, purposes and how consent is managed (often in a separate cookie policy).
It is easy to check: open your own policy and for each tool on the list below answer whether it is described there. If not - the document is incomplete.
Cookies and Consent - How to Do It Properly
The rules are less complicated than ready-made plugins suggest. Cookies and similar technologies fall into two groups.
Necessary - the site does not work without them: session, cart, security, remembering the cookie decision. They do not require consent, but must be described.
Optional - analytics, marketing, personalisation, embedded content. They require consent, which must be:
- prior - the script must not run before the user gives consent,
- voluntary - no blocking of content and no consent walls,
- specific - separately for individual purposes,
- withdrawable - as easily as it was given.
A banner is correct when the Reject button is as visible as Accept. A banner where refusing takes three clicks in the settings and consenting takes one is, in practice, forcing consent.
For Google tools there is also Consent Mode v2, which passes Google a signal about whether the user has consented to analytics and advertising. For ad campaigns targeting users in Europe it is a practical requirement, because without it you lose some measurement and remarketing features.
Forms - the Information Clause and Consents
A contact form is the most commonly used data collection mechanism and the most commonly poorly described one.
The information clause should be visible before sending, in a shortened form with a link to the full policy. It does not have to be a checkbox. An example that works:
The controller of your data is [company name]. We will use the data from the form to reply to your message - the basis is our legitimate interest and taking steps before entering into a contract. We describe the details and your rights in our privacy policy.
Consent appears only where it is needed - usually for a newsletter and marketing. The rules:
- a separate checkbox, unticked by default,
- a specific description of what you are agreeing to,
- no link to sending an ordinary enquiry,
- a record of proof of consent (date, content, IP address or identifier).
Data minimisation is a principle that is easy to implement: do not ask for a phone number if you will reply by email anyway; do not ask for an address if you are not sending anything. The fewer the fields, the less data to protect - and, pleasantly, the higher the form's conversion. We write about how to lay out the form itself in the article on conversion forms.
External Tools - the Silent Problem
This is where violations most often happen, because they take place in the background and without the owner's knowledge.
| Tool | Problem | Solution |
|---|---|---|
| Google Fonts from Google's servers | Passing the IP without consent | Hosting fonts locally |
| Google Maps embedded on the page | Loads scripts and cookies | Static preview + consent after a click |
| YouTube videos | Cookies and tracking | youtube-nocookie mode or loading after consent |
| Social media widgets | Tracking even without a click | Plain links instead of embeds |
| Advertising pixels | Profiling | Running only after consent |
| Chat and session recordings | Conversation content, behaviour recording | Consent, field masking, a description in the policy |
A practical rule: every external request that sends an IP address to a third party is data processing and must have a basis, a description and an agreement with the provider.
Processing Agreements and Providers
If a provider processes data on your behalf (hosting, a mailing system, a CRM, a form tool, online accounting), you need a data processing agreement with them under Article 28 of the GDPR. With most large providers this is a standard addendum accepted in the panel - you just need to find it and accept it. It is worth keeping a simple table: provider, purpose, country of processing, date the agreement was signed.
A separate matter is transfers outside the European Economic Area. For US providers, check whether they take part in the Data Privacy Framework or use standard contractual clauses. This is an area that has changed several times in recent years, so look at the provider's documentation once a year.
Technical Security as Part of GDPR
GDPR compliance is not only documents. Article 32 requires appropriate technical measures. For a business website that means the following at minimum:
- HTTPS across the whole site, with an automatic redirect,
- updates of the CMS, plugins and libraries,
- strong passwords and two-factor authentication for the admin panel,
- backups outside the production server,
- restricted access - an account for each person, no shared passwords,
- protection of forms against spam and abuse,
- an incident response plan: who does what and within what time when a leak occurs.
The obligation to report a breach to the supervisory authority within 72 hours applies when the breach may pose a risk to people's rights and freedoms. It is good to have the procedure prepared in advance rather than looking for it in the middle of an incident. We describe the technical side of security more broadly in the article on technical SEO, which covers HTTPS and security as a ranking signal.
People's Rights - How to Handle Requests
A user has the right to ask what data you process about them, to ask for it to be corrected or deleted, and to object to marketing. You have a month to respond. The biggest problem is not the request itself but the fact that nobody knows where the data lives.
A simple setup that solves most situations:
- one contact mailbox for data matters (e.g. the address given in the privacy policy),
- a list of storage locations: CRM, email, spreadsheets, the invoicing system, the mailing tool,
- a ready response template and an identity verification procedure,
- a register of requests with dates.
The same register is useful in the event of an inspection, because it shows that the procedure works in practice and not only on paper.
The Most Common Mistakes on Polish Business Websites
From reviewing the websites of small and medium-sized businesses, the same patterns keep recurring:
- A policy copied from another company - with someone else's name, someone else's address or a description of tools that are not on the site.
- A banner without real script blocking - the user's decision changes nothing.
- Forced consents - one checkbox for everything.
- No clause under the form - only a link in the footer that nobody sees.
- External fonts and maps loaded without consent.
- No processing agreements with providers.
- Outdated documents - a policy from 2018, unchanged since launch.
- No incident procedure - only in the middle of a leak does it turn out that nobody knows what to do.
A Checklist to Print
How to Approach It in Practice
If you are starting from zero, the order matters. First the data map, because without it you cannot write any document correctly. Then technical fixes (external resources, analytics scripts, HTTPS), because they create the real risk. Last, the documents that describe the actual state.
For companies building or rebuilding a website, the cheapest approach is to include GDPR from the start: local fonts, privacy-respecting analytics, forms with a clear clause and a consent banner built into the design. Bolting it on afterwards always costs more. If you are wondering what a solid website costs in the first place, see what the price of a website depends on, and if you are laying out the content of a site from scratch - what a business website should contain.
GDPR compliance is not a state you reach once. It is a habit: a new tool on the site means updating the policy, a new provider means an agreement, a new form means a clause. Companies that put this in place gain an advantage beyond compliance - their website inspires more trust, and that is exactly what matters in online sales.