App Store 4.4.2 rejection: Safari extensions

A Safari extension can work on one page while asking for access to far more sites than it needs. Guideline 4.4.2 requires current Safari compatibility, appropriate website access, and respect for Safari and system interface behavior.

Compare requested access with the feature

List the sites and data the extension actually needs. Check permissions, injected scripts, and settings. We’d test on the current Safari version and include a site outside the intended scope.

Narrow and repair the integration

Request only the website access needed for the feature. Remove misleading behavior, harmful code, or interference with browser and system controls. If the feature genuinely needs broad access, explain why with a specific user task rather than a general future possibility.

Test installation, permission denial, permitted sites, and unrelated sites. Verify that the extension stops acting where it shouldn’t. Give Apple the setup instructions, relevant domains, and corrected build. Check 4.4 for the rules covering the host app and extension metadata too.