Are Digital Business Cards Safe? A Privacy Guide With Test Data

Is the digital business card you just shared at a conference quietly tracking the person who scanned it? And how much of your own contact data is sitting on a page anyone can read?
I run linkutm, a link management tool. We don’t make card apps, so I have no card to sell you. But I spend my days looking at what happens between a click and a page load, so I tested digital business card privacy from the recipient’s side. On November 17, 2026, I opened three vendors’ demo cards in a clean browser and logged every request and cookie.
Short answer: digital business cards are safe to use, but they are not private by default. The card page is a website. It can run analytics, session replay tools and ad scripts on the person who opens it. Your details also sit in plain HTML that a scraper can read. The risk is low for a work email and office number. It is higher for a home address or personal mobile.
| Risk | Who it affects | How likely | Fix |
|---|---|---|---|
| Analytics and ad scripts on the card page | The recipient | High (2 of 3 cards I tested) | Pick a vendor with fewer scripts, cut embeds |
| Contact details readable without JavaScript | You (the owner) | High (3 of 3) | Share only work contact details |
| Guessable card URL | You | Medium (2 of 3 use names) | Use a random ID or your own short link |
| Leads you collect under privacy law | You and the recipient | Depends on your region | Tell people, collect less, delete on request |
| NFC or QR tampering | The recipient | Low, mostly at events | Lock tags, check the URL preview |
| Vendor breach or policy change | Both | Low, but out of your control | Read the policy, delete cards you stop using |
Who Is at Risk? The Three Parties Behind Every Digital Business Card
Every digital business card involves three parties, and each faces a different risk. Most safety advice only talks about one of them.
A digital business card is a web page, hosted by a card app, that holds your contact details. You share it by QR code, NFC tap, link or wallet pass. All four of those only carry a URL. The page itself lives on the vendor’s server. (I covered how this chain works in my comparison of free digital business card apps.)
Here is how the three parties relate:
- You, the card owner, publish your data to the vendor and decide what fields and embeds go on the card.
- The vendor (Blinq, Popl, Wave Connect and others) hosts the page, chooses which scripts load on it, and stores the views and leads.
- The recipient opens the card in their browser. Their phone runs whatever the vendor and you put on that page. If they fill in a “share your details back” form, their data goes to the vendor and then to you.
That last step flips the roles. The recipient becomes the person whose data is at risk, and you become responsible for it.

The honest limitation: this model assumes a hosted card. A vCard QR code has no vendor in the middle at all, which changes the picture (more on that below).
What Happens When Someone Opens Your Card? My Tracker Test
Two of the three demo cards I tested loaded third-party analytics before the recipient tapped anything. One loaded none.
Here’s the setup. I used headless Chrome with a fresh, empty profile for each card and an iPhone user agent. I made no taps and clicked no consent buttons. Each page got 20 seconds. Chrome’s network log captured every request, and I read the cookies straight from the browser’s own cookie store afterwards. I ran a blank page first and removed Chrome’s own background traffic from the results. Then I ran the whole test twice. Request counts matched within two.
| Demo card | Unique URLs loaded | Third-party domains | Cookies set | Analytics, ads or replay tools | Cookie banner |
|---|---|---|---|---|---|
| Blinq | 67 | 3 | 10 | Amplitude, Amplitude Session Replay config, Datadog RUM, Cloudflare Web Analytics, Google Analytics 4 via Cloudflare Zaraz | None |
| Popl | 92 | 11 | 8 (4 from YouTube) | Amplitude, Amplitude Session Replay config, Google DoubleClick, Stripe.js, YouTube and Calendly embeds | None |
| Wave Connect | 103 | 5 | 2 | None (Google APIs, jsDelivr and reCAPTCHA only) | None |

Three things surprised me.
Google Analytics can hide from a network check. Blinq’s card never called a Google Analytics domain. But it set cookies named cfz_google-analytics_v4. That is Cloudflare Zaraz, a tool that runs third-party scripts on Cloudflare’s servers instead of in your browser. So a privacy extension that blocks Google domains would miss it.
Session replay tools were configured on two cards. Both Blinq and Popl fetched Amplitude’s Session Replay settings. Session replay records clicks, scrolls and taps so a company can watch a visit back later. A config request does not prove a recording happened. It proves the tool was on the page and checking whether to record.
Your own embeds add trackers. Most of Popl’s third parties came from the demo card’s content. The YouTube video set four YouTube cookies before anyone pressed play. The Calendly widget added Calendly. If you add a video or booking link to your card, you add those companies to every view.
Real talk, this test has limits. It ran from India. Vendors often show cookie banners only to EU or UK visitors, so a visitor in Berlin may see a banner I didn’t. These were vendor demo cards, not customer cards, and a paid plan might load different scripts. And three vendors is a sample, not a ranking. I kept the script and raw data, so I can rerun it when these pages change.
Can Strangers Scrape Your Contact Details From a Card?
Yes. All three demo cards put contact details in the raw HTML, so a scraper can read them without running any JavaScript.
I fetched each card with a plain HTTP request, the way a basic scraper would. Blinq’s page held an email address. Popl’s held an email and a phone number. Wave’s held two email addresses and a phone number. (I counted them and redacted the values in my data. They are the vendors’ demo personas, but there is no reason to republish them.)
That is by design. A card has to show your details to work. The question is how easy the page is to find without your QR code. That comes down to the URL format:
- Blinq uses a random 12-character ID, like
blinq.me/C2LNoocPOe84. With 62 possible characters per position, that is about 3.2 x 10^21 combinations. Nobody is guessing that. - Popl uses a name, like
poplme.co/jason/.... - Wave Connect uses first and last name, like
app.wavecnct.com/jessy.diamond.
A name-based URL is easier to remember and easier to guess. If someone knows your name and your card app, they can try a few URLs and find you.

Search engines are a separate question. All three demo cards carried a noindex tag, which asks Google not to list the page. I covered card indexing in the app comparison post, so I won’t repeat it here. The limitation: noindex stops polite crawlers. It does nothing against a scraper.
Do Digital Business Card Apps Sell Your Data?
The three vendors I tested all say they don’t sell personal data. But “don’t sell” and “no advertising” are different promises, so read both lines.
| Vendor | Sells personal data? | Advertising | Role for leads you collect | Deletion |
|---|---|---|---|---|
| Blinq | “We do not sell your personal information to third parties.” | Says it does not share customer data with advertisers | Not stated clearly | “Completed within 30 days,” including backups |
| Popl | “Does not sell, lease, or rent personal information that it processes as a service provider.” | “We may work with third party advertising partners to show you ads” | Processor; “Popl’s customers act as the Data Controllers” | Non-customer data removed or anonymized after 7 years |
| Wave Connect | “We do not sell your personal information” and does not share it for cross-context behavioral advertising | Ad pixels on its marketing site “with your consent only” | Processor “on the customer’s behalf” | On request, no fixed period |
Sources: Blinq privacy policy (updated October 23, 2026), Popl privacy policy, Wave privacy policy. Quotes checked against the live pages on November 17, 2026.
On digital business card security, all three claim SOC 2 Type II on their enterprise pages. SOC 2 Type II is an independent audit of a company’s security controls over a period of months. It is a good sign. But it is self-reported on a marketing page, and I did not see the reports themselves.
Here’s the thing: the policy matters less than the page. Popl’s policy says it may work with ad partners, and my test found DoubleClick on its demo card. Wave’s policy limits ad pixels, and its card loaded none. The test and the policy told the same story. Check both.
When You Collect Contacts, You Become Responsible
If your card has a “share your details back” or lead capture form, you are not just a card owner. Under GDPR, you are usually the data controller for those contacts.
A data controller decides why and how personal data is used. A data processor handles it on the controller’s instructions. Popl and Wave both say this outright: they are processors, and their customers are the controllers. The European Data Protection Board’s guidelines on controllers and processors define it by function, not by contract. If you decide to collect leads at a trade show and send them follow-up emails, you are deciding the purpose.
What that means in practice:
- Tell people what happens to their details before they submit them.
- Collect what you need. Name and work email beat a 10-field form.
- Delete a contact when someone asks, in your CRM as well as in the card app.
- If you use the card app’s “enrich” feature to add data about a contact, you are adding personal data they never gave you.
Okay, so this is not legal advice, and the rules differ by country. In the US, state laws like California’s CCPA treat some cookie-based sharing as a “sale”. Browsers can also send Global Privacy Control, a signal that tells sites not to sell or share your data, and some state laws require sites to honor it. If you collect leads at scale, ask your legal team which rules apply.
Are NFC Business Cards Safe?
NFC business cards are about as safe as QR codes. The chip usually holds nothing but a URL, and it only works within a few centimeters.
The risk is not someone stealing data from your phone through the card. It is someone changing where the card points. An unlocked NFC tag can be rewritten by anyone with a phone and a free app. A sticker can cover a QR code. Both send the recipient to a page you never chose.
So lock the tag if your vendor lets you, and test your card after any event where it left your hands. My NFC tag explainer covers tag types and locking. For the scanner’s side of tampering, see how fake QR codes work.
One limitation people forget: a lost NFC card works for whoever finds it. If your card links to your full profile, a stranger can tap it in the parking lot. That is another reason to keep the card page to work details only.
Is a vCard QR Code More Private Than a Hosted Card?
Yes, for the recipient. A vCard QR code holds your details inside the code itself, so scanning it loads no web page, no scripts and no cookies. Zero requests.
A vCard is the standard contact file format (.vcf) that phones import. A vCard QR code prints that file as a QR code. Here’s how the main sharing options compare on privacy:
| Option | What the recipient’s phone loads | Can you update or revoke it? | Who sees view data |
|---|---|---|---|
| Paper card | Nothing | No | Nobody |
| vCard QR code | Nothing, the contact is inside the code | No, it is printed forever | Nobody |
| Apple NameDrop | Nothing from the web, phone to phone | No, they keep the contact | Nobody |
| Hosted digital card | The vendor’s page, scripts and embeds | Yes | The vendor, and you |

Apple says NameDrop “shares only your name, the phone number or email address you choose, and Contact Poster information,” and not your home address or birthday (Apple personal safety guide). NameDrop is on by default. You can turn it off in Settings > General > AirDrop by switching off Bring Devices Together.
The trade-off is control. With a vCard or NameDrop, once someone has your details, you can’t take them back or change them. A hosted card can be edited or deleted. That’s why I don’t think “most private” is automatically “best”. It depends on whether you change jobs often.
How to Make Your Digital Business Card Safer: 7 Steps
These seven steps take about 15 minutes and cut most of the risks above.
- Remove home and personal details. Delete your home address, personal mobile and birthday from the card. Use a work email and a work or VoIP number.
- Check your embeds. Every video, booking widget or social feed you add brings that company’s scripts and cookies to every view. Keep only the ones that earn their place.
- Use a random card URL. If your vendor lets you choose, pick a random ID over your full name.
- Put your own link in front of the card. Print a short link on your own domain that redirects to the card. If you switch vendors or want to shut the card off, you change one redirect instead of reprinting.
- Rewrite your lead form. Add one sentence saying what you’ll do with the details. Remove fields you don’t use.
- Lock NFC tags and test after events. Tap your own card after a conference to make sure it still goes where you expect.
- Delete cards you stop using. Then delete the matching contacts from your CRM if people asked you to. Remember that contacts people already saved stay on their phones.
On step 4: a branded domain in linkutm does exactly this, and it is the part I’d actually recommend paying for. To be fair about it, a redirect through linkutm also records a click with country and device, so it is one more party in the chain. If you want zero view data at all, a vCard QR code is the honest answer.
Is It Safe to Scan Someone Else’s Digital Business Card?
Yes, in almost every case. Scanning a card QR code or tapping an NFC card just opens a web page, and your phone shows you the URL first.
Before you open it, check that the domain matches a known card app or the person’s company. Then decide whether to fill in the exchange form. You don’t have to. You can save their contact without sending yours back.
If you care about trackers, open the card in a browser with tracking protection. Where a cookie banner appears (sites run them through a consent management platform), choose “reject”. For general link checks before you tap, my guide to telling whether a link is safe walks through the steps. The limit: tracking protection may not catch server-side tools like Zaraz, because nothing loads from the tracker’s own domain.
Frequently Asked Questions
Are digital business cards safe to use?
Yes, digital business cards are safe for sharing work contact details. The card is a vendor-hosted web page, so the main risks are trackers on that page and contact details a scraper can read. Keep the card to a work email and number, and avoid adding your home address or personal mobile.
Can a digital business card track you when you scan it?
Yes, it can. In my test, two of three vendor demo cards loaded analytics tools such as Amplitude before I tapped anything, and one also loaded Google’s DoubleClick. The card owner usually sees views and taps, and the vendor’s tools may record device and location data from your IP address.
Can someone hack my phone with an NFC business card?
No, not in any practical way. An NFC business card usually holds only a URL, and it works within a few centimeters. The real risk is a rewritten or swapped tag that sends you to a fake page, so check the URL your phone shows before you open it.
Do digital business card apps sell your data?
The three vendors I checked, Blinq, Popl and Wave Connect, all state they do not sell personal data. But Popl’s policy also says it may work with advertising partners to show ads, and its demo card loaded DoubleClick. Read the advertising section of a vendor’s policy, not just the “we don’t sell” line.
Is NameDrop safer than a digital business card?
Yes, for privacy. Apple says NameDrop shares only your name, the phone number or email you choose and your Contact Poster, directly between phones with no web page involved. The trade-off is that you can’t update or take back a contact once it is shared, while a hosted card can be edited or deleted.
Is a digital business card GDPR compliant?
The card app can be GDPR compliant, but compliance for the leads you collect is your job. Popl and Wave Connect state that their customers are the data controllers for collected contacts. That means you need to tell people how you’ll use their details, collect only what you need, and delete contacts on request.
The Bottom Line: Are Digital Business Cards Safe?
Yes, as long as you treat the card as a public web page, because that’s what it is. Put only work details on it, keep embeds to a minimum, and read the vendor’s advertising policy alongside the “we don’t sell” line.
If you’re sharing a card at events, put a link you control in front of it. Set up a branded domain in linkutm and you can repoint or shut off every printed card from one place.