6 ms·

The section on “ How to avoid GDPR fines in 2022” is naïve to a fault. My personal opinion is that after recent rulings startups need to be very careful. GDPR

by mritun 5y ago

The section on “ How to avoid GDPR fines in 2022” is naïve to a fault. My personal opinion is that after recent rulings startups need to be very careful. GDPR compliance is practically a nightmare for any entity that even so much implements visitor counter with default http logging turned on. It will be interesting to see how solutions and landscape evolves once GDPR fines come to smaller companies and startups.

thaway2839 5y ago
Maybe defaults should not be designed to capture personal information. This indicates a massive need for GDPR or something like it, as opposed to the opposite. The lack of disincentives to collect personal information is why so many softwares default to collecting it. GDPR flips the equation completely, where GDPR aware software (and lots of software now market their GDPR compatibility) will default to not collecting personal information.
yawnxyz 5y ago
just embedding a tweet from Twitter's official embed code makes you violate GDPR (e.g. if you have a blog and want to reference a tweet). Twitter injects a ton of cookies and there's not much you can do about it
- elygre 5y ago
  Maybe the trickle down economy will work. First some web site operators get fined for not realizing that their subcontractor (twitter) captures personal data. They stop using said subcontractor, and at some point this trickles down to twitter, who will provide a compliant solution.
- gundmc 5y ago
  Using Google fonts is a violation now. It's a nightmare for web developers.
  - throwaway2048 5y ago
    Maybe web devs should more carefully consider how much crap third party scripts and resources inject into their sites, rather than caring about a tiny bit of convenience.
    - shukantpal 5y ago
      Maybe users should be responsible for what they intentionally run on their machines.
      - Daishiman 5y ago
        Nobody in their right mind is going to carefully peruse the cookies and injected JS scripts of every page they visit. No, the onus is clearly on the developers, who are the ones with the professional responsibility to make software that abides by the laws.
        hulitu 5y ago
        When the law is not enforced, there is no hope.
        Daishiman 5y ago
        Clearly the GDPR is being enforced
        shukantpal 5y ago
        I’m talking at the meta level. The laws can start nationalizing every company. But I think it shouldn’t. The law can put the burden on developers — but shouldn’t. I shouldn’t have to abide by some stupid rules to plug my server onto the Internet and listen on port 80.
      - white_dragon88 5y ago
        That’s absurd. That’s like saying car owners should be held responsible for how safe their car is to drive. It makes unrealistic assumptions about the competency of the end user to judge such things.
- kungito 5y ago
  Can someone explain to me how GDPR makes you responsible for twitter collecting data? It's not your faukt if twitter has their own cookies... What matters is whi stores the data who in this case is not the person embedding twitter
  - unicornporn 5y ago
    Quite simple. You just facilitated Twitter's data collection. Without you it would not have happened. Even worse, the user loading your page could probably not have known you embedded a Tweet (and sent their data to Twitter) before actually loading the page (if you didn't implement a consent dialog with a reject option).
  - CodesInChaos 5y ago
    The user only has a business relationship with the website they visit. The website is responsible for the services it employs, just like any other general contractor is responsible for their subcontractors.
- tluyben2 5y ago
  You should not do any tracking (in which case you do not need any pop-up and approval dialog) and if you put things like twitter feeds, Google analytics and Adsense, you need to have a choice for the user which, if they do not want this, will not put them on your site. The thing is; most sites do not honour your choices or make them as hard as possible as analytics and Adsense are required for monetising. Analytics can be replaced by friendly versions that are gdpr compliant without personal info storage or cookie tracking, but then your monetising (Adsense) or internet marketing (AdWords and landing pages) are not integrated into funnels and a lot harder. I have tested it with some of our assets (most of which do no tracking at all and only have 1 necessary cookie for login without SaaS cannot work) but a few have Adsense and analytics; we have a small and simply bar; accept or not accept; both is one click. ~90% (not exact as we try to compare the Google analytics which means they did say Accept vs the none cookie analytics which means both accept and not accept) clicks Accept which is enough. We use [0] by the way. [0] https://plausible.io https://plausible.io
- atoav 5y ago
  Good. If you want to quote text, copy it. Has the advantage that it still will be around once the tweet is gone or Twitter is offline. With a little css it will look the same as the original tweet to which a simple link could lead you. This is what you do if you value your users privacy. If not, then you have (under GDPR) at least give them the choice not to get these cookies. Which destroys the usability of your site for your privacy conscious users.
- Schroedingersat 5y ago
  Good. Don't foist untrusted code onto your visitors' devices.
jacquesm 5y ago
GDPR compliance is totally doable, in fact, if you take 'don't screw your users and be careful with their data' as your guideline you will make almost all of the decisions the right way. Note that fines are almost exclusively for repeat offenders, and that were they were not there was clear evidence of malice rather than accident.

by mritun 5y ago

thaway2839 5y ago

Maybe defaults should not be designed to capture personal information. This indicates a massive need for GDPR or something like it, as opposed to the opposite. The lack of disincentives to collect personal information is why so many softwares default to collecting it. GDPR flips the equation completely, where GDPR aware software (and lots of software now market their GDPR compatibility) will default to not collecting personal information.

yawnxyz 5y ago

just embedding a tweet from Twitter's official embed code makes you violate GDPR (e.g. if you have a blog and want to reference a tweet). Twitter injects a ton of cookies and there's not much you can do about it

elygre 5y ago
Maybe the trickle down economy will work. First some web site operators get fined for not realizing that their subcontractor (twitter) captures personal data. They stop using said subcontractor, and at some point this trickles down to twitter, who will provide a compliant solution.
gundmc 5y ago
Using Google fonts is a violation now. It's a nightmare for web developers.
- throwaway2048 5y ago
  Maybe web devs should more carefully consider how much crap third party scripts and resources inject into their sites, rather than caring about a tiny bit of convenience.
  - shukantpal 5y ago
    Maybe users should be responsible for what they intentionally run on their machines.
    - Daishiman 5y ago
      Nobody in their right mind is going to carefully peruse the cookies and injected JS scripts of every page they visit. No, the onus is clearly on the developers, who are the ones with the professional responsibility to make software that abides by the laws.
      - hulitu 5y ago
        When the law is not enforced, there is no hope.
        Daishiman 5y ago
        Clearly the GDPR is being enforced
      - shukantpal 5y ago
        I’m talking at the meta level. The laws can start nationalizing every company. But I think it shouldn’t. The law can put the burden on developers — but shouldn’t. I shouldn’t have to abide by some stupid rules to plug my server onto the Internet and listen on port 80.
    - white_dragon88 5y ago
      That’s absurd. That’s like saying car owners should be held responsible for how safe their car is to drive. It makes unrealistic assumptions about the competency of the end user to judge such things.
kungito 5y ago
Can someone explain to me how GDPR makes you responsible for twitter collecting data? It's not your faukt if twitter has their own cookies... What matters is whi stores the data who in this case is not the person embedding twitter
- unicornporn 5y ago
  Quite simple. You just facilitated Twitter's data collection. Without you it would not have happened. Even worse, the user loading your page could probably not have known you embedded a Tweet (and sent their data to Twitter) before actually loading the page (if you didn't implement a consent dialog with a reject option).
- CodesInChaos 5y ago
  The user only has a business relationship with the website they visit. The website is responsible for the services it employs, just like any other general contractor is responsible for their subcontractors.
tluyben2 5y ago
You should not do any tracking (in which case you do not need any pop-up and approval dialog) and if you put things like twitter feeds, Google analytics and Adsense, you need to have a choice for the user which, if they do not want this, will not put them on your site. The thing is; most sites do not honour your choices or make them as hard as possible as analytics and Adsense are required for monetising. Analytics can be replaced by friendly versions that are gdpr compliant without personal info storage or cookie tracking, but then your monetising (Adsense) or internet marketing (AdWords and landing pages) are not integrated into funnels and a lot harder. I have tested it with some of our assets (most of which do no tracking at all and only have 1 necessary cookie for login without SaaS cannot work) but a few have Adsense and analytics; we have a small and simply bar; accept or not accept; both is one click. ~90% (not exact as we try to compare the Google analytics which means they did say Accept vs the none cookie analytics which means both accept and not accept) clicks Accept which is enough. We use [0] by the way. [0] https://plausible.io https://plausible.io
atoav 5y ago
Good. If you want to quote text, copy it. Has the advantage that it still will be around once the tweet is gone or Twitter is offline. With a little css it will look the same as the original tweet to which a simple link could lead you. This is what you do if you value your users privacy. If not, then you have (under GDPR) at least give them the choice not to get these cookies. Which destroys the usability of your site for your privacy conscious users.
Schroedingersat 5y ago
Good. Don't foist untrusted code onto your visitors' devices.

jacquesm 5y ago

GDPR compliance is totally doable, in fact, if you take 'don't screw your users and be careful with their data' as your guideline you will make almost all of the decisions the right way. Note that fines are almost exclusively for repeat offenders, and that were they were not there was clear evidence of malice rather than accident.