You are here:


The cookie provision of the Dutch Telecommunications Act came into force in 2012. This law stipulates that websites must inform their visitors clearly and completely about the use of cookies. In addition, the law requires users to give their permission for websites to use most cookies. In 2015, an amendment to the law was enacted, placing cookies with no or minor privacy consequences outside the scope of the cookie legislation. The law still requires users to grant their permission for websites to use privacy-sensitive cookies.
On this page we will tell you what cookies are and exactly what they are used for, inform you about how Ridder handles cookies and explain how you can nevertheless disable them should you choose to do so.

What are cookies?

Cookies are small pieces of information that your browser stores on your computer when you visit a website and which are used, for example, to remember your personal preferences. Ridder also uses cookies.
Some cookies are set by Ridder (first-party cookies), others by parties that either produce content shown on the Ridder website or data that we use (e.g. analytics) (third-party cookies).

Cookies on our website

The Ridder website uses the following types of cookies:

Strictly necessary cookies
These are cookies that are strictly necessary for the site to function. Without these cookies the Ridder site would not function optimally. According to the cookie provision, your permission is not required for use of this type of cookie.

Social media cookies
These cookies make it possible to directly share a page via social media when you are logged in. To make these buttons work, Facebook, Twitter and other social media platforms place cookies so they can recognize you. We have no influence on this.

Analytics cookies
Ridder uses statistics tools and cookies to measure where our visitors come from, which operating system they use, how many people read certain pages etc. This information is of great importance to us, because this measurement data enables us to optimize the site and make it more user-friendly. Ridder uses cookies from Google Analytics for this. We also advertise regularly via Google Ads. To measure the effectiveness of these advertisements we also use cookies from that system.

Embedded Vimeo & YouTube videos
We also embed videos from Vimeo and YouTube on our site. Those parties usually also place cookies, to identify visitors. Ridder has no influence on this. You can find more information about their cookie policies on their websites.

Facebook advertising
The Facebook Pixel enables us to also show visitors of the Ridder website relevant advertisements on Ridder’s Facebook page and measure the results. This allows us to reach people who are interested in Ridder.

Google Tag Manager
Container for managing and configuring tags.

Google Maps
To display the map and locations when using the dealer locator to search for other locations/sales outlets.

ReCAPTCHA (invisible)
To prevent third parties from sending us spam via the forms on our website.

Other cookies

  • Session ID cookie: cookie containing a unique reference code
  • User prefs cookies: cookies used to save user preferences (country selection, language selection, navigation selection (via groups or articles)
  • Auto-login (via ‘remember me’ option): cookie containing saved login details

Disable cookies

If you do not want cookies to be installed, you can disable them in your browser. Consult your browser’s help function and/or settings:

Amendments to the privacy and cookie statement

We reserve the right to amend this privacy and cookie statement. Changes will be published on this website. It is recommended that you consult this statement regularly so you will be aware of any changes.


If you disable these cookies in your browser, you will not always be able to use all the features of the Ridder website. As a result, your experience using the site may be disappointing. Disabling cookies only affects the computer and browser on which you perform this operation. If you use multiple computers and/or browsers, you will need to repeat this operation on each of them.