Apps that let a user remotely control another computer need to be connecting to hardware the user owns, manages, or has explicit permission to access — a remote-access app can't be a general-purpose tool for unauthorized access to arbitrary machines.
Comes up when a remote-desktop app's onboarding doesn't clearly establish that the connecting user has legitimate authorization to the target machine.
"Your app functions as a remote desktop client but does not ensure users are only connecting to devices they own or have permission to access, per guideline 4.2.7."
Guideline 4.2.7 sets conditions for remote desktop clients, apps that let a person control another computer. They must connect to machines the user owns, manages or has permission to access. A remote-access app that works as a general tool for reaching arbitrary machines raises obvious security and abuse concerns, so the authorisation of the user matters in review.
Remote control software is powerful. In legitimate hands it supports work and support, but it can also be misused to gain access to a computer without the owner's knowledge. Apple therefore expects such apps to establish that the person connecting is entitled to do so, and to avoid features that make unauthorised access easy, such as discovery of random machines or hidden operation.
Yes, with the conditions described.
There are specific limits about streaming content from a host.
The app should make sure the connecting user is authorised for the target.
Platform rules change often. This page is a plain-language explanation written by AppReviewFix, not official guidance. Check the current App Store Review Guidelines for the exact wording.