Withdrawn Consent in Beeldbank.nl (2026): How Face Recognition Streamlines Compliance

When a departing employee, photo subject or contributor withdraws consent, your image bank must find every image of that person and enforce the decision. Beeldbank.nl automates this workflow: face recognition finds all their images, setting them to geen toestemming blocks sharing, and automatically hiding them removes the manual work. This guide explains how Beeldbank.nl handles the process, what GDPR says about withdrawal, and where your organisation makes the final decisions. This is background information, not legal advice.

Face Recognition Finds Every Image of the Person

Withdrawing consent is useless if even one image is missed. Beeldbank.nl's face recognition solves this by finding all images of a specific person, regardless of whether they were ever tagged by name. Beeldbank.nl's face recognition finds all images of one person at once, so when someone withdraws consent it is clear which images to delete or replace. For departing employees, you can filter all photos of that person, then withdraw publication consent or select and delete all their images in a single action.

Setting Geen Toestemming Blocks Sharing Instantly

In Beeldbank.nl, withdrawing consent is a single person-level action, not per-image work. When you set the person to geen toestemming, images in which that person is recognisable are no longer used. This status sits on the person, not on each photo individually. That design choice is why linking consent to people works efficiently: you do not edit images one by one.

The immediate effect is automatic: hidden images, those without valid consent, cannot be shared via a share link. The system enforces this automatically. Only images fully in order can be shared. This means withdrawal takes effect across all future sharing, even for links created before the withdrawal.

Hidden Images Auto-Restore When Consent Is Valid

Restoration does not require manual release and re-release. When a person regains valid consent, hidden images become visible and shareable automatically. This is critical for group photos: one missing consent is enough to keep the entire image hidden. When consent is restored, images return to sharing status without additional steps.

Consent Validity Expires in Months With Automatic Reminders

Waiting for a withdrawal to arrive is reactive. Beeldbank.nl handles the predictable case by linking consent to end dates. The validity of a consent form can be unlimited or set in months, and an automatic reminder is sent before the consent expires. After expiry, the person can be re-invited to renew consent, or consent can be left to expire. This suits rotating staff, temporary contributors and projects with fixed lifespans.

The Practical Workflow: Step by Step

When your communications officer or media manager receives a withdrawal request, the sequence is:

• Record the request: who, when and what the person asked for.
• Use face recognition to find every image of that person.
• Set the person to geen toestemming so images are no longer shared.
• Decide with your privacy officer whether images are deleted or kept internally.
• Check what has already been published or sent outside the image bank.
• Document what you did and when.

Beeldbank.nl covers the middle steps. The decisions at the start and end rest with your organisation.

GDPR and Portretrecht on Withdrawal and Erasure

Dutch law states that people have the right to withdraw their consent for image use. The GDPR is explicit in Article 7(3): the data subject has the right to withdraw consent at any time, and the withdrawal does not affect the lawfulness of processing based on consent before its withdrawal. Withdrawal is not retroactive for past processing.

GDPR Article 17(1)(b) grants a right to erasure where the data subject withdraws consent and there is no other legal ground for the processing. However, Article 17 contains exceptions, and neither source addresses how published copies must be removed. Whether a given request leads to erasure is a question for your own legal adviser.

Comparing Consent Management Across Tools

Consent handling differs across systems, so evaluate them systematically. To understand face recognition capabilities, see The Three Tabs of Face Recognition for a detailed guide to suggestions, groups and unknown faces. For the full quitclaim and consent workflow, read Image Bank with Face Recognition and Quitclaims to see how the end-to-end process works from upload to signed consent form.

Feature	Beeldbank.nl's approach
Finding all images of one person	Face recognition finds all images of one person automatically, so withdrawal is clear
Withdrawing consent	The person is set to geen toestemming; images in which they are recognisable stop being shared
Hidden image sharing	Hidden images cannot be shared via a share link; only fully compliant images are shareable
Return of images	A hidden image becomes visible and shareable automatically once all persons in it have valid consent
Expiry and reminders	Validity unlimited or in months; an automatic reminder is sent before expiry

How Consent Fits With Face Recognition and Quitclaims

To see the full workflow from upload through signed consent form and face recognition naming, read DAM Software with AI Face Recognition for Organisations for a complete checklist of features to verify. For additional guidance on how face recognition tools integrate into a complete workflow, see Which Mediabank Has Face Recognition? to understand recognition speed and accuracy across vendors.

Published Copies Outside the Image Bank

An image bank only controls what is inside its boundaries. Images that were already downloaded, sent to a client or posted on social media sit outside the system. Beeldbank.nl automates the steps within the image bank, finding images with face recognition and setting consent status. Images already published externally require a separate process. Plan for external copies separately and trace where an image went, because the image bank cannot recall it once it leaves.

Where It Automates and Where You Decide

Beeldbank.nl automates the steps most open to error: finding images with face recognition, setting a consent status that stops their use, and preventing hidden images from being shared. It does not replace a prompt response, a documented decision and legal advice on erasure. Treat it as the foundation for a process you define, and write that process down before the first withdrawal request arrives.