Data protection on your website protects not only your visitors but also your company: it builds trust, reduces legal risk and improves data quality for marketing and product development.
The General Data Protection Regulation (GDPR) sets the framework. Particularly relevant are, among others, the principles in
- Art. 5 GDPR (e.g. purpose limitation and data minimisation),
- the legal bases in Art. 6 GDPR,
- the information obligations in Art. 13/14 GDPR,
- "data protection by design and by default" under Art. 25 GDPR,
- the documentation obligations (including the record of processing activities under Art. 30 GDPR),
- security of processing (Art. 32 GDPR),
- the data protection impact assessment for high risks (Art. 35 GDPR)
- and the rules on transfers to third countries (Chapter V GDPR).
For cookies and similar technologies, Section 25 TDDDG also applies in Germany: storing information on a user's device or accessing information stored there generally requires consent unless it is strictly necessary to provide the service.
Depending on their severity, infringements can lead to fines of up to EUR 20 million or 4% of worldwide annual turnover, in addition to reputational damage and the effort involved in handling complaints or audits.
Your solution for the best data protection
Trust is the foundation of every good business relationship. Strengthen your relationships with customers by leveraging our expertise in data protection. This will give your company a strong competitive advantage, allowing you to focus fully on your business.
The 7 key aspects: what to check, what to watch out for and what best practice looks like
1) Transparency and legal bases
What do companies need to look at?
Check your privacy notice and cookie information to make sure that every service you use (e.g. an analytics tool or chat widget) is listed with its purpose, legal basis, recipients, storage period and any transfers to third countries. Name the controller, a contact address and the data protection officer.
What do you need to watch out for?
Make sure the description in your privacy notice is technically accurate: whatever it states (such as IP anonymisation) must actually be configured that way. Write clearly and in plain language so that users can understand what happens to their data.
What is best practice?
Keep an up-to-date internal data inventory (a list of all tools and data flows) and use it to generate your privacy notice, with a "last updated" date and a short change log. Add micro-transparency at sensitive points, for example a short explanation right next to a form of why a field is needed.
2) Consent and tracking
What do companies need to look at?
Review your consent banner (consent management platform, CMP for short), its text modules and the cookie categories (e.g. statistics, marketing). Check whether non-essential scripts are actually blocked until consent has been given. Make sure a consent log (proof of consent with a timestamp) exists.
What do you need to watch out for?
Offer equivalent choices ("Accept all" and "Reject all") and allow users to withdraw their consent at any time via a footer link such as "Cookie settings". According to the Administrative Court (VG) of Hannover (10 A 5385/22), the "Reject all" option belongs on the first layer of the banner and must be as visible as "Accept all". Do not load any analytics or marketing tags before consent has been given (no "pre-tracking").
The EU's Digital Omnibus proposal of November 2025 would move the cookie rules into the GDPR. It has not been adopted yet. In its negotiating mandate of 21 October 2026, the Council keeps the rules in the ePrivacy Directive. Cookie banners therefore remain necessary for the time being.
What is best practice?
Offer clear, granular categories with short descriptions of their purposes and use Consent Mode (measurement with heavily reduced data) or server-side tagging (tags run on the server instead of in the browser) to achieve data minimisation. Spot-check pages and pop-ups every quarter to make sure the blocking actually works.
3) Forms, newsletters and communication
What do companies need to look at?
Review all contact, quote request and job application forms as well as chat and support widgets. For newsletter sign-ups, check whether double opt-in (two-step confirmation by email) works without gaps.
If your chat widget is AI-based, users must be informed that they are interacting with an AI system unless this is obvious from the context. This requirement under Art. 50(1) AI Act has applied since 2 August 2026. Check whether your provider covers it or add the notice yourself.
What do you need to watch out for?
Reduce fields to what is necessary (data minimisation) and keep purposes clearly separate: a contact request is not automatically consent to marketing. Set retention periods and implement them technically, for example through automatic deletion runs.
What is best practice?
Word checkbox texts unambiguously ("I would like to receive the newsletter") and use CAPTCHAs (tests to keep out bots) or server-side checks. Set up automated deletion runs that regularly remove form entries, uploads or chat logs.
4) Embedded third-party content and measurement tools
What do companies need to look at?
List embedded content such as YouTube videos, maps, podcast players, social plugins and web fonts, as well as measurement tools such as A/B testing, heatmaps (session recordings) and error/performance monitoring.
What do you need to watch out for?
Block every embed that tracks people as long as no consent has been given. For social plugins, check whether joint controllership (shared responsibility under data protection law) may apply. Mask sensitive fields in session recordings and truncate IP addresses so that no plain-text data is recorded.
What is best practice?
Use two-click solutions (content only loads after consent) or privacy-friendly embedding options and, where possible, host fonts and scripts locally. Limit tracking to the measurement events you actually need and enable security headers such as Content-Security-Policy, Referrer-Policy and X-Frame-Options to protect against unwanted data leakage and embedding.
5) Operations and infrastructure
What do companies need to look at?
Check your hosting, content delivery network (CDN), DDoS protection (defence against overload attacks), server and proxy logs, the content management system (CMS) and its plugins, as well as your backup and test/staging environments.
What do you need to watch out for?
Conclude the necessary data processing agreements pursuant to Article 28 GDPR with all service providers, document locations and sub-processors, and define which log data (e.g. IP address, timestamp) is stored and for how long. Do not use production data in test systems, or anonymise it thoroughly.
What is best practice?
Create a short supplier fact sheet for each provider (data categories, purpose, storage location, legal basis) and keep raw log data only for a short time before anonymising or aggregating it. For international data transfers, use appropriate safeguards such as standard contractual clauses (SCCs) and assess possible risks with a transfer impact assessment (TIA), a risk analysis for third countries.
For US providers certified under the EU-US Data Privacy Framework, the Commission's adequacy decision applies. The EU General Court upheld it in September 2025, but an appeal is pending before the Court of Justice (C-703/25 P). Keep a fallback such as SCCs in your contracts.
6) Security (technical and organisational measures) and privacy by design/default
What do companies need to look at?
Review transport encryption such as TLS (Transport Layer Security; protects data in transit), ideally with HSTS (HTTP Strict Transport Security; enforces HTTPS), password rules, multi-factor authentication (MFA), role and permission concepts (RBAC, role-based access control) and how you handle secrets such as API keys (secret management).
What do you need to watch out for?
Secure administrator accounts with multi-factor authentication and grant only the permissions that are strictly necessary ("least privilege"). Avoid sensitive data in plain text in logs and keep an incident response plan ready (predefined steps for security incidents). Carry out patch management, vulnerability scans and, depending on the risk, penetration tests (planned attacks to test your defences).
What is best practice?
Store a security baseline as code (e.g. a standard CSP and header templates), run exercises such as phishing simulations every six months and document the results. Apply privacy by default consistently: tracking is disabled by default until consent has been given; export and deletion functions are directly accessible to users.
7) Governance, documentation and data subject rights
What do companies need to look at?
Maintain your record of processing activities (RoPA), your data processing agreements and, where necessary, agreements on joint controllership. Check whether a data protection impact assessment (DPIA) (assessment of high risks) is required and provide an easily accessible channel for data subject rights (access, erasure, objection).
What do you need to watch out for?
Make sure you can demonstrate compliance with consent logs, versioned policies and an audit trail (tracking of changes). Include backups and restores in your deletion concept and train web, marketing and support teams regularly.
What is best practice?
Keep a central evidence map that shows where each piece of evidence is stored and offer self-service functions (delete/export profile, cookie settings in the footer). Run a small audit with spot checks every quarter and document the results so that you are "records-ready" when audits take place.
FAQ (quick answers)
#1 Do I always need a cookie banner? No, only if you use non-essential cookies or trackers. Essential cookies (e.g. for the shopping cart) do not require a banner but should still be listed in your privacy notice.
#2 May I load web fonts via a CDN? It is possible, but check data flows and consent requirements. Hosting fonts locally is often more privacy-friendly.
#3 When is a data protection impact assessment required? When the processing is likely to result in a high risk to the rights and freedoms of individuals, e.g. extensive tracking/profiling or sensitive data.
#4 How long may I store server logs? As briefly as possible. Define a period (e.g. a few days to a few weeks), then anonymise or aggregate the logs and justify the duration in terms of security and troubleshooting.
Your solution for the best data protection
Trust is the foundation of every good business relationship. Strengthen your relationships with customers by leveraging our expertise in data protection. This will give your company a strong competitive advantage, allowing you to focus fully on your business.