Sensitive personal data under the FADP: office examples
Sensitive personal data under the FADP
If you search for sensitive personal data under the FADP, you usually need to know which files in a Swiss SME need stricter handling than a name and an email address. The revised Federal Act on Data Protection lists the categories in Art. 5(c) FADP: health, religious or philosophical beliefs, trade union membership, and data on intimate life or racial or ethnic origin, among others. Genetic and biometric data used to identify someone count as well.
This note is for HR, office managers and owners in a firm with perhaps 20 to 250 staff. It is orientation, not legal advice, and not a full catalogue of obligations.
Everyday office cases
- HealthHR inbox
Sick notes, accident reports, occupational health files, vaccination status if collected.
- BeliefsPayroll or forms
Church tax deductions, voluntary entries on diversity forms.
- UnionsNegotiation
Membership lists when you negotiate with a union.
- BiometricsAccess
Fingerprint time clocks when templates are stored.
A made-up example: A fiduciary with 45 employees forwards a scanned sick note through the general inbox because the assistant “only wanted to pass it on quickly”. The note is sensitive. The customer invoice in the same thread is not. Leaving both in one “Inbox” folder is the mistake, not mislabelling the invoice.
HR collects sick leave
Every certificate and every email that mentions a diagnosis belongs in a restricted HR store, not in the managing office group chat.
Reception asks for the reason
For attendance, “not in today” is enough. Asking about illness or religion on the phone creates data you do not need.
Fingerprint time tracking
If the system stores templates, plan retention and access like health files, not like the petty-cash log.
What is usually not “sensitive” on its own
A name, email, phone number, invoice amount, job title or customer number is personal data, but not in the special category, unless health or belief data is attached. A performance note (“good teamwork”) without a health link stays outside the list. Add a disability or diagnosis in the same row and the row moves into the special category.
In payroll, salary structure is personal; the band alone is usually not sensitive. Supplementary health insurer details or line items with a health link often are. Team event photos follow usual image rules; religious holiday planning counts as sensitive only if you systematically store people’s beliefs.
Counts as sensitive
- Medical certificate in an application file
- Note “employee X is in therapy” in a board spreadsheet
- Biometric template for the door
Usually does not
- Complaint with no health link
- Salary band without supplementary insurer details
- Team photo without stored religious affiliation
A customer complaint is not automatically health data. A medical certificate attached to the same email is.
What an SME should do differently
Sensitive data mainly needs less sharing and clearer folders in daily work, not necessarily a new IT project.
- Separate folders and permissions from “ordinary” HR; access only for people who need the file.
- No scans on personal phones or in group chats without a rule.
- Set retention periods and delete when they end.
- Before pasting into AI tools: use the same traffic light as for customer data; health and payroll stay red.
If you process sensitive data on a large scale, the exemption from keeping a full register of processing activities under Art. 24 of the Data Protection Ordinance may not apply even below 250 employees. What “large scale” means depends on context; a practice with many patient files every day is not the same as a trading firm that archives one sick note per year. Both still treat that one note carefully.
Breaches, trust and GDPR overlap
Losing a laptop with health files, or emailing a sick note to the wrong person, makes it more likely the FDPIC will see a high-risk breach. Context on fines and personal liability: FADP fines and personal liability. Intent still matters for criminal fines; carelessness still damages trust with staff and clients.
EU customers often use “special categories” in contracts (GDPR Art. 9). The labels are similar; the assessment stays case by case. Whether the GDPR applies to your firm depends on whether you offer goods to people in the EU or monitor their behaviour there. A Swiss address on the invoice does not settle that.
For staff training on handling personal data in Swiss offices, see data protection awareness training.
Written by
Aurum Avis Labs
Builds and ships at Aurum Avis Labs. Writes here about what we learn working with founders and SMEs in the DACH region.
Related Articles
You might also be interested in these articles
FADP fines and personal liability in Switzerland
FADP fines up to CHF 250'000 target natural persons with intent, not every honest mistake. What owners and managers should know about Swiss penalties.
Does the GDPR apply to Swiss companies?
Does the GDPR apply to Swiss companies? Art. 3(2) EU scope, Swiss home law, and signs your SME processes EU residents' data.
What counts as a data security breach under Swiss law?
What counts as a data security breach in Switzerland: unauthorised access, loss, destruction, and examples beyond a wrong email.