Tuesday, August 20, 2019


Not sure I understand this one.
Al Restar reports:
The Australian court ruled that employees are allowed to refuse to provide biometric data to their employees. The ruling follows the lawsuit filed by Jeremy Lee getting fired from his previous job due to his refusal of providing his fingerprint samples for the company’s newly installed fingerprint login system.
Jeremy Lee from Queensland, Australia, won a landmark case after he was fired from his job at Superior Wood Pty Ltd, a lumber manufacturer, in February 2018, for refusing to provide his fingerprints to sign in and out of his work, citing that he was unfairly dismissed from the company.
Read more on Z6Mag.
From the article:
If I were to submit to a fingerprint scan time clock, I would be allowing unknown individuals and groups to access my biometric data, the potential trading/acquisition of my biometric data by unknown individuals and groups, indefinitely,” reads Lee’s affidavit.
We accept Mr. Lee’s submission that once biometric information is digitized, it may be very difficult to contain its use by third parties, including for commercial purposes,” case documents state.
The case of Lee is a first in Australia. While it did not change the law, it opens a new perspective on the ownership of biometric information like fingerprints and facial recognition and reinterpreted privacy laws on how they will apply to data like these.




It’s a small step, but at least it’s a step.
Twitter Flexing its Muscles Against State Misinformation
Twitter first announced Monday, August 19, 2019, that is updating its policy on state media advertising. "Going forward," it said, "we will not accept advertising from state-controlled news media entities. Any affected accounts will be free to continue to use Twitter to engage in public conversation, just not our advertising products."
This policy is global and not targeted at any specific nation or nations, but does not "apply to taxpayer-funded entities, including independent public broadcasters" (so organizations like the BBC -- were it to advertise -- should be okay). The organizations targeted are not banned from using Twitter to engage in organic conversation, but will not be allowed to advertise on the platform.
The immediate catalyst is almost certainly mainland China's propaganda campaign against the ongoing Hong Kong protest movement, but it will reduce the capacity of all foreign countries to manipulate public opinion ahead of elections. The longer-term catalyst will be to help protect the U.S. 2020 elections from foreign influence, whether that comes from China, Russia, Iran or elsewhere.




Reading this, I think IT will have problems complying. Perhaps we should dedicate a lawyer to make the records and draft the notices? Can IT explain things to the lawyer in plain English?
Actionable takeaways from new Irish and Polish Data Protection Authorities'​ guidance on personal data breach notification under GDPR
The Irish Data Protection Commission and the Polish Data Protection authority both recently issues guidance on the notification requirements under GDPR in the event of a Personal Data Breach.
What is "become aware"?
  • A controller should be regarded as having become ‘aware’ when they have a reasonable degree of certainty that a security incident has occurred and compromised personal data.
  • Controllers should have a system in place for recording how and when they become aware of personal data breaches and how they assessed the potential risk posed by the breach.




Représailles is French for retaliation. What did they think would happen?
Amazon is passing along costs of a new digital tax to thousands of French sellers
The reason the company cited was simple: a 3% digital tax passed by the French government in July.
Amazon’s move appears to directly conflict with the French government’s aim of leveling the playing field between Big Tech and small and medium-sized enterprises, and further complicates France’s effort to rein in companies like Amazon, Facebook and Google.




We covered Intellectual Property last week. Perhaps we should reopen the debate?
Linking Liability
Inside Higher Education – Sci-Hub, a repository for pirated research papers, is widely acknowledged to be illegal. But is sharing a link to the site illegal, too? There is little dispute that Sci-Hub, the website that provides free access to millions of proprietary academic papers, is illegal. Yet, despite being successfully sued twice by major American academic publishers for massive copyright infringement, the site continues to operate. Some academics talk openly about their use of the repository — a small number even publicly thank Sci-Hub founder Alexandra Elbakyan for her contribution to their research. Most academics who use the site, however, choose to do so discreetly, seemingly aware that drawing attention to their activities might be unwise. Just how careful academics should be about using Sci-Hub has become a topic of concern in recent weeks, with many questioning whether sharing links to Sci-Hub could in itself be considered illegal. The discussion started when the team behind Citationsy, a bibliography management tool based in Europe, tweeted that lawyers for Elsevier, a major publisher of academic journals, had threatened to pursue legal action if Citationsy did not remove a link to Sci-Hub from Citationsy’s website. The link formed part of a blog post titled “Hacking Education: Download Research Papers and Scientific Articles for Free.”


(Related)
    What the site does is not permitted, according to the law, but in the academic world, Sci-Hub is praised by many. In particular, those who don’t have direct access to expensive journals but aspire to excel in their academic field.
This leads to a rather intriguing situation where many of the ‘creators,’ the people who write academic articles, are openly supporting the site. By doing so, they go directly against the major publishers, including the billion-dollar company Elsevier, which are the rightsholders.




For the student toolkit? New to me.
English Language & Usage Stack Exchange



No comments: