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.
Ah, now that you mention it, the part at the bottom makes it pretty obvious too:
>Last updated: never
>No further pages. No hidden clauses.
Exactly the sort of cutesy language the LLMs use when they're trying to agree with you. "You got it! Here's a page with simple, easy to understand terms and conditions. No further pages. No hidden clauses. Nothing hidden behind another link."
"Often one generation values things much more than others. Boomers and their wristwatches. One generation is like 'only from my cold dead hands,' the others 'what would I even need this for?!' What are examples of things the youngest generation did away with?"
If OP were a checklist, the answer would have checked every point.
I like how, even when the whole point is to not have any terms or conditions, there are still disclaimers. "Only for lawful purposes," "no warranty," "we are not responsible."
I know this is mostly parody, but I'm curious if anyone has good starter templates for something that covers the general stuff and doesn't require a lawyer to customize
41 comments
[ 2.6 ms ] story [ 59.8 ms ] threadThe Zen Koan of T&C's.
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.
>Last updated: never
>No further pages. No hidden clauses.
Exactly the sort of cutesy language the LLMs use when they're trying to agree with you. "You got it! Here's a page with simple, easy to understand terms and conditions. No further pages. No hidden clauses. Nothing hidden behind another link."
"Often one generation values things much more than others. Boomers and their wristwatches. One generation is like 'only from my cold dead hands,' the others 'what would I even need this for?!' What are examples of things the youngest generation did away with?"
If OP were a checklist, the answer would have checked every point.
Those are still terms and conditions!
that this site definitely
does not, legally
I’m pretty sure this is already questionable in the EU.