GDPR Requirements: GDPR vs ePrivacy Directive for European Privacy Compliance

Use the GDPR and the ePrivacy Directive together, not as substitutes. The GDPR governs how personal data is collected, used, stored, and shared. The ePrivacy Directive governs the privacy of electronic communications, including cookies, tracking pixels, direct marketing, and confidentiality of communications.

TLDR: If your company serves users in Europe, GDPR compliance alone is not enough. A SaaS business that uses analytics cookies, email campaigns, and account profiling may need a GDPR lawful basis for processing, plus ePrivacy consent for non-essential cookies and certain marketing messages. For example, if 40% of website visitors reject analytics cookies, you must respect that choice and avoid loading those trackers anyway. Treat GDPR as the broad data protection rulebook and ePrivacy as the specialist rulebook for online communications and tracking.

GDPR vs ePrivacy Directive: the core difference

The General Data Protection Regulation, or GDPR, applies when an organisation processes personal data. That includes names, email addresses, customer IDs, IP addresses, device identifiers, location data, and many analytics records if they can identify or single out a person.

The ePrivacy Directive applies to electronic communications. It covers the confidentiality of communications, cookies, tracking technologies, metadata, and electronic marketing. It is sometimes called the “cookie law,” but that label is too narrow. It also affects SMS marketing, email marketing, call rules, and telecom-related privacy.

The catch is that both laws often apply to the same activity. If a website places an advertising cookie on a user’s device, ePrivacy may require prior consent to store or access that cookie. The GDPR then controls what happens to any personal data collected through it.

How the GDPR works

The GDPR is an EU regulation. This means it applies directly across the EU, with some national differences in areas where member states have discretion. It also applies outside the EU when a company offers goods or services to people in the EU or monitors their behaviour.

Under the GDPR, organisations must have a valid lawful basis for processing personal data. The main bases are:

  • Consent, where the individual gives a clear and informed choice.
  • Contract, where processing is needed to provide a service or fulfil an agreement.
  • Legal obligation, where the law requires the processing.
  • Vital interests, usually in emergency or life-critical cases.
  • Public task, mainly for public authorities.
  • Legitimate interests, where the organisation’s interest is not overridden by the person’s rights.

The GDPR also requires transparency. Privacy notices must explain what data is collected, why it is used, who receives it, how long it is kept, and what rights users have. These rights include access, deletion, correction, objection, restriction, portability, and withdrawal of consent.

How the ePrivacy Directive works

The ePrivacy Directive is different. It is a directive, not a regulation. EU member states had to turn it into national law. That means cookie and marketing rules are not perfectly identical across Europe. This can be annoying for compliance teams. A cookie banner that looks fine in one country may need changes in another.

For websites and apps, the most visible ePrivacy rule is simple: storing information on a user’s device, or accessing information from it, usually needs consent unless the technology is strictly necessary.

Common examples that often need prior consent include:

  • Analytics cookies that are not strictly necessary.
  • Advertising cookies and retargeting pixels.
  • Social media tracking plug-ins.
  • Fingerprinting scripts.
  • Heatmap and session replay tools, depending on setup and local law.

Strictly necessary cookies may not need consent. These can include cookies used for login sessions, shopping cart functions, security, fraud prevention, and user-requested language settings. Even then, the organisation should explain them in a cookie notice.

Consent under both rules

Consent is where GDPR and ePrivacy meet most often. Under the GDPR, valid consent must be freely given, specific, informed, and unambiguous. For sensitive data, it must be explicit. Users must also be able to withdraw consent as easily as they gave it.

Under ePrivacy, consent for cookies and similar technologies must meet the GDPR standard. This means pre-ticked boxes are not acceptable. “By continuing to browse, you agree” is risky and often rejected by regulators. A banner should offer real choice, including a clear reject option where consent is requested.

Honestly, it feels like some consent tools are built to pass a screenshot review, not to respect users. If rejecting cookies takes four clicks while accepting takes one, regulators may see that as pressure. Good design matters because consent is not valid if the interface pushes people toward “accept.”

Email marketing and electronic communications

Email marketing sits at the intersection of GDPR and ePrivacy. The GDPR applies because email addresses often identify individuals. The ePrivacy rules apply because the message is an electronic communication.

Many EU countries require prior consent for direct marketing emails to individuals. Some allow a “soft opt-in” for existing customers if all conditions are met. Typically, the recipient must have bought or shown interest in a similar product, received a clear chance to object at collection, and received an easy unsubscribe option in every message.

Business-to-business marketing rules vary by country. Some states are stricter than others. This is why a single EU-wide marketing process should be checked against the countries being targeted.

Practical compliance checklist

A serious European privacy programme should cover both laws. Start with the highest-risk public-facing tools, then work inward.

  1. Map your data and trackers. List cookies, pixels, SDKs, analytics tools, marketing platforms, and session recording tools.
  2. Classify each technology. Decide whether it is strictly necessary, analytics, functionality, advertising, security, or marketing.
  3. Identify the legal basis. Use GDPR lawful bases for personal data processing and ePrivacy consent rules for device access.
  4. Fix consent flows. Use clear buttons, equal visibility for accept and reject choices, and no preselected optional cookies.
  5. Keep proof. Store consent logs, banner versions, cookie scans, privacy notices, and vendor assessments.
  6. Review vendors. Check processors, sub-processors, international transfers, retention terms, and security measures.
  7. Update notices. Align privacy notices, cookie notices, and marketing notices with real practices.
  8. Test regularly. Run scans after releases, tag changes, marketing campaigns, and new plug-ins.

Common mistakes

One common mistake is assuming a privacy policy fixes cookie compliance. It does not. If non-essential trackers load before consent, a polished policy will not solve the problem.

Another mistake is relying on legitimate interests for advertising cookies. Even if legitimate interests might apply to later processing under the GDPR in limited cases, ePrivacy may still require consent before placing or reading the cookie.

A third mistake is treating anonymised analytics too casually. True anonymisation is hard. If data can still single out a device or user, regulators may treat it as personal data. Pseudonymised data remains personal data under the GDPR.

Enforcement and risk

GDPR penalties can reach €20 million or 4% of annual worldwide turnover, whichever is higher. ePrivacy penalties depend on national law, but they can still be painful. Regulators across Europe have also taken action against poor cookie banners, unlawful tracking, and weak consent design.

The reputational risk can be just as damaging. Users notice when a site ignores their choices. Business customers also ask sharper privacy questions during procurement. A weak cookie setup can delay sales, trigger contract objections, or create problems during due diligence.

What to prioritise first

Focus first on visible, high-volume practices. Audit your website and app trackers. Fix cookie consent. Review marketing lists. Confirm unsubscribe handling. Check that analytics and advertising scripts do not fire before consent when consent is required.

Then move to governance. Maintain processing records. Train marketing and product teams. Set rules for adding new tags. Review vendor contracts. Document decisions. This evidence matters when a regulator, customer, or auditor asks how your privacy controls work.

The safest view is simple: the GDPR protects personal data, while the ePrivacy Directive protects private electronic communications and devices. Most digital businesses need both. If you build your programme around that split, European privacy compliance becomes far more manageable and far less risky.