project-strobe
Latest
Google Chrome extensions must obey new privacy rules by October 15th
Time is running out for Chrome developers to follow Google's new privacy rules. The company announced today that third-party developers have until October 15th to comply with updated restrictions on user data, or risk getting kicked off Chrome's Web Store. Google unveiled the changes earlier this year as a result of Project Strobe, its audit on how third-party services handle user privacy.
Google unveils new privacy rules for Chrome extensions and Drive
Google announced new rules that will restrict access to user data for third-party add-ons in Chrome and Drive. From now on, Chrome extension developers must request the least amount of user data their app requires to function. Apps that connect with Google Drive -- such as Pixlr and many popular document signing apps -- will be barred from accessing the entirety of the user's files. The changes are a result of Project Strobe, an audit Google launched in October to study how third-party services handle user data.
IFTTT loses some Gmail triggers on March 31st
Google's push to tighten third-party API access is already going to cost the world Google+, but a change that more of you might notice is coming to IFTTT. The service sent out emails alerting users that their "recipe" scripts involving Gmail triggers and an action that could create a draft will go away as of March 31st. According to Google, the shift is a result of the Project Strobe sweep it announced last October. IFTTT said it worked with Google to keep the integration that will support triggers to Send an email, or to Send Yourself an email, but the API lockdown that's coming would've required too much work to change its services. Otherwise, integrations with Google will still be the same, but anyone relying heavily on the automated scripts may want to double check things before they get a surprise in a few days.