Image Consent in a Shared Drive vs an Image Bank: Beeldbank.nl for Quitclaim Tracking

A team that keeps its photos in shared folders may be asked a simple question: how do you know this person agreed to appear here? A folder can hold the picture, but it has nowhere to hold the answer. This article starts from what KVK and the GDPR say about consent, then walks through how Beeldbank.nl tracks quitclaims, so you can compare it with whatever system you use today. Tools support this work but do not make an organisation compliant, and nothing here is legal advice.

What KVK and the GDPR Say About Consent for Publishing Images

You need permission from the people shown in order to publish footage of them. That permission must be given of their own free will, and you must make clear in advance what the images will be used for. People have the right to withdraw their consent again. The legal requirements also leave open how long images may be kept or what happens to copies that were already published, so those questions need advice from your own legal adviser.

The GDPR says the same about withdrawal in Article 7(3): the data subject has the right to withdraw consent at any time, and withdrawal does not affect the lawfulness of processing that took place before it. In plain terms, consent is specific and it can end. Withdrawal does not by itself prescribe how published copies must be removed, and it is not retroactive for processing already done.

Why a Shared Drive Cannot Answer the Question of Image Consent Alone

A shared drive stores files and folder names. It does not know who is in a picture, whether that person signed anything, or when their permission ends. A team may fill the gap with a second record: a spreadsheet of names and dates, an email thread, a folder called something like approved. These work if the person who keeps them is careful and the archive stays small. If your files sit in a Microsoft environment, why SharePoint is not built for photos looks at that setup, and a team whose files sit in OneDrive can read what OneDrive lacks for digital asset management.

The weak spots show up in everyday situations. A new colleague uploads photos without knowing the spreadsheet exists. A person withdraws consent and the list is not updated. An old photo turns up in a search and gets published because the file itself looks perfectly fine. In each case the picture and the permission live in two different places, and the only link between them is a person remembering to look.

How Beeldbank.nl Tracks Digital Quitclaims for Image Consent

Beeldbank.nl offers digital consent forms, known as quitclaims, per person, with monitoring of the expiry date. The vendor states that it automatically links the person in a photo to his or her quitclaim, so users know whether the image may be published. It also states that one consent form per person is valid for all of that person's images, which means you do not collect a new form for every picture of the same individual.

Expiry dates are configurable. That matters because consent given for a campaign or a school year may be meant to end, and a system that watches the date does not rely on someone's calendar reminder. The practical result is that the question of whether an image can be used is answered where the image is, not in a separate file.

How Beeldbank.nl Handles Group Photos and Sharing Warnings

Beeldbank.nl says images without valid consent can be hidden automatically. For group photos it goes further: an image with multiple people only becomes visible once everyone in the image has valid consent. That rule closes a gap that a manual list can miss, where one person in a group of several has an expired form and nobody notices because the other faces are fine.

The vendor also describes a warning at the moment of sharing. When a user shares images, a pop-up shows a warning if not all persons in the images to be shared have given consent. A check at the last step is valuable because it catches the case where an image was selected quickly, or collected into a selection weeks earlier, before someone's status changed.

Shared Drive and Image Bank Compared Task by Task

The table sets the two approaches next to each other. The shared drive column describes the work you would have to arrange yourself around a plain folder, whichever shared drive your team uses today. The image bank column reflects only what Beeldbank.nl states about itself.

Which Questions to Ask Any Image Consent Tool Before Relying on It

Whichever route you take, put the same questions to the tool in a live demonstration with your own material. Where does the signed form sit, and can a colleague see it from the image? What happens on the day a consent form expires? What does a group photo do when one person has no valid form? What does a person see when they try to share a selection that includes such an image? And what happens to a person's images when they withdraw?

Ask also what the tool does not do. Hiding an image inside the system does not remove a copy that was already published or downloaded. Withdrawal does not automatically remove previously published copies. Keep your own written procedure for those cases, and let your data protection adviser review it.

How to Plan the Move From Folders to Beeldbank.nl Quitclaims

Start with the people, not the pictures. List everyone who appears in your archive, collect the proof of consent you already hold, and note which images have no proof at all. Those without proof are the ones to leave out of the first import until you have clarified their status. Moving the clean part first gives colleagues a working system quickly and keeps the uncertain part visible instead of buried.

If you are still deciding between a drive, a DAM and an image bank, comparing a drive, a DAM and an image bank compares the three approaches. If your team keeps company photos in a consumer cloud drive, seven signs it is time for an image bank gives a checklist for deciding when to move.