Privacy annoyance of the day... basically Apple knows about every app you launch for the first time. And for every every update you install, the first time you run it.

They make effort to forget these phone-home events, but it's a trust-me-bro privacy model. Which is not acceptable in a country with the Patriot Act. Even if that Act has some built-in protections, those are degraded by a declining appreciation for rule of law.

So when reading company statements like this, it's useful to replace some words - which I've done in square brackets. I'm still fully assuming good faith here, as well as no coerced lying.

> Privacy protections

> macOS has been designed to keep you and your data safe while respecting your privacy.

> Gatekeeper performs online checks to verify if an app contains known malware and whether the developer’s signing certificate is revoked. We have never [but could] combined data from these checks with information about Apple users or their devices. We do not [but could] use data from these checks to learn what individual users are using on their devices.

> Notarization checks if the app contains known malware using an encrypted connection that is resilient to server failures.

> These security checks have never included the user’s Apple Account or the identity of their device [but we can see your IP address]. To further protect privacy, we don't [but could] log IP addresses associated with Developer ID certificate checks, and we make sure that any collected IP addresses are removed from logs [but could stop doing that] .

https://support.apple.com/en-qa/102445

There is a stapling mechanism that developers can use to (maybe?) prevent these phone home events, but it's not mandatory and not always practical. More importantly, it's intended as a convenience for users that are offline when they first run an application, it's *not* intended as a privacy measure.

Reply to this note

Please Login to reply.

Discussion

Apple code signing has been a headache for open source projects for half a decade. But with notarisation it gradually turned into a privacy problem.

https://github.com/bitcoin/bitcoin/issues/15774

It seems both Apple and the vast majority of open source projects aren't worried about the phone home privacy issue, partially because they need all their mental energy to at least make their apps usable, it's hard to find good documentation on the exact privacy trade-offs here.

don't use mobile phones

don't use proprietary operating systems

cry harder about having to learn something technical

Almost everything is trust-me-bro in the Apple ecosystem. I read their whole privacy policy. You can insert "could" almost everywhere. It is very likely that they even know what you're typing on your QuickType keyboard. You can't verify anything and I don't trust their "differential privacy" gibberish. They had been caught lying several times in the past. All they do when someone finds out something is to change their privacy policies or just sweep it under the rug. Last month or so I looked at the network traffic of an iPhone which was set-up in the most possible private way (no iCloud, not logged in with an Apple-ID, every optional data sharing turned off). I was shocked about the amount of servercalls this thing still made (especially if you consider that this company claims or once claimed that everything what you do on the iPhone stays on the iPhone). It was permanently calling home no matter what you did. Open an app -> some Apple server is pinged. Type something on your keyboard, same. Look at your photos and some apple-image-servers (of course none of them are documented) were called. Even when it was idle it didn't stop. I find it really crazy and terrifying.

The Patriot Act is expired Sjors. You probably worry about the CLOUD Act and FISA 702.

I'm getting old :-) Just going to keep calling It Patriot Act, you can put lipstick on a pig...