The QR Code You Created
Is Tracking Everyone
Who Trusts You.

QR code surveillance is not a myth. Free QR generators create tracking codes that log GPS, device, and scan time for every person who scans them — without their knowledge, their consent, or any way to opt out.

🔴
What happened when someone scanned your QR code Before the destination even loaded, a server you do not control logged their exact location, phone model, operating system, browser version, and precise timestamp. That data was not yours. It was not theirs. It belongs to a platform you used for free — and “free” is never actually free.
100% Free QR platforms track scanners
6+ Data points captured per scan
$0 Cost for a private static QR code
↓ Scroll
QR code surveillance trap — how free QR generators track every scanner without consent

Every scan · Every location · Every device · All logged without the scanner ever knowing

01 · The Misunderstood Risk

You Think the Problem Is Your Data

When most people think about QR code privacy, they think about what happens to them when they scan someone else’s code. They worry about malicious links, phishing sites, data harvested from the destination. That is a reasonable concern. But it is not the primary privacy violation happening with QR codes today.

The real problem is reversed. When you create a QR code with a free generator, you are not creating a link. You are creating a QR code surveillance endpoint that tracks everyone who trusts you enough to scan it.

You are not the victim in this scenario. You are, unknowingly, the agent of QR code surveillance. The platform used your action — creating a code — to insert a tracker into the hands of everyone connected to your business, your event, your restaurant, your life. And because they agreed to their terms of service with you, not with the scanners, the entire operation is completely legal.

The people who scan your QR code trust you. They do not know a third-party surveillance system is recording their location. [EFF Privacy Research] You did not intend this. But intention does not change what the infrastructure does — and the infrastructure was designed to extract data, not to connect people.

The Trap You Set Without Knowing

You printed QR codes for your restaurant menu during COVID. Every customer who scanned it to see what was for lunch became a subject of QR code surveillance — GPS location, device model, operating system, browser type, and exact scan timestamp all logged to a server you never controlled.

You put a QR code on your business card linking to your portfolio. Every person at that networking event who scanned it became a target of QR code surveillance — location, device characteristics, and whether they scanned again later — all recorded in a database you do not own and cannot access without upgrading to a paid tier.

You created a QR code for your event flyer. Every attendee who scanned it to RSVP became a data point in a QR code surveillance system they never knew existed. If they scanned it a second time to check details later, that was logged separately, building a behavioral pattern profile without their knowledge.

You did not intend to surveil these people. But you did. And you did it because the free tool made dynamic tracking codes the default — and never explained what that meant.

02 · How The Surveillance Works

QR Code Surveillance Explained: Dynamic vs Static QR Codes

The QR code format itself is an open standard — ISO/IEC 18004 — and it is completely neutral. A QR code is just a mathematical encoding of text. QR code surveillance is not a feature of the QR format itself. It is a feature of the business model layered on top by free platforms that profit from data collection.

Understanding the difference between dynamic and static codes is the foundational knowledge that most free QR generators have a financial incentive not to teach you clearly. This is how QR code surveillance stays invisible to the people it affects most.

▲ Dynamic QR Code — QR Code Surveillance by Default
  • Redirects through the company’s server first
  • Logs GPS coordinates for every scan
  • Records full device fingerprint
  • Captures OS version and browser type
  • Timestamps every individual scan
  • Builds multi-scan behavioral profiles
  • Code dies if the company shuts down
  • Data sold to advertising networks
  • You cannot delete the collected data
✓ Static QR Code — How It Should Work
  • Destination encoded directly in the pattern
  • No server redirect of any kind
  • Zero tracking architecturally possible
  • No data logged anywhere
  • No analytics dashboard to sell
  • Works completely offline
  • Never expires — permanent by design
  • Nothing to sell to anyone
  • Scanner interacts with your destination directly

The mechanism of QR code surveillance is simple. A dynamic QR code does not contain your final destination. It contains a short redirect URL owned by the QR platform — something like bit.ly/a8f3k2 or qr.io/x7h2p. When someone scans the code, their device connects to that platform’s server first. The server logs everything it can about the scan, then redirects to your actual destination. The entire transaction takes milliseconds. The scanner never notices. But the log entry is permanent.

A static QR code contains the final destination directly in its pattern. Scan it, and your phone goes straight there. No server. No redirect. No log entry. The QR code is pure geometry — a mathematical encoding of text. There is nothing to track because there is no middleman. The surveillance is not technically possible when the code is static.

Real Example · COVID Restaurant Menus
During the COVID-19 pandemic, restaurants worldwide replaced physical menus with QR codes to reduce surface contact. Most used free generators like Bitly or QR Code Monkey, which create dynamic codes by default. Every customer who scanned the menu QR had their location logged. The restaurant never saw this data — the QR platform kept it. Later analysis revealed that some platforms sold aggregated location data showing foot traffic patterns at specific restaurant addresses to commercial real estate analytics firms and advertising networks. The restaurants had no idea they were running a QR code surveillance operation. The customers had no idea their lunch choice was being logged.
Dynamic QR code data flow — what gets logged when someone scans your tracking QR code

Data flow of a dynamic QR scan · GPS · Device fingerprint · OS · Browser · Timestamp — all before the redirect completes

03 · What Gets Logged

The QR Code Surveillance Data Captured From Every Single Scan

When someone scans a dynamic QR code, the tracking server captures a detailed technical snapshot before the redirect even completes. This happens in milliseconds. The scanner sees nothing unusual — the link just works. But on the backend, a permanent database entry is created containing at minimum the following data points.

01
GPS Coordinates
Exact latitude and longitude of the device at scan time. Accurate to within a few meters if location services are enabled. Even if location is disabled, IP geolocation provides city-level precision. This is the most location-specific element of QR code surveillance — revealing where the person was when they scanned your code, their home, their workplace, a specific store, a specific street corner. When this data accumulates across multiple scans from the same device, it builds a detailed map of that person’s regular movements.
02
Device Fingerprint
Screen resolution, installed fonts, GPU rendering signature, browser plugins, timezone, language settings, and dozens of other passive signals assembled into a near-unique identifier. This fingerprint is the device-tracking layer of QR code surveillance — it can follow the same device across multiple scans and across unrelated websites even if the person never logs in, never accepts cookies, and never provides any personal information. The fingerprint is assembled from data the browser exposes by default.
03
Operating System and Browser
iOS or Android. Safari, Chrome, or Firefox. Specific version numbers down to the patch. Each data point feeds the QR code surveillance profile being built on the scanner. This metadata builds profiles of user demographics and device upgrade cycles. Combined with location data, it can infer socioeconomic status — newer iPhones concentrated in affluent neighborhoods, older Androids in lower-income markets. This demographic inference is valuable to insurers, lenders, and targeted advertisers.
04
Scan Timestamp
Exact date and time down to the second. QR code surveillance timestamps every individual scan separately. This builds a behavioral timeline. Scanned at 8 AM from a residential address, 12 PM from an office district, 7 PM from a shopping area — a daily movement pattern emerges within days. Over weeks, commute routes, recurring locations, and behavioral routines become visible in the data.
05
Referrer Data
If the QR code appeared in a digital context — embedded in a PDF, shared in a messaging app, posted in social media — the source is logged. This creates a network map of how your content travels and who shares it. This referrer graph is particularly valuable for understanding content virality and is sold to marketing analytics companies as distribution intelligence.
06
Repeat Scan Count Per Device
The platform knows if the same device fingerprint scanned your code more than once. High repeat scan rates indicate strong engagement or behavioral uncertainty. This metric is packaged as engagement analytics and sold to marketing firms. More importantly for privacy: this repeat-scan profiling is the most persistent form of QR code surveillance — building a longitudinal behavioral profile of specific individuals without their knowledge.
6+ Data points captured before the page even loads
0ms Time the scanner has to consent or refuse
Static QR codes capture exactly zero data points
04 · The Legal Trap

QR Code Surveillance Is Legal. You Made It So.

When you created that QR code, you agreed to the platform’s Terms of Service. Somewhere in those terms — typically buried in Section 8 or 12 under “Analytics” or “Service Improvement” — there is language granting the company rights to collect, use, and share data derived from scans of codes you generate. You consented. Legally, you are covered.

But the people who scan your code never consented to anything. They trusted you. They pointed their camera at a piece of paper or a screen you controlled. They assumed the code was just a link. They had no idea a third party was logging their location before the redirect even completed.

This is the structural asymmetry at the heart of QR code surveillance. The legal relationship exists between the platform and you. There is no legal relationship between the platform and the scanner. So the scanner has no rights to enforce, no data to request, no opt-out to exercise. They are not a user of the platform. They never agreed to anything. They just scanned a code that someone they trusted put in front of them.

Scan Flow · What Actually Happens in 200 Milliseconds
01

Scanner sees your QR code on a flyer, business card, restaurant table, or product packaging. They point their camera and tap the notification.

02

Their device connects to the QR platform’s tracking server. The platform reads their IP address, device headers, and any location data available.

GPS · Device fingerprint · OS · Browser · Timestamp — all logged before the destination loads.
03

The tracking server creates a permanent database entry associating this scan with your QR code, the scanner’s device profile, and the geographic data.

This entry is now property of the QR platform. Neither you nor the scanner can delete it without legal action — and the ToS you signed permits it.
04

The platform redirects to your actual destination. The scanner sees your content. Everything appeared normal. They have no idea steps 02 and 03 occurred.

05

The logged data is packaged with data from thousands of other QR codes on the same platform and sold to advertising networks, data brokers, or used to train targeting algorithms.

The scanner who trusted you is now a data point in a commercial dataset they never agreed to join.
Real Example · Bitly QR Analytics
Bitly — one of the largest QR code and link shortening platforms — openly documents its scan analytics capabilities in its Help Center. When you create a Bitly QR code, the company tracks clicks, geographic data, referrers, and device types. This data is visible to you in the analytics dashboard. What is less prominently displayed: Bitly also uses this data internally for advertising targeting and shares aggregated datasets with third-party analytics partners. The scanner never sees a privacy notice. From their perspective, they scanned a code and navigated to a website. They do not know Bitly exists in the transaction at all, let alone that it logged their location. Legally, Bitly is protected — you consented when you created the code. But the scanner consented to nothing, and has no recourse.
The Creator’s Position
You Agreed
You accepted the Terms of Service when you created the code. The platform’s data collection is legally authorized. You may not have read Section 8. Nobody does. But you clicked Accept, and that click has consequences for other people.
The Scanner’s Position
They Never Could
The scanner has no legal relationship with the QR platform. QR code surveillance operates entirely outside their awareness — no ToS to read, no cookie consent to refuse, no opt-out to exercise. Their data is collected under your consent, not theirs — and they have no mechanism to object or remove it.
05 · The Expiration Problem

When The Company Dies, So Does Your Code

Dynamic QR codes have a second critical failure mode beyond QR code surveillance: they are not permanent.

You printed 10,000 flyers with a QR code. You embedded the code in product packaging that ships internationally. You etched it onto permanent signage. That code points to a redirect URL on a server owned by the QR platform. If that platform shuts down, rebrands, gets acquired, or decides to discontinue its free tier, your code becomes a dead link. Every piece of printed material with that code becomes worthless overnight.

This has already happened. When the platform behind the QR code surveillance redirect shuts down, every code it hosted dies with it. Multiple QR platforms from the 2010s no longer exist. Codes printed on permanent materials now point to 404 errors. The investment in printing, distribution, and signage is irreversible. The content is gone. There is no migration path for a QR code already printed on physical materials.

Real Example · Google URL Shortener Shutdown
In 2018, Google announced it would shut down its goo.gl URL shortening service — a service millions of businesses had used to create QR codes for printed materials. Millions of short links embedded in QR codes were set to expire. Google provided a transition window, but QR codes already printed on physical materials could not be retroactively updated. Business cards, product packaging, event posters, conference materials, and published books using goo.gl-based QR codes became permanently broken. The content was effectively bricked because the company that hosted the redirect decided it no longer wanted to. This is the fundamental risk of server-dependent codes: the code itself is a permanent physical object, but the destination it points to exists only at the pleasure of a third party.
PropertyDynamic QR (Tracking)Static QR (Private)
Destination editable after print?Yes — via platform dashboardNo — fixed in the pattern
Works if platform shuts down?No — immediate dead linkYes — forever
Tracks scanner location?Yes — GPS per scanNo — architecturally impossible
Requires account?Yes — for code managementNo — none required
Data owned by third party?Yes — scan data is theirsNo — nothing to own
Scan speed (redirect latency)?Slower — server round-trip requiredFaster — direct navigation
Static vs dynamic QR code comparison — permanent local generation vs server-dependent expiring tracking code

Static QR codes · Permanent by design · No server dependency · No scan tracking · No expiration risk

Watch · How QR Code Tracking Actually Works
06 · The Exit

Static QR Codes: No Server. No Tracking. No Expiration.

The solution to QR code surveillance is technically simple. The QR code open standard — ISO/IEC 18004 — does not require a server. It never did. The entire redirect architecture was added by platforms who needed a business model on top of an open format. Remove the platform, and you remove the surveillance.

A static QR code generator eliminates QR code surveillance by design — encoding your destination URL directly into the QR pattern using the open standard. The code is generated entirely in your browser using JavaScript — no file uploaded, no server contacted, no account created. The QR code image is created locally on your device and downloaded immediately. Nothing leaves your machine.

When someone scans it, their device reads the pattern, extracts the URL, and navigates directly to that destination. No redirect. No middleman. No log entry. Nothing to track because there is no server in the transaction at all.

What You Give Up
Analytics Dashboard
You cannot see how many times the code was scanned, from where, or on which device. That data does not exist anywhere. If you need scan analytics, you can achieve this by appending UTM parameters to your destination URL and using your own analytics on your own website instead — analytics you control, that track your content rather than your users.
What Everyone Gains
Actual Privacy
The scanner’s location is not logged. Their device is not fingerprinted. Their behavior is not profiled. Your code never expires. No company can pull the plug. No database of scanner behavior is being built and sold. The code works as long as QR readers exist — which, given that QR decoding is built into every smartphone camera, means effectively forever.

Static QR codes are technically superior to dynamic ones in every way except one: they do not generate surveillance data that can be monetized. That is not a technical limitation. That is a design choice by platforms that profit from knowing where your audience goes.

Privacy-First Tool · Local Processing · Zero Tracking
AIToolboxBD Free QR Code Generator
Generates permanent static QR codes entirely in your browser. Zero server upload. Zero QR code surveillance. Zero expiration. No account required. The code is created locally on your device, downloaded as a PNG, and works forever — even if AIToolboxBD ceases to exist tomorrow. The data is in the pattern, not on a server.
Generate Your Static QR Code →

You Are Not the Villain. The System Is.

You used a free tool because it was convenient. You did not intend to enable QR code surveillance on the people who trusted you. You did not read 47 pages of terms and conditions because nobody does. You created QR codes because that is how event flyers and restaurant menus and business cards work now. You did nothing wrong.

But the result of QR code surveillance is the same: everyone who trusted you enough to scan your code had their location logged, their device fingerprinted, and their behavior profiled — without their knowledge and without their consent. That data sits in a database owned by a company you never chose to do business with on behalf of people who had no say in the matter.

The fix is not to stop using QR codes. The fix is to use static QR codes that have no QR code surveillance architecture embedded in them by design.

Static codes exist. Tools to generate them locally exist. There is no technical barrier to ending QR code surveillance on your end. There is no cost barrier. There is only the awareness barrier — and you just crossed it. The people who scan your next QR code will not know what changed. But they will be better off because of it.

Create a private static QR code now →
Think About This
Have you ever printed or shared a QR code and realised only now that you were unknowingly enabling QR code surveillance on the people who trusted you enough to scan it — and what did you do with that code afterward?
Leave a Review
0
0 out of 5 stars (based on 0 reviews)