If you really, actually do value the data, then the best way to assure its safety is to take control of it. One company I worked had a practice of taking a set of offsite backups to an emergency facility, restoring the data and doing some sample processing. Every month they did this, without fail. That's caring about your data.
These are not binary decisions. People vastly overestimate the value of doing things in-house. Most of the candidates for those "in-house" data management jobs couldn't cut it at Google. Why not leverage Google's HR and recruitment, training, and expertise in infrastructure operations to your benefit, esp. when you consider:
(1) that your own hires offer you no better protection; and
(2) backup solutions are necessarily imperfect.
There's a lot that you can do about your employee that you can't to with Google. You can educate them, align their motivations with yours, etc. You can review the process and make sure it doesn't depend on one person. The list goes on.
Of course there are times to outsource. Times when practicality makes it necessary, when money makes it desirable, and so on. I do not take issue with the very idea. Sometimes it's the right choice. But sometimes it's the wrong choice.
I'd rather have a 1% chance of losing my valuable data if I feel in control than a 0.1% chance of losing it while feeling like there is nothing I can do about it.