A QR code business card is a simple thing, but it touches personal data at both ends: the details you publish and the details other people might send you. This guide explains what each scan shares, who holds what, and what privacy law expects of you. It is general information, not legal advice.
What a scan shares
When someone scans your card, their phone opens your profile in the browser. They see what you chose to publish. They do not send you their name, number or email by scanning.
Like any website, the server that hosts the profile receives the technical details every web request carries, such as the phone's IP address and browser type. What the profile platform keeps, and for how long, is set by its privacy notice.
What your dashboard shows you
On our cards, profile analytics show:
- Profile views: how often your profile was opened.
- Link clicks: which links people tapped.
- Contact saves: how often someone tapped Save contact.
These are counts. They tell you how the card is used, not who used it.
If you add the location tracker, a separate add-on that is not part of either plan, it shows where your leads were captured. That is location data about real people, so mention it in your privacy notice if you use it.
What you only get when people choose to share
On the Business Add-ons plan, your profile can collect details that people choose to send you:
- Contact leads: visitors leave their details for you to follow up.
- Enquiries and custom forms: the fields you set.
- Bookings: a name and contact details with a chosen time.
- Subscribers: sign-ups for your mailing list.
You can keep these in the built-in CRM and export them. The Brand Presence plan does not include these tools. Our guide to capturing contacts from QR card scans covers the forms in detail.
Data type vs who holds it vs what to tell people
| Data | Who holds it | What to tell people |
|---|---|---|
| Your published profile details | The profile platform, on your behalf; anyone who scans can see them | Nothing extra: you chose to publish them |
| Technical request data (IP address, browser) | The profile platform | Covered by the platform's privacy notice |
| View, click and save counts | Shown to you in the dashboard | Not personal to any one visitor |
| Contact leads, enquiries, bookings | You, in your dashboard (Business Add-ons) | Who you are, why you collect them, how long you keep them, how to ask for deletion |
| Mailing list subscribers | You (Business Add-ons) | A separate, unticked opt-in and an easy way to unsubscribe |
| Exported contacts in your own CRM | You and your CRM provider | The same notice, plus your CRM provider's role |
| Lead locations (separate location tracker add-on) | You, in your dashboard | That you record where leads were captured |
The basics under UK GDPR and the EU GDPR
If you collect contacts in the UK or the EU, data protection law applies to them. In the UK that is the UK GDPR with the Data Protection Act 2018, overseen by the Information Commissioner's Office. In the EU it is the General Data Protection Regulation (Regulation (EU) 2016/679).
Four things matter most:
- A lawful basis. You need a reason the law recognises. For a contact form, the clearest is usually consent: the person asks you to get in touch. The ICO's guide to lawful basis explains the options, including legitimate interests.
- A clear notice. Tell people who you are, why you want their details and how long you keep them. A short line next to the form, with a link to your full notice, works well.
- Collect only what you need. Name and email for a follow-up. Not date of birth, not job history.
- Rights. People can ask to see, correct or delete their details. Have a simple way to act on those requests.
For marketing emails, keep consent separate. A newsletter sign-up should be its own unticked choice.
Short notes on other laws
- California, US. The California Consumer Privacy Act, as amended by the California Privacy Rights Act (CCPA/CPRA), gives California residents rights to know, delete and opt out of the sale or sharing of their personal information. It applies to businesses that meet its thresholds. The California Attorney General's CCPA page explains it.
- Canada. PIPEDA generally applies to personal information collected in the course of commercial activity, built on meaningful consent. Quebec has its own, stricter rules.
- Australia. The Privacy Act 1988 and its Australian Privacy Principles apply to many organisations; some small businesses are exempt, but following the principles is good practice.
- India. The Digital Personal Data Protection Act 2023 is built on notice and consent and is being brought into force with its rules.
Wherever you are, the same habits go a long way: say why you collect, collect little, keep it safe and delete on request.
Retention and deletion
Decide how long you keep captured contacts before you start collecting them.
- Set a period. For example, delete leads you have not worked with after a set time you choose and write down.
- Clean up after events. Remove test entries, duplicates and contacts who asked not to hear from you.
- Delete on request. When someone asks, remove their details from your dashboard and from any CRM you exported them to.
- Keep exports tidy. An export saved on a laptop is still personal data. Store it securely and delete old copies.
What to tell people, in plain words
A short notice next to your form might say: "I will use your details to follow up on our conversation. I keep them for as long as we are in touch, and you can ask me to delete them at any time." Link to a fuller notice if you have one.
For how this store handles personal data on its own website, see our privacy policy.
Sharing captured contacts with others
If you pass a lead to a colleague or a partner business, the person should know that could happen. Say so in your notice, and only share what the other person needs to follow up. If someone asked only to hear from you, keep it that way.
A short checklist before you switch on a form
- Decide exactly which fields you need, and drop the rest.
- Write one sentence on why you collect them.
- Decide how long you keep them, and write it down.
- Put the notice next to the form, not behind a link.
- Keep newsletter sign-ups as a separate, unticked choice.
- Know how you will find and delete one person's details if they ask.
- If you export to a CRM, check that it lets you delete records too.
Trust and safety
Privacy and security go together. A trustworthy card shows the domain your profile opens on and never asks visitors for passwords or payments. Our guide to QR code phishing and business cards explains how to make your card easy to verify. For what the analytics numbers do and do not tell you, read our guide to QR code scan analytics.
Where our cards fit
Our QR code business cards open an editable profile, with an NFC chip as a backup tap. Contact capture, bookings, forms, CRM and export come with the Business Add-ons plan. More guides are on the blog.
Frequently asked questions
No. A scan only opens your profile. They share details only if they choose to fill in a form.
No. Analytics show counts of views, link clicks and contact saves, not names.
You need a lawful basis. For a contact form, consent is usually the clearest. Tell people why you collect their details and how to ask for deletion.
Data protection law applies to personal data whatever the volume. The obligations are proportionate, but the basics still apply.
Only as long as you need them for the reason you gave. Set a period, write it down and delete contacts after it.
No. It is general information. Check the rules that apply in your country, or ask an adviser.
If you only publish your own details and collect nothing, there is little to explain. Once your profile collects other people's details, add a short notice next to the form.