People have certainly run afoul of the law when the data Google has about them is misused.
>Innocent man, 23, sues Arizona police for $1.5million after being arrested for murder and jailed for six days when Google's GPS tracker wrongly placed him at the scene of the 2018 crime
https://www.dailymail.co.uk/news/article-7897319/Police-arre...
We are only talking about what happens when you try to send the data to the cloud, after all. Not about all the data on the device.
None of this is true. A sibling comment describes the process:
>1. Only if you're uploading files are the files matched. 2. Only if the matches are very close are they considered matches. 3. Only if you have multiple very close matches is Apple able to decrypt the low-res versions of the images themselves. 4. Only if a human reviewer discovers any of the decrypted low-res images to be illegal content is any of your information shared with anyone else.
Google does reporting on how many National Security Letters requesting information about it's users that it responds to annually.
Why doesn't it just ignore them?
So does Apple[1]. Apple gave data on over 31,000 users/accounts based on National Security Letters in the first half of 2020 alone[1].
> Why doesn't it just ignore them?
In the first half of 2020, Apple provided data to the US government (non-FISA or NSL) about 9,000 times, and responded to requests for data with the data about ~85% of the time, and 92% in cases of "emergencies"[1].
Apple does not have a legal obligation to install spyware on your phone (at least not in the US, not yet).
2. What’s more important is you can reverse engineer algorithm that’s used locally to compare these hashes. Unlike with cloud-based searches other providers run, this puts significant limitations to what Apple or LEA can do on your phone. E.g. they can’t extract strings from PDF or grep through image metadata or request all images of certain users without knowing what these images would depict in advance. The frequency of hash database updates even if opaque will still provide more insight into what is being searched for compared to current status quo where public has zero insights because all search / aggregation queries are run on the server.
I get the arguments for why the fix for #2 is too dangerous to be worth it, but also get why they'd be inclined to choose it.
To the user - using your line of reasoning - they're both the same, right?
This isn't supposed to be a technical comparison, I just want to point out that the implementation matters as much (or more) than the customers' experience.
Technically Apple can do a scan regardless of wether or not you posted it to iCloud if they so desired to, or were ordered to.
Do you think it's likely they will do so?
Also, Google sells your data already don't they? Probably not a great counterpoint.
https://www.tampabay.com/news/2021/05/07/google-selling-user...
Nothing is happening to files you don't attempt to upload to the cloud.
Also, if Google is selling everyone's data to third party data brokers, it's news to me.
I am aware, but because the scanner now exists on the device, they have the capability of scanning images on your device regardless of whether or not you upload it to the cloud if they so choose to OR ARE ORDERED TO. Do you not see the difference in capability?
There is also the risk of algorithm mistakes. Without the trust + safety team or any cloud verification, does this just get immediately forward to the FBI?
What is the process to be made non-guilty if the Apple algorithm thinks you have something illegal and you don't if there is no human in the loop involved before it's forwarded to authorities?
At least if you upload to a service someone on the trust + safety team can verify the algo worked properly. I would be very nervous building this kind of system of the risk of false positives! Maybe even so nervous to introduce many more false negatives - which is in itself terrible in the case of something like CSAM.
1. Images which are going to be uploaded to iCloud are matched against known hashes. A match has to be very close in order to actually be flagged as a match. The results are uploaded to iCloud Photos along with your image. 2. If your account hits a sufficient threshold of matches (i.e. you have to have multiple/many images matched) then Apple is alerted and they are able to decrypt low-resolution versions of the relevant stored images. 3. Apple's team performs a manual review of the images to ensure that they are in fact inappropriate images and not false positives. 4. If any of the matched images are actually illegal, then Apple reports you to the authorities.
In other words, there are several safeguards in this process:
1. Only if you're uploading files are the files matched. 2. Only if the matches are very close are they considered matches. 3. Only if you have multiple very close matches is Apple able to decrypt the low-res versions of the images themselves. 4. Only if a human reviewer discovers any of the decrypted low-res images to be illegal content is any of your information shared with anyone else.
In my opinion, this is a vastly better system than literally any other cloud provider at the moment; it allows Apple to find and report even more CSAM with effectively no risk of reporting false-positives to law enforcement, while also preserving your privacy through encryption in transit and at rest.
Didn't Microsoft just start removing people's torrent clients from their computer without permission and announce that you wouldn't be allowed to use your own PC running Windows 11 Home without using an online Microsoft account to log in?
I am a user uploading a photo to the cloud.
Google's servers scan photos after they are uploaded to the cloud, and have done so for the past decade.
>a man [was] arrested on child pornography charges, after Google tipped off authorities about illegal images found in the Houston suspect's Gmail account
https://techcrunch.com/2014/08/06/why-the-gmail-scan-that-le...
Apple wants the device to scan the photo before it is uploaded to the cloud.
Both are equally invasive and both can only be avoided by refusing to use the cloud.