Google and the Italian Data Protecion Authority fine

The news is making the round that Google has been indicted to pay a 1.000.000,00 Euros’ fine for the Street View’s “privacy infringement” under Italian Privacy Act. But (at least in this case) Google didn’t violate the Italian Laws and the Data Protection Authority did a blatant mistake: let’s see why.

1 – Google has not been investigated under “privacy” law, the relevant statute being the Data Protection Act (as I wrote, there is no superimposition between the two legal concepts);

2 – The Data Protection Act, being an enforcement of the EU Directive 95/46/CE only handles “personal data”, i.e. data that either identify a natural person or make a natural person identifiable;

3 – As the Italian Supreme Court said more than once – and so did the same Data Protection Authority ? – outdoor there is no reasonable privacy expectation,

Then, as soon as Street View shots pictures in open spaces and doesn’t identify people, there is no “privacy” infringement.

But this is just a conclusion drafted by interpreting the law. Real life is a horse of different colour.

EU “Privacy” Directives and the Haunted Companies

The right to privacy is a pre-requisite of the EU Directive 95/46/CE ? and not its object. Art. 1 states it loud and clear:

1. In accordance with this Directive, Member States shall protect the fundamental rights and freedoms of natural persons, and in particular their right to privacy with respect to the processing of personal data.

This means that that calling the data protection-related directive – as well as the upcoming new regulation – “privacy law” or whatever similar is not just a terminology’s mistake but an error with actual (and costly) consequences negatively affecting companies’ budget allocation, legal compliance and marketing capabilities.

Under the EU data protection legal framework, companies are not required to protect “privacy” as such, but only to handle personal data on a “need-to-know” basis provided that fundamental rights are not endangered. This has nothing to do with the “hush-hush” attitude commonly “sold” by “expert” consultants summoning the right to privacy as a threatening devil to haunt a company.

Stop using “privacy” as a substitute for “data protection” and your (corporate) life will keep smiling at you again.

 

Friday Night (Data Retention) Fever

Here is a real case that happened just a couple of days ago, while helping an ISP to find a way to handle the deletion of data after the mandatory term imposed by the Eu Data Retention Directive expires. Whatever the solution, thank to the rigidity of the provisions, a law will not be obeyed.

Background:

  •  ? The automatic processing of the data-deletion is usually made so that a script matches daily the data-creation date with the current date, and if the match says that the retention term is expired, then the script delete the data,
  • The only exception is a “freeze” order issued by a Court or a prosecutor. In this case it is possible to avoid the requested data to be destroyed,
  • The “freeze” order are notified either by fax, secure email or direct order to the “Protocol department” (that handles the incoming communications, and that “route” the messages to the concerned people),
  • While when the offices are closed there is always at least one resource belonging to the technical department to be alerted in case of urgency, the administrative offices just shut down the curtains of Friday at – say – 5P.M.,

Scenario:
– let’s say that a secure mail or a fax containing the “freezing” order arrives when the Protocol Department is closed. This means that the request will be processed the next day,

– let’s say that the “freezing” order concerns data that are going to be destroyed the very same Friday night when the order arrived,

What happens is that the “freezing” order arrived timely, before the data were destroyed, but since the internal route of the order is handled when the term is expired, the data have been deleted.

A possible solution could be to extend the deleting time frame of three days (thus accounting for the week-end gap) but it doesn’t work. Here is why.

If I have to destroy the data on Friday, and I kept it until Monday just to check if some Court order has been notified in the meantime, it might happens that on the very same Monday a Court order might be notified in relationship to the Friday-to-be-deleted data (when the data are supposed not to exist anymore).

So, if I follow the DRD I must refuse to comply with the Court order because though the data are there, they can be processed only if the Court order were notified within the original term. On the other hand, I can’t refuse to obey to a Court order, if I still have the concerned information.

A contemporary version of the Buridan’s Ass Paradox.

 

The Security Excuse

This is a close-up of a banner belonging to the Prefecture de police, Paris, Rue de la citè.

Actually this banner says nothing special but what a public police power is supposed to do; nevertheless ? – as I wrote commenting the picture – I don’t know why, but every time I hear a public power saying that he cares about me I feel a bit worried.

Why the UE Cookie Directive doesn’t actually protect the final user

All the fuss generated by the use of cookies by almost every website on the traditional Internet that led the EU to pass the Cookie Directive just produced a pop-up that warns the anonymous user about the presence of these digital candies. Thus, the Ad-dicted can claim to be law-abiding netizens while giving no actual privacy protection for the users. Want a proof? What follows is a cookie left on my computer by a well-known e-commerce giant: A0CJfSiKBUmZik9DPj7fCXA. Firefox tells me about it existence and expiring date, but how am I supposed to know what does this cookie means? And what difference does it make whether I am aware or not of its presence, since I have no way of understanding what’s its function?

Short: the Cookie Directive is useless and, as Cicero used to say, Summum Jus, Summa Injuria.