Proof of EULA Acceptance
<p>I know I need to have a mandatory EULA accepted before allowing users onto my system.</p>

<p>Simply recording information about the user and having a database column with "accepted" doesn't seem like it would act as proof someone actually accepted the terms before use.</p>

<p>Someone could just claim my system never presented them with any EULA, and they never agreed to such terms. Seems this would be a "your word against mine" sort of thing.</p>

<p>How do I go about proving a user accepted my terms before using the system?</p>

<p>IANAL, but from my understanding, a EULA is a Contract of Adhesion <a href="https://www.law.cornell.edu/wex/adhesion_contract_contract_of_adhesion" rel="nofollow">https://www.law.cornell.edu/wex/adhesion_contract_contract_of_adhesion</a></p>

<p>And the clickwrap EULAs and TOSs you click through everywhere are reasonably safe for you to use: <a href="https://ilt.eff.org/index.php/Contracts:_Click_Wrap_Licenses" rel="nofollow">https://ilt.eff.org/index.php/Contracts:_Click_Wrap_Licenses</a></p>

<p>But, if you are recording user "click through" information in your own database, there are a few more aspects to your EULA that concern possible protections and liabilities to you. </p>

<p>By gathering personal information, you can be more certain the EULA has been clicked <em>(or even read, god-forbid)</em> by someone a bit more real than your average software clicker-and-user. The amount of info you gather depends on your needs, and could also include an email response from that user to confirm details and the EULA. That would seem to add more protection to you from the EULA.</p>

<p>And, when you say "your system," it sounds like they are logging in and accepting the EULA on a server you control. If so, you will have IP access logs for users, in addition to their EULA.</p>

<p>But, gathering that information could be a liability. A web user who clicks on a EULA sets a cookie in their browser or in a preference file on their hard-drive. You are gathering personal information and storing it yourself or at a third party, and you need to store it securely if it is anything more than name, email and phone. And ditto your own server; if the records are on the same server as the software and the user logins, you should be sure they are separate and secure.</p>

<p>And, of course, it is illegal to store many types of financial information without complying with strict state and federal laws. But if you are selling the software, you could also have the EULA integrated into a sales receipt and/or have a condition of them checking off they have accepted the EULA before they get a receipt.</p>

<p>Some/all of those options would make it hard for a customer to prove they didn't know what they were getting and dissuade them from complaining when faced with different types of proof showing they knew about the EULA.</p>

<p>A vendor usually has no need at all to prove that you accepted a EULA. </p>

<p>When you buy software, you have some very limited rights to use the software given to you by copyright law. These rights are <strong>very</strong> limited; basically you don't have the right to do anything that involves copying the software. </p>

<p>The EULA typically gives you more rights than the copyright law would. Not as many rights as you would like, maybe, but more than you have without the EULA. Therefore, if you claim that you didn't accept the EULA you will just lose the rights given to you by the EULA and be worse off. </p>

contract-law software eula