To clear a few things up
We are terribly sorry about this event. Dedoose is built and designed by well known academic researchers. We are not a giant corporation, we are a small team of researchers, and technology visionaries that built a collaborative tool for our own research needs, and are trying to share this tool with the world at large. This is a giant tragedy, and we accept responsibility for this event, and are offering our staff of methodologist to assist in recreating lost data, coding, analysis, etc. If you are affected by this data loss, please call us or shoot an email to email@example.com. We did have a multiple backup strategy in place using proprietary software. It has been very challenging finding software to handle this job at the scales of data we are working with. Unfortunately the software we chose to use corrupted occasional backups. In our testing we did not encounter an issue, but during the event the full backups needed to restore were unrecoverable. This situation is complicated by the many layers of encryption our systems use, the database encryption, the backup encryption, the transfer encryption, etc. We are now running mirrors upon mirrors, off-site mirrors on a seperate cloud, off-site mirrors locally, and our team developed a tool that is automatically copying the encrypted database backups to amazons s3 cloud, glacier storage, as well as an onsite copy. We will be adding additional measure to ensure the app automatically downloads a local backup of the data needed to restore a project whenever logged in. When we developed Dedoose, we developed it initially for our research team. The biggest factor affecting our teams was the inability to collaborate on projects, thus we designed an online tool to do so. We continue to work on a non-collaborative offline version, but that was never our main focus. We recognize the seriousness of this event, but urge you to understand we have put the protections in place to ensure a data loss event is not possible in the future short of a global cataclysmic event. Ultimately it was our fault for not having backups of backups, backups of those backups, and more backups of those backups. We have resolved that issue and this will not happen again. We are deeply, deeply, sorry and more than willing to assist affected users with our team of Dedoosers.