Software Disclaimer

[doobyscoob]

What sort of "disclaimer" should I put in software that I leave with a client as part of a contract? I'm not licencing it to them, it's just "there" as part of the work done for them and they can do what they like with it after I go. I'm happy to fix bugs during the contract (indeed I'm obliged to) but I don't want to be liable in 20 years time when they purchase a nuclear reactor and decide that my stock control system will probably work ok with it.
I know there's a limit to the usefulness of disclaimers in a legal fight but I feel
as if I should put SOMETHING in there?!
Thanks for any tips!

[Bluebird]

What sort of "disclaimer" should I put in software that I leave with a client as part of a contract? I'm not licencing it to them, it's just "there" as part of the work done for them and they can do what they like with it after I go. I'm happy to fix bugs during the contract (indeed I'm obliged to) but I don't want to be liable in 20 years time when they purchase a nuclear reactor and decide that my stock control system will probably work ok with it.
I know there's a limit to the usefulness of disclaimers in a legal fight but I feel
as if I should put SOMETHING in there?!
Thanks for any tips!

isn't there anything in your contract about this ?

[doobyscoob]

Well, you might have expected it to but it's just 2 pages and doesn't say very much other than very general stuff on termination clauses, requiring insurance etc. It doesn't say anything at all about ownership of my software. I don't care that they get to keep it lock, stock and barrell - it's long term liability for anything they do with it in future that I'm more worried about.