Apple updated its Developer Program License Agreement on October 13, highlighting security requirements, HomeView support and multi-seat subscriptions. Its announcement asks developers to review the changes and accept the revised agreement through their account. For teams shipping Apple-platform apps, the practical starting point is identifying which flagged features and commercial arrangements they use. [1]
Consent and feature boundaries
Section 3.2 bars collecting or transmitting user data beyond the consent disclosure, including through third-party code. Providing services to third parties using a user’s device or network requires explicit prior consent. SDK behavior therefore belongs in that review. [2]
The Live Assistance API is limited to user-invited accessibility services joining a FaceTime call, such as captioning or translation. App Replacement requires both apps to belong to the same Developer Program membership and retain substantially the same main purpose and functionality. [2]
HomeView and shared subscriptions
The agreement permits iOS widgets on CarPlay and HomeView, plus access on HomeView to eligible CarPlay apps running on a paired iOS device. The widget suitability assessment and disfavoredLocations requirement specifically concern CarPlay, including widgets that require extensive interaction while driving or an unlocked iPhone. [2]
Apple also flags Group Purchases for multi-seat subscriptions and Volume Purchasing for Apple Business and Apple School Manager organizations. Those arrangements merit a review of how subscriptions are offered and managed. [1]
Group Purchase refund terms allow full refunds or partial refunds for unused subscriptions, excluding seats currently accessed by active members from partial refunds. When developers manage invitations, Apple relies on their activity information to determine that status. [2]
The notice also identifies tax-reporting provisions and limits developers’ use of customer tax information supplied by Apple to legally required purposes. [1]
Check the Account Holder’s deadline
Apple’s public update does not state an acceptance deadline. Its account-access guidance says Apple emails the deadline to the Account Holder and displays it on the developer account page. Teams should check that specified timeframe rather than assume the announcement date is the cutoff. [1, 3]
Under that general guidance, missing the timeframe pauses certain resources for the whole team, including automatic signing, Xcode Cloud, TestFlight and Mac notarization. This does not establish that access is already paused for any particular account. [3]
The announcement identifies revised areas but provides no historical redline. The details above describe the current agreement, without treating every clause as newly introduced. Apple says translations will follow within one month. [1, 2]
