No cookies / Session or Local Storage by default

  • antmg

    (@antmg)


    1 year, 6 months ago

    I’m trying to create a site that doesn’t drop any cookies, or store any data in local or session storage until the user consents to make a compliant website (the “cookie law” pertains to any storage on the user’s device, not exclusive to cookies).

    I’ve wrapped youtube embeds in something that won’t render the embed unless a consent cookie exists (since simply by showing it on the page it writes a load to localstorage), but there’s still the wpEmojiSettingsSupports data getting written to session storage. I’ve found a disable emoji plugin but it bothers me that if that somehow falls out of date with changes in wordpress that the site will revert to storing data on the first page load (before consent) again.

    Could there be settings to disable this emoji script built into wordpress (and therefore sure to be maintained / compatible with future versions of wordpress), ideally disabled by default?

    • This topic was modified 1 year, 6 months ago by antmg.
Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter antmg

    (@antmg)

    1 year, 6 months ago

    Or perhaps could the functionality be pulled out into a regular plugin that can be disabled, but could be installed by default on a fresh install (or completely independent of course)

    • This reply was modified 1 year, 6 months ago by antmg.
    threadi

    (@threadi)

    1 year, 6 months ago

    You can also deactivate emoji support with your own code. See: https://smartwp.com/disable-emojis-wordpress/

    However, with every update there is a theoretical risk that something will change functionally that you or one of the plugins you use relies on. You cannot prevent this. You have to check after each update whether your WordPress still works the way you want it to. By the way, this is exactly what staging systems are used for – copies of the live website in which you can test updates before you apply them to the live system.

    Thread Starter antmg

    (@antmg)

    1 year, 6 months ago

    Hi,

    Indeed I see it’s possible to do at least for now. It’s concerning that as soon as you deploy a WordPress site you’re instantly not compliant until you get emojis disabled.

    Fines for being non-compliant can be pretty high.

    And as said by @threadi a future update could cause the disabling of the emojis to break (eg by renaming the scripts), silently becoming non-compliant again, which means a call between disabling auto updates and reviewing the situation manually on on offline second install before allowing each update as you can’t have it accidentally going live in a non-compliant way.

    Even if you’ve got a GDPR / CCPA notice on the page, this data is written on the first page load, so before they have a chance to accept.

    I guess this is a feature request to have a built in mechanism to disable (or preferably disabled by default so a fresh install is compliant with US / European laws) for the emoji plugin.

    Thread Starter antmg

    (@antmg)

    1 year, 6 months ago

    I’ve just discovered this was done as an optimization quite recently here: https://core.trac.wordpress.org/changeset/56074 

    I’m surprised it got merged, and I’d say it should be reverted ASAP as I’m sure people are not realising it’s happening on their sites and that they are non-compliant with the relevant privacy laws.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘No cookies / Session or Local Storage by default’ is closed to new replies.