Digital business cards are inherently public — that is the point. The card profile is meant to be shared, scanned, and viewed by people who do not have an account on the platform. But "public profile" and "no privacy considerations" are not the same thing. The platform around the card still handles login data, contact details, and behavioral analytics, and the practices around all three vary widely between vendors.
What Is Collected
Three buckets of data exist in any digital card platform:
- Profile data — your name, role, photo, links, and contact details. This is intentionally public and exists to be shared.
- Account data — your login email, billing details, plan, and any team affiliations. This is private.
- Analytics data — views, clicks, scan source, approximate location, device family. This is mostly aggregated and rarely identifies the viewer.
Profile vs Analytics Data
The most common confusion is between what you publish and what the platform tracks. Profile data is what you put on the card on purpose. Analytics data is the trail of activity around it: who opened the card, when, from what referrer, and what they clicked. The viewer is generally not identified by name unless they explicitly sign in or fill in a form on your card. They show up as a session or a region, not a person.
If a platform claims to identify anonymous viewers by name or email without their consent, that is a major red flag. It usually means the platform is doing reverse-IP lookup or fingerprint matching with third-party data brokers — and that practice is increasingly illegal in major regulatory jurisdictions.
Are NFC and QR Themselves Risky?
NFC and QR codes are not networks. They are short-range delivery mechanisms that hand off a URL. Tapping an NFC card is the same security model as someone reading a URL out loud — the phone opens the link in the browser, and the browser handles it like any other webpage. There is no background data exchange, no app install, no permission prompt.
The risk that does exist is link-spoofing. A malicious actor could program an NFC tag with a phishing URL. The mitigation is the one your phone already does: it shows you the URL before opening it. Your own NFC card, programmed once with your card URL, is not a vector — and you control what is on it.
Who Owns the Data
Read the terms of service for any platform you sign up with. The right model is: you own your profile data and your contact list, and the platform provides storage and processing under a license that ends when you cancel. The wrong model is one where the platform claims any kind of resale right or "perpetual license" over the contacts you collect through the card.
Export should be free, complete, and machine-readable (CSV or JSON). If you cannot get your data out cleanly, you do not actually own it.
Five Questions to Ask a Vendor
- Where is the data hosted, and under what jurisdiction's privacy law?
- Is account data encrypted in transit and at rest?
- What does the analytics layer collect, and is the viewer ever individually identified?
- Can I export my profile data and contact list at any time, in a standard format?
- What happens to my data if I cancel — is it deleted, anonymized, or retained?
Controls You Should Expect
A reasonable platform gives you three controls: delete or rotate your card slug at will, hide specific fields from the public view (e.g. show role but hide phone unless someone actively saves your contact), and download or delete all of your data on request. If any of these is missing, treat it as a deal-breaker — these are baseline requirements in 2026, not premium features.
Privacy on a digital card is not about secrecy — the card is meant to be shared. It is about clarity: knowing what is collected, who can see what, and being able to walk away with your data intact.