Do QR Codes Track You? How QR Code Analytics Actually Work
Some QR codes can track exactly when and where they were scanned. Others are physically incapable of tracking anything at all. Which one you're dealing with has nothing to do with how the code looks — it comes down entirely to whether scanning it involves a server sitting in between you and the destination.
The mechanism, plainly
A static QR code encodes its destination directly in the pattern — a URL, a phone number, a WiFi network's credentials. When a camera scans it, the phone decodes that string locally and acts on it (opens the URL, dials the number, joins the network). No network request to any third party happens as part of the decoding itself — the QR code never touches a server, because there's no server involved in reading it. Anyone claiming a static code encoding a plain URL is "tracking" you is describing the destination website's own analytics (the same page-view logging any website does for any visitor, QR-driven or not), not something the code itself is doing.
A dynamic QR code works differently by design: it encodes a short redirect link pointing at a tracking service's server, which logs the scan — timestamp, approximate location from IP address, device type — and then forwards you to the real destination. This is the entire point of dynamic codes for the businesses that use them: knowing how many times a specific poster or menu got scanned, broken down by day or location, in a way a plain static URL can't provide on its own.
Why this is a genuine, deliberate tradeoff
Neither approach is objectively "better" — they're built for different priorities. If you're running a marketing campaign across multiple print locations and want to know which one actually drove scans, dynamic tracking gives you real data a static code can't. If you're printing something you need to keep working indefinitely with zero ongoing dependency on a third party's server staying online and your subscription staying current, static is the only option that guarantees that — see static vs. dynamic QR codes for the fuller breakdown of that decision.
Where it gets genuinely worth being skeptical is a code that claims to be "just a URL" but actually routes through an unfamiliar shortener domain first — that's a dynamic code wearing static clothing, and it's tracking scans whether or not that's disclosed anywhere near the code itself.
What QRSen's codes do
Every code the generator produces is static: the destination is encoded directly, generated entirely in your browser, with nothing ever sent to a server as part of creating or scanning the code. There's no scan log to view because there's no infrastructure logging anything — which is also exactly why a code generated here has no expiry risk tied to a service shutting down (see do QR codes expire for that side of the same underlying tradeoff).
The short version
Whether a QR code "tracks" anyone comes down to one structural fact: does scanning it involve a server in between the scan and the destination, or not. Static codes don't and can't; dynamic codes do, by design, because that's the feature they're built to offer. Knowing which kind you're looking at tells you everything about its tracking behavior — nothing else about the code matters.