QRCDN

Scan analytics

Every scan, counted honestly.

Daily rollups by country, city, device, and referrer, with a live today count. Hashed at the door: raw IP addresses are never stored.

sha256(ip + daily rotating salt) → raw IPs never stored

What you see.

One window per code: the scan curve, totals, today so far, and breakdowns by country, device, and referrer.

qrcdn.com/codes
Scan activity
7d30d90d1y
Jun 22Jul 1Jul 10Jul 19
Scans

5,631

last 30d

Peak day

941

Jul 19

Today so far

318

Top countries

  • United States2,540
  • United Kingdom890
  • Germany612
  • Canada401

Devices

  • Mobile4,206
  • Desktop1,180
  • Tablet245
30-day history free · 365-day + city-level on Pro

by day · country · city · device · referrer

How counting works.

The redirect layer logs each scan at the edge. An hourly job rolls logs into daily counts per code, and the dashboard reads those rollups: fast to load, boring to break. The today tile reads the live edge count.

edge log → hourly rollup → scan_daily · today reads live

Totals update hourly by design. If another tracker shows different numbers, see the FAQ: both are probably right.

Privacy is the design, not a setting.

We never store a raw IP address. Each scan is hashed with a salt that rotates daily, so we can count unique visitors within a day but cannot trace anyone across days, and neither can anyone who ever reads our database.

stored: country, region, city, device class, referrer

hashed: ip + daily rotating salt, one way

never stored: raw IP, precise location, cross-day identity

The same words, legally binding, in the privacy policy.

Retention

History that matches your plan.

Free keeps 30 days of scan history, country-level. Pro extends that to 365 days, with city-level geography.

Every number, on the pricing page

Questions

Before you trust the numbers.

Why do my numbers differ from my web analytics?
We count scans at the redirect; your site counts page loads after it. Bots we can identify are excluded from rollups, ad blockers do not affect us, and neither tool is wrong: they measure different doors.
Do you use cookies or fingerprinting?
No cookies, no fingerprinting. Uniqueness within a day comes from the salted hash, which cannot survive the day boundary.
Is the today number exact?
It is the live edge count and can drift slightly from the final daily rollup; the rollup is the number of record.
Can I get analytics over the API?
Yes: per-code series and breakdowns.

Know what your print is doing.

Start free. No card, no trial clock.

Start free

your code never dies