Saving Rise Source Files to Local Hard Drive

I'll add another voice into the mix.  We switched to Articulate 360 last year, and have been using Rise 360 a lot in the past few months.  A few weeks ago, one of our Rise courses mysteriously disappeared - the published content was gone, resulting in a 'Hmmm, we can't find what you're looking for' message to the user, who reported it to us.  When we viewed the link, it was gone - and when we went to re-publish, we found the source file was also missing.  

Articulate Support was unable to locate the source file and insisted that we must have deleted it - which we didn't.  The course had been stable and working from December, had not been modified or updated, none of my team had touched it.  Yet it was gone.  Because nothing was stored locally or backed up, we didn't even have the published version to refer to - we had to re-create the entire module from scratch.

Obviously this had made me extremely motivated to not only backup all of my content, but to deliver it from our own servers and not through Articulate servers.  If I can't depend on the content being stable, and if files are just going to disappear and I can't back them up, it's not a reliable solution for us.

So... what exactly is Articulate suggesting that I do?  Send a copy of every file to myself, and manage the duplicates?  I hope you realize this isn't a viable solution.  We need a way to store and/or backup our content.  Make it editable only through a valid Rise 360 subscription, for sure - but if you can't guarantee that my content is stable, especially if you can't recover something that has disappeared (for whatever reason), you need to provide me with a way to back it up and store it on my own server.