• Resolved lang74

    (@lang74)


    The Complianz generated Cookie Policy page has the following Cookies as “purpose pending investigation”:

    _I_
    WP_DATA_USER_2
    mtnc_upsell_shown_timestamp
    mtnc_upsell_shown
    __ssid

    I have tried to use the Complianz wizard to sync Cookies many times and this has no effect. I have searched for the cookies at?https://cookiedatabase.org/?and they cannot be found + I have submitted a request for the cookies to be added but this has had no impact.

    Having read support tickets, I understand the following options are available:
    – Manually update the cookies service/purpose/function in Complianz Wizard
    – Untick “Show on Cookie Policy” in Complianz Wizard
    – “Delete” cookies in Complianz Wizard

    My concern with all of these options is that I don’t know what the service/purpose/function of these Cookies are and I don’t want to cause issues because of these changes.

    What is the best solution to ensure there are no ‘purpose pending’ cookies on the Complianz generated Cookie Policy page in this instance?

    Thanks for your help!

Viewing 1 replies (of 1 total)
  • Plugin Support fritsiub

    (@fritsiub)

    Hello Lang74,

    Thank you for your message.

    I’m afraid we’re limited in providing you with a exact answer as we can provide absolutely zero legal advice. If the cookies are actually released from your domain I’d suggest you not to delete the cookies or to not have them show in the Cookie Policy.

    The best advice I could give is to research which services these cookies belong to, and to set a cookie purpose (category) based on your understanding of that specific service. You could even reach out to those service providers asking them for guidance on the cookies that their services use.

    If you then manually add these purposes to said cookies, they should show under those categories in your Cookie Policy and thus you won’t see ‘Pending’ cookies anymore.

    I hope this helps!

Viewing 1 replies (of 1 total)
  • You must be logged in to reply to this topic.