Recently Google released a search tool, Google Desktop 4 , that allows users to search the contents of their computer's stored data. Like other Google services, Desktop indexes the content of files on to a Google server. The difference is that the files being indexed are located on the user's local and possibly shared network drives. Third party indexing of Restricted information (e.g. patient information, SSN, financial data) is typically a violation of Johns Hopkins Information Technology policies regarding disclosure of Restricted information (http://www.it.jhu.edu/policies/itpolicies.html) and Johns Hopkins HIPAA privacy and security policies. Google Desktop may not therefore be installed on any computer that stores Restricted Johns Hopkins information, and installation is strongly discouraged on any computer used to access an administrative network share including home computers used to attach to the network. Users that do not store Restricted information should consider carefully whether they want the content of their workstations indexed and copied to the servers of any third party, in this instance, Google. For those who may install Google Desktop on their PC's, please remember to disable any feature that would allow indexing to extend beyond the user's workstation so as to avoid inadvertently indexing JH-owned machines or networks. The University of Michigan provides useful tips for users and administrators. http://www.itd.umich.edu/itcsdocs/s4340/ In addition, we are concerned with caching of temporary files, other vulnerabilities and how Google Desktop combines Internet traffic with indexed local files. The tool has been out for several months, and there is still much that we don't know regarding how Google Desktop works. Google has heard concerns from privacy advocates and organizations like ours and is making adjustments. However, we have not yet seen a change that would assuage our concerns with this powerful but risky tool. Thank you for your attention and cooperation. If you have questions regarding this message, please contact itpolicy@jhu.edu. | 
