Apple updates the Developer Program License Agreement and App Review Guidelines (June 2026)

Original announcement (source): Apple Developer News - “Updated Apple Developer Program License Agreement and App Review Guidelines now available” (June 8, 2026)

• https://developer.apple.com/news/?id=a233fmpw

What changed (high signal)

Apple updated both the Apple Developer Program License Agreement and the App Review Guidelines.

From a growth and release-ops perspective, the practical themes are:

• More explicit developer identity and compliance obligations (including responding to questions and providing information).
• More specific language around “AI / models” usage (Apple models and ML tech grouped and clarified).
• More “you’re responsible” framing around safety (kids/teens guidance, and developer responsibility for guideline-violating content).
• Tighter language around engagement surfaces (e.g., Live Activities cannot be used to spam, phish, or send unsolicited messages).

Details Apple called out (quick read)

License Agreement

Apple listed updates that mention (among other things):

• Developer identity and information requirements (including export compliance contexts).
• Clarifications for use of frameworks/APIs such as Sensitive Content Analysis, Suggested Actions API, Trust Insights, Customer Engagement APIs, and updates to Foundation Models requirements.
• Notes that analytics may be available via Xcode and/or App Store Connect API.
• Clarifications around App Store Connect information and protections for end users who are minors.

App Review Guidelines

Apple highlighted changes to:

• Introduction (kid and teen safety guidance)
• 1.2 (developer responsibilities for content that violates the guideline)
• 4.3(a) and 4.3(b) (clarifications + examples)
• 4.5.3 (Live Activities not for spam/phishing/unsolicited messaging)

Why this matters (for app marketing teams)

These updates usually show up as:

• “small” copy or workflow tweaks that become big review risk later, especially for:
  • kid/teen surfaces
  • user-generated content
  • any always-on messaging surface (Live Activities, in-app inboxes, feeds)
• unplanned engineering work when “marketing” surfaces are treated like a free channel.

What to do (tiny win)

1. Audit your always-on surfaces (Live Activities, in-app inbox, persistent banners): write down what counts as “unsolicited”, and where you could look spammy.
2. Update your internal checklist: add one pre-release question for kid/teen safety, and one for developer identity/compliance responses.
3. If you use AI features: document what data is sent, where it’s processed, and what user control looks like (before you need it for review).

Read the original: https://developer.apple.com/news/?id=a233fmpw