I can cite explicit text later if you require it
The DMA, DSA, GDPR as well as apples API documentation( you can read the preamble in the DMA).
In what service that Apple uses high level permissions are related to any of their CPS that meta could plausibly use?
My interpretation is that no such requirement can’t be argued on legal basis. Especially when Apple doesn’t have direct access to anybody the information. Apple can just allow existing APIs that do the same thing, make new APIs that enable the functionality without any privacy violations. If Apple allowed drivers and background processors they would be long past the line of legal obligations.
I could possibly try and steealman such points if it has any legal basis( stronly, weakly or zero) but then I would need some narrow examples.
I think there are cases where Apple can’t reasonably offer equivalent functionality to third-party devices without allowing persistent background access. So I will concede that the DMA doesn't explicitly require allowing high-level permissions, but it does say "you have to allow others to have the same features you give yourself", and certain features by definition require a background daemon or process running, then yes, the DMA requires giving third parties the ability to do that.
Two examples jump to mind. That said, I’m happy to be corrected by someone more knowledgeable. I'm about at my limit of understanding how these features work.
Universal Clipboard:
To do this, a third-party device would need to:
• Continuously monitor the clipboard for changes (requires a background process)
• Transmit clipboard contents securely to other nearby devices
• Inject data into the receiving device’s clipboard buffer
I don’t think this is something they can “just make an API for” without significant architectural tradeoffs. Apple would either have to allow a third-party daemon or fundamentally alter sandboxing - which would absolutely come with privacy and security implications that I don't think you can just waive away.
Device Unlock via Watch:
For a third-party smartwatch to unlock the iPhone like Apple Watch can, it would need:
• Always-on proximity sensing and Bluetooth/Wi-Fi negotiation
• A trusted identity framework tied to the OS
• Background execution to trigger the unlock action passively
Again, this requires privileged access not currently available to third-party devices. I don’t think it’s realistic to say they can “just create APIs” and check the box. These are deep integration points that go to the core of iOS. And unlocking the device absolutely has security and privacy implications. Which is why I think you're never getting iPhone mirroring in the EU.