I also feel confident that if I kindly asked for the contents of my site, the team at ReadMe would send it on over in what ever way they could. That may change in a year, but I doubt it, if anything, I bet they'll have a more automated way to get content in and out.
The ToS sounds pretty standard for "content" sites... that is, they have to have the rights to display the content, since they are the host. In my experience you're much more likely to get a shady crawler copying your content and reposting it than the service you pay using it in ways you didn't expect.
edit: woops you deleted. I think your questions were very valid, so I'll leave my reply :)
My question was basically "Are you okay with publishing content on a site that owns the content?"
I imagine they are building export tools in the future, and this is just the first version.
I'm OK with it. I've found that more often than not, questionable third parties skimming content and republishing outside any control tend to steal your content and misuse it more than providers that have a solid service do. I trust the ReadMe team to do the right thing and if they don't, instead of leaving supportive comments on Hacker News, I'll rant :)
The ReadMe team is really responsive and helpful, the documentation is beautiful and the interface goes above and beyond.
Just to give you an idea of how polished the service is, if you select a background color that contrasts poorly with the text, the interface will let you know. It also automatically generates a "white" logo for darker pages. This has almost nothing to do with writing documentation, but has a lot to do with making documents readable for users, which is easy to overlook if you're not a designer.
See our docs: http://docs.heapanalytics.com/
Right now they are a transcription from http://heapanalytics.com/docs but we're planning more robust docs and ReadMe will make that process a lot smoother.