I will fix your rejected chrome extension

S
sserpolar
S
sserpolar
Zack Wu

About this gig

Your extension got rejected? Usually it is one specific permission, not your product.


Review rejects for a few reasons: unjustified permissions, a single-purpose statement that reads like a feature list, a data-usage form that contradicts your manifest, a bad privacy policy, or wrong screenshot sizes. On Firefox, a build their reviewer cannot reproduce.


WHAT I DO

- Read your manifest and source, and name the exact permission blocking you

- Cut permissions to the minimum your features need, code changes included

- Rewrite your permission justifications, single-purpose statement and data-usage answers

- Supply a privacy policy and correctly sized store assets

- Prepare replies for the reviewer's follow-up questions


WHY ME

Two extensions of my own, five store listings, zero rejections. One ships to Chrome, Edge and Firefox with two permissions and no host access, so its install prompt never says "Read your data on all websites."


WHAT I NEED

Your source or submitted zip, plus the rejection email.


Not sure which package fits? Send the rejection notice first and I will tell you.

Get to know Zack Wu

Zack Wu

fix your rejected chrome extension

  • FromChina
  • Member sinceAug 2026
  • Languages

    English
I build browser extensions that pass store review the first time. Two of my own are live across five store listings with zero rejections, one of them on Chrome, Edge and Firefox from a single code base with only two permissions Extension projects stall in the same place: the manifest asks for more than the product needs, review pushes back, launch slips. Idesign permissions before writing features, so the install prompt never says "Read your data on all websites" Already rejected? Send the rejection email and your source.