It sounds like this was a bug where slight updates to geolocation data (his address updated its physical location, probably to be more accurate) triggered a "location moved" process. Annoying, but not indicative of a new policy.