- 148 Posts
Concern over Motorola access to log files
Is anyone besides me concerned over the access Motorola through MotoBlur has to log files on the phone? As an example; I write medical software a d if I crash while browsing a confidential file the patient name may be exposed, which is a violation of HIPAA (federal) and I am potentially liable.
Another example, you are browsing or viewing information that you don’t necessarily want others to be aware of and you crash, the log of what you were doing is automatically sent to Moto.
I find this disturbing and creepy. I bought a phone, did not relinquish my privacy to Moto. This is way too intrusive for me, and because you must register for MotoBlur, this is part of the rights given to the, and they use this frequently.
- 03-10-2011, 11:50 AM #2
I posted something about some issues over on the moto site a week or two ago and they came back and said that my crash logs showed x,y & z. I replied back asking how did they get that data and here is their response
Crash data is reported back to Motorola to help better analyze failures and so we can promplty fix any major problems seen in the field. For example, the significant number of crashes in different 3rd party applications allows us to follow up with the authors of those applications so they can make the necessary updates to minimize or eliminate future crashes on ATRIX.
With this sort of real world feedback we can ensure the software upgrades our consumers receive address not only the functional issues reported in the forum, but the major crashes and device resets as well.
I personally don't have an issue with it but I am not dealing with confidential information like you are. However, this is going to become more of an issue as we all continue to live out of "the cloud".
- 03-11-2011, 08:43 AM #3
- 170 Posts
- CM9 Beta
Disclaimer- I am a software engineer, and I used to work at a medical device company developing 3D GUIs for physicians to assist them with operating on their patients. I had actually researched a very similar issue dealing with the Microsoft crash handler (since our stuff ran on Windows- it wasn't safety critical). Problem is, our systems supported remote operation via TCP/IP, and was connected to the internet (web browsers were disabled however). If it crashed, a Doc could hit "send report" on the crash dialog, which did send stuff to Microsoft. Turns out we didn't violate HIPAA as long as our stack trace remained clean.
Last edited by corneliusm; 03-11-2011 at 09:02 AM.
- 03-11-2011, 09:04 AM #5
- 170 Posts
- CM9 Beta