Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

So, the problem with this is: the law. If you use session management: GOOD NEWS GDPR AND CPPA UNDER PENALTY OF THE COURTS DEMAND YOU INFORM USERS and if you know a better way than an intrusive "accept this before you can continue" by all means pipe up but the problem is overbearing laws, not "people following them". The law requires that you disallow access until people tell you their position on your handling of their personally identifiable information and welcome to modern web dev hell. If you don't like it, hell has done its job.

Both Europe and California consider IP addresses PII and this is the result.



Session management does not require a cookie consent. Implementation-relevant technical cookies are exempt, it's the 337 different analytics services that sites use that require the cookie consent


1. you don't need consent for functionality strictly required for the functionality of your product. Such as session management

2. You are allowed to legitimately process PII for legitimate purposes related to your business: e.g. combating fraud

3. What you emphatically aren't allowed without consent: collect vast amounts of data, store it indefinitely, and sell it to 15 000 third party "partners"


gdpr works a bit differently. You can use cookies for providing website operations, for it you don't even need a banner. You can't easily use cookies/trackers for ad purposes. You can still display ads but these shouldn't use cookies (this way again - no need for banner).




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: