GDPR & Link Tracking: What Marketers Need to Know
GDPR link tracking in 2026: what data shorteners collect, when IP addresses count as personal data, the legal basis you need, and a 10-point checklist.
Nobody loves a privacy law audit. But if your business sends links to people in the EU, EEA, or UK (even accidentally, through a tweet or a public newsletter), your link shortener has been quietly processing their personal data every time they clicked. GDPR link tracking is not optional once you're in that situation. It just means somebody on your team should know what the shortener logs, under what legal basis, and for how long.
The honest version: most of this is manageable. The compliance posture of a decent shortener in 2026 is closer to "configure correctly, keep records" than "lawyer up." But a few of the questions are genuinely load-bearing, and getting them wrong is where supervisory authorities tend to issue fines.
This guide covers what GDPR link tracking actually means, which fields a shortener collects, when those fields count as personal data, the two legal bases that fit (and when each applies), how ePrivacy sits on top of GDPR for cookies, what IP hashing does and doesn't change, a 10-point compliance checklist, data subject rights you'll have to honor, and the retention windows that make sense. Nothing here is legal advice. For a real compliance decision, run the specifics past a lawyer qualified in your jurisdiction.
GDPR link tracking is the processing of personal data (including IP addresses, device identifiers, approximate location, referrer, and user-agent) that happens when someone clicks a shortened URL. Under the EU General Data Protection Regulation, those click fields can qualify as personal data because an IP address or device fingerprint can indirectly identify a natural person. A compliant setup requires a lawful basis under Article 6 (legitimate interests for security logging, consent for cross-site profiling), a privacy notice that names the shortener, a defined retention period, and support for data subject rights.
GDPR link tracking is the collection of click data from shortened URLs in a way that complies with the EU General Data Protection Regulation. It requires a lawful basis under Article 6, a lawful ePrivacy basis for any cookies dropped during the redirect, a privacy notice that names the shortener as a processor, a documented retention period, and mechanisms for access, erasure, and portability requests.
Table of Contents
- What GDPR Says About Link Tracking
- The Data a URL Shortener Actually Collects
- When Click Data Becomes Personal Data
- Legitimate Interests vs Consent: Which Legal Basis Fits
- ePrivacy and the Cookie Question
- IP Hashing: What It Fixes and What It Doesn't
- Data Subject Rights That Apply to Click Data
- Data Retention: How Long Can You Keep Clicks?
- 10-Point GDPR Link Tracking Compliance Checklist
- How U2L AI Handles the Privacy Plumbing
- Frequently Asked Questions
What GDPR Says About Link Tracking
GDPR covers link tracking because a shortener that logs click data from people in the EU is processing personal data - even though the regulation never mentions URL shorteners by name. It doesn't need to. The regulation covers "the processing of personal data" by any controller or processor established in the EU, or by any controller or processor outside the EU that offers goods or services to, or monitors the behavior of, people in the EU. A link shortener that logs an IP address every time someone in Berlin clicks a link fits comfortably inside that scope.
That means the standard GDPR obligations attach: identify a lawful basis, inform the data subject, respect their rights, limit retention, keep records, pick processors who meet the same bar, and (for cross-border transfers) use the right transfer mechanism. The novel bit for link tracking is not the obligations. It's figuring out which ones hit which fields.
The simplest frame: your shortener is typically a data processor acting for you (the controller). You decide why clicks are being logged and what happens to the data. The shortener runs the pipes. That relationship calls for a data processing agreement (DPA) between you and the shortener under Article 28. The European Data Protection Board publishes guidelines on controller and processor roles that walk through the distinction.
The Data a URL Shortener Actually Collects
A URL shortener typically logs some mix of the fields below on every click. Not every service collects every field, so read the privacy policy rather than assuming:
- IP address (full or truncated), used to resolve approximate location and detect abuse
- Approximate location (country, region, sometimes city) derived from the IP
- User agent string, which reveals browser, operating system, version, and often device model
- Referrer header, showing where the click originated
- Timestamp of the click
- Device type (desktop, mobile, tablet) and operating system, inferred from the user agent
- Short link slug and destination URL that was resolved
- Unique visitor identifier, if the service distinguishes repeat clicks (often a hash or a cookie)
- Click source identifiers (UTM parameters, custom tags) attached to the destination
- Retargeting pixel firings, if the owner enabled retargeting on that link
That is the raw material. Everything downstream (dashboards, click-timeline charts, geo heatmaps, device breakdowns) is aggregation on top of these fields. Our breakdown of the mechanics of a short link click walks through where in the redirect flow each signal is read, and our link tracking pillar guide covers how the same signals get used downstream.
When Click Data Becomes Personal Data
Click data becomes personal data when it can identify a person directly or indirectly - and in the EU and UK, an IP address usually can. That is the question that trips most teams up.
The Court of Justice of the European Union held in Breyer v Germany (Case C-582/14, 2016) that a dynamic IP address is personal data in the hands of a website operator when the operator has legal means to obtain the subscriber's identity from the ISP, even if the operator never actually does that. That is the controlling test for most click-level logging, and European regulators broadly treat IP addresses as personal data by default.
The implication for link tracking: the moment your shortener stores the IP of a clicker in the EU, you are processing personal data, and GDPR applies in full. The same logic extends to user-agent strings when they are detailed enough to fingerprint a specific device, and to any cookie or ID that lets you tie clicks to the same person across sessions.
Two things narrow this. First, truly anonymized data (where re-identification is not reasonably likely, taking into account all the means reasonably likely to be used) falls outside the GDPR, per Recital 26. Second, aggregate statistics (how many clicks from Germany on Tuesday) are not personal data as long as identifiable records aren't kept underneath them. Honest aggregation is a legitimate compliance strategy - arguably the strongest one available.
Legitimate Interests vs Consent: Which Legal Basis Fits
Link tracking usually rests on one of two of the six lawful bases in Article 6: legitimate interests (Article 6(1)(f)) and consent (Article 6(1)(a)).
The practical split most data protection authorities seem comfortable with:
Legitimate interests covers:
- Processing an IP for abuse detection, bot filtering, and link safety (network and information security is called out as a legitimate interest in Recital 49)
- Keeping an aggregate record of clicks for operational reasons (how many clicks did this campaign get?)
- Retaining raw logs for a short, defined period to investigate security incidents
Consent covers:
- Dropping a persistent identifier (cookie, local-storage ID, device fingerprint) to profile the clicker across sessions or sites
- Firing retargeting pixels, Meta Conversions API events, or any marketing identifier
- Enriching click data with third-party information to build an attribution picture
- Any cross-context behavioral advertising use
Legitimate interests is not a free pass. It requires a documented three-part test: a specific purpose, the processing being necessary to achieve it, and a balancing exercise showing your interest isn't overridden by the data subject's rights. Most teams write this up as a short memo (the UK ICO calls it a legitimate interests assessment), review it annually, and reference it from the privacy notice.
Consent, when you need it, has to be freely given, specific, informed, and unambiguous. Pre-checked boxes don't count. "By using this site you agree" doesn't count. Burying it on page six of the terms doesn't count. And the clicker has to be able to withdraw as easily as they consented.
ePrivacy and the Cookie Question
The ePrivacy rules decide whether a shortener may store or read anything on the clicker's device, while GDPR governs what happens to the data afterward. The ePrivacy Directive (implemented differently in each EU member state) covers cookies, local storage, and anything else dropped during the redirect.
ePrivacy's rule is tighter than GDPR's. Non-essential cookies need prior consent, and legitimate interests is not available as a basis for cookies that aren't strictly necessary. The practical categories:
- Strictly necessary cookies (session identifiers needed for the service the user requested, abuse-prevention tokens). No consent required, but you should still name them in your privacy notice.
- Analytics and performance cookies (unique-visitor tracking, click deduplication). Consent is generally required in the EU, though some national regulators allow narrow exemptions for first-party audience measurement with strict safeguards - France's CNIL sets out its conditions in its guidance on analytics tools.
- Marketing / retargeting cookies and pixels. Consent required, always.
For a shortener, the clean path is a redirect flow that does not drop a cookie at all unless the owner has turned on a feature that requires one. Our cookieless tracking guide covers the techniques that let you keep most of the analytics signal without touching the user's device.
IP Hashing: What It Fixes and What It Doesn't
IP hashing reduces risk but doesn't take click data outside the GDPR. A common privacy posture for shorteners is to hash the IP address before storage: SHA-256 the IP (ideally with a rotating salt), store the hash for unique-visitor deduplication, and throw the raw IP away.
What that accomplishes: you can still count distinct clickers within a time window, you can still spot simple abuse patterns, and you can still aggregate by country if you resolved the location before hashing. What you can no longer do easily is recover the original IP, which shrinks a few attack surfaces (a data breach, an overly broad legal request, employee misuse).
What it does not accomplish: a GDPR exemption. Hashing an IP is pseudonymization, not anonymization, and the IPv4 address space is small enough that unsalted hashes can be reversed by brute force. Pseudonymized data is still personal data - Article 4(5) defines pseudonymization, and Recital 26 is explicit that pseudonymized data remains personal data. The regulation treats pseudonymization as a privacy-enhancing technique with real benefits, but it doesn't take the data outside the regulation.
There is a stronger option than hashing: don't keep the IP at all. If you count unique visitors in memory and store only the resulting totals, there is no per-person record left to protect, request, or leak. That's the design we chose, and we describe it below.
Data Subject Rights That Apply to Click Data
Any EU, EEA, or UK resident whose identifiable data your shortener keeps has rights over it. The relevant ones for link tracking:
Right of access (Article 15). They can ask what data you hold about them. For click data this is awkward, because you usually can't link a specific click to a specific person without extra information from them (an IP, a timestamp window, a device). You're expected to make a reasonable effort based on the identifiers they can give you.
Right to erasure (Article 17). They can ask you to delete their data. For click-level logs this means deleting records that match an identifier they provide, or confirming (truthfully) that no record identifying them is retained.
Right to object (Article 21). If your lawful basis is legitimate interests, they can object. You then have to stop unless you can demonstrate compelling grounds that override their interests. For security processing, "we need it to keep the service safe" is a strong argument; "we use it for marketing enrichment" is a weak one.
Right to portability (Article 20). Narrower, and applies only where processing is based on consent or contract.
Mechanically, you handle these the same way you handle them for any system: a documented request process, identity verification (careful not to over-collect data in the name of verification), a response within one month as Article 12 requires, and an audit trail. The less identifiable click data your shortener keeps, the shorter that work gets.
Data Retention: How Long Can You Keep Clicks?
GDPR doesn't set a fixed retention period for click data; it requires that personal data not be kept "for longer than is necessary." A few common patterns:
- Raw click logs with IP: 30-90 days, long enough for debugging and incident response, short enough to limit breach exposure
- Hashed or pseudonymized unique-visitor data: 6-24 months for most marketing purposes, longer only with a defensible reason
- Aggregate counts (clicks per day per campaign, with no identifiable records underneath): can usually be kept for as long as they're useful for business reporting
The right number depends on what the data actually gets used for. If your campaign reporting horizon is 12 months, retaining raw logs for five years is hard to defend. If your fraud investigations occasionally go back six months, 30 days is probably too short. Pick a window, write it in the privacy notice, and have your tools enforce it automatically.
On U2L AI, how far back your analytics dashboard goes depends on your plan, with longer history on higher tiers. Because what we keep is aggregate counts rather than per-person click logs, a longer analytics window doesn't mean a longer trail of personal data. Check u2l.ai/pricing for the current history on each plan.
10-Point GDPR Link Tracking Compliance Checklist
This 10-point checklist covers what most teams need in place for GDPR-compliant link tracking:
- Put a DPA in place with your shortener. Article 28 expects a processor agreement. Ask your provider how it handles one.
- Name link tracking in your privacy notice. Call out the shortener, the data categories (IP, device, location, referrer), the lawful basis, and the retention window.
- Document your legitimate interests assessment. A one-page memo covering purpose, necessity, and the balancing test. Review it annually.
- Separate cookies from redirects. Make sure the shortener doesn't drop a non-essential cookie by default. Turn on retargeting pixels only where you have consent in place.
- Minimize IPs at rest. Prefer a shortener that doesn't store visitor IPs at all; failing that, one that pseudonymizes them with a salted hash before storage. Ask for the specific mechanism.
- Pick a retention window and enforce it. 30-90 days for raw logs is reasonable for most purposes. Longer windows need written justification.
- Build a data subject request flow. Decide who handles requests, how you verify identity, how you locate records, and how you log the resolution.
- Check transfer mechanisms for non-EU providers. If your shortener processes data outside the EU, check the transfer mechanism - often Standard Contractual Clauses plus a transfer impact assessment.
- Handle UTM parameters carefully. If a UTM field encodes identifying information (customer IDs, email hashes), that lands in your analytics. Keep UTM parameters generic.
- Review annually. Privacy rules and regulator guidance keep moving, and new EU laws like the AI Act add obligations around data use. Treat compliance as a yearly audit, not a one-time setup.
Our first-party data guide and cookieless tracking guide cover the measurement side of this (how to keep useful analytics while staying inside the lines). This checklist covers the paperwork and plumbing.
How U2L AI Handles the Privacy Plumbing
U2L AI keeps link analytics as aggregates and never stores visitor IP addresses. Full disclosure: U2L AI is our product, so this section is us describing our own setup - specifically, because specific claims are what you need for an audit.
No stored visitor IPs, hashed or otherwise. When someone clicks a link, the IP is used in memory at the edge to count unique visitors and is then dropped. Approximate location comes from edge geolocation at click time. What we store is daily totals per link - clicks, unique visitors, and breakdowns by country, city, device, browser, OS, referrer, and language - not a per-person click log. Our privacy policy states it plainly: we do not store the full IP address of link visitors.
No cookies on redirects. Our redirects don't set cookies on the clicker's device, so the ePrivacy cookie question doesn't arise for ordinary click tracking. If you turn on retargeting pixels for a link, those pixels are your marketing tags and need your consent basis - they're switched on per link, and they never fire for bots or link-preview crawlers.
Safety checks don't touch clicker data. Our link safety screening (Google Safe Browsing, URL scanning, and moderation, covered in our short link security deep dive) runs on the destination URL when a link is created or edited, not on the people who click it.
Simpler data subject requests. Because there's no stored per-person click history, a clicker's access or erasure request usually comes down to confirming that no record identifying them is kept. Your account data and links are yours to manage from the dashboard or the public REST API.
If you're building a GDPR-aware stack from the ground up, you can start on the free plan and see exactly what gets recorded. Our features page has the full breakdown.
Frequently Asked Questions
Is link tracking GDPR compliant?
Link tracking can be fully GDPR compliant when you have a lawful basis (usually legitimate interests for security logging, consent for marketing identifiers), a privacy notice naming the shortener and the data processed, a processor agreement, and a defined retention window. The regulation doesn't ban click analytics; it regulates how you collect and keep it.
Do URL shorteners violate GDPR?
URL shorteners don't inherently violate GDPR. Compliance depends on how the specific service collects, stores, and retains click data, and on whether you (as the controller) have the right paperwork and privacy notice in place. A shortener that minimizes stored IPs, keeps aggregates rather than per-person logs, and avoids cookies on redirects makes compliance much easier.
Is an IP address personal data under GDPR?
Yes, in most practical cases. The Court of Justice of the European Union held in Breyer v Germany (2016) that a dynamic IP address is personal data when the operator has legal means to identify the subscriber. European regulators treat IPs as personal data by default, and the main exception is truly anonymized aggregate data where re-identification isn't reasonably likely.
Do I need consent to track clicks on short links?
It depends on what you're tracking. For security logging and basic click counts, legitimate interests under Article 6(1)(f) usually suffices, with the required balancing test. For non-essential cookies, retargeting pixels, or cross-site profiling, prior consent is required under the ePrivacy rules and GDPR.
What is a Data Processing Agreement (DPA)?
A DPA is a contract between a data controller (you) and a data processor (your shortener) that spells out the processor's obligations under GDPR Article 28: processing only on documented instructions, confidentiality, security measures, sub-processor rules, assistance with data subject requests, and deletion or return at the end of the contract. Article 28 expects one whenever a processor handles personal data on your behalf.
How long can I store click data under GDPR?
The regulation requires that personal data not be kept longer than necessary. Common patterns are raw logs with identifiable fields for 30-90 days, pseudonymized unique-visitor data for 6-24 months, and anonymized aggregate counts for as long as they're useful. The right window is whatever matches your documented business purpose, written in the privacy notice.
Does GDPR apply if my business is outside the EU?
It can. GDPR applies to any controller or processor that offers goods or services to people in the EU or monitors their behavior, regardless of where the business is based. If you run marketing campaigns that reach European clickers (even accidentally through social media or a public newsletter), the regulation likely applies to that processing.
What happens if someone asks me to delete their click data?
You generally have one month to respond under Article 12. Verify the request without over-collecting data, find any matching records using identifiers they can give you, delete them, and send written confirmation. If your shortener keeps only aggregate counts, the answer is often simply that no record identifying them exists.
Privacy That's Boring in the Best Way
A GDPR-aware link tracking setup is boring in the best way: a processor agreement, a privacy notice that names the shortener, minimal identifiable data at rest, a sensible retention window, and a documented request flow. None of it is exotic, but all of it matters when a supervisory authority asks. Pick a shortener that keeps as little personal data as possible by default, and most of the hard questions answer themselves. Try U2L AI free and build on links that never store visitor IPs and never set cookies on the redirect.