Actually, "structured wiki" was exactly what my friend and I were calling it when we came up with the original concept :)

The security model isn't super-strong, but I'll be adding password protection soon. For now I wanted something that people could easily email to their friends and collaborate on creating databases.

If you add password protection later on, I can't claim my existing databases... because I never gave you my registration information when creating them. I mean if the openness is by-design it's OK, but in that case you should definitely make it more clear to the user (if it's a wiki you shouldn't call it "secret URL" but admit that "everyone can edit your tables"). But hey, it's your app and your users :)

But the idea is that security isn´t necessary, just as I could enter by name here as "Philipp Lenssen" but I don´t.

Splasho, no you can't enter Philipp Lenssen here. But that's another story. As I said, if it's by-design then it's OK but it has to be made clear, i.e. by not talking about "secret" URLs.

Long and short.. I don't like it. :)