Personal Data Protection Act

Wbp, Personal Data Protection Act, WBP, Personal Data Act, Privacy Act
The Personal Data Protection Act (Wbp) was the Dutch privacy law until May 2018. Since then, the AVG applies as the replacement framework.

What is the Personal Data Protection Act?

From 2001 until May 25, 2018, the Personal Data Protection Act (Wbp) was the Dutch law governing how organizations had to handle personal data. The law required companies to collect data from customers, employees or visitors only for a clear purpose, and to inform people about the use of their data. Since May 25, 2018, the Wbp has been replaced by the General Data Protection Regulation(AVG), a European law that takes immediate effect in all member states. For Dutch SMEs, it is especially relevant to know that all obligations that applied under the Wbp are now covered by the AVG, often with stricter rules and higher fines.

How the Wbp worked in practice

The Wbp required companies to keep a register of what personal data they collected, for what purpose and how long they kept it. When in doubt or with sensitive data, you had to report to the Dutch Data Protection Authority (CBP), the regulator. Customers had the right to see, correct or have their data deleted. Companies had to take security measures against data breaches. In practice, many SMEs saw that the Wbp remained a paper exercise: a privacy statement on the website and an Excel list of processing operations, but little structural control. That changed abruptly with the arrival of the AVG, which introduced higher fines and more active enforcement.

Why the Wbp was replaced by the AVG

The Wbp was based on a 1995 European directive, when the Internet and data-driven marketing were in their infancy. The law could no longer keep up with cloud storage, marketing automation, tracking and international data flows. That's why the European Union developed the AVG, a regulation that applies directly in all member states without national implementation. The AVG sets stricter requirements for consent, introduces the right to data portability and increases the maximum fine to 4% of global annual turnover or 20 million euros. For Dutch companies, this meant redesigning their processes. More information about the current rules can be found on the website of the Personal Data Authority.

What the transition from Wbp to AVG means for your business

Although the GDPR no longer applies, the basic principles are carried over into the AVG. If you already complied with the Wbp at the time, you have a good foundation. But the AVG requires more: active consent instead of tacit consent, processor agreements with all external parties processing data, and a duty to report data breaches within 72 hours. In practice, we find with SME clients that the documentation requirement in particular is a stumbling block. You have to be able to demonstrate that you are compliant, not just claim to be. A good starting point is an SEO strategy that takes cookie banners and tracking into account, coupled with a clear privacy statement. A link to your privacy policy also helps visitors understand how you handle their data.

Applications of the Data Protection Act in historical context

Although the Wbp has not been in force since 2018, you still regularly come across the term in old contracts, records and processor agreements drafted before that date. It is useful to know how the Wbp was applied back then, so you can understand what obligations are now covered by the AVG and how to interpret old agreements.

Duty to report to Data Protection Board

Under the Wbp, you were required to report certain data processing activities to the CBP, for example, if you processed sensitive data such as medical or criminal information. New processing activities or changes also had to be reported. This led to a central registry in which organizations described their processing activities. Many small and medium-sized enterprises (SMEs) reported their CRM systems, newsletter lists, or personnel files. Since the GDPR took effect, that reporting requirement has been eliminated, but you are now required to maintain an internal register yourself. In practice, this means you can use your old Wbp notifications as the basis for your current processing register, provided you update them with new purposes, retention periods, and security measures.

Consent for direct marketing and newsletters

The Wbp allowed you to use data for direct marketing if people did not object, called the opt-out method. You were allowed to send a newsletter to customers who had purchased from you unless they indicated they didn't want it. The AVG reversed this: now you must seek active consent before including someone in your mailing list, except with existing customer relationships under strict conditions. Many companies that had built up a large newsletter list before 2018 under the Wbp had to clean up their list and ask permission again after the AVG was implemented. This often led to a big drop in subscribers, but improved quality and higher open rates.

Retention periods and archival obligations

The Wbp prescribed that you could not keep data longer than necessary for the purpose for which you collected it. At the same time, you often had a legal retention obligation under tax law, for example seven years for invoices. Under the Wbp you solved that by stating in your privacy statement that you kept data as long as the law required it. The AVG uses the same principle, but now requires an explicit retention period per processing purpose. In practice, this means that you have to translate old WBP agreements into concrete periods: customer data three months after last contact, quotation data one year, personnel files five years after leaving employment. A well thought-out data management policy will help you take a structured approach to this.

When the Wbp is still relevant and when it is not

The Wbp is only still relevant if you need to interpret old contracts, processor agreements or documentation created before May 2018. For example, if you have an agreement with a supplier that refers to the Wbp, you need to update it to the AVG. All new processing operations, consents and privacy statements are subject to the AVG. So don't rely on old Wbp texts or procedures. Many companies make the mistake of continuing to use a privacy statement from 2016 because it was approved by a lawyer at the time. That is no longer sufficient. You now need an AVG-compliant statement that addresses rights such as data portability and automated decision-making, which did not exist under the Wbp.

Want to apply this to your business? Monkey Vision helps SME entrepreneurs with web design, SEO and smart digital solutions. Schedule a no-obligation meeting and find out what's possible for you.

Schedule an introduction

Frequently Asked Questions

No, the Wbp and the AVG are two different laws. The Personal Data Protection Act was the Dutch privacy law from 2001 until May 2018. The AVG is the European regulation that applies in all EU member states since May 25, 2018 and has replaced the Wbp. The AVG is stricter: higher fines, more rights for data subjects and an active consent requirement instead of opting out. Many basic principles are the same, but implementation and enforcement differ considerably. If you are still working with documents or contracts that refer to the Wbp, you need to update them to the AVG to stay compliant.

Yes, absolutely. A privacy statement drafted under the Wbp no longer meets the requirements of the GDPR. The GDPR requires you to address new rights such as data portability, the right to be forgotten, and automated decision-making. You must also be clearer about the legal basis for processing, retention periods per purpose, and data transfers to countries outside the EU. In practice, we see that many small and medium-sized businesses still have outdated text on their websites. This can lead to fines in the event of an audit or complaint. Update your privacy statement to a GDPR-compliant version and ensure it aligns with your current data processing activities, such as your CRM system and marketing automation.

Under the Wbp, CBP could impose a fine of up to €820,000, but that rarely happened. Most violations resulted in a warning or an order under penalty. Since the AVG, the Personal Data Authority can impose fines of up to 20 million euros or 4% of global annual turnover, whichever is higher. Moreover, enforcement is much more active: inspections are carried out more frequently and fines are imposed, including on SMEs. A data breach that you fail to report within 72 hours can already result in a hefty fine. The difference is mainly in the deterrent effect and the international scope of the AVG.

The transition from Wbp to AVG requires a thorough check of your processes. Start with a processing register in which you describe all data processing: what data, what purpose, what legal basis, what retention period. Check your consents: are they active and specific? Update your privacy statement and ensure processor agreements with all parties processing data on your behalf, such as your hosting party or marketing automation platform. Set up a procedure for data breaches and train your team. Want to know where you stand now and what the biggest risks are? Schedule a free 30-minute privacy scan at Monkey Vision. You will immediately receive three points of improvement and a realistic roadmap to become compliant, tailored to your situation. Learn more through our SEO services, where we also cover cookie banners and tracking.

About the author

Monkey Vision

Monkey Vision is a full-service digital agency at Nijmegen, specializing in web design, SEO, and AI automation for small and medium-sized businesses. The knowledge base has been compiled by our team of online strategists and is continuously updated based on current insights.

Publication date: 26-04-2026
Last update: 26-04-2026