Website Terms of Service and Online Contract Formation

By Hank FasthoffJuly 23, 2026

Your terms of service bind only the users who received legally sufficient notice and assented to them. When a dispute arrives, the company holding the arbitration clause has to prove which terms it offered, how the screen presented them, what action signified acceptance, who took that action, and which version governed the transaction.

That proof comes from the interface rather than the document linked in your footer. Strong terms paired with a weak acceptance process leave you litigating under default law instead of the limits, forum, and dispute procedure you paid to have drafted.

Online Contract Formation

Courts sort online agreements into clickwrap, scrollwrap, sign-in wrap, and browsewrap. Those labels describe interface designs rather than legal rules, and formation turns on applicable state contract law, the notice presented to the user, and the conduct that signified assent.

Clickwrap requires the user to select a box or button tied to identified terms. Scrollwrap goes a step further and presents the terms in a window the user scrolls through before accepting. Sign-in wrap places a notice near a registration or purchase button and states that clicking the button signifies agreement. Under a browsewrap design, terms appear only behind a link, and the operator later argues that using the site constituted acceptance. Courts often reject that theory when users lack actual or inquiry notice.

You should require the user to take an action whose only purpose is accepting identified terms. A checkbox reading "I agree to the Terms of Service" provides stronger formation evidence than a button labeled Continue, especially when Continue appears on four other screens in the same flow.

In Berman v. Freedom Financial Network, LLC, 30 F.4th 849 (9th Cir. 2022), the Ninth Circuit, applying New York and California law it treated as materially identical, required reasonably conspicuous notice of the terms plus conduct unambiguously manifesting assent. Formation failed because the text was tiny and gray, the underlined hyperlinks appeared in the same gray, and no language tied the Continue button to the agreement. One sentence stating that clicking Continue signified agreement would have cured the second defect. The defendants also needed to make the notice and links visually conspicuous.

The Second Circuit reached the opposite result in Meyer v. Uber Technologies, Inc., 868 F.3d 66 (2d Cir. 2017), applying California law. Uber presented an uncluttered registration screen, placed the notice directly below the registration button, styled its hyperlinks in blue underlined capitals, and told the user that creating an account constituted agreement. The court held the notice reasonably conspicuous and the registration an unambiguous manifestation of assent.

Read together, the two opinions amount to a design manual rather than competing rules. Font size, contrast, proximity, button language, screen clutter, transaction context, and the mobile viewport determine whether the same terms become a contract.

Electronic Signatures and Assent

The Electronic Signatures in Global and National Commerce Act, commonly called E-SIGN, prevents a court from denying effect to a signature, contract, or record solely because it appears in electronic form. Section 101 of the Act preserves the other rules governing formation, disclosure, validity, and enforceability, and it doesn't require anyone to accept electronic records in the first place. For consumer transactions, Section 101(c) adds consent and access requirements when another law requires information to be provided in writing.

Texas follows the same structure. Section 322.005 of the Texas Business and Commerce Code applies the Texas Uniform Electronic Transactions Act only when the parties agreed to conduct the transaction electronically, as determined from context and surrounding circumstances. Section 322.007 prevents denial of legal effect solely because a record or signature is electronic, and Section 322.009 governs attribution, the question of whose act the electronic signature reflects.

Aerotek, Inc. v. Boyd, 624 S.W.3d 199 (Tex. 2021) shows what disciplined proof accomplishes. Aerotek established its electronic arbitration agreements through unique credentials unknown even to Aerotek, a required sequence of steps, timestamps on every action, records no one at the company could alter, and a witness who explained how the system operated. The Texas Supreme Court held that the employees' bare denials didn't raise a fact issue against that record. The statutes validate the medium, while your interface and your evidence establish notice, assent, attribution, and the terms of the bargain.

The Acceptance Screen

The acceptance notice belongs on the screen where the user completes the purchase, creates the account, or obtains the service, next to the action button, stating the legal consequence in plain words, "By selecting Create Account, you agree to the Terms of Service." Language naming the button and the consequence beats an unanchored agreement recital floating in fine print, which is the design Berman refused to enforce.

The hyperlink should look like a hyperlink. Contrasting color, underlining, readable type, and surrounding white space help a user recognize that the text opens a contract, while decorative text, competing buttons, popups, and a dense checkout can bury notice even when every required word appears somewhere on the screen.

Users should be able to open and retain the terms before accepting them. When a statute requires the contract to be in writing, E-SIGN conditions enforceability on an electronic record capable of accurate retention and reproduction.

You should test the complete flow on every screen size and operating system your customers use. A desktop screenshot proves little about a disputed acceptance completed on a phone, and a redesign proves nothing about what the user saw before the change.

The Formation Record

A defensible record connects each acceptance event to the user, the terms version, and the interface that presented it. You should preserve the account identifier, date and time, document version or cryptographic hash, acceptance action, relevant authentication event and identifiers, and an image or reproducible rendering of the screen. Store proof that authentication succeeded rather than passwords or security-answer contents.

Logs require a witness. Someone familiar with the system has to be able to explain how a user entered the flow, how the system displayed the terms, which action recorded acceptance, whether the user could proceed without accepting, how the database stored the event, and whether anyone could alter the record afterward. Aerotek turned on exactly that combination, credentials plus unalterable records plus a person who walked the court through them.

Release records deserve the same treatment for every terms update and interface revision. When a motion to compel arbitration arrives three years after a checkout, your litigation team will want the terms and the screen from that checkout rather than the current website. You should align the retention period with applicable legal duties and the company's privacy, security, and deletion schedules.

Matching the Terms to the Transaction

When the terms name only a brand, the parties end up litigating which affiliate contracted, which entity received payment, and who can enforce the arbitration or forum clause. You should identify the legal entity making the contract and the service, product, or access the user receives.

For software and subscription services, you should address account eligibility, authorized users, access rights, payment, renewal, suspension, termination, support, data treatment, and service changes. If you sell goods online, you should address product descriptions, orders, acceptance, payment, taxes, shipping, risk of loss, returns, defective goods, and available remedies instead.

Marketplaces require another allocation entirely. You should state whether the operator acts as seller, payment intermediary, listing service, or platform, and allocate responsibility for listings, fulfillment, refunds, taxes, user disputes, and prohibited products according to how the marketplace operates in fact.

When an order form, service schedule, acceptable use policy, data processing agreement, or product policy also governs, you should identify each document, make it available before assent, preserve the accepted version, and state which document controls in a conflict. A complete contract stack prevents a generic website term from displacing a negotiated business term by accident.

Payment, Renewals, Returns, and Refunds

Your payment terms should state price, billing frequency, taxes, authorization, failed payment consequences, and the point at which an order becomes binding. For online negative-option sales, the Restore Online Shoppers' Confidence Act requires clear and conspicuous disclosure of material terms before obtaining billing information, express informed consent before charging, and a simple way to stop recurring charges. State laws may add acknowledgments, renewal notices, cancellation methods, and other requirements addressed in the firm's auto-renewal guidance.

For ordinary sales of conforming goods, the stated return policy usually governs a buyer who changes their mind, subject to state law and rules for particular products or sales. A complete policy covers the return period, required condition, authorization process, shipping responsibility, restocking charges, refund method, and items that can't be returned. You should present the policy before purchase so it can become part of the bargain.

Shipping obligations come from federal law as well as contract. The FTC Mail, Internet, or Telephone Order Merchandise Rule requires a merchandise seller to have a reasonable basis for its advertised shipping time. When the seller states no shipping time, the default period is 30 days after receipt of a properly completed order, or 50 days when the buyer applies for seller-provided credit with the order. If the seller can't ship within the applicable period, it must send the delay notice required by the rule, give the buyer the option to cancel for a prompt refund, and obtain any consent the rule requires.

Card network chargeback procedures govern the relationship among merchants, acquiring banks, issuers, and cardholders. Those procedures affect your economics and your evidence, and they don't substitute for the return and refund obligations your contract and applicable law impose.

Warranties and Liability

A warranty disclaimer belongs to its transaction and governing law rather than to the last deal's template. Under subsection (b) of Section 2.316, a disclaimer of merchantability must mention merchantability and, when written, must be conspicuous. An exclusion of the implied warranty of fitness must appear in a conspicuous writing. Subsection (c) supplies additional methods and qualifications.

Federal law adds another limit for consumer products. Under the Magnuson-Moss Warranty Act, a supplier generally can't disclaim implied warranties when it provides a written warranty or enters a service contract with the consumer, although the Act permits qualifying limits on duration.

SaaS, data services, digital content, and mixed transactions can fall under different law. An Article 2 disclaimer pasted into a services agreement leaves common law warranties, contract promises, service commitments, consumer statutes, and duties tied to the product untouched.

A limitation of liability identifies the claims it covers, excluded damages, the cap, the cap period, and the exceptions. You should test the provision against governing law, public policy, consumer statutes, indemnity obligations, data claims, intellectual property claims, confidentiality duties, and any liability the law prevents a party from waiving.

Intellectual Property and User Content

You should separate ownership of the website and service from the limited rights each user receives. When users submit reviews, images, code, listings, or comments, the license should cover the uses the business needs. Those uses may include hosting, displaying, reproducing, adapting, distributing, moderating, promoting, and granting necessary rights to service providers, distribution partners, and successors. You should tie the scope and duration of the license to identified operational purposes.

The same section should address the user's authority to submit the content, responsibility for rights held by others, the operator's moderation rights, and the procedure for copyright complaints. If you rely on the safe harbors in 17 U.S.C. § 512, a terms clause supplies only part of the required process. Eligibility may also require a registered agent, a reasonably implemented repeat-infringer policy, and compliant notice-and-takedown procedures. Your license, acceptable use rules, privacy disclosures, and operational practices should describe the same conduct.

Arbitration, Governing Law, and Forum

Section 2 of the Federal Arbitration Act generally requires courts to enforce written arbitration provisions in contracts involving commerce, subject to generally applicable contract defenses and statutory exceptions. Before that analysis begins, the business seeking arbitration must prove formation of the agreement containing the provision, which returns everything to the acceptance screen.

A complete arbitration clause identifies covered disputes, the administrator, applicable rules, hearing location, the decision maker for arbitrability, available relief, fee allocation, class treatment, and any right to reject arbitration. You should draft for a process the company can administer, including coordinated and mass filings, the applicable fee rules, and any batching procedure the governing law and administrator permit. When California law may apply, you should also test the clause against the rule discussed in Stover that a contract can't waive the right to seek public injunctive relief in every forum.

Governing law and forum provisions require their own analysis for each transaction. A Texas company can select Texas law and a Texas forum, and another jurisdiction's consumer protections, public policy, personal jurisdiction rules, or venue statutes can override that choice for particular users. You should identify where your users reside and where you perform before assuming the chosen clause controls every dispute.

Amendments Require Notice and Assent

A clause reserving the right to revise the terms doesn't bind users to every revision posted online. In Stover v. Experian Holdings, Inc., 978 F.3d 1082 (9th Cir. 2020), the Ninth Circuit held that both parties must have notice of changed terms and an opportunity to review them before the changes become binding under a change-of-terms provision. A single website visit four years after the original assent didn't bind the visitor to terms she never saw.

Notice belongs in a channel reasonably calculated to reach the user, with the effective date identified. Material changes to arbitration, pricing, renewal, liability, data use, or ownership call for renewed assent through the same defensible process used at formation, and version control connects old terms, new terms, notice, effective date, and acceptance record. A generic sentence that continued use accepts every revision provides weak protection when the company can't prove notice or identify the conduct that followed it.

Privacy Notices Do a Different Job

Terms of service and privacy notices perform different legal functions. The terms govern the contractual relationship, while a privacy policy describes data practices and supplies disclosures required by applicable privacy law.

Both documents can share one interface, but the acceptance language should state which document forms part of the contract and which serves as notice. Treating every privacy statement as a contractual promise can support a contract claim independent of whether the governing privacy statute supplies a private remedy.

The Enforcement File

Terms, interface, transaction records, and operating practices form one system. The contract should describe the business users encounter, and the acceptance record should prove the contract each user made.

When litigation begins, a polished PDF won't establish assent by itself. A veteran litigator will ask for the exact screen, exact terms, exact acceptance event, and the witness who can authenticate the process. You should preserve that evidence when each version is in use because contemporaneous records provide the strongest proof.