Chrome Web Store Spam enforcement — clarification needed on latest remediated package

13 views
Skip to first unread message

Team UNOLO

unread,
5:10 AM (1 hour ago) 5:10 AM
to Chromium Extensions

Hello Chrome Extensions team,

We are the developers of UNOLO Wallet and are seeking clarification regarding a Chrome Web Store enforcement decision.

Extension: UNOLO Wallet
Extension ID: hifbhejmbomilbfmlhpjjfpcdhhmgini
Current version: 1.0.2
Support case: 5-3393000041463

Our submission was rejected under the Spam policy, and we submitted an appeal.

After the appeal had already been submitted, we continued our internal review and identified additional technical issues that we believed could potentially contribute to the concern. We performed substantial remediation and uploaded an updated package to the same existing item.

The important detail is that the updated package retained the same version number, 1.0.2, as the earlier package.

Chrome Web Store Developer Support subsequently informed us that the item had been thoroughly checked and would not be reinstated. We completely understand that anti-abuse signals and details about spam detection cannot be disclosed, and we are not requesting disclosure of those signals.

Our question is much narrower:

Could the Chrome Web Store team please confirm whether the review included the latest 1.0.2 package that was uploaded after our appeal and after the additional remediation?

Because both the earlier artifact and the subsequently remediated artifact used the same version number (1.0.2), we are concerned that there may be ambiguity about which artifact was reviewed.

We asked this question through the existing support case, but the response reiterated that details of spam activity could not be disclosed and did not confirm whether the latest uploaded artifact was included in the review.

We respect the Chrome Web Store policies and are not attempting to bypass the enforcement decision. We simply want to ensure that the latest remediated package was the artifact evaluated before determining our next compliant step.

If someone from the Chrome Web Store team could help verify this or route the case for clarification, we would greatly appreciate it.

Thank you,

Team UNOLO

Reply all
Reply to author
Forward
0 new messages