Choose the smallest useful public introduction
A good professional introduction does not require publishing every way someone could reach you. Start with a name, relevant role and one suitable contact route. Add details only when they help the intended audience. A work email may be enough for a conference card; a personal phone number or home address often adds little to that exchange.
Decide who the card is for before entering information. A public exhibition profile, a consulting card and a personal introduction can serve different audiences. Treat this as an editorial choice you can explain: what should a stranger be able to learn, save or forward? Review the complete public result, including linked files and images, rather than checking only the visible contact fields.
Understand the difference between a link and embedded contact details
A website QR contains an address. A contact QR can contain the actual name, phone number, email and other selected details. A person who obtains the image can read the encoded data with a suitable reader. The vCard specification describes a contact-exchange format; it does not give those details inherent authentication or confidentiality, and saved contact information can become outdated.
Choose direct contact encoding only for details you are comfortable distributing in a lasting copy. A hosted page gives you a place to change what future visitors see, but it cannot update every contact record someone previously saved. Neither a decorative design nor a QR pattern makes public information secret.
Further reading: [1]
Review publication as a deliberate step
In Weyno, drafts and account information are separate from the approved public card. Review the public fields and content before publishing, then open the public link while signed out. Confirm that the page shows what you intended and that documents do not reveal extra contact details, collaborator information or material meant for a smaller audience.
Anyone with a public card's link or QR can view and share its published content. Editing or unpublishing a page cannot recall downloaded images, printed codes, saved contacts or other people's copies. Weyno's current privacy notice explains these boundaries. Read it alongside your organization’s own sharing rules when preparing a work or team card.
Further reading: [3]
Make the next action explicit
Offer a useful choice in the conversation: 'Would you like the project link?' or 'May I contact you about the method we discussed?' Those questions identify a purpose. A scan can simply mean someone wanted to read a page. It is not a reliable signal that the person wants recurring updates or unrelated sales messages.
When a contact form or follow option is available, explain what will happen and keep participation voluntary. Ask only for information needed to respond. If someone prefers to take your details without giving theirs, make that a comfortable outcome. This guide describes a practical exchange workflow; it does not claim that one script or checkbox establishes legal compliance everywhere.
Illustrative example: two people choose different ways to continue
Imagine Noor meeting two people after a workshop. This fictional example demonstrates choices, not a measured case study. One person wants only the slides, so Noor shares the resource link. The other asks for a discussion about a future project and voluntarily gives a work address for that purpose. Noor records the topic and the agreed next step.
The first person does not become a contact-list entry merely for viewing the slides. The second person's address is used for the requested discussion rather than silently added to a general newsletter. A short factual note such as 'Asked about the accessibility workshop' is more useful than speculative personal judgments or unnecessary sensitive details.
Help visitors recognize a trustworthy destination
The US Federal Trade Commission warns that malicious QR codes can hide links to deceptive sites and recommends inspecting the URL before opening it. Make that inspection easier: print or display a recognizable destination beside your code, explain what opens and avoid surprising people with a sign-in or payment request unrelated to the introduction.
When receiving a card yourself, check the domain shown by your phone and pause if the page asks for information the exchange does not require. Do not assume a familiar-looking logo proves who controls the site. If a physical QR sticker appears to cover another code, use an independently known route to verify the destination before continuing.
Further reading: [2]
Plan for changes and copies
Set aside a short review whenever your role, contact preference or project changes. Update the hosted public introduction and check old documents that still contain previous details. On a shared device, avoid leaving a saved Wallet or downloaded card files behind. Removing a device's offline copy is a separate task from changing the online profile.
- Publish only details that serve the card's intended audience.
- Inspect the public page, documents and image content while signed out.
- Treat downloaded contacts and printed QRs as copies you cannot recall.
- Ask about the purpose of follow-up rather than inferring it from a scan.
- Review the destination before entering information on someone else's page.
Sources & further reading
Primary references support the technical guidance. Product behavior is described separately. Examples are illustrative; no customer results are claimed.
Share this guide
What should go on your digital business card? Decide what belongs on a public profile, what to share by choice, and what to leave off.