Review process for chrome v3 app beta publish with private visibility

[Abhijeet Chandrakamal]

Hi all, 

Recently, we successfully published a beta version for our v3 extension with visibility set to private. We need to make sure that there is no difference between the review process if it would have been for a public distribution as mentioned here.

For our extension, we need to reuse our existing web components(internally developed and maintained by us). So, we are loading scripts to register those in an iframe. We just need to make sure that it doesn't violate any chrome v3 policies. 

Hope, there won't be any difference in private and public publish review process.

Thanks.

[Stefan Van Damme]

Hi there,

There is no other review process for the private and public Chrome extensions.

It said that too on this developer page:

All visibility settings have the same policy requirements and will go through the same review process.

Source: https://developer.chrome.com/docs/webstore/cws-dashboard-distribution/#setting-the-visibility:~:text=All%20visibility%20settings%20have%20the%20same%20policy%20requirements%20and%20will%20go%20through%20the%20same%20review%20process.

Thanks,

Stefan vd

[Abhijeet Chandrakamal]

Thanks.

[Stefan Van Damme]

Hi there,

You are welcome.

Thanks,

Stefan vd