So basically the same idea as my http://qcl.me while I build mine for a side weekend project, it has evolved into much more than that. I can tell you alot of people will be in the camp of "I trust no one", so get ready to deal with that. Also you may want more trust or a verifiable database. Even though I been around for while, and my database is very harden with multiple layers of security and verifiable data, people were still very hesitan to switch to my system. So I hope your ready to debate/fight for your site, but welcome to space. Also someone tried to hack my system already so that is something you should be ready to deal with. (My site of course held up and he didn't get into anything just downloaded some CSS files) I am actually going to be doing a little pivot on my service (coming soon) so I am not too threaten, but this will keep me on my toes now. Good Luck!
I've got it set up to include the first 7 characters of a sha-256 hash of the saved data in the URL, and check it against that of the saved data, so if it's modified by a third party, it will raise a red flag. That's the only real danger I see.
Don't forget about the data which isn't public, like for example statistical data. Dates/times/IPs?
Do you use some kind of salt? Otherwise there are only 4 billion hashes to compare against (which wouldn't take long).