Collecting Staff Details for a Card Order: A Data Protection Checklist
By Wholesale Visiting Cards Editorial Team | Published | Updated

Every team card order starts with a spreadsheet of staff details. Names, titles, phone numbers, photos. Those details are personal data, and once they sit on a profile that anyone can open with a tap, they are published personal data. This checklist covers what to collect, the lawful basis for employee profiles, how to handle optional fields, who can see what, and what happens to the data when someone leaves. It is one of the guides behind our procurement checklist for ordering visiting cards in bulk.
This is general information for planning a card order, not legal advice. Your data protection officer or adviser should confirm what applies to your company.
The rules that usually apply
Three sets of rules come up most often for team card orders:
- In the EU: the General Data Protection Regulation (GDPR). Article 5 sets the principles, including data minimisation and storage limitation. Article 6 lists the lawful bases. Article 88 allows member states to add specific rules for employee data.
- In the UK: the UK GDPR and the Data Protection Act 2018, with guidance from the Information Commissioner's Office.
- In California: the CCPA, as amended by the CPRA, which has covered employee personal information since 2023. The California Privacy Protection Agency enforces it alongside the Attorney General.
Other countries have their own laws. The checklist below follows principles that appear in most of them: collect only what you need, have a clear reason, tell people, keep it no longer than necessary.
Collect the minimum
Start from the card and the profile, not from the HR record. For each field, ask whether it will actually appear on the card or the profile, and whether the person's job needs it there. If not, do not collect it for the card order.
A minimal set for most teams is:
- Name, as it should be printed
- Job title
- Work email
- Work phone or switchboard number
- Office or location
Do not copy the HR record into the card spreadsheet "just in case". Home addresses, dates of birth and personal emails have no place in a card order, and every extra field is one more thing to secure and delete later.
Everything else is optional and should be treated differently.
| Field | Needed? | Likely basis | Retention after a leaver |
|---|---|---|---|
| Name | Yes | Employment contract or legitimate interests | Remove from the profile on the last day |
| Job title | Yes | Employment contract or legitimate interests | Remove from the profile on the last day |
| Work email | Yes | Employment contract or legitimate interests | Remove or replace with a team address |
| Work phone | Usually | Employment contract or legitimate interests | Remove or replace with a team number |
| Office or location | Usually | Legitimate interests | Remove or keep only as a branch detail |
| Photo | Optional | Consent | Remove on the last day |
| Personal mobile | Optional | Consent | Remove on the last day |
| Personal social links | Optional | Consent | Remove on the last day |
| Booking link | Optional | Legitimate interests or consent | Remove on the last day |
The "likely basis" column is a planning prompt, not a ruling. Your adviser decides the basis for your company.
The lawful basis for employee profiles
Under the GDPR and UK GDPR you need a lawful basis for each use of personal data. For visiting card profiles, two come up most:
- Contract or legitimate interests for the core work details. A sales role that involves meeting customers usually needs a way to share a work email and phone number.
- Consent for anything personal, such as a photo or a personal mobile number.
Consent between an employer and an employee needs care. The European Data Protection Board's guidelines on consent explain that the imbalance of power at work makes it hard for consent to be freely given. In practice, that means optional fields should be genuinely optional. Saying no must have no consequences, and people must be able to withdraw later.
Optional fields and consent
Handle optional fields with a short, separate question for each one:
- "Do you want a photo on your profile?" with a yes or no.
- "Do you want to add a mobile number?" with a note that a work number is fine.
- "Do you want to add a personal LinkedIn page?"
Do not bundle them into one tick box. Record each answer with the date. If someone later changes their mind, remove the field and update the record.
A work number avoids most of the question. Many companies put a switchboard or work mobile on every card and leave personal mobiles off entirely.
Tell people what happens to their data
Before you collect anything, tell staff in plain words:
- What will appear on their card and their profile.
- That the profile is public to anyone who taps the card or scans the QR code.
- Who can edit it, and how they ask for a change.
- What happens to the profile when they leave.
- Where to find your privacy notice.
Profiles are hosted by our platform partner. Our privacy policy explains how we handle personal information. Your own staff privacy notice should still cover the card profiles.
Who can see what
Separate three audiences:
- The public. Anyone who opens a profile. Show only what the person and the company have agreed.
- The card owner. The person who manages profiles and the register. They see the full staff list for the card order.
- Everyone else inside the company. They do not need the spreadsheet. Keep it out of shared folders the whole company can open.
The Brand Presence plan includes password protection and visibility controls on a profile. Use them if a profile should not be fully public, for example for a role that only shares details with existing clients.
Retention after a leaver
When someone leaves, decide on the day:
- Remove their personal details from the profile, or change the profile to a team profile.
- Remove optional fields, such as the photo and personal mobile, straight away.
- Delete their row from the card spreadsheet, or keep only what you need for the register.
- Decide what happens to any contact leads collected through their profile, and how long they are kept.
Our guide to managing visiting cards when staff join or leave covers the leaver steps in full. If you are building this into HR's process, adding visiting cards to employee onboarding shows where the consent questions fit. Estate agency offices, where agent photos are common, may also find our guide to NFC visiting cards for real estate brokerages useful.
A request form you can adapt
Send every person the same short form. Keep the required and optional parts visibly separate.
Name as printed: [required] Job title: [required] Work email: [required] Work phone or switchboard: [required] Office or location: [required] Photo on profile: [yes / no; if yes, attach a head-and-shoulders photo] Mobile number on profile: [yes / no; if yes, the number] Personal LinkedIn on profile: [yes / no; if yes, the link] I have read how my profile data is used: [link to your staff privacy notice]
Store the completed forms with the card register, not in email threads.
Who owns this process
Someone has to own the data side of the card order. In most companies that is the card owner working with HR, with the data protection officer checking the form and the notice once. Our guide on who should own company visiting cards covers how to split the work.
Review the form, the notice and the leaver step once a year, or sooner if the law or your card set-up changes.
Common data mistakes in card orders
- One tick box for everything. Consent for a photo, a mobile and social links should be separate questions.
- Personal mobiles by default. A work number avoids the consent question for most people.
- The spreadsheet in a shared folder. Keep it where only the card owner and HR can open it.
- No leaver step. Details stay public long after the person has gone.
- No record of answers. Nobody can show later who agreed to what, or when.
- Forgetting the notice. Staff should know their profile is public before it goes live.
Frequently asked questions
Do we need consent to put staff details on visiting cards?
Not always for core work details, which often rest on the employment contract or legitimate interests. For optional personal details, such as a photo or personal mobile, consent is the usual basis. Your adviser should confirm the basis for your company.
Can employees refuse a photo on their profile?
Yes. Optional fields should be genuinely optional, with no consequences for saying no, and people should be able to withdraw consent later.
Is a profile public?
Yes, to anyone who taps the card or scans the QR code. Show only what the person and the company have agreed. Password protection is available on the Brand Presence plan if a profile should not be fully public.
What should we do with a leaver's details?
Remove personal details from the profile on the last day or change it to a team profile, delete optional fields, and decide how long any leads are kept.
Does California law apply to employee profiles?
For employees who are California residents, the CCPA as amended by the CPRA can apply to their personal information. Check with your counsel.
Is this legal advice?
No. It is general information for planning a card order. Ask your data protection officer or adviser to confirm what applies to you.
Next step
When your form and notice are ready, request a bulk quote for team digital visiting cards, or see the team digital visiting card options first.