Apple has updated its Developer Program License Agreement to govern how third-party accessories can access iPhone notifications and Live Activities establishing the Apple privacy rules for third-party notifications and Live Activities before the features ship. For EU iPhone users, the practical outcome is this: you will be able to route notifications to a non-Apple smartwatch, but you’ll have to give up Apple Watch notifications to do it, and the rival watch still won’t get Apple Watch-level actions such as replying, dismissing, or muting notifications.

The updated agreement adds section 3.3.3(J), formally establishing the Accessory Notifications Framework and Accessory Live Activities Framework as official developer terms, according to 9to5Mac this week. Apple is locking in the legal architecture before the features ship. The privacy restrictions attached to that architecture look unusually strict by Apple API standards.

Apple itself has characterized this kind of access as a serious privacy threat. Notification data can include message content, medical alerts, and one-time codes information that, as Apple noted about three and a half months ago, would be exposed to third parties in ways that even Apple cannot access today. The new license terms are Apple’s answer to its own concern.

Why Apple is doing this: the DMA forced the issue

These features exist because the EU compelled them, not because Apple chose to extend its ecosystem. That context is prerequisite to reading the privacy rules correctly: they are simultaneously a user protection and a compliance posture.

About a year ago, the European Commission formally instructed Apple to open nine iOS connectivity features to third-party device makers, including notification-related integrations, NFC access, and device pairing. Non-compliance with the Digital Markets Act carries penalties of up to 10% of global annual turnover, TechCrunch reported.

The Commission has since confirmed that Apple will roll out the interoperability features in Europe during 2026. That timeline reflects external pressure, not an internal product roadmap, MacRumors reported this week. Notification forwarding, Live Activities support, and proximity pairing for third-party wearables are scoped exclusively to EU users. Apple has given no indication it plans to extend any of this globally, keeping the entire exercise as a compliance obligation rather than a platform evolution.

The EU also pushed Apple for more predictable timelines and better technical documentation for interoperability requests, per TechCrunch a pointed signal that Apple’s compliance has been opaque as well as reluctant. The AccessoryNotifications and AccessoryLiveActivities frameworks remain undocumented on Apple’s developer portal today.

How Apple privacy rules for third-party notifications and Live Activities limit wearable makers

The new license terms don’t just define what third-party accessories can receive. They define, at unusual length, what accessory makers are forbidden from doing with that data: a list that maps closely onto the most commercially valuable uses of notification content.

Under section 3.3.3(J), developers are barred from using forwarded notification or Live Activities data for advertising, user profiling, AI or machine learning model training, or location tracking. They also cannot pass the data to any other application or device beyond the single accessory a user has configured to receive it, per 9to5Mac.

Remote storage is prohibited except when strictly necessary to complete delivery. Decryption is permitted only on the accessory itself, and the encryption keys tied to the data cannot be shared with any other device, including the user’s own iPhone. Accessories also cannot alter forwarded content in any way that changes its meaning, and cannot relay it onward, the same report notes.

In practice, the rules specifically foreclose:

Syncing notification history to a companion app
Summarizing messages with an on-device AI model
Building a cross-device notification hub
Relaying data to cloud infrastructure for processing or storage beyond delivery

These constraints are structured to prevent forwarding access from becoming a data collection channel. They protect users, and they happen to eliminate the most commercially interesting things a rival accessory maker might build around notification data. Both things are true at once.

Why Live Activities are a separate concession

Notifications and Live Activities operate under the same framework restrictions, but they represent meaningfully different types of data and Apple’s consent language treats them differently.

A standard notification is a discrete event: a message arrives, a payment clears, an alarm fires. Live Activities are something else. They expose ongoing, real-time context: a flight’s current gate and boarding status, a food delivery tracking its route, a sports score updating as the game progresses, a rideshare driver’s position on a map. That data stream can reveal purchasing behavior, travel patterns, and health-related activity in ways that a one-off notification typically doesn’t.

That’s why iOS will explicitly warn users, when enabling Live Activities forwarding, that shared content may include “app names and app content, which may contain personal information such as your health data, location data, and purchasing history,” according to 9to5Mac. That warning does not appear in the baseline notification forwarding flow. Users can grant access per-app or across all current and future installed apps, with Apple explicitly flagging the risks of the broader option.

The AccessoryLiveActivities framework was identified in iOS 26.5 beta 1 code this week, per 9to5Mac. Apple has not published documentation for it, and the feature has not been announced publicly. The stricter consent requirements for Live Activities aren’t incidental they reflect the richer, more persistent data exposure involved, which is also why this access represents a distinct regulatory concession rather than a footnote to notification forwarding.

What EU users and third-party wearable makers actually get

Apple has structured both frameworks around the user rather than the app developer. Apps do not need to integrate with the Accessory Notifications Framework for their data to be forwarded. Sharing is governed by a user-level setting, meaning a third-party wearable could receive notifications from any app on the device once the user enables it without requiring any action from app developers, according to 9to5Mac.

Worth noting: when notification forwarding appeared in Settings on iPhones outside the EU during iOS 26.3 betas, it showed up on devices worldwide, MacRumors reported about three and a half months ago. Apple is building these hooks into iOS universally while limiting functional access by region confirming the infrastructure is global even if the permission isn’t.

The one-device-at-a-time limit is not a minor implementation detail. EU users who own an Apple Watch and want to try a third-party wearable face a hard choice: enabling notification forwarding to the rival device turns off notification delivery to Apple Watch entirely. Apple states this plainly in the setup flow. That’s a meaningful disincentive to switching, built directly into the system design.

Here is what each group actually gains:

EU users get genuine wearable choice, but with a real tradeoff if they already own an Apple Watch, and with constrained functionality on whichever third-party device they choose.
Third-party wearable makers get system-level access to display notifications and Live Activities but cannot perform Apple Watch-level actions such as replying, dismissing, or muting, and cannot build cloud-connected or AI-enhanced experiences around the data, per TechCrunch.
Non-EU users get no near-term change. The features are geographically locked, and Apple has given no indication they will travel.
Where this leaves Apple, wearable makers, and the EU

Apple has now set both the technical architecture and the legal terms for third-party access to iPhone notifications and Live Activities. The frameworks are in the iOS 26.5 beta, the license language is live, and the European Commission has confirmed a 2026 launch window. This is moving toward an actual product, not a regulatory press release.

The privacy restrictions are aggressive by any standard: no model training, no advertising use, no cloud sync beyond delivery, end-to-end encryption to the accessory only. They protect users, and they happen to constrain every commercially interesting thing a rival accessory maker might want to build around notification data, as 9to5Mac documented this week.

The one-device limit and the absence of rich notification actions mean the functional gap between Apple Watch and a compliant third-party smartwatch remains wide. That gap was the core complaint that triggered EU scrutiny to begin with, and it has not been resolved, per TechCrunch’s original reporting.

What adequate DMA compliance looks like here is reasonably defined: broader notification action support, documented public APIs with predictable review timelines, and a one-device limit that doesn’t function as a structural deterrent to switching. Apple has not met that bar yet. Whether Brussels treats the 2026 launch as compliance or a starting point is the question that will determine whether any of this matters beyond Europe.