No prior consent

  • Resolved niblan7

    (@niblan8)


    2 years, 11 months ago

    Hello,

    Scanning my site with some online services about GDPR compliance, there are some problems about prior consent. I have a pdf file with the result of scan, but it’s not possible to attach it. Could you please tell me if there is some specific configuration of the plugin to solve the issue?

    Thank you in advance.

    Best regards.

    The page I need help with: [log in to see the link]

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Contributor Jarno Vos

    (@jarnovos)

    2 years, 11 months ago

    Hi @niblan8,

    Which service(s) does the report mention that are not yet blocked before obtaining prior consent?

    Kind regards, Jarno

    Thread Starter niblan7

    (@niblan8)

    2 years, 11 months ago

    Hi Jarno,

    Thank you for your time.

    These are the cookies not blocked before obteining prior consent:

    • VISITOR_INFO1_LIVE
    • YSC
    • ct_cookies_type
    • ct_has_scrolled
    • apbct_site_landing_ts
    • bot_detector_browser_supports_cookies
    • bot_detector_event_token
    • bot_detector_has_scrolled
    • bot_detector_headless
    • bot_detector_mouse_moved
    • bot_detector_page_hits
    • bot_detector_page_start_timestamp
    • bot_detector_pointer_data
    • bot_detector_referrer
    • bot_detector_referrer_previous
    • bot_detector_screen_info
    • bot_detector_user_agent

    The first two of them are related to Youtube, while the other ones are related to CleanTalk.

    Thank you again.

    Best regards.

    Plugin Contributor Jarno Vos

    (@jarnovos)

    2 years, 11 months ago

    Hi @niblan8,

    YouTube

    The YouTube cookies (VISITOR_INFO1_LIVE, YSC) are loaded when your theme calls the YouTube API, which is done in a theme file called core.js.

    Blocking that core.js file with Complianz is possible and will block YouTube to prevent the cookies from being set, however, it will break other functionalities from your theme as these are included in the same core.js file.

    A solution in this case would have to be provided by your theme developer, they can integrate with Complianz to ensure that the YouTube API is only enabled after consent has been obtained.

    CleanTalk

    This security tool will set a number of items in the LocalStorage of your browser (used to detect/filter requests from bots). I would expect that these can be regarded as “Functional”, although your CookieBot report doesn’t seem to classify them as such.

    While you can block the tool with Complianz and stop it from creating those cookies/items, this means that you are effectively preventing the anti-spam solution from performing its’ functions and protecting your site; at least before consent is obtained.

    If you still want to proceed with blocking your anti-spam solution (which I do not recommend), you could do it by using this configuration under Complianz > Integrations > Script Center > Block a script, iframe or plugin.

    Kind regards, Jarno

    Thread Starter niblan7

    (@niblan8)

    2 years, 11 months ago

    Hi Jarno,

    Thank you again for your help.

    From what you have explained I’ve understood that it is better not to block the CleanTalk cookies.

    About the Youtube cookies, I am waiting for a reply from the customer service of my theme.

    Thank you.

    Best regards,

    Nicola

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

The topic ‘No prior consent’ is closed to new replies.