Who sees QR code scan data

Who sees QR code scan data is a short list. The account owner dashboard shows totals, device type, and a country from headers. The scanner sees a page. Team roles on shared codes see the same anonymous fields. Wi-Fi has empty logs because there is no hop.

Who sees QR code scan data

SmartQRCode records scans on redirect and landing-page types only. The payload in the ink is a hosted URL. Each request can increment a total, store a coarse device class, and store a country inferred from headers. That is the data. There is no scanner mailbox, no legal name, and no GPS trail.

The scanner sees a page: a website, a menu, a video landing, or an OS prompt. They do not receive a receipt of what the owner can see. There is no scanner-facing analytics portal.

Wi-Fi is static. The phone reads the password from the modules. The owner cannot see who joined. Brief volunteers accordingly. A Wi-Fi generator is a convenience print, not a door log.

A Canva one-off with a giving URL is the right tool for a one-night church appeal that will never be edited or counted. Use a hosted tracking code when the campaign runs for months and someone has to report whether the poster worked. See churches and nonprofits.

Do not promise lock-screen scanning as a data-collection feature. iOS can offer a banner from the lock-screen camera; behaviour varies by version. That banner does not add a name to your dashboard. It only makes a scan more convenient.

Can staff see a named visitor

No. Owner, admin, and member roles share codes. They do not gain a secret identity column. If a volunteer asks for "the list of people who scanned," the honest answer is that the list does not exist.

Country from headers can be wrong. Do not use it to target a neighbourhood. Device type is for "mostly phones," not for asset tags.

What does the scanner see in return

A destination. For a website code, that is whatever URL you set, reached via 302 so later edits still work. For a landing-page type, that is the hosted page. The scanner might also see their own browser's cookie banners on the far site. Those belong to the destination, not to the scan log.

If the print is a sticker-over, the scanner sees the attacker's page. The original owner sees either nothing new or scans on a host they no longer control. Physical security of the paper is not a dashboard setting.

Who sees data after you cancel

Pause is a separate state from archive. User-archived codes keep scanning. Pause is how you stop the live hop. Cancelling a subscription is a billing event; it is not a new audience for the logs. Provider dependence still applies: hosted prints need the host to resolve.

When you wanted nobody on your side to see even anonymous totals, do not create a hosted code. Print a static https URL with Canva, Google, or the phone generator. Continue with QR code analytics and GDPR if you need a processor narrative.

A nonprofit board pack should not invent scan totals. If the dashboard says 12, write 12. If the fetch failed, write that it failed. Zero from a failed fetch is a lie in an admin console and a lie in a trustee PDF.

Event badges that encode a vCard still wait for the contacts confirmation. The owner log, if the type is hosted, still has no name from the scan. The name appears only if the person saves the card and later gives it to you by other means.

A guest who scans from the lock screen, on versions that offer a banner, still produces the same three fields. Convenience is not identity. Do not write a privacy notice that claims otherwise.

If two people share a login, both see the same anonymous chart. That is still not a named visitor. Rotate the password; do not invent a column. Support at support@smart-qrcode.com can talk about account access. They cannot magically attach a guest identity that the hop never stored.