Guideline 4.5.3
Guideline 4.5.3 - Design: Spam via Push Notifications
Our Take
Apple is rejecting your app because it uses Apple Push Notification service (APNs) to send spam, including unsolicited promotional messages, phishing attempts, or deceptive content through push notifications. Guideline 4.5.3 specifically prohibits using push notifications for advertising, promotions, or direct marketing purposes unless users have explicitly opted in and there is a clear way to opt out. This rejection can also be triggered if Apple's review team examines your push notification implementation and determines that the app's notification patterns are likely to result in spam-like behavior — even if you haven't sent any yet. If your backend shows marketing campaign infrastructure tied to push tokens, or if your notification categories suggest promotional intent, the reviewer may preemptively flag this. The key distinction is between transactional notifications (order updates, reminders the user set, security alerts) and promotional notifications (sales announcements, feature promotions, re-engagement campaigns). Transactional notifications are expected and welcome. Promotional notifications require explicit opt-in. The fastest compliant path is to implement a clear notification preferences screen where users can control exactly which types of notifications they receive, with marketing/promotional notifications defaulted to off.
Resolution Guide
Categorize your notifications
Separate your push notifications into categories: transactional (order updates, security alerts, reminders), informational (content updates the user subscribed to), and promotional (sales, re-engagement, feature announcements).
Build a notification preferences screen
Create an in-app settings screen where users can toggle each notification category on or off. Marketing/promotional categories must default to OFF.
Implement opt-in for promotional notifications
Add an explicit opt-in flow for marketing notifications. Don't bundle it with the iOS notification permission prompt — it must be a separate, clear choice.
Add opt-out to every promotional notification
Each promotional push should deep-link to notification preferences so users can easily turn off that category.
Remove spam patterns from your backend
If your push notification backend has campaign/blast functionality, ensure it only targets users who have opted in to promotional notifications.
Document in Review Notes
Explain your notification categories and that promotional notifications require explicit opt-in.
Prevention
Example Rejection Email
Consider Appealing
Appeal if the reviewer miscategorized your transactional notifications as promotional. Provide examples of the actual notification content and explain how each type relates to user-initiated actions. If you are sending marketing notifications, add opt-in controls and resubmit.
Before & After
App requests push permission on first launch and sends daily promotional notifications about sales and new features to all users with no way to opt out of marketing content specifically
App separates notifications into 'Order Updates' (on by default), 'Content Updates' (on by default), and 'Promotions & Deals' (off by default, requires explicit opt-in), with a preferences screen accessible from Settings
What changed: Push notifications must be categorized, with promotional content requiring explicit opt-in and an easy opt-out mechanism.
Community Solutions · 0
Sign in to share your solution.
More Guideline 4 (Design) rejections
- Guideline 4.0 - Design: App Does Not Include iOS Features
- Guideline 4.0 - Design: App Looks Like a Website
- Guideline 4.0 - Design: Apple Pay Button Not Following Guidelines
- Guideline 4.0 - Design: Blurry Icons or Low-Resolution Assets
- Guideline 4.0 - Design: Broken Layout on iPad
- Guideline 4.0 - Design: Content Clipped by Notch or Safe Area