Short-link analytics and privacy: map what each service sees
Understand redirect records, account access, destination tracking and campaign parameters, then write privacy descriptions that match the whole link journey.
“No cookies on the redirect” describes one step of a link’s journey. It doesn’t mean the destination page sets no cookies, that no network handles the visitor’s request, or that the campaign is anonymous. Map each service along the way before you decide what data to collect or how to describe it.
This guide explains what Links records and shows in its statistics. It’s a practical checklist for your own records, not legal advice.
Draw the journey before reading a dashboard
For a made-up workshop invitation, write down: the app where the message appears, the short link, the workshop page and the booking service. Add any analytics tool running on the workshop page. Each of these can have its own accounts, data collection and policies.
Keep the visitor separate from the person who manages the links. Signing in to the Links app is a different thing from opening a public short link. A statement about cookies on the redirect shouldn’t be stretched to cover the account website or every connected service.
Know what the redirect records
For each counted click, Links keeps the time, country, main language, platform, device type, browser, the site the visitor came from and which rule matched. It doesn’t store the visitor’s IP address or full browser string. The redirect sets no cookies and runs no scripts.
Those facts are about Links’ own click records. Links still has to read each visit to choose a destination and sort the click into categories, and the visit also passes through the networks that carry it. So don’t turn “Links doesn’t store IP addresses” into “no service ever sees an IP address” or “every visitor is anonymous.”
Interpret categories without identifying people
A country isn’t a verified home address or nationality. A browser language isn’t a confirmed personal preference. The site a visitor came from isn’t their browsing history; when an app or browser doesn’t pass it on, the click shows as direct.
Links shows totals and breakdowns, not a list of individual clicks. The breakdowns show the top categories for each period. The 7-, 30- and 90-day views don’t tell you how long the underlying data is kept.
Links leaves out the bots and link previews it recognizes. The remaining clicks still aren’t guaranteed to be different people, because one person opening the link twice counts twice. Use the analytics guide when you compare click counts with visits or bookings on the destination.
Keep campaign labels free of personal data
Name placements and campaigns, not people. For example, a public invitation might use utm_source=newsletter and utm_campaign=workshop_autumn. Don’t put someone’s email, membership number or a private note into a public web address just to recognize them later.
Check the full saved destination before sharing. An address copied while you were signed in somewhere may include a temporary access code that has nothing to do with the campaign. Get the host’s proper public sharing address instead. An unlisted short link doesn’t make its destination private; use the destination’s own access controls for restricted material.
Review the destination and reporting access
Go through this short list with the page and account owners:
| Part | Question to answer |
|---|---|
| Messaging app | Does it fetch a preview or rewrite the address? |
| Short link | Which categories and counts does it keep? |
| Destination page | Which analytics, cookies or embedded services run there? |
| Booking service | What registration details does the attendee enter? |
| Team reporting | Who needs to see statistics, and who can change destinations? |
Answer from the real settings and each service’s current documentation. Removing analytics from the destination doesn’t change data that’s already stored elsewhere. Give each colleague only the access their task needs; the team management guide explains how seeing statistics differs from editing links.
Write a narrow statement and maintain it
A useful internal note might say: “We use Links to count visits through our short links, and we check completed registrations in the booking system.” Add checked details about the services your links actually lead to. Avoid broad promises like “tracking-free everywhere” based only on the short link.
Keep the date, owners and open questions together. Look at the list again when you add an embedded form, change providers or change who can see reports. Ask each service directly how long it keeps data and how to delete it, rather than guessing from the length of a dashboard view. Links gives you privacy-first click statistics; to understand the whole journey, check every part of it.