![]() ![]() The privacy failure will further weaken confidence that Facebook is a responsible steward for our private data. But photos users uploaded but either decided not to post, that got interrupted by connectivity issues, or that they otherwise never finished sharing could have winded up with app developers. The bug wouldn’t have exposed photos users never uploaded to Facebook from their camera roll or computer. With reference to these data breaches, including the breach in question, we have this week commenced a statutory inquiry examining Facebook’s compliance with the relevant provisions of the GDPR.”įacebook tells me the bug did not impact photos privately shared through Messenger. The head of communications for the IDPC Graham Doyle tells TechCrunch “The Irish DPC has received a number of breach notifications from Facebook since the introduction of the GDPR on May 25, 2018. It says that it had to investigate to make that conclusion and let the IDPC know within 72 hours once it had. However, Facebook tells me it notified the IDPC that oversees GDPR on November 22nd, as soon as it established the bug was considered a reportable breach under GDPR guidelines. The delay could put Facebook at risk of GDPR fines for not promptly disclosing the issue within 72 hours that can go up to 20 million pounds or 4 percent of annual global revenue. ![]() They say it took time for the company to investigate which apps and people were impacted, and build and translate the warning notification it will send impacted users. It’s recommending users log into apps to check if they have wrongful photo access. Here’s a look at a mockup of warning notification users will see:įacebook initially didn’t disclose when it discovered the bug, but in response to TechCrunch’s inquiry, a spokesperson says that it was discovered and fixed on September 25th. The company plans to notify people it suspects may have been impacted by the bug via Facebook notification that will direct them to the Help Center where they’ll see if they used any apps impacted by the bug. It will provide tools next week for app developers to check if they were impacted and it will work with them to delete photos they shouldn’t have. The IDPC has begun a statuatory inquiry into the breach.įacebook provided merely a glib “We’re sorry this happened” in terms of an apology. Facebook tells TechCrunch it discovered the breach on September 25th, and informed the European Union’s privacy watchdog the Office Of The Data Protection Commissioner (IDPC) on November 22nd. ![]() Facebook says the bug ran for 12 days from September 13th to September 25th. The bug allowed apps users had approved to pull their timeline photos to also receive their Facebook Stories, Marketplace photos, and most worryingly, photos they’d uploaded to Facebook but never shared. Subscribe now.Reset the “days since the last Facebook privacy scandal” counter, as Facebook has just revealed a Photo API bug gave app developers too much access to the photos of up to 5.6 million users. Stay informed and gain unlimited access to the Daily Beast's unmatched reporting. Get the Daily Beast's biggest scoops and scandals delivered right to your inbox. At the time, Facebook described it as “trouble” caused by “a configuration change.” In November, 2022, users reported seeing an uptick in people commenting on celebrity pages in their feed, even if they did not follow the commenter or the celebrities. Last month, a glitch in Facebook ads overcharged customers and forced the company to briefly stop all advertising. This latest bug comes as Facebook’s parent company Meta is in the midst of mass layoffs, which have seen the company cut at least 13 percent of its staff, firing more than 11,000 people. I have no idea what's going on but i was JUST gonna stalk someone's profile on facebook and it automatically sends a friend LEAVE ME ALONE I DON'T WANNA ADD THESE kei May 12, 2023 ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |