Mobile identifiers for analytics can be accessed and used by apps on mobile devices in much the same way that websites access and use cookies. When visiting Enterprise Marketing pages, like resources.github.com, on a mobile device these may allow us and our third-party analytics and advertising partners to collect data for sales and marketing purposes.</p> <p>We may also use so-called “flash cookies” (also known as “Local Shared Objects” or “LSOs”) to collect and store information about your use of our Services. Flash cookies are commonly used for advertisements and videos.
APPROVED
No comment given
While I get everything about the unnecessary permissions, the title of the case says "App required for this service" but I would say in the case of GitHub, the mobile app is definitely not required. Except for the improved mobile UX & the possibility of getting push notifications, the app has less features than the mobile website. And everything what you can do on the GitHub desktop site you can also do on the mobile GitHub website.
Also for authentication purposes GitHub does provide enough & good alternatives to using the mobile app for MFA, not like other services do, such as passkeys, TOTP & also still U2F.
While I'm not sure how this case is usually used here, from its wording it feels to me it should only apply to services which actually force you to use their mobile app to access important features. Such as streaming services like Netflix.
Previous Status: PENDING
Updated Status: APPROVED
Title: App required for this service requires broad device permissions
Analysis: Generated through the annotate view
Status: PENDING