Skip to content
Glossary · Privacy

GDPR

General Data Protection Regulation

How it works

The GDPR has applied across the EU since May 25, 2018. It kicks in as soon as data can be linked to a person. That's not only names, email addresses and phone numbers: IP addresses, cookie IDs and click IDs usually count as personal data too. Every processing needs a legal basis from Art. 6. In marketing, two come up most:

  • Consent (Art. 6(1)(a)): the person agrees freely, informed and actively, for example in the cookie banner, and can withdraw at any time.
  • Legitimate interest (Art. 6(1)(f)): your interest is weighed against the interests of the person.

Storing and reading information on the device, such as cookies and localStorage, is covered by extra rules from the ePrivacy Directive. Germany has them in § 25 TDDDG (formerly TTDSG), Austria in § 165 TKG 2021. Anything not strictly needed for the service generally requires consent there.

Why it matters

Tracking almost always processes personal data, in the browser and on the server. A conversion API also sends data about people to ad platforms, just by a different route. Violations can mean fines of up to €20 million or 4% of worldwide annual turnover, whichever is higher. Which legal basis covers which tracking is for you and your data protection advisor to settle, and the tracking then has to follow that decision. TSO has three privacy modes per project for this and reads the decision of common cookie banners automatically.

Example

A coaching business runs Meta ads to a landing page with a form. Together with its data protection advisor it decided: before consent in the banner, tracking sets no cookies and only counts visits anonymously. If a visitor agrees, they are recognized, and their later inquiry goes to Meta with a hashed email address. If they decline, the inquiry still reaches the coach, but Meta learns nothing about them.

Common mistakes

  • Treating hashing as anonymization: a hashed email address is pseudonymized, not anonymous. It is still personal data, and the GDPR still applies.
  • Thinking only about cookies: sending data from the server to ad platforms needs a legal basis too. In TSO, IP address and user agent go to the conversion APIs by default even without consent; you can switch this off per destination. Agree on this setting with your data protection advisor.
  • Expecting a tool to make you "GDPR compliant": compliance isn't a property of software but of your processing as a whole: legal basis, privacy policy, contracts and settings.
  • Forgetting the DPA: if a service provider processes data on your behalf, Art. 28 requires a contract with them.

How TSO handles it

Frequently asked questions

Does the GDPR apply to companies outside the EU?

Yes, if they offer goods or services to people in the EU or monitor their behavior in the EU, for example through tracking (Art. 3(2) GDPR).

Articles on this topic

Related terms

From the term to clean measurement.

TSO connects ads with leads, deals and revenue and reports them back to the ad platforms.