Disclaimer

johnnyutah · Post by **johnnyutah** » Mon Nov 22, 2004 7:43 pm

Hi,

Does anyone know where I can find standard wording for a proper, legally-approved disclaimer that I can include with my software applications?

Thanks

benny · Post by **benny** » Tue Nov 23, 2004 9:29 am

Hi,

I put the following disclaimer in my zip archives when I release some
freeware applications. I found it somewhere on the net. However, I
do not know if this kind of disclaimer is legally-approved

This program is provided 'as is', without warranty of any kind,
express or implied. The author shall not be liable for any damages
caused by the use of or inability to use this program. This means
that the user must assume the entire risk of using this program.

Use of this program commercially without prior consent of the
author is prohibited.

This program may be freely distributed, but may not be sold.

Modification of this program or any of it's documentation is
prohibited. This program is freeware.

Use of this program indicates you understand and agree to the
conditions of this license agreement.

johnnyutah · Post by **johnnyutah** » Tue Nov 23, 2004 9:48 am

Thanks benny! I'm just wondering how much of a problem there is in terms of legal action against software developers (I guess if your program works as it should there's no problem!) and how much a disclaimer actually protect you from this. Althought it can't hurt to include one just in case and yours looks fine to me.

Thanks for your help!

benny · Post by **benny** » Tue Nov 23, 2004 11:36 am

@johnnyutah:

I asked this question myself also a thousand times before I release something.
You'll never know how your program runs under a certain system configuration
and it is nearly impossible to test it.

That's why I enclose such disclaimer.

Generally speaking, if it would happen that a user of your program claims
that your program destroyed important data - who will responsible for that

IMHO, in this case it (if it would go to court e.g.) it should be enough to
proof your innocence by simply showing your source that there isn't any
code inside malicious code inside.

Hmm ... but maybe there is anyone around in this forum who has some
experience in this field of "legal questions"