DEV Community

William Chenyin
William Chenyin

Posted on AI-assisted

What "Purple Potassium" means, and how to write a permission justification that doesn't get sent back

When I submitted my first Chrome extension, the code wasn't the hard part. The hard part was a tab in the developer dashboard called Privacy, which asked me to justify every permission, state a "single purpose", declare what data I handle, and tell a reviewer how to test the thing. Google's guidance for those fields is spread across about a dozen policy pages, and none of them shows what a good answer looks like.

My extension (Typer.AI, an autocomplete tool) runs on every site and reads what you type, so the dashboard flagged it for a potentially longer review. It got through. If it hadn't, the email would have contained a two-word code like "Purple Potassium", which means excessive permissions.

This is what I'd want to know before a first submission.

The three-part justification

The dashboard reads your manifest and gives you one text box per permission. Every justification that holds up has the same three parts:

  1. The feature. What the user gets.
  2. The data. What the permission lets you read or change, and where it goes.
  3. The limit. What you don't do with it.

Here's a justification that will probably get questioned:

Needed for the extension to work.

Every permission is needed for the extension to work. The reviewer wants to know which feature. Here's the one I used for storage:

Save the user's completion toggle, suggestion level, background AI opt-in, and paused-site preferences locally. No document text or writing history is saved to extension storage.

The first sentence is the feature and the data. The second is the limit. It takes thirty seconds to write once you know the shape.

A few things I'd avoid: "for future features" (the policy says not to request permissions to future-proof), the same sentence pasted into every box, and describing the API ("allows access to tabs") when the question is about your use of it.

Delete before you justify

The fastest way through that page is to remove permissions before you write about them. Google's policy is to request the narrowest permission the feature needs. If you can't point to the line of code that uses a permission, it shouldn't be in your manifest, and no sentence will fix that.

This matters more if an AI assistant wrote your manifest, because they tend to add permissions "to be safe". Go through permissions and host_permissions one at a time and search your code for each.

The four that people get wrong

Google's troubleshooting page names these as commonly misunderstood:

  • activeTab gives you temporary access to the current tab after the user clicks your icon. If your feature starts with a click, you often don't need host permissions at all.
  • tabs is only needed to read a tab's url, title or favIconUrl. chrome.tabs.query, create, update and sendMessage all work without it.
  • cookies does nothing without matching host permissions, and Google lists that pair among the things that lengthen a review.
  • storage is needed for chrome.storage. localStorage in your own extension pages doesn't need it.

How I avoided adding tabs

After launch I found a bug: my popup has a "pause on this site" button, and sometimes it was disabled because the popup couldn't see the current tab's URL. The obvious fix is to add the tabs permission.

Adding a permission in an update can trigger a fresh review and a permission prompt for existing users. My content script was already running on the page, so the fix has the popup ask it for the hostname. The response is just the hostname, nothing else, and the manifest didn't change. That version was submitted on October 18 and was live on October 20.

I think that's the habit worth building. When you need something new, check whether code you already have permission to run can answer the question.

If you do get rejected

The email will name a policy and a code. The six I'd read up on first:

Code What it means
Purple Potassium A permission you don't use, or a broader one than you need
Yellow Magnesium The reviewer couldn't get it to work
Blue Argon Code that isn't inside the package, like a CDN script tag
Purple Lithium Privacy policy missing, broken, or in the wrong field
Yellow Zinc Missing icon, screenshots or description
Red Magnesium, Copper, Lithium, Argon More than one purpose

Two things worth knowing before you react. A rejection doesn't touch your published version, and your users aren't told. And you can appeal a decision once, so fix and resubmit when the reviewer is right, and save the appeal for when you can show they're mistaken.

I wrote up all 36 codes, with what to check first and how to fix each one, in a free repo: Chrome Web Store rejection codes, in plain English. It's all taken from Google's own troubleshooting page, and if you've hit one and the fix was different from what I wrote, open an issue and I'll correct it.

I also packaged the rest (a checker that reads your extension before you upload it, and a fill-in template for each dashboard field) into a paid kit, which is linked from that repo. The table is free and stays free.

Top comments (1)

Collapse
 
komopdf profile image
KomoPDF •

For the hostname workaround, it is worth testing restricted pages and tabs where the content script is absent. The popup can show a clear unavailable state there instead of assuming every active tab can respond.