The store process.
WHAT PUBLISHING REQUIRES
A developer account, with a registration fee A packaged extension Store listing content and images A privacy policy Declarations about data handling Justification for permissions requested
WHAT REVIEW ASSESSES
Whether the extension does what it claims Whether permissions are justified Whether data handling matches declarations Policy compliance
WHAT COMMONLY CAUSES REJECTION
Permissions broader than the functionality requires Vague or missing justification Undisclosed data collection Functionality unrelated to the stated purpose
WHAT TO PROVIDE
Clear justification for each permission, referencing the specific feature.
WHAT TO EXPECT
Review taking days, and longer for sensitive permissions.
WHAT TO USE FOR TESTING
Unlisted publishing, or a trusted tester group.
WHAT TO DO FOR INTERNAL EXTENSIONS
Publish privately to your organisation, or deploy by policy.
WHAT TO MONITOR AFTER PUBLISHING
Reviews Error reports Whether the pages you depend on have changed
WHY THAT LAST POINT
Extensions modifying specific sites break when those sites change.
WHAT TO PLAN
Ongoing maintenance, which is continuous for such extensions.
