Cookie-List – what all is shown here without further explanation?

Hi @bestcases,

We would gladly investigate what service places these Cookies. Would it be possible for you to provide an URL to the website in question, so we can check this?

You may also reach out to us by e-mail on: support(at)complianz.io. If you attach the system status report (Complianz > Dashboard > Tools > System Status) to your e-mail as well, this will provide us with a list of plugins that could be responsible for placing these.

Kind regards,
Jarno

Hello.

I will gladly provide any information you might require.

The one thing I can not realize is access to the site. It’s in development state and on a local staging setup.

For now I will supply the system status report.
I will supply it here in the forum, since it might be of use for others, assuming this way of communicating is OK with you.

One question upfront: The site is a MULTISITE – could this cause issues with complianz?

Domain:https://mysite.local
Detected console errors: none found

General
---------
Plugin version: 6.0.6
WordPress version: 5.8.3
PHP version: 7.4.25
Server: Apache
Multisite: yes

Active plugins: 

General settings
---------

Wizard settings
---------
regions : eu
eu_consent_regions : yes
california : yes
wp_admin_access_users : yes
cookie-statement : generated
privacy-statement : custom
impressum : custom
disclaimer : none
organisation_name : First Last
address_company : Streetname
12345 CITY
country_company : DE
email_company : [email protected]
telephone_company : 
records_of_consent : no
respect_dnt : no
compile_statistics : no
accepted : 0
no-sharing : 0
ip-addresses-blocked : 0
accepted : 0
no-sharing : 0
ip-addresses-blocked : 0
matomo_anonymized : 
consent_for_anonymous_stats : yes
configuration_by_complianz : no
yandex_id : 87
yandex_ecommerce : no
uses_thirdparty_services : no
google-fonts : 0
google-recaptcha : 0
google-maps : 0
openstreetmaps : 0
vimeo : 0
youtube : 0
videopress : 0
dailymotion : 0
soundcloud : 0
paypal : 0
spotify : 0
hotjar : 0
addthis : 0
addtoany : 0
sharethis : 0
livechat : 0
hubspot : 0
calendly : 0
block_recaptcha_service : no
block_hubspot_service : no
uses_social_media : yes
facebook : 0
twitter : 0
linkedin : 0
whatsapp : 0
instagram : 0
tiktok : 0
disqus : 0
pinterest : 0
uses_firstparty_marketing_cookies : no
uses_ad_cookies : no
uses_ad_cookies_personalized : no
uses_wordpress_comments : yes
block_wordpress_comment_cookies : yes
region_redirect : no

I am surprised, that your report does not list any active plugins. There are some wordpress-plugins installed, or are the plugins which are supposed to be listed there specific plugins for complianz?

Hi @bestcases,

The plugin works fine on multisite installations as well, though it seems that the list of active plugins isn’t being attached when generating the System Status report on a multisite. I’ve raised that within the team for investigation.

Attaching screenshot(s) of the plugin of the active plugin list would be the workaround for now, which can either be done here, or through our support mail.

Kind regards,
Jarno

Hi, @bestcases,

Could you post a URL, or at least a plugin list so we can have a look, probably a module from your theme or plugin that use a slider or carousel.

regards Aert

Hello.

An URL is not possible at this point, because the site is on a LOCAL staging environment.

Here is a list of all installed (active and inactive) plugins.

View post on imgur.com

Thank you.

Hi @bestcases,

Thank you for the screenshot. Coincidentally, another user posted a thread where we noticed these same cookies.

tADu, tTE, tMQ, tADe, tAE, tC, tTf, tTDe, tTDu, tnsApp, t3D, tPL, tk_qs seem to be LocalStorage set by Gutenberg-centered page builders. These are used on the front-end and classify as Functional.

The information on cookiedatabase.org will soon be updated accordingly.

Hope this helps for now!
Kind regards,
Jarno

Hi @bestcases and @jarnovos

Just wanted to inform you that Cookiedatabase.org has been updated and the kadence pagebuilder cookies have now been “published”.

Hello and thank you for the update of the Database @jarnovos & @paapst.

Glad this is sorted out. Still am wondering, that with so many users of you software, none had the Kadence-issue before. Kadence seems to be pretty widely used these days.

From your (professional) point of view: Why would Kadence use so many cookies on the front end for the user? My layman point of view is: Something must be wrong somewhere…? Any thoughts?

It seems wrong to have that many cookies in the list for the end user, just because of Kadence. Are you in contact with their developers and can elaborate this question/issue?

One cookie is still “unknown” / “Cookies without selected service”: “sp_*” (as already shown on the initial picture above).

@bestcases

The problem with sp_ is indeed that we do not know what service or vendor places that particular cookie. Maybe you can help us track it down?

Kadence is being built upon an existing page builder framework that already placed this huge amount of cookies in the past. That information was already available as pending data (we have around 14000 pending cookies) in the backend of cookie database, but it was not until now that we realised that Kadence is using those same cookies.

I sure will try to help tracking it down.

For clarification: In case I deactivate a plugin, then the corresponding cookies will not be “active” anymore, meaning Complianz will not find them?

Am I correct with the above assumption? If so, I guess I have to deactivate plugings, until the cookie in question is gone. With that, we will know where the cookie comes from. Is this the way to go? If not: Let me know what to do to get this last cookie sorted out.

In regards to Kadence: I did like this plugin for Gutenberg, but with all the cookies, and if it’s build on an existing framework, I wonder how clean the code is. Maybe one should put Kadence aside, if a clean running website is the goal?
If you have an further information in regards to the “existing framework” before Kadence, I would like to hear. Maybe this is the wrong place here?
However: If you happen to be in contact with their developers, I would appreciate pointing them at this thread, because I firmly believe, they have to sort out this mess with all these cookies, if they want to survive and thrive in today’s market with all the cookie banners, and data protection acts. For me at least, it’s pretty much a no-go to show site-visitors 10+cookies, just because of the Kadence plugin. And in case I am wrong in regards to my view on the massive usage of cookies, I would like to hear it too. I’m pretty good at changing my point of view, as soon as good information comes along ??

I did deactivate Kadence Blocks, and did switch from the Kadence theme to the native WP-theme. Then did re-scan for cookies.

All the cookies which are from Kadence, are still there. I assume, there must be something off. Maybe the cookies are not from Kadence after all? They should be gone with Kadence disabled, right?

Here is a screenshot:

View post on imgur.com

Would be great to hear back. Did also ask Kadence about the cookies. Maybe they will chip in.
—————————–
Did activate Kadence Blocks and the Kadence Theme again. Opened the site.
If Complianz is deactivated, my site in it’s current state will not set cookies at all, but has a few with Complianz activated, there are a few, but only Complianz itself. See the picture.

View post on imgur.com

So the question at this point is:
Why does Complianz find all these cookies in the back-end, when it scans, while there are none on the front-end?

• This reply was modified 2 years, 9 months ago by bestcases.

Hi @bestcases
As Complianz scans the cookies set in your browser, it is possible it picks up cookies that were installed previously, but are not active anymore.

On the cookie scan page, you can use the “clear cookies” option. Then also clear your browser cache to make sure all cookies are cleared.

If you then run a new cookie scan, these cookies won’t appear again if they aren’t used on your site anymore.

Let me know if that helps.

OK. Thank you.

I did clear all cookies for the domain of my (staged) site.

Then – with the deleted cookies – I had to login again to perform Complianz cookie scan.

Below is what Complianz found, vs what is in the browser.
According to the browser, Complianz should hardly find anything. What am I missing?

Note the cookie “Youtube” shows nothing, but “no data present for this host”, so I did not make another screenshot for YT-cookies.

View post on imgur.com

Currently I don’t know how to proceed to get a clean (and law abiding) cookie banner..

If you have no other idea why these names keep popping up, and if you are absolutely sure that you have indeed deleted the local storage and are no longer using a Gutenberg centered page builder (such as Kadence) I would suggest manually deleting those names from your cookie policy. They are actually classified as being “functional”, so there is no legal need to ask for consent anyway. But if they are being placed you still need to inform you visitor about them. This is why I usually say, better safe than sorry.
Maybe @jarnovos might have some additional ideas about what can be going on.

Thank you for getting back to me.

I guess, I should attempt to clarify the current scenario/situation:

In the test from my previous post, Kadence was activated again.
I however could not see the cookies found by scanning with Complianz in the browser, as the picture shows.

Maybe I have a wrong understanding about how Complianz finds cookies.

From one of your previous posts

As Complianz scans the cookies set in your browser, it is possible it picks up cookies that were installed previously, but are not active anymore.

I did get the idea, that Complianz will just check the cookies currently in the browser. This however does not seem the case, so I guess I misunderstood.

Question:
Where can I learn about the process how Complianz determines which cookies will be found by the “Scan”? It clearly does not (just) utilize the cookies currently set in the browser.

Clarification:
If I deactivate Kandence Theme, the cookies will not be found by the Complianz Scan, even if Kadence Blocks is activated. So is seems, the cookies are coming from Kadence Them, not Kadence Blocks. Maybe it’s useful to update the Cookie-Database, so is shows that the cookies belong to Kadence Theme, rather than just “pagebuilder”. Or are such details not desired/useful in the database?

Thank you for the help, I guess there is some light at the end of the tunnel ??