AppReviewFix
Guideline library
Apple App Store — Design

4.5.4 — Push notification abuse

Official source: App Store Review GuidelinesTopic overview: Spam, copycat apps, ads and deceptive design explained
What this guideline means

Notifications have to be tied to functionality the user actually wants — promotional or advertising content sent as a push notification, without being explicitly opted into, violates this guideline.

Why apps actually get flagged

Usually caught after user complaints about promotional pushes, or when a review build's notification permission prompt doesn't match what's actually sent afterward.

A real example

"Your app sends push notifications that are being used for advertising, promotions, or direct marketing purposes, which is not permitted per guideline 4.5.4."

The short version, in more detail

Guideline 4.5.4 says push notifications must be tied to something the user wants. Promotional or advertising content sent as push notifications, without explicit opt-in, is a violation. Reviewers often discover this when the notification permission request does not match what is sent afterwards, or after users complain about promotional messages.

Why this rule exists

Push notifications interrupt people at any time and appear on the most personal screen of the device. If apps used them freely for marketing, users would switch notifications off altogether, and legitimate alerts would be lost. By limiting notifications to functions users care about, and requiring consent for promotions, Apple protects the usefulness of the channel for every developer.

What this guideline covers

  • Notification permission requests and what they promise.
  • Promotional and advertising notifications.
  • Opt-in requirements for marketing messages.
  • Notifications that are required to use the app.

What usually triggers this rejection

  • Promotional pushes sent without opt-in.
  • A permission prompt that does not describe the kinds of messages sent.
  • Notifications used as advertisements.
  • Making notifications a condition of using the app.
  • Messages that are unrelated to app functionality.

How reviewers evaluate it

  • Reviewers examine the permission flow and any notification content.
  • They compare what the app says it will send with what arrives.
  • They respond to user complaints about unwanted messages.
  • They look for an opt-in for marketing messages.

Common misunderstandings

  • Having permission to send notifications is not permission to send promotions.
  • A reminder tied to app functionality is different from an advertisement.
  • The rule is about content type and consent, not just frequency.

Common questions

Can I send marketing notifications?

Only if users have explicitly opted in to them.

Are transactional alerts allowed?

Yes, notifications tied to the user's activity and needs are expected uses.

Do notification extensions matter?

They are reviewed against related rules about extensions.

Platform rules change often. This page is a plain-language explanation written by AppReviewFix, not official guidance. Check the current App Store Review Guidelines for the exact wording.

Got this exact rejection?Paste it in and get a diagnosis specific to your app, free.
Decode my rejection
Related guidelines
Ads — Ads policyAd Fraud — Ad fraud (Mobile Unwanted Software)Deceptive Behavior — Deceptive behaviorSocial Engineering — Social engineering and scarewareSystem UI Imitation — Unauthorized imitation of system UI
AppReviewFix
ProductDecoderPricingGuideline library
CompanyAboutFAQContact
ResourcesGuidesTopic overviewsCommon rejection reasons
LegalTermsPrivacy
© 2026 AppReviewFixBuilt by a developer, not a committee.