# Guideline 4.5.3 - Design: Spam via Push Notifications

**Guideline:** 4.5.3 · **Store:** Apple App Store · **Severity:** high · **Fix difficulty:** medium · **Typical turnaround:** 2-8 hours

Canonical URL: https://appstorereject.com/rejections/apple/4/guideline-453-design-spam-via-push-notifications

## Description

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.

## Common variations

- App uses push notifications for unsolicited promotional content
- Push notifications used for advertising without explicit opt-in
- App sends marketing messages through APNs without user consent
- Push notification implementation suggests spam-like patterns
- No opt-out mechanism provided for promotional notifications

## Example rejection email

```
Guideline 4.5.3 - Design - Apple Sites and Services

Your app appears to use the Apple Push Notification service for purposes that could be considered spam. Specifically, the app sends unsolicited promotional or marketing content through push notifications without explicit user opt-in.

Push notifications must not be used for advertising, promotions, or direct marketing purposes unless the user has explicitly opted in to receive such messages and a clear method to opt out is provided within the app.

Next Steps:
Please revise your push notification implementation to ensure:
- Promotional notifications require explicit user opt-in
- Users can easily opt out of promotional notifications within the app
- Push notifications are primarily used for transactional, informational, or user-requested content
```

## Resolution steps

## Quick Assessment
- **Risk level:** High — push notification abuse can lead to APNs certificate revocation
- **Resolution path:** Implement notification preferences with opt-in for promotional content
- **Typical turnaround:** 2-8 hours

## The Fix

01. **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).

02. **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.

03. **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.

04. **Add opt-out to every promotional notification** — Each promotional push should deep-link to notification preferences so users can easily turn off that category.

05. **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.

06. **Document in Review Notes** — Explain your notification categories and that promotional notifications require explicit opt-in.

## Prevention
- Default all promotional notification categories to off
- Build notification preferences into your app from day one
- Never send push notifications that the user didn't explicitly ask for or expect
- Rate-limit promotional notifications even for opted-in users
- Test your notification flow with Apple's 'provisional notifications' feature

## Appeal guidance

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 examples

**Before:** 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
**After:** 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
**Why it works:** Push notifications must be categorized, with promotional content requiring explicit opt-in and an easy opt-out mechanism.

## Common questions

**Can you appeal a 4.5.3 rejection?**

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.

**How long does this typically take to fix?**

Typical turnaround is 2-8 hours (difficulty: medium). After resubmission, most re-reviews complete within 24-48 hours.

---
*Machine-readable source: https://api.appstorereject.com/api/rejections/detail?slug=guideline-453-design-spam-via-push-notifications*