Update (incorrectly) rejected for not having a privacy policy. Next steps?

[Adi Bhaskar]

An update to one of my extensions[^1] was rejected for not having a privacy policy listed in the designated field (violation reference: "purple lithium"). However, I've always had a link to the privacy policy[^2] listed in the designated field. The link to privacy policy has also been visible in the Chrome extension listing since whenever CWS started showing it.

The privacy policy link points to a page that lists privacy policies for all my Chrome extensions and Android apps. My guess is that the reviewer rejected it because they didn't find the link to exact privacy policy for this extension[^3], or couldn't locate the privacy policy for this extension on the page.

I used the developer support page to get back in touch with them and point this out. 

As per the response message on the support page, and my past experience, I may or may not get a response in anywhere from a day to a few weeks. Meanwhile the extension update is still showing as 'rejected'. What ought to be my next step?

- Wait indefinitely for a response which, if successful, will automatically enable the update, or

- Submit the update for review again, to trigger a new review with my note to support.

If anyone has been in this boat before, I'll appreciate any suggestions.

If Simeon or anyone else from the CWS team is reading, I'll really appreciate the suggestions for the next step.

Cheers!

Adi

[^1]: https://chrome.google.com/webstore/detail/accelereader-power-up-you/ndaldjfflhocdageglcnflfanmdhgfbi

[^2]: https://c306.net/apps/privacy

[^3]: https://c306.net/apps/privacy/accelereader-pocket/ (6th item on the list page)

[Adi Bhaskar]

Updated the link in account settings to list only Chrome extensions' privacy policy[^1], filtering out the Android app privacy policies. Submitted for review, and got rejected again for 'No privacy policy' within a few minutes.

Haven't heard back, or even received confirmation email for support form submissions.

Not really sure at the moment what else I can do :(

[^1]: http://c306.net/apps/privacy/tags/chrome

[Adi Bhaskar]

Not sure what change worked, but a third attempt went through, and the update has been published.

It'd really help if there was a way to figure out what worked—between the two rejections and the one successful review.

Closed.

[Simeon Vincent]

Hey Adi,

This looks like a inconsistency between reviewers. Typically the extensions privacy policy points directly to the individual extensions policy, but as you know the Chrome Web Store only allows you to specify a privacy policy at the account level. Do you have, rather reasonably IMO, attempted to work around this by linking to a page with multiple privacy policies. The difference between the rejection and the approval is that one review were canceled this violation and the other did not. 

I'll start a conversation with the review team about this to see if we can clarify our expectations here.

Cheers,

Simeon - @dotproto

Developer Advocate for Chrome Extensions