|
|
|
|
|
by shadowgovt
2395 days ago
|
|
If the user had the phone configured as a corp phone and was taking photos and did not have Cloud backup enabled to automatically shunt those photos to their personal account, then when the phone is forcefully de-corped, it will try to purge local photo cache (because there's no way to know if photos in local cache were corp-sensitive or not, so the conservative solution is "Burn it all down"). Of course, if the user does have their Cloud backup enabled to automatically shunt photos, they're at risk of using the phone in a work environment and accidentally storing proprietary info in their personal account. The fact the camera UI doesn't really allow you to choose what account you're snapping photos under makes the whole arrangement lose-lose, and this is a really easy failure mode for a user to find themselves in if they don't see it coming. |
|
Sounds like a lose-lose and I'm a strong believer in that if a company the size and as wealthy as big G wants a contractor to make use of a device to accomplish a task for them, they can provide the device and do what they will to it afterward and then re-purpose it for the next round of business. This isn't a new operational pattern, and I've never experienced otherwise. They don't need to buy new, just keep a supply of devices for contractors.