Four Myths About Google Timeline Evidence in Custody Cases
In late 2024, Google started moving Maps Timeline off its servers and onto the phone itself, and by the following year the on-device rollout was reaching users worldwide. The web version went away. Timelines became tied to a single handset, and the default retention window shrank. For most people, this was a privacy footnote. For anyone in the middle of a custody fight, it changed what a lawyer can subpoena, what a client can export, and what the other side can plausibly claim was deleted.
Family courts have been absorbing this kind of evidence for years. What’s changed is how much of it now sits on the device in your pocket, and how many assumptions people still carry about it that fall apart in a courtroom.
Myth: Turning Off Location History Wipes the Trail
Toggling Location History off in Google Maps stops new Timeline entries from being written. It doesn’t clear what’s already there, and it doesn’t touch the dozen other places your phone records where it’s been. App logs, photo metadata, ride-share receipts, food delivery confirmations, toll transponder pings, and carrier records all keep going.
A family law attorney asked to preserve evidence in a custody matter will typically send a preservation letter that reaches well beyond a single Google setting.
Worse, deleting Timeline entries after a case is filed can look like spoliation. Judges have wide latitude to instruct a jury (or themselves, in a bench trial) that missing evidence should be presumed unfavorable to the party that erased it. The safer move is to preserve everything and let counsel decide what’s relevant.
Myth: A Blue Dot on a Map Proves Where a Parent Was
Timeline data is powerful, but it shows a device, not a person. Forensic analysts who work these cases draw a sharp line between device presence and person presence, and courts are learning to draw the same line. A phone left charging on the kitchen counter while a parent runs an errand will produce a Timeline that says the parent was home. A teenager borrowing mom’s old handset for the afternoon will produce a Timeline that says mom was at the mall.
This is why cross-examination on Timeline exhibits tends to get technical fast. Whose account was signed in? Which handset produced the entry? Was the location derived from GPS, Wi-Fi triangulation, or a cell tower estimate with a half-mile radius? A single screenshot answers none of that.
Myth: A Screenshot Is Good Enough for Court
Screenshots get filed all the time, and they get challenged all the time. Opposing counsel can argue the image was cropped, edited, or pulled from a device whose clock was wrong. Under Rule 902, machine-generated records can be self-authenticated with a certification and a hash value, but only if someone did the work to preserve the file that way at the time of collection.
In practice, the useful version of Timeline evidence is a full export, hashed and dated, not a phone photo of a phone screen. If a client hands over screenshots months after the fact, an examiner may still be able to work with them, though the fight over admissibility gets longer and more expensive.
Myth: The Other Parent Can Just Pull the Records From Google
That used to be closer to true. With Timeline now stored on the device, a subpoena to Google returns much less than it once did for the same time period. The data a court actually wants often lives only on the handset, which means access flows through discovery orders directed at the other parent, not through a third-party subpoena to a tech company.
That changes who holds the cards. It also raises the stakes on device preservation orders early in a case, because a factory reset, a lost phone, or an upgrade to a new handset can make the Timeline effectively unrecoverable.
What to Actually Do If Your Phone’s History Might Matter
Timeline evidence is one more record the phone was making all along, neither magic nor a trap. Handled early, it can corroborate a parent who’s telling the truth. Handled late, it becomes a fight about what got deleted and why.
