I am evaluating Apple Music integration for a paid Windows desktop application that lets users migrate playlists they own between music services. The app would not stream, download, cache, redistribute, or monetize Apple Music audio, artwork, or previews. The Apple Music integration would be limited to: reading the user’s playlists; matching songs using catalog identifiers and metadata; creating playlists in the user’s Apple Music library; reconstructing the user’s playlists on another music service at their explicit request. I would like to clarify whether this type of user-initiated playlist migration is compatible with MusicKit / Apple Music API terms, especially for a paid application. If this is not the correct forum for a policy question, could an Apple engineer please point me to the appropriate channel? Thank you.

Hello, I am building a Windows desktop application that lets users migrate their own playlists between music services. Apple currently documents automatic Music User Token management for Apple platforms and web apps, and manual token management for Android. I could not find a documented native Windows authorization flow. My proposed architecture is: Windows desktop app → system browser → MusicKit on the Web authorization → return authorization to the same Windows desktop app. The desktop app would then call Apple Music API directly using a developer token issued by my backend and the user authorization obtained through MusicKit. My questions are: Is there a supported way for a Windows desktop app to obtain a Music User Token through MusicKit on the Web and then use that token from the desktop process? Is handing the token back from the browser to the same Windows device supported? If yes, is there a recommended handoff mechanism or lifecycle/refresh guidance? Is secure local storage of that Music User Token on Windows supported? I am not asking about playback. The intended usage is only reading the user’s playlists and creating playlists through Apple Music API. The Media Services private key would remain server-side and would never be shipped with the desktop application. Thank you.