Apple Updates Developer Program License Agreement: New API Rules, HomeView Integration, Subscriptions, and Tax Compliance

Apple has released an updated version of the Apple Developer Program License Agreement, introducing revised security requirements, new API and entitlement terms, expanded provisions for CarPlay and Apple HomeView integration, and important clarifications concerning subscription distribution and tax compliance.

Announced on October 13, 2026, the update is intended to support new platform capabilities, reflect updated policies, and clarify developers’ contractual responsibilities when building and distributing apps across Apple’s ecosystem. Developers enrolled in the Apple Developer Program are required to review the revised agreement and sign in to their accounts to accept the updated terms. Source: Apple Developer

1. Updated Security Requirements — Section 3.2

Apple has revised Section 3.2, which governs how developers may use Apple software and services. The agreement establishes requirements relating to lawful software use, platform security, user privacy, and compliance with Apple's technical and program requirements.

The updated section covers several important responsibilities, including restrictions on software that interferes with Apple's security mechanisms, compromises system integrity, deceives users about an app's purpose or behavior, or collects data beyond what users were informed about when consent was requested.

Developers must also avoid creating software that impersonates Apple or other organizations to obtain sensitive information, deliberately weakens security protections, or uses a person's device or network resources to provide services to third parties without the user's prior explicit consent.

What this means for developers: Apps and services should be reviewed for their data-collection practices, authentication mechanisms, permission handling, and compliance with Apple's documented platform requirements. Developers should also ensure that software updates and post-review changes do not introduce behavior that contradicts the app's stated purpose or privacy disclosures.

Apple's announcement confirms that Section 3.2 has been updated, although its summary does not enumerate every individual textual change to that section. The examples above describe the relevant security obligations in the published agreement, rather than claiming that every provision is newly introduced by this update. Source: Apple Developer Program License Agreement

2. New Live Assistance API Terms — Section 3.3.8(j)

The revised agreement introduces specific contractual terms for the Live Assistance API, which allows an application or corresponding product to connect to an end user's FaceTime call.

Under the agreement, the API may be used, at the end user's invitation, to enable an accessibility service provider to join the call and deliver accessibility services. Examples expressly identified by Apple include captioning and translation.

This creates a defined contractual framework for accessibility experiences that operate during FaceTime calls. For example, a compatible service could help a participant access live captions or language translation during a conversation.

However, the agreement limits this use to the stated accessibility purpose. Developers should not interpret the new definition as general permission to connect third parties to FaceTime calls for unrelated purposes.

Developer takeaway: Teams developing accessibility applications or services that interact with FaceTime should review the API documentation, consent flows, and applicable entitlement requirements before integrating the capability.

3. App Replacement Entitlement — Section 3.3.8(k)

Apple has also specified the terms governing the App Replacement Entitlement, a capability designed to facilitate the transition from an existing application to its replacement.

According to the agreement, the entitlement can display a system interface when the replacement app launches for the first time. That interface gives the user the option to transfer data and settings from the previously installed application and delete the original app.

Apple also places an important restriction on eligibility: both the original application and its replacement must belong to the same developer's Apple Developer Program membership, and they must have substantially the same primary purpose and functionality.

This is particularly relevant to developers who rebuild an existing application, migrate users to a replacement version, or restructure their apps while preserving continuity for existing customers.

Developer takeaway: Before planning an app migration around this entitlement, developers should verify that both applications qualify, assess data-transfer compatibility, and design a migration experience that gives users an informed choice. The entitlement should not be treated as a general-purpose mechanism for replacing unrelated applications.

4. CarPlay and Apple HomeView Integration — Sections 6.4, 6.4.1, and 6.4.2

The updated agreement clarifies how iOS application widgets and eligible applications may be made available through CarPlay and Apple HomeView.

iOS widgets on CarPlay and Apple HomeView

Under Section 6.4.1, an iOS application widget may be made available on CarPlay and Apple HomeView. Developers are responsible for evaluating whether their widgets are functional and appropriate for the relevant environment.

For CarPlay, Apple specifically identifies widgets that require extensive interaction while driving or require the iPhone to be unlocked as examples of potentially unsuitable experiences. Developers must use the documented disfavoredLocations function to indicate locations where their widgets should be disfavored when they are not suitable for use.

Apple also reserves the right to disfavor widgets it considers inappropriate for CarPlay.

This makes the design of a widget more than a visual or technical consideration: its suitability for the context in which it appears is also important.

Availability of iOS apps through Apple HomeView

Section 6.4.2 addresses access to iOS applications through Apple HomeView. If an application has a CarPlay entitlement profile belonging to a category identified by Apple in its documentation, Apple may make that application accessible through HomeView while the app is running on a paired iOS device.

This provision establishes conditional availability rather than a guarantee that every iOS app will appear in HomeView.

Developer takeaway: Developers working on CarPlay-compatible apps should review their entitlement eligibility, applicable documentation, and widget behavior. Apps and widgets should prioritize clear information, minimal interaction, and suitability for their intended context.

5. Expanded Subscription Group Purchase Terms — Schedule 2

Apple has revised several provisions in Schedule 2 concerning Group Purchases, which enable subscriptions to be purchased together for use by multiple end users.

The updated provisions cover Sections 1.1(b), 1.2(d)(iv), 3.1, and 3.8(c).

These changes are relevant to subscription developers whose products support multi-user access, including services that an organizer can purchase for a group of people.

The agreement addresses Apple's role in facilitating group purchases through a single transaction, alongside the developer's responsibility to deliver the subscription benefits promised to users. The subscription must be fulfilled throughout the applicable subscription period, including any authorized billing grace period. The agreement also sets out refund provisions for certain group purchases when contractual obligations are not met.

Developer takeaway: Teams offering group subscriptions should examine their subscription configuration, entitlement management, invitation processes, and refund handling. They should ensure that subscription benefits remain available to eligible group members for the promised duration.

6. Volume Purchasing for Apple Business and Apple School Manager — Schedule 3

Schedule 3 has received corresponding revisions concerning subscriptions offered to organizational customers through Apple Business and Apple School Manager.

The affected provisions are Sections 1.1(b), 1.2(d)(iii), 3.1, 3.8(a), and 3.8(c).

Volume Purchasing is relevant to organizations that acquire applications or subscriptions for multiple employees, students, or other authorized users. Under this model, an institutional purchaser can obtain an eligible auto-renewable subscription for access by a group of individuals.

The revised agreement specifies contractual terms for making these subscriptions available through Apple's organizational purchasing channels.

For developers, this makes it important to distinguish consumer-facing group subscriptions from subscriptions purchased by an institution. Each distribution model operates under its relevant schedule and program requirements.

Developer takeaway: Businesses developing productivity software, educational platforms, collaboration tools, or other multi-user subscription products should review their eligibility and purchasing configuration in App Store Connect, as well as the applicable requirements for organizational customers.

7. Tax Reporting and Customer Tax Information — Schedules 2 and 3

The update also clarifies Apple's and developers' obligations concerning tax compliance and information disclosure.

Reporting information to tax authorities

Sections 3.3(a) of Schedules 2 and 3 specify that Apple may disclose information supplied by developers to applicable tax authorities when required by law. The information may include tax, sales, and contact details.

The agreement makes clear that legally required disclosures do not constitute a breach of Apple's otherwise applicable confidentiality obligations.

Restrictions on the use of customer tax information

Sections 3.3(b) of both schedules address information Apple may provide to developers when disclosure is legally required.

Developers receiving such information may use it only for legally required tax-compliance purposes, including tax reporting, tax remittance, and audits. The information cannot be repurposed for unrelated activities.

These provisions are especially important for developers whose applications are sold internationally or whose distribution arrangements involve tax reporting in multiple jurisdictions.

Developer takeaway: Developers should review their tax documentation, confirm that their information in App Store Connect is accurate, and ensure that any customer tax data they receive is handled under appropriate access controls and used only for permitted purposes. These contractual requirements do not, by themselves, eliminate developers' separate tax obligations under applicable law.

8. What Developers Should Do Next

Although the announcement does not indicate that every developer must immediately redesign an existing application, the revised agreement should be reviewed in the context of each developer's products and services.

Recommended next steps include:

• Review and accept the agreement: Sign in to the Apple Developer account and review the updated terms.
• Audit security and privacy practices: Check data collection, consent flows, authentication, security protections, and third-party integrations.
• Evaluate relevant API eligibility: Developers using or planning to use the Live Assistance API or App Replacement Entitlement should review the corresponding documentation and contractual restrictions.
• Assess CarPlay and HomeView compatibility: Verify widget suitability, entitlement eligibility, and the relevant interaction requirements.
• Review subscription distribution: Confirm that group subscriptions and organizational subscriptions are configured and fulfilled in accordance with their respective schedules.
• Check tax compliance procedures: Validate tax information, review reporting workflows, and restrict the use of customer tax information to permitted purposes.

Developers should consult the full agreement rather than relying solely on the announcement's abbreviated change log, particularly when a provision affects their app's architecture, entitlements, data handling, or commercial model.

Conclusion

Apple's October 13, 2026 update addresses several areas of the developer ecosystem: security and responsible software use, accessibility-related FaceTime integration, application migration, CarPlay and HomeView availability, multi-user subscriptions, and tax compliance.

The practical impact will depend on the application's features and distribution model. Developers building accessibility services, migrating existing apps, supporting CarPlay, or offering subscriptions to groups and institutions should pay particular attention to the corresponding sections.

Action required: Sign in to the Apple Developer account to review and accept the revised Apple Developer Program License Agreement.

Official announcement: https://developer.apple.com/news/?id=17mwd36z

Full agreement: https://developer.apple.com/support/terms/apple-developer-program-license-agreement/