Apple scans files on your device, using your resources (storage, compute, power).

Google scans files on their devices, using their resources (storage, compute power).

It is you who decided to upload files to Google's cloud.

However, it is difficult to use your own device if you don't have privacy there.

Apple’s proposal means that your data will never leave your device unencrypted - they can’t scan it on their servers due to inherently having quite good privacy in the first place.

The feature Apple proposed would only apply to files you were uploading to iCloud. Turning off iCloud photos prevented scanning.

The whole point of the Apple system was to enable end to end encryption so Apple couldn’t view your data on their servers. The only way they could get access is when a threshold of CSAM likely files were met. e.g the keys are sharded.

With the Apple approach you have considerably more privacy.

For now. The foot would be in door to enable it system-wide.

Why would they care about getting a foot in a door that they have the keys to and is wide open?

Modern SoCs have security domains that are invisible to the main CPUs. Apple can run just about anything it wants on the security coprocessor and users will be none the wiser.

The American DOJ, FBI etc do not want end-to-end encryption and use ‘think of the children’ as an excuse. This gives Apple the plausible pushback to say ‘We have thought of the children…’

Politicians feet not Apple's.

Apple don’t scan files on your device, they backtracked on the plan (for now at least).

Apple absolutely scans your files on iCloud.

ybeh intended to but the backlash was too strong. not a vote of confidence in them either way.