Chrome Web Store Notice

gistfile1.txt

Chrome Web Store


Dear Developer,

Your Google Chrome item "Pushbullet" with ID:  
chlffgpmiacpedhhbkiomidkjlcfhogd did not comply with our policies.

Your item is still published, but is at risk of being removed from the  
Chrome Web Store.



Your item did not comply with the following section of our Program Policies:


"User Data Privacy"

Your product violates the "Use of Permissions" section of the policy, which  
requires that you:


Request access to the narrowest permissions necessary to implement your  
product's features or services.
If more than one permission could be used to implement a feature, you must  
request those with the least access to data or functionality.
Don't attempt to "future proof" your product by requesting a permission  
that might benefit services or features that have not yet been implemented.



Please make the necessary changes within 14 days in order to avoid removal.


Once you have made these changes you may submit and publish a new draft in  
the Chrome Web Store Developer Dashboard.

Your draft will then be reviewed for policy compliance. If the outcome of  
the review is successful, your existing store listing will get replaced by  
the approved draft. However, if the new draft fails to comply with our  
policies, both the draft and the existing store listing will be removed.  
Please note that the rectification window expires the moment a new draft is  
submitted. After this point, you will not be able to make iterative changes  
regardless of the days remaining in the warning period.


If you have any questions about this email, please respond and the Chrome  
Web Store Developer Support team will follow up with you.


Important Note:

Your item will still be subject to review and may be removed from the store  
within the warning period.

Repeated or egregious policy violations in the Chrome Web Store may result  
in your developer account being suspended or could lead to a ban from using  
the Chrome Web Store platform.

This may also result in the suspension of related Google services  
associated with your Google account.


Sincerely,

Chrome Web Store Developer Support

------------------------------------------------------
Developer Terms of Service
Program Policies
Branding Guidelines


Google
© 2020 Google LLC, 1600 Amphitheatre Parkway, Mountain View, CA 94043 , USA
Email Preferences: You have received this mandatory email service  
announcement to update you about important changes to your Chrome Web Store  
developer account.

Google couldn't resist being Google, I guess. I hope you have the chance to talk to a "human" there and actually get this resolved.

Google is dumb they want to control everything uhh!!!!!!!!!!!!!!!!!!!!!!!!! I agree with saladthieves also.

Bad and sad story indeed. But what is the thing to do if Google does not explicitly say what is wrong with the extension !??

This honestly is silly

If you have any questions about this email, please respond and the Chrome
Web Store Developer Support team will follow up with you.

if you reply asking them to detail which permission is problematic, do they answer?

If you have any questions about this email, please respond and the Chrome
Web Store Developer Support team will follow up with you.

if you reply asking them to detail which permission is problematic, do they answer?

I emailed 3 days ago but haven't received a response. It is totally possible they'll respond, but 14 days time limit + slow response is stress-inducing to say the least.

Google has done the same to me on the Play Store. Ridiculous automation

It's good when you're a big enough extension like Pushbullet to get a human response telling you what permission was the problem: https://twitter.com/DotProto/status/1260621826939445249

If you're working on a new extension, your extension will probably be removed :\

It sounds like they did tell you. Change the requested permissions in your manifest to be narrower or add text/documentation clearly explaining why you needed those permissions. Or make them optional so they can be enabled by users on demand as they use features that need them.

https://developer.chrome.com/extensions/declare_permissions
https://developer.chrome.com/extensions/permission_warnings

It sounds like they did tell you. Change the requested permissions in your manifest to be narrower or add text/documentation clearly explaining why you needed those permissions. Or make them optional so they can be enabled by users on demand as they use features that need them.

https://developer.chrome.com/extensions/declare_permissions
https://developer.chrome.com/extensions/permission_warnings

https://blog.pushbullet.com/2020/05/13/lets-guess-what-google-requires-in-14-days-or-they-kill-our-extension/

Statement is too generic. They did try submitting a new release with "reduced" permissions. Still got rejected. I think the issue here is that Google expects you to play charades while the clock is ticking. That's not the way to keep your developers happy.

Yes