Cloud storage is an increasingly popular way to store research data. Being able to upload and access files from any location is useful and makes transfer between computers much easier. But for all of the upsides of cloud storage, there are also a few downsides.<\/p>\n
Data Ownership<\/strong><\/p>\n While most of us don’t usually read terms of service agreement, it’s worth doing a little digging when it comes to your cloud reader. For example,\u00a0Google Drive’s terms of service<\/a> includes this little tidbit:<\/p>\n When you upload or otherwise submit content to our Services, you give Google (and those we work with) a worldwide license to use, host, store, reproduce, modify, create derivative works… communicate, publish, publicly perform, publicly display and distribute such content.<\/p><\/blockquote>\n You retain intellectual properties rights over the content you put on Drive but Google can still do a lot of things with your content. This should make you a little worried about any research data you put on Drive.<\/p>\n There are some ways around this problem. One example comes from UW-Madison, which has negotiated Google Drive terms of service<\/a> for faculty and students where Google has no ownership or use permissions. The other option is just to pick a cloud storage provider that won’t use your data, but even that isn’t always perfect. Dropbox, for example, doesn’t take quite the same liberties Google does with your data but does it spell out in\u00a0its terms of service<\/a>\u00a0how it can use your personal information (name, address, log-in information, etc) or provide your files to law enforcement.<\/p>\n My best advice? Read the terms of service before choosing a cloud storage provider for your data.<\/p>\n Security<\/strong><\/p>\n The other natural concern when giving your data to a third party is security. This is especially important when putting sensitive information or student information (covered under FERPA<\/a>) in the cloud. You need to take a lot of extra precautions in the cloud if your data is sensitive.<\/p>\n One secure cloud storage option I’ve run across is SpiderOak<\/a>. Unlike other cloud storage options, SpiderOak cannot actually read any of your data because it gets encrypted before it even arrives at the SpiderOak servers. And in this Ars Technica review<\/a>\u00a0,\u00a0SpiderOak favorably compares with other popular cloud services like Dropbox and SugarSync.<\/p>\n So unless you find such a service like SpiderOak that guarantees security, the cloud is not the best place for your sensitive data.<\/p>\n The Limitations of the Cloud<\/strong><\/p>\n Cloud storage can be a blessing in the laboratory, but putting your data in the cloud does not automatically mean that your data is well backed-up\u00a0nor well managed. This is because your data is outside of your control when you give it to another entity. If your cloud storage provider folds or suddenly changes their terms of service (as seen in\u00a0the recent<\/a> Instagram debacle<\/a>), you could suddenly be in a tight spot. For safety’s sake, it’s better to have other back-ups besides your cloud drive.<\/p>\n I’m in no way saying that you should not use cloud storage for research. Instead, you should be smart about choosing a service provider and know that service’s limitations. With a little bit of forethought, cloud storage can be a valuable asset in the laboratory instead of a potential security hole.<\/p>\n","protected":false},"excerpt":{"rendered":" Cloud storage is an increasingly popular way to store research data. Being able to upload and access files from any location is useful and makes transfer between computers much easier. But for all of the upsides of cloud storage, there … Continue reading