QR analytics privacy scope, country

QR analytics privacy scope is country and device on hosted codes, not a name, email, or GPS trace. Unique figures are a keyed hash per owner. Wi-Fi and Canva static files record nothing, which is the honest choice when you do not need a count.

What qr analytics privacy scope includes

There is no scanner name or email. Trust header country not gps. Unique values are a keyed hash per owner. Remember wifi has no scan row.

Redirect and landing-page types record totals over time, device type, and country. That is the entire public claim. no scanner name or email appears in the series. If a legal review asked whether the symbol is an identity check, the answer is no. The destination might collect a form. The scan hop does not.

header country not gps is the geography. The edge sets a country header. A scanner who spoofs one in production gets it replaced. Locally there is no edge, so tests can lie. Do not demo a UK rule against production by sending GB from your laptop.

keyed hash per owner is how unique scanners are approximated where that panel exists. The secret is required. An empty secret stores null rather than a weak hash. Nulls cannot be recovered later. One office NAT looks like one visitor. A phone that changes network looks like two.

Paid options are $1.99, $29, $97, and $197. We do not sell an unpaid tier. How to mint one code per object is QR campaign tracking by code. How UTMs ride the destination is UTM QR code parameter plan. Who may see account-side logs is enterprise QR code governance.

Tracked QR codes, dynamic QR codes, and the website URL generator are the hosted faces. Retail marketing codes are the usual place this scope is over-promised to a brand team.

Does a scan identify the person holding the phone

It does not. The camera opened a URL. The server saw headers. That is closer to a web hit than to a check-in. Do not write "footfall" on a slide unless you measured doors.

A member of staff scanning the same endcap every hour inflates raw scans. That is D120. It is not a privacy leak. It is a counting leak. Train the team or accept the number as hops.

Landing pages you author can still contain a form. That collection is yours, with your notices. It is not this product inventing a shopper profile from the QR modules.

How country is inferred without GPS

The symbol has no radio. Country is a property of the request that arrived. Stores in a border city will mix. Tourists will mix. That is not a defect in the code. It is the method.

Device type is the user agent classifier on the scan path. Keep routing rules and pie charts on the same classifier. Tablets before phones is the current rule so iPads are not silently mobile.

wifi has no scan row. Do not ask analytics why the guest network cards are quiet. They never hopped.

If a DPIA template asks for retention of shopper emails from the QR hop, the accurate fill-in is that those emails are not collected. Country and device may be stored as scan metadata. Unique hashes, where enabled, are not reversible to a person without the secret, and even then they are not a login. Do not volunteer a GPS story. There is no GPS.

A stakeholder who wanted footfall should buy a door counter. QR analytics privacy scope will not become that counter if you squint.

When you should not count at all

A Canva one-off or another free static generator is the right file when the payload will never change and you do not want a server to see the hop. Privacy is then absolute because there is no hop. You also cannot answer "how did the flyer do?" from the symbol.

A hosted code you pause still existed. Pausing is not deletion of history. If the brief is "never store a scan," do not use a hosted type. Use static. Accept F91 in reverse: no provider, no count, no edit.

If the brief is "count without naming people," qr analytics privacy scope is the contract. Write it into the DPIA as country, device, and optional keyed uniqueness, not as identity.