AppReviewFix
Guideline library
Apple App Store — Extensions

4.5.3 — Apple Services spam prevention

Official source: App Store Review Guidelines
What this guideline means

Integrations with Apple's own services — Game Center leaderboards and invites, iCloud sharing, contact-based invites — can't be used to blast unsolicited invitations or notifications to other users at scale.

Why apps actually get flagged

Common with social or gaming apps whose "invite friends" flow auto-sends messages to a user's entire contact or Game Center friends list without individual confirmation.

A real example

"Your app sends unsolicited messages or invitations to users via Apple services, which is considered spam under guideline 4.5.3."

The short version, in more detail

Guideline 4.5.3 stops apps from using Apple's own services, such as Game Center, iCloud sharing or contact-based invitations, to send unsolicited messages in bulk. Features that automatically invite a user's entire friend list or contacts without individual confirmation are what the rule targets. Social and gaming apps with growth-driven invite flows are the usual source.

Why this rule exists

Services such as Game Center and iMessage rely on trust between people who know each other. If an app could use them to blast invitations to everyone on a list, users would receive unwanted messages and the services would lose value. The rule keeps invites a deliberate act by the user and prevents developers from treating Apple's social graph as a free marketing channel.

What this guideline covers

  • Game Center invites, challenges and leaderboards.
  • iCloud sharing and contact-based invitations.
  • Messaging through Apple-provided features.
  • Automatic or bulk invitations sent on the user's behalf.

What usually triggers this rejection

  • An invite flow that sends messages to every contact automatically.
  • Game Center invitations sent without per-recipient confirmation.
  • Notifications to friends that the user did not choose to send.
  • Prompts that pressure users to share with many people.
  • Using the services to promote the app to non-users at scale.

How reviewers evaluate it

  • Reviewers run the invite and share flows.
  • They look at whether the user confirms each recipient.
  • They consider the volume and nature of messages sent.
  • They respond to complaints about unsolicited invitations.

Common misunderstandings

  • Permission to access contacts is not permission to message all of them.
  • A one-tap "invite all" is not treated as individual consent.
  • The rule is about unsolicited bulk messages, not all sharing.

Common questions

Can my app invite friends?

Yes, when the user chooses the recipients.

Does this cover SMS invites?

The principle is the same: invitations should be individually initiated.

What about group challenges?

They are fine when the user controls who is included.

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
4.3 — Spam4.1 — Copycats and app impersonation4.2 — Minimum functionality4.5.4 — Push notification abuse4.2.3 — App independence
AppReviewFix
ProductDecoderPricingGuideline library
CompanyAboutFAQContact
ResourcesGuidesTopic overviewsCommon rejection reasons
LegalTermsPrivacy
© 2026 AppReviewFixBuilt by a developer, not a committee.