> A more troubling use of the data, not mentioned in the discussion so far, would be query driven usage, for example: Prosecutor: OK, lets query all phones with activity showing X among men in this geography and find ourselves a suspect.
That was long a problem with DNA data.
I don't know how completely they test DNA nowadays in criminal cases, but in the early days and for many many years afterwards the tests did not determine a unique individual. It just narrowed it down. There could be a large number of people in the world that would match the sample.
There were two correct ways to use DNA with that level of matching.
1. After you have narrowed down your list of suspects through ordinary, non-DNA police work to a small number of good suspects, then check their DNA. If exactly one suspect matches it is extremely likely that is the correct suspect.
2. It can be used to nearly conclusively eliminate suspects. (I say "nearly conclusively" because you are almost never sure that the DNA you are testing from the crime scene is actually from the criminal. There are almost always ways someone who was not the criminal could have left DNA at a crime scene).
Then there was the completely wrong way to use it, which, unfortunately WAS often used:
• Keep a database of DNA samples from a small subset of the general population, such as people who have been arrested. When you start investigating a crime and think you have a DNA sample of the criminal, check that against your database, and if you get a single match conclude that person was involved.
This approach of starting by looking up DNA from the crime scene in your database and focusing everything on a single match is only valid if:
A) the database includes everyone who could possibly be the criminal, or
B) your DNA test is comprehensive enough that it does identify people uniquely.
We don't do A yet, and as I said I don't know if the test they use nowadays are good enough to satisfy B.