Hi there! When I run the Cookies scan in the Complianz Wizard, it finds the WordPress cookies wp-settings and wp-settings-time. (See screenshot below.)
Both of the cookies you mentioned are actually present in our cookiedatabase.org, but they’re listed under a wildcard pattern that catches all the variants:
wp-settings-* covers wp-settings, wp-settings-1, etc.
wp-settings-time-* covers wp-settings-time and its numbered variants.
So the entries you linked to are correct, and the plugin should be picking them up via these wildcards.
Could you please try re-running not only the cookie scan but also the sync with cookiedatabase.org itself, and let us know if the cookies get properly associated afterwards? Sometimes a fresh sync resolves the mismatch.
For reference, I tried to reproduce the issue on my local setup and the sync works correctly on my end, both cookies are detected and assigned to the right service, so it might be a sync state on your specific install that needs refreshing.
Strangely, when I now go try to re-run the website scan, it starts itself automatically when I load the step in the wizard and it gets stuck for hours (infinitely) at “The scan found 23 cookies on your domain. Scanning, 75% complete.” It never progresses forward.
I’ve tried closing and re-opening the page, re-completing the whole Wizard flow again, refreshing the page. Nothing seems to change it being stuck at 75%. I’m afraid to uninstall the plugin because I don’t want to lose our two policy pages.
Is there any assistance you could provide in helping get this scan unstuck? Thanks so much, again, for your response!