No Terms. No Conditions

> Access is not conditioned on approval.

The Zen Koan of T&C's.

Hope this slop doesn’t get anyone into trouble.

  Last updated: never
  No further pages. No hidden clauses.

Not sure “last updated=never” works, but I don’t make terms and conditions websites.

use at your own risk

> 8. You are responsible for what you do, what you build, and what follows from either.

This does not read like it was written by a professional. Non-professionals writing licenses and T&Cs cause problems because no organization, for profit or not, wants to be dragged into court to get a "common sense" definition of a word or comma defined, at their expense.

I've heard of large organizations reaching out to places who use amateur T&Cs and licenses, saying "if we give you $X, can you dual license this as MIT, Apache, BSD, or hell anything standard?".

> Access is not conditioned on approval

Is this obvious enough legalese to not waste tens of thousands of dollars in legal fees if you get sued?

Note before you reply: I will not argue with you about how obvious it is. If you are actually a lawyer then it'd be interesting to hear your guidance, which I very much understand is not legal advice. If you're not a lawyer then I'm not.

Read carefully if you are of a feline persuasion