• Resolved woorooo

    (@woorooo)


    Hi guys,

    Recently I was trying to make Geodirectory work with the Complianz Plugin and unfortunately I was told it was basically not possible without some cooperation from Geodirectory developers. This is the message I received from their support team:

    As the WP Geodirectory plugin does not seem to account for GDPR requirements (such as disabling Google Maps functionality before consent), it would indeed not be GDPR-proof.

    This specific case is a difficult one, because if we’d block everything related to the script (without cooperation from the plugin author), certain functionality of the Geodirectory plugin would likely break completely. Due to the nature of this plugin, it would be very difficult for us to create a stable integration without the cooperation of the developers of this plugin.

    The best course of action would be to contact the developer and recommend them to conform to the WP Consent API (https://github.com/rlankhorst/wp-consent-level-api). In short, this API proposal is a standardized way for WordPress core, plugins, and themes to obtain consent from users.

    Would appreciate any feedback if that is indeed the case, and if you plan to make GD GDPR compliant in the future.

    Thank you,

    Roman.

Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Author Stiofan

    (@stiofansisland)

    Hey Roman,

    I have not used that specific plugin before.

    Currently we have compatibility with this premium plugin https://borlabs.io/borlabs-cookie/

    Other than that you can set the maps to only load on click, this setting is found under GeoDirectory > Settings (advanced) > Lazy Load Maps > Load Maps on click.

    Thanks,

    Stiofan

    Thread Starter woorooo

    (@woorooo)

    Hi Stiofan,

    I have not found any information on Borlabs integration with GD, can you explain how it works? Does it automatically block all non-essential GD cookies and replaces maps with some kind of image requesting user to consent?

    Thank you,

    Roman.

    Plugin Author Stiofan

    (@stiofansisland)

    Hi Roman,

    I am very sorry, the task for this was never 100% finished and therefore not in core, i thought it was added a long time ago, this will be in the next release.

    In the meantime, i would suggest changing the maps to “click to load” which will prevent cookies from loading until a user click.

    You can follow the task here to see when its added to core (should be today) https://github.com/AyeCode/geodirectory/issues/1682

    Thanks,

    Stiofan

    Plugin Author Stiofan

    (@stiofansisland)

    FYI, Google maps (and OSM) no longer seem to set cookies so this should not even be needed. If you are seeing cookies set, please clear them (might be old) and then refresh, if you still see them set let me know and i do not see them in any of my test sites.

    Thanks,

    Stiofan

    Aert

    (@aahulsebos)

    Hi @stiofansisland,

    Anyway we can help to integrate with Complianz as well? Some documentation, https://complianz.io/developers-guide-for-third-party-integrations/

    You can contact us there as well,

    regarding cookies, it’s about the API call to Google.

    regards Aert / Complianz.io

    Plugin Author Stiofan

    (@stiofansisland)

    Hi @aahulsebos,

    I have added a task for us to add compatibility with your plugin.

    Thanks,

    Stiofan

    Hi,

    I just wanted to check status on this, sounds like it would be a great match?

    @stiofansisland , I’m using GeoDirectory suite and I was looking for possible cookies set but strangely it seems like google maps sets cookies sometimes but not always (I tried multiple sessions clearing cookies in between). Did you find anything else there?

    Thanks!

    Plugin Author Stiofan

    (@stiofansisland)

    Hi @aggk,

    Cookies seem to be related to address searches only (as far as I can tell).
    We are currently working on this task, it should be in version v2.1.0.17

    Thanks,

    Stiofan

    Thank you Stiofan!

Viewing 9 replies - 1 through 9 (of 9 total)

The topic ‘GDPR Compliance’ is closed to new replies.