Personally, I wouldn't have a problem with a UUID and the occasional "phone home" - if UUID X hasn't phoned home in Y days, it's no longer part of the install b

Personally, I wouldn't have a problem with a UUID and the occasional "phone home" - if UUID X hasn't phoned home in Y days, it's no longer part of the install base. Given that more CM users tend to be obsessive device-wipers, it may make sense to phone home more often; given the limited data points they're collecting, it's a negligible hit to users' data plans (though given some Android users' network misconfigurations, may be more of a hit to CM's servers than they'd expect). Transmitting and storing md5 hashes of device IMEIs and MAC addresses, though? No bueno. That the project owners don't see a problem with this (and that they believe cracking these hashes is non-trivial, especially given the restricted address space of these two data points) worries me far more than the data collection itself.