data protection

Staff photos on the website: consent in Switzerland

AA
Aurum Avis Labs Author
6 min read

Staff photos on the website: what Swiss SMEs should decide first

Publishing staff photos on the website is common for trust and recruiting, but names and faces are personal data under the FADP. You need a lawful basis, usually consent for marketing use, clear information (Art. 19 FADP), and a process when someone refuses or leaves (Art. 32 FADP on withdrawal). This is not legal advice; it is orientation for owners and HR in firms of about 20 to 250 people updating a team page.

Password rules for systems are separate; see password policy for a small business if IT asked about credentials rather than portraits.

  • BasisConsent

    Marketing team pages usually rely on voluntary consent; other bases are narrow and need documentation.

  • ScopeWhere used

    Define site, LinkedIn, print brochures, and employer branding.

  • WithdrawalMust work

    Removing a photo after objection should not require a lawyer each time.

  • MinorsExtra care

    Apprentices under 16 need guardian involvement where applicable.

Consent must be informed and specific: what you show, where it appears, and how long. A blanket line in the employment contract is weak if it does not describe the website and social use. Prefer a short form or e-mail confirmation stored with HR: “I agree to publication of my name, role, and photo on our website and company LinkedIn until I withdraw.”

Group photos are harder. If one person objects, crop or reshoot rather than keeping the group image online. Document the date consent was given and the version of the privacy notice linked at that time. Consent from 2018 deserves a fresh look if channels or purpose grew; silent reuse is risky when nobody asked again.

Reasonable approach

  • Opt-in before the shoot, not only opt-out after
  • Alternative avatar for those who decline
  • Annual reminder that withdrawal is possible

Usually avoid

  • Publishing a new hire before HR files consent
  • Reusing event party shots without checking each face
  • Leaving ex-employees visible for years

Some firms argue legitimate interest in a recognisable team page. That bar is high: marketing, recruiting, and trust must be weighed against personality rights (Art. 6 FADP). For a voluntary gallery with names, documented consent is usually the clearer route. Executive portraits in press releases can sit under different rules; borderline cases need counsel.

What the privacy notice should say about the team page

Your site notice should state that you show staff portraits and names, for which purpose (trust, recruiting, contact), and how long you keep them visible. Point to where consent is managed, usually HR or a central inbox. Whoever maintains the notice should know that a new shoot or a new channel may need text changes, not only a new image in the CMS.

If marketing e-mails portraits to an agency, treat that like any other personal data transfer; see sending personal data by email.

When someone leaves or withdraws

Offboarding should include website and social: remove or replace the profile within a defined period (often days, not months). Cache and Google results may lag; note that in your reply to the person. If marketing keeps an “alumni” story, get separate consent.

Old CMS backups may still contain photos; IT should know whether restores could republish withdrawn images. Portraits stored in marketing cloud folders need the same deletion rhythm as the site; see sharing files that contain personal data.

  • Log the withdrawal (e-mail, HR ticket, or letter)
  • Check website, intranet, and scheduled social posts
  • Tell the agency or photographer to delete copies
  • Confirm to the person, noting possible cache delay

CV photo versus team page

A photo from recruitment is not automatic consent for a public team page. Job applications have their own retention rules and purpose. If HR wants to reuse a CV portrait, get separate documented consent for the website. Otherwise recruiting data and marketing get mixed. Borderline uses such as press or crisis communication need counsel; aim for a transparent process under Swiss law.

What this is not

Not guidance on customer photos or event attendees. Not a template privacy policy. Not recruitment retention (how long to keep job applications).

A made-up example: the outdated team page

A made-up example: a 30-person IT firm in Zurich refreshes branding. Marketing uploads new headshots for everyone except one engineer who declined. Six months later the engineer leaves; the old photo stays next to a blog post. They complain. HR had no checklist item for the web team. The firm adds offboarding ticket “remove web profile”, stores consent PDFs, and uses silhouettes for two roles that regularly object.

Photos in email signatures and at trade fairs

Many firms show the same portrait in signatures, on roll-ups, or at a trade fair stand. That is not automatically covered by the website consent when the wording only names the website. List channels explicitly, or get a short confirmation when new channels appear. Fair photos with the public in the background are a different picture: there it is often about visitors, not only employees.

Whoever considers a complaint to the FDPIC should first document internally what was published and when the withdrawal arrived. That does not replace counsel, but it helps the conversation with HR and marketing.

LinkedIn, agencies, and freelancer shoots

If an agency stores RAW files, contract deletion when consent ends. Freelancer portfolios may keep your team visible without your knowledge; ask for takedown in the brief. Clarify whether company Instagram or LinkedIn profiles show faces and who holds admin rights. On exit, review scheduled posts as well as the website.

Contractors, temps, and intranet

Agency staff on your site need the same consent path as employees, usually coordinated with the agency contract. Intranet photos are lower risk but still personal data if the directory is accidentally reachable from outside. State in consent whether the image may appear only internally.

Recruiting pages that show “meet the team” should not include people who declined website use; use role titles instead.

Who can keep it simple

A five-person firm with one static page may use written consent per person and manual removal.

A growing firm with monthly hires and agency photographers needs owner, HR, and marketing in one workflow.

Can we use photos taken at the Christmas party?

Only with clear consent for website use. Party context is not automatic permission for marketing.

Does consent last forever?

No. Withdrawal is possible at any time. After a long gap or new channels, a short reconfirmation helps.

Must every employee take part?

No. Refusal is allowed. Plan placeholders or roles without faces instead of applying pressure through the employment contract.

Datenschutz training

A live session covers employee-facing data on sites and social channels, with time for your team page, in one to two hours. Details on data protection awareness training.

Collect consent before the photo goes live, and take it down when the person withdraws or leaves the company. Once a year a short check is enough: do the visible faces still match the consents? If someone is missing from the list, sort it out before the next shoot.

data protection website consent fadp switzerland
AA

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.

Customize your cookie preferences. Essential cookies cannot be disabled as they are required for the website to function properly.

Essential Cookies

Required for basic website functionality, security, user authentication, and error tracking.

Always active

Analytics Cookies

Help us understand how visitors interact with our website to improve user experience. Includes Google Analytics and Microsoft Clarity session recordings.

Marketing Cookies

Used to track visitors across websites to display relevant and engaging advertisements.