News for hackers. Stuff that matters.
Re:GDPR Enforcement Tracker: List of GDPR fines by TomVDB on Tuesday June 25, 2019 @06:40PM (#20279843)
Last year, when GDPR was heavily discussed, people were criticizing those who decided to just stop their small hobby websites because of the potential GDPR exposure.

The argument back then was that they were overreacting, that we didn't understand how Europe works, that you'd only get fined after repeated warnings about violating procedures etc.

I'm sure the private person was dumb for doing what he did, but that doesn't invalidate the general point: unless you're sure you that can afford making these kinds of mistakes, don't provide a service on the internet that might be used by EU citizens.

The benefits, whatever they might be, just don't justify the risks.

Re:GDPR Enforcement Tracker: List of GDPR fines by NeedMoreTea on Tuesday June 25, 2019 @07:45PM (#20280442)
Except we see just the fine. We have no idea how many attempts and warnings to get them to comply were sent first. It wasn't one email, it was multiple emails, multiple times over months.

This site makes no mention of warnings and escalations, and ICO at least doesn't normally announce that for individual cases. Though they do put out aggregate stats. When they have fines are clearly shown as arising in a small minority of cases.

Re:GDPR Enforcement Tracker: List of GDPR fines by easytiger on Wednesday June 26, 2019 @08:18AM (#20284180)
There are other examples at least from Germany where no warning or time to rectify was given, just a fine.

https://iapp.org/news/a/germanys-first-fine-under-the-gdpr-o...

Re:GDPR Enforcement Tracker: List of GDPR fines by NeedMoreTea on Wednesday June 26, 2019 @11:51AM (#20286127)
800k email records and passwords in plain text when breached. I don't know how big Knuddels are, so I don't know if that fine sounds lenient, right or high. Yet as it's a large breach it seems fitting of no warning first, considering the scale of negligence, mitigated by their "exemplary cooperation" afterwards.

Which goes to show why the regulators get the discretion to decide appropriate action from warning only to maximum fine. Without context and aggravating and mitigating factors we can't know, which was my point. If a penalty is disproportionate there's well worn appeal tracks.

Other comments seem to point to the small case in OP comment being some guy running a list to harass people, which seems like a huge aggravating factor to me. Maybe he got one warning, maybe in context he didn't deserve even that.

Re:GDPR Enforcement Tracker: List of GDPR fines by TomVDB on Tuesday June 25, 2019 @07:55PM (#20280541)
> We have no idea how many attempts and warnings to get them to comply were sent first.

True. But I doubt that even the most ruthlessly efficient GDPR enforcement authority could multiple enforcement requests between mid July and end July.

Re:GDPR Enforcement Tracker: List of GDPR fines by sgift on Wednesday June 26, 2019 @03:01AM (#20282519)
Why are multiple requests needed? You do shit, you get a request to stop it, you don't do it, you get hit with a fine. How many requests do you expect the authorities to send? 5? 10? 100? If I get summoned to court and don't follow it I get a fine. How is this any different?
Re:GDPR Enforcement Tracker: List of GDPR fines by NeedMoreTea on Tuesday June 25, 2019 @08:09PM (#20280633)
Sure, but offences between July and September 2018, and convicted Feb 2019 only against the small sub selection in July.

There's potential time for quite a few ignored warnings before prosecution, but I don't know and can't find out from here if or if not.

Re:GDPR Enforcement Tracker: List of GDPR fines by tjoff on Wednesday June 26, 2019 @01:52AM (#20282236)
They almost certainly got complaints from the users on that list. You tend to get pretty swift response from that.

Very likely that they just ignored it.

Re:GDPR Enforcement Tracker: List of GDPR fines by comboy on Tuesday June 25, 2019 @08:14PM (#20280667)
> unless you're sure you that can afford making these kinds of mistakes, don't provide a service on the internet

DOT

sounds good

Re:GDPR Enforcement Tracker: List of GDPR fines by llao on Wednesday June 26, 2019 @01:52AM (#20282237)
What does DOT mean?
Re:GDPR Enforcement Tracker: List of GDPR fines by comboy on Wednesday June 26, 2019 @07:42AM (#20283979)
.
Re:GDPR Enforcement Tracker: List of GDPR fines by llao on Wednesday June 26, 2019 @11:01AM (#20285646)
Thanks, I thought it was some acronym.
Re:GDPR Enforcement Tracker: List of GDPR fines by losvedir on Wednesday June 26, 2019 @09:08AM (#20284557)
What does . mean?
Re:GDPR Enforcement Tracker: List of GDPR fines by comboy on Wednesday June 26, 2019 @09:26AM (#20284753)
It is used for several purposes, the most frequent of which is to mark the end of a declaratory sentence. (why are we doing this?)
Re:GDPR Enforcement Tracker: List of GDPR fines by tremon on Thursday June 27, 2019 @06:10AM (#20293078)
I thought English uses PERIOD to verbally mark the end of a declaratory sentence, not DOT. That's probably where the confusion comes from.
Re:GDPR Enforcement Tracker: List of GDPR fines by triplesec on Tuesday July 09, 2019 @01:10PM (#20394113)
To be strictly accurate, English uses 'full stop', and American English uses 'period'.
Re:GDPR Enforcement Tracker: List of GDPR fines by comboy on Thursday June 27, 2019 @06:28AM (#20293183)
I should have written "period".
Re:GDPR Enforcement Tracker: List of GDPR fines by TomVDB on Tuesday June 25, 2019 @08:19PM (#20280708)
Everybody makes mistakes. Which makes GDPR a recipe to hand over whatever remains of the Internet to only corporations that afford paying for them.
Re:GDPR Enforcement Tracker: List of GDPR fines by comboy on Tuesday June 25, 2019 @08:48PM (#20280872)
Sure, but there are different kind of mistakes. Surgeon can make a mistake, but it's a different kind of mistake if instead of a surgeon, a plumber cuts the patient with a kitchen knife.

I agree it's a difficult problem and it's hard to define boundaries, but some level of competence is welcome when handling data that belongs to other people.

If you start some internet service, I expect you not to lose my data (in some lame way, s.h.), just like I expect my car mechanic not to destroy my engine.

edit: to give it context, I closed my programming website with thousands of active users that I had for almost 20 years because of GDPR, I'm not a big fan of it, but what I like even less is when complete incompetence when handling personal data results in zero consequences

Re:GDPR Enforcement Tracker: List of GDPR fines by cyphar on Wednesday June 26, 2019 @12:10AM (#20281831)
Yes, people make mistakes. And by deciding to create a business around other people's personal information some mistakes are bad enough to merit a fine.

All sorts of civil offences and crimes can be mistakes. While "it was an accident" might lower the penalty it doesn't negate the fact the mistake was made and people might have been hurt.

The idea that we should hold companies that profit off people's personal data blameless if they manage to "make a slip-up" with it is absurd. The only other industry where we accept those kinds of mistakes is Wall Street and we all know how well that policy has gone.

Re:GDPR Enforcement Tracker: List of GDPR fines by closeparen on Wednesday June 26, 2019 @01:36AM (#20282165)
>deciding to create a business around other people's personal information

>profit off people's personal data

Have you "decided to create a business around destroying the environment" and "profit off CO2 emissions" because your office is heated in the winter? GDPR is not specific to the adtech or data brokerage industries.

Re:GDPR Enforcement Tracker: List of GDPR fines by cyphar on Wednesday June 26, 2019 @03:50AM (#20282736)
Yes, climate change effects would probably be a more accurate analogy -- but many people are very much against carbon tax schemes so it felt best to avoid that comparison.
Re:GDPR Enforcement Tracker: List of GDPR fines by TomVDB on Wednesday June 26, 2019 @12:29AM (#20281927)
I used to have a website that did stuff with GPS data that was uploaded by users.

It was purely a hobby affair that was a net loss, but Google ads ($10 per month) reduced the cost somewhat.

Those ads probably made it a for profit business.

I shut the thing down before GDPR, but if I hadn’t it surely would have been an excellent reason to do so.

Those are the kind of websites that you lose.

I consider that a loss.

Re:GDPR Enforcement Tracker: List of GDPR fines by ygra on Wednesday June 26, 2019 @01:45AM (#20282207)
GDPR doesn't prevent you from collecting personal data. It only requires you to have a clear reason for collecting everything and being transparent about what data is collected and how it is processed.
Re:GDPR Enforcement Tracker: List of GDPR fines by closeparen on Wednesday June 26, 2019 @01:54AM (#20282247)
The examples here make clear that "a clear reason for collecting everything" means an ironclad justification for each field, each bit of precision, each minute of retention. That is not a casual thing. As in, one of the fines here is for retaining a phone number to fulfill a need to communicate, when postal mail could have worked instead.

It is doable, if you have the lawyers and the time. But that's not a degree of scrutiny you want to gamble your life savings on for a personal project.

Re:GDPR Enforcement Tracker: List of GDPR fines by hdfbdtbcdg on Wednesday June 26, 2019 @02:06AM (#20282294)
If you don't need a phone number why collect a phone number?

I might need it later is not a clear reason!

Re:GDPR Enforcement Tracker: List of GDPR fines by closeparen on Wednesday June 26, 2019 @03:13AM (#20282569)
"Don't need" as in "there are feasible alternatives."

HN doesn't need to know or share your username to post your comment, it is clearly possible to run a message board without usernames, and conversations could be maintained by generating a random pseudonym for each thread.

Re:GDPR Enforcement Tracker: List of GDPR fines by La1n on Wednesday June 26, 2019 @07:40AM (#20283973)
Also, the fine (if we are talking about the Danish one) was not for collecting a phone number. It was for retaining it after the retention limit (in this case 2 years, and they kept them for 5 years) without a good cause. The company argued they were and essential part of the database. People love to make GDPR look bad, but it's often not as bad as it looks from a one line summary.
Re:GDPR Enforcement Tracker: List of GDPR fines by hdfbdtbcdg on Wednesday June 26, 2019 @01:24AM (#20282120)
Why could GDPR possibly make someone shutdown such a website?

Pure FUD.

EDIT: Downvotes don't change reality. The OP is spreading FUD.

Edit: unless the website was actually abusing users privacy in which case I'm glad it is gone.

Re:GDPR Enforcement Tracker: List of GDPR fines by closeparen on Wednesday June 26, 2019 @01:49AM (#20282225)
Well, suppose he does some transformation involving position. GPS points also have altitude in them. He neglects to sanitize altitude at the point of collection, and is therefore collecting and retaining more data than necessary to perform the service. He plots positions on a relatively zoomed-out map. Only the first six significant figures make a perceptible difference in the map position, but he retains the same precision that was uploaded, usually higher. Again, failure to minimize. Worse, he enabled automated periodic VM snapshots with his VPS provider, so is not properly complying with deletion requests.

Now he has "decided to build a business around profiting from the abuse of personal data" and the consensus in this thread looks on his destruction with glee.

Re:GDPR Enforcement Tracker: List of GDPR fines by hdfbdtbcdg on Wednesday June 26, 2019 @02:01AM (#20282282)
> Worse, he enabled automated periodic VM snapshots with his VPS provider, so is not properly complying with deletion requests.Worse, he enabled automated periodic VM snapshots with his VPS provider, so is not properly complying with deletion requests.

This is typical FUD. GDPR allows backups. Right to be deleted doesn't mean grovelling through backups. If those snapshots are rotated out after e.g. 3 months he is fine.

And regarding sanitizing altitude. Again pure FUD. There is no way that that would be a problem.

Of course if he stores the data in a personally identifying way and then is either incompetent or abusive then he could attract a fine...

In the real world GDPR enables such websites because users can trust that he has to follow some minimum standards.

Re:GDPR Enforcement Tracker: List of GDPR fines by closeparen on Wednesday June 26, 2019 @02:11AM (#20282321)
The great thing about TFA is we can stop speculating and see what the regulators are actually doing.

>After the controller succeeded to identify the data subjects he refused to comply with the deletion request, arguing he is legally obliged to retain backup copies according to the Accountancy Act and internal policies. Since he did not properly inform about these policies, the NAIH held the controller breached the principle of transparency.

So maybe if his backup regime were precisely specified in his privacy policy. But even a conflicting legal requirement is no defense, here.

Regarding minimization, 4 other cases:

>During an inspection, the Lithuanian Data Protection Supervisory Authority found that the controller processed more data than necessary to achieve the purposes for which he was a controller.

>Data was not only processed if adequate, relevant and limited to what is necessary in relation to the purposes for which they are processed

> The video surveillance subject of the proceedings is therefore not limited to areas which are under the exclusive power of control of the controller.

> The Commissioner considered that the aim could be achieved by referring only to the initials of their name and/or their faces being blurred and/or publishing photographs drawn from a distant distance

"Of course if he stores the data in a personally identifying way..." GDPR cares not for identifying but for identifiable. It's GPS data. If someone uploads data pertaining to their home, workplace, frequent travel routes, etc. then it is definitely identifiable.

Regarding FUD, it seems FUD is exactly what the DPAs intend, since they are punishing rather than helping when asked for advice!

>Kolibri Image had send a request to the Data Protection Authority of Hessen asking how to deal with a service provider who does not want to sign a processing agreement. After not answering Kolibri Image in more detail, the case was forwarded to the locally responsible Data Protection Authority of Hamburg. This Auhtority then fined Kolibri Image as controller for not having a processing agreement with the service provider.

Re:GDPR Enforcement Tracker: List of GDPR fines by johndough on Wednesday June 26, 2019 @03:41AM (#20282691)
Statement from Kolibri Image (German):

https://kolibri-image.com/causa-datenschutz/

Google translate:

https://translate.google.com/translate?hl=&sl=de&tl=en&u=htt...

tl;dr

The Data Protection Authority of Hessen suggested Kolibri Image to draft their own data processing agreement and get Packlink, located in Madrid, to sign it. [1]

Kolibri Image then stated that they would "leave things as they are", which was incorrectly interpreted to mean that they'd use Packlink without an agreement instead of not using Packlink in the future.

In addition, Kolibri Image forgot to update one of their six data processing agreements on various websites which still mentioned Packlink, so their clarification of the matter was not believed.

Finally, the case was dropped because it (partially?) happened before the 24th of Mai.

[1] Drafting a data processing agreement for Packlink is of course not very practical because who knows how they handles their data and why would Packlink sign it in the first place if they don't want to offer a data processing agreement. In addition, the cost of drafting and translating the agreement is much more expensive than the savings from using Packlink as a shipping processor.

In any case, I agree that fining after asking for advice is not a friendly move.

Re:GDPR Enforcement Tracker: List of GDPR fines by hdfbdtbcdg on Wednesday June 26, 2019 @02:17AM (#20282346)
I think you should dig into these cases a little deeper.
Re:GDPR Enforcement Tracker: List of GDPR fines by closeparen on Wednesday June 26, 2019 @03:05AM (#20282533)
The people who can be relied on to do that correctly when money is on the line are called lawyers, and they aren't cheap.
Re:GDPR Enforcement Tracker: List of GDPR fines by TomVDB on Wednesday June 26, 2019 @03:47AM (#20282718)
You receive an email with a request for a privacy statement? Great, one way or the other, that's work with potential legal repercussion, which means you probably should talk to a lawyer. Additional expenses and hassle for no good reason.

You make a fix in the email system that accidentally emails everybody at the same time? (It almost happened.) Oops. There's your exposure to some nice fine.

You don't need to be abusing somebody's privacy to be concerned about legal exposure. Just like there are asshole companies, there are asshole users as well who can make your life miserable.

Any hobbyist who doesn't take this kind of exposure into consideration is naive.

Re:GDPR Enforcement Tracker: List of GDPR fines by Angostura on Wednesday June 26, 2019 @07:08AM (#20283793)
I'm sorry but every website collecting personal data should set out clearly and simply what it is used for and how it can be distributed. For asmall hobbyist site you don't need a lawyer, there are plenty of decent templates out there.
Re:GDPR Enforcement Tracker: List of GDPR fines by ubercow13 on Tuesday June 25, 2019 @10:19PM (#20281324)
That's a pretty weak argument in and of itself. Many crimes are mistakes.
Re:GDPR Enforcement Tracker: List of GDPR fines by TomVDB on Wednesday June 26, 2019 @12:31AM (#20281940)
Similarly, many simple mistakes shouldn’t be treated as a crime.
Re:GDPR Enforcement Tracker: List of GDPR fines by Angostura on Wednesday June 26, 2019 @07:04AM (#20283770)
If you make a mistake and you do so honestly, not out of malice and fix it, you are very unlikely to get a fine - you will get guidance and a warning. Unless you are being egregiously slip-shod.
Re:GDPR Enforcement Tracker: List of GDPR fines by easytiger on Wednesday June 26, 2019 @08:19AM (#20284194)
Re:GDPR Enforcement Tracker: List of GDPR fines by josefx on Thursday June 27, 2019 @03:52AM (#20292483)
Storing user names and passwords in plain text when you have several hundred thousand users is not a "honest mistake" in 2019. In other fields a commercial entity failing basic security practices can be considered criminally negligent.
Re:GDPR Enforcement Tracker: List of GDPR fines by cosmodisk on Tuesday June 25, 2019 @07:25PM (#20280301)
That's absurd. Talking purely about the UK right now: there were tens of thousands of cases logged with ICO since GDPR came into power. So far,there were only a handful of companies that had to pay fines and their actions were either borderline criminal,or deliberate refusal to cooperate with ICO.