GDPR-Compliant Cookie Consent
Information About the Cookies Used
Section titled “Information About the Cookies Used”WP-ImmoMakler sets cookies that should be disclosed in your privacy policy and in a cookie consent banner. The following cookies are classified as technically necessary:
- Navigation within property listings
- Remembering the selected sort order
- Saving properties to the favorites list
- Cookie names:
wp-immomaklerfor navigation and sorting,wp-immomakler-cartfor the favorites list (from version 5.70.0; before that, the favorites list was also stored in thewp-immomaklercookie) - Lifetime: 8 days
- Data transmission: exclusively to the website operator; no data is shared with the plugin manufacturer
Blocking Google Maps from Version 5.36
Section titled “Blocking Google Maps from Version 5.36”Starting with version 5.36, WP-ImmoMakler automatically blocks Google Maps displays and does not set any cookies without explicit visitor consent. Please verify that this feature is working correctly on your website. If you are using an older version, update the plugin via your shop customer account or contact support.
You can disable the native consent box in WP-ImmoMakler if you prefer to block Google Maps through Borlabs Cookie instead.
Blocking YouTube and Vimeo Videos from Version 5.66
Section titled “Blocking YouTube and Vimeo Videos from Version 5.66”Starting with version 5.66, WP-ImmoMakler displays videos on the property detail page as a preview image with a play button. The video only plays in a lightbox after a click. For YouTube and Vimeo videos, WP-ImmoMakler obtains visitors’ consent before playback — as with the Google Maps consent box, consent is stored in the browser’s local storage.
The preview images are cached server-side and served from your own website. Before consent is given, visitors’ browsers therefore transmit no data to YouTube or Vimeo. Once consent is given, YouTube videos play in the privacy-friendly youtube-nocookie mode.
You can disable this behavior in your website’s backend (wp-admin) under WP-ImmoMakler → Settings → Display if you prefer to implement video blocking with a third-party consent plugin instead. Videos will then be embedded directly in the page as before.
Blocking Virtual Tours from Version 5.66 (PLUS)
Section titled “Blocking Virtual Tours from Version 5.66 (PLUS)”Starting with version 5.66, WP-ImmoMakler also displays virtual tours on the property detail page as a preview image with a 360° button. The tour only opens in a lightbox after a click. Before opening, WP-ImmoMakler obtains visitors’ consent to the data transmission to the respective provider — the consent box names the provider and links to its privacy policy. Consent is stored per provider in the browser’s local storage.
The preview images are automatically determined from the tour’s provider — including Matterport, Ogulo, Giraffe360, and Feelestate — cached server-side, and served from your own website. Before consent is given, visitors’ browsers therefore transmit no data to the tour provider.
You can disable this behavior in your website’s backend (wp-admin) under WP-ImmoMakler → Settings → Display if you prefer to implement tour blocking with a third-party consent plugin instead. Virtual tours will then be embedded directly in the page as before.
Integration with Borlabs Cookie
Section titled “Integration with Borlabs Cookie”Version 3.x
Section titled “Version 3.x”The Borlabs library includes a compatibility patch that blocks Google Maps in WP-ImmoMakler. Borlabs classifies the cookies set by WP-ImmoMakler as technically necessary, so no separate consent is required — please have this verified by your data protection officer.
Version 2.x
Section titled “Version 2.x”Compatibility with Borlabs Cookie 2.x has been built into WP-ImmoMakler since version 5.13. The settings are pre-populated automatically; you only need to complete the following steps in the dashboard.
Step 1: Open the Borlabs Cookie settings and navigate to the section for external services.
Step 2: Create a new cookie entry for Google Maps or adjust the existing entry.
Step 3: Save the configuration and test the blocking in a private browsing window.
