![\"Google](\"https:\/\/isquaredemo.com\/MLT\/threegraceslegal\/wp-content\/uploads\/2025\/10\/google.jpeg\" "\\"Google")
<\/p>\n<\/p>\n
Following Google\u2019s announcement this week (8 October 2018) regarding a data breach in 2015, they have temporarily shut down their social network Google+, where a security bug enabled third party developers to gain access to user data, potentially affecting around 496, 951 Google+ users.<\/p>\n
The announcement on Monday was the first time Google discussed the breach, which although occurred three years ago, was not exposed and remedied until March 2018. Google\u2019s reasoning for late exposure was relayed in an internal memo, which discussed the avoidance of \u201cregulatory interest\u201d<\/em><\/strong>, and potential comparisons to Facebook\u2019s Cambridge Analytica<\/em> scandal.<\/p>\n The bug may have allowed third party developers to gain access to usernames, email, gender, data of birth, location, pictures, as well as occupation and relationship status. However, there is no concrete evidence to confirms this (as Google only holds API data for two weeks) therefore they cannot determine how many users were exposed. Google have advised that there was \u201cno evidence that any profile data was misused\u201d<\/em><\/strong> as well as there being \u201cno evidence that any developer was aware of this bug, or abusing the API\u201d<\/em><\/strong>.<\/p>\n Although the bug has now been fixed, the tech giant has evidently promoted mistrust, casting doubts on the transparency of Google and other companies such as Facebook and Twitter. This calls for an increase in regulation and re-evaluation of the codes of practice utilised by tech companies.<\/p>\n In terms of punishment and penalties, Google have avoided General Data Protection Regulation (GDPR) fines, as the bug was fixed before GDPR was implemented. However, they may still face class-action lawsuits, as well as public scrutiny, which will impact them significantly.<\/p>\n Google have discussed their next steps:<\/p>\n \u201cin the coming months, we\u2019ll roll out additional controls and update policies across more of our APIs.\u201d<\/em><\/strong>.<\/p>\n They have also discussed their aims for the future, stating:<\/p>\n \u201cOur goal is to support a wide range of useful apps, while ensuring that everyone is confident that their data is secure. By giving develops more explicit rules of the road, and helping users control your data, we can ensure that we keep doing just that.\u201d<\/em><\/strong><\/p>\n <\/p>\n If you have been the victim of a data breach, we can assist you with a compensation claim.<\/strong><\/p>\n Contact us for assistance on <\/strong>0151 659 1070.<\/strong><\/p>\n<\/div>\n<\/div>\n<\/div>\n <\/p>\n","protected":false},"excerpt":{"rendered":" Following Google\u2019s announcement this week (8 October 2018) regarding a data breach in 2015, they have temporarily shut down their social network Google+, where a security bug enabled third party developers to gain access to user data, potentially affecting around 496, 951 Google+ users. The announcement on Monday was the first time Google discussed the […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[9],"tags":[],"class_list":["post-278","post","type-post","status-publish","format-standard","hentry","category-news"],"acf":[],"yoast_head":"\n\n\n\n