Re:How Google is forcing us to make our open source VoIP app...
by happymellon on Thursday October 20, 2022 @03:38PM
(#33279616)
Indeed, and you can also use cookies without requesting permission.
Re:How Google is forcing us to make our open source VoIP app...
by colejohnson66 on Thursday October 20, 2022 @05:01PM
(#33280643)
For example, a login cookie is “essential” and does not require consent
Re:How Google is forcing us to make our open source VoIP app...
by someweirdperson on Thursday October 20, 2022 @08:20PM
(#33282617)
But don't start that php session (which sets the session cookie) before the user sends login credentials.
Re:How Google is forcing us to make our open source VoIP app...
by happymellon on Friday October 21, 2022 @12:38AM
(#33284573)
You are allowed a session cookie if it is for the operation of a website.
You don't need to ask permission to store a shopping cart or anything like that as a cookie.
Re:How Google is forcing us to make our open source VoIP app...
by someweirdperson on Friday October 21, 2022 @03:45AM
(#33285561)
I agree, it's not necessarily only login credentials, but could be a shopping cart. However, no shopping cart is needed until the user adds an item to it. Watching the shopping window doesn't need a cookie.
The typical practice seems to be to set a session-cookie unconditionally, to be able to store user-related data within that session, even if the user has not provided any such information.
Re:How Google is forcing us to make our open source VoIP app...
by happymellon on Friday October 21, 2022 @04:23AM
(#33285807)
Are you using that cookie for tracking or analytics?
If not then that's fine.
The GDPR is exactly the same. Even the ePrivacy Directive (the so-called "cookie law") actually covers more than just cookies - any method of storage in a user's terminal (whether browser local storage, or an app's own database) is also in scope.