I had a map open in the browser, one of the standard ones, with seven pins I had placed over the past three weeks. All the locations where I had documented him. I refreshed the page because it was loading slow and when it came back three of the pins were gone. Not the oldest ones, not the newest ones. Three from the middle. There is no mechanism in that software for selectively removing three mid-sequence pins from a saved list unless someone accessed the account, but the account session was still active on my device and I had not logged out, which means either the session was accessed remotely while still valid or the server-side list was edited directly. I understand how that sounds.

What the browser history shows is the route request from the previous day is still there, pointing to an address that corresponds to one of the removed pins. The route request did not disappear. Only the pin did. I do not know what that distinction means but I believe it means something because the route request is client-side history and the pin was server-side storage. Whoever removed it had write access to the server-side data but apparently did not think to also clear the local history. That is a specific kind of partial cleanup. That is the kind of cleanup that knows what it is doing but worked faster than it should have.

I have the four remaining pins and the browser history from the day before. I am not relisting the addresses here. If the map can be edited, this page can be edited, and I am not interested in making it easier to clean the record a second time. I have the printout. I have it somewhere they cannot reach. That part is handled.