GDPR compliance

[pmaojo]

This gem is ok with the new law?
The cookies should be disabled for rails if user declines their use.
It would also be a good feature to be able to be more strict, not allowing cookies until the user clicks OK.
I'll see if I can help.

[damonbakker]

I think there needs to be some form of modification.
The user should be able to disable all optional categories of cookies. Only necessary cookies shouldn't be able to be opted out of by the user as far as I'm aware.

[gabskoro]

Not sure if we really should complicate with this, we should be honest, we need cookies, if they don't allow it, they should leave the page.

[pmaojo]

Own cookies (session for example) are needed and should not be blocked only third party cookies are a problem for the law.

[scarroll32]

Do you mean GDPR compliance?

[gabskoro]

@seanfcarroll I think he just made a typo :)

@pmaojo So, how did you imagine that? Having a "Not agree" button which will call a method in which you can do whatever you want?

[pmaojo]

GDPR in English
RGPD in Spanish

[pmaojo]

@gabskoro The button should be "Agree", but if the Agree cookie is not set, all cookies should be rejected. In Spain, in theory, third party cookies that store data that could identify user should be disabled until user allows them.

[hlascelles]

Yes, looks like this is still a necessary change. We probably also need a configurable list of cookies, put into categories (mandatory, analytics etc...), that the user can opt into and out of.

[gabskoro]

I think this gem should not be in charge of that. Maybe we could just render a "NO" button which will trigger a specific route and then you can block whatever you would like. What do you think?