The developer now plans to make a few other changes to the permission requests and submit the extension for review again. When asked for further clarification, Google didn't respond to the developer's email. However, the updated extension was rejected once again and the company gave the same reason as before. In response to the aforementioned reply, Pushbullet's developer reduced the extension's permission requests and resubmitted the extension for review. Don't attempt to "future proof" your product by requesting a permission that might benefit services or features that have not yet been implemented.".If more than one permission could be used to implement a feature, you must request those with the least access to data or functionality.Request access to the narrowest permissions necessary to implement your product's features or services."Your product violates the "Use of Permission" section of the policy, which requires that you: When the developers reached out to Google inquiring how their extensions violated the privacy policy, the company reverted back with a generic reply that states:
The developers behind Pushbullet and Join were recently alerted by Google that their extensions didn't comply with the Chrome Web Store's privacy policy and violated the "Use of Permissions" section.
0 kommentar(er)
