Online Terms and Consumer Contracts Toolkit: Formation, Arbitration, and Dark Patterns

By Casey Scott McKay · 2026-03-07

An online contract is only worth what its formation record can prove, and most companies cannot prove theirs. This toolkit works the formation spectrum from clickwrap to browsewrap, the two-part standard that has emerged - reasonably conspicuous notice plus an unambiguous manifestation of assent - and the interface design decisions that determine which side of the line a flow falls on. It covers unilateral modification and why a change nobody was told about is generally unenforceable, then arbitration: what the Federal Arbitration Act does, how class waivers and delegation clauses operate, and why mass arbitration has changed the economics. It closes with the negative option and dark pattern rules that now govern subscription flows.

IP and Technology > Internet | Toolkit | Published 7 March 2026 - Updated 8 July 2026 | Casey Scott McKay - marksy.us

Summary. An online contract is only worth what its formation record can prove, and most companies cannot prove theirs. This toolkit works the formation spectrum from clickwrap to browsewrap, the two-part standard that has emerged — reasonably conspicuous notice plus an unambiguous manifestation of assent — and the interface design decisions that determine which side of the line a flow falls on. It covers unilateral modification and why a change nobody was told about is generally unenforceable, then arbitration: what the Federal Arbitration Act does, how class waivers and delegation clauses operate, and why mass arbitration has changed the economics. It closes with the negative option and dark pattern rules that now govern subscription flows.

Keywords: online terms · clickwrap · browsewrap · sign in wrap · reasonably conspicuous notice · unambiguous manifestation of assent · Specht v Netscape · Nguyen v Barnes and Noble · Meyer v Uber · Berman v Freedom Financial · unilateral modification · arbitration clauses · Federal Arbitration Act · class action waivers · delegation clauses · mass arbitration · ROSCA negative option · dark patterns · cancellation flows · evidence of acceptance

Start Here

A company is sued in a putative class action. Its terms of service contain an arbitration clause with a class waiver, and counsel moves to compel arbitration.

The plaintiff's response is not that the clause is unconscionable. It is that no contract was formed, because the sign-up flow in 2021 — the version the plaintiff used — displayed the terms link in grey text below the fold, and the button said "Sign Up" rather than anything about agreeing to terms.

The company cannot produce the 2021 flow. Its records show the current flow, which is fine, and a changelog that does not go back that far.

The motion fails, and the class action proceeds on the merits. Not because the terms were bad, but because nobody could prove the plaintiff agreed to them.

This toolkit answers three questions.

What makes an online contract enforceable? Conspicuous notice and an unambiguous manifestation of assent, evidenced.
What can the terms actually do? Arbitration, class waivers, limitations, and modifications, each with its own constraints.
What can the flow not do? Negative option and dark pattern rules now govern how subscriptions are sold and cancelled.

If you read only one thing, read Terms That Actually Bind. It works the formation spectrum with the interface facts that decide cases.

The Formation Spectrum

Clickwrap. The user must click a box or button that says they agree, with the terms displayed or linked immediately adjacent. Routinely enforced.

Sign-in wrap. The user completes an action — creating an account, placing an order — and adjacent text states that by doing so they agree to linked terms. Enforceability depends entirely on the interface.

Browsewrap. Terms are linked somewhere on the site, with no affirmative assent step. Generally unenforceable against consumers.

Specht v. Netscape Communications is the foundational case: a download button with terms available only by scrolling below it did not form a contract, because a reasonably prudent user would not have known of the terms.

Nguyen v. Barnes & Noble holds that where a website provides no notice or prompt to take affirmative action, a consumer's constructive knowledge of the terms cannot be inferred from a hyperlink alone.

Meyer v. Uber Technologies upheld a sign-in wrap where the notice was uncluttered, in a legible font, immediately visible above the registration button, and the terms were hyperlinked in contrasting text.

Berman v. Freedom Financial Network states the two-part standard clearly: the website must provide reasonably conspicuous notice of the terms, and the consumer must take some action unambiguously manifesting assent. It also holds that a hyperlink must be readily apparent as a hyperlink — conventional blue underlined text or an equivalent — and that the action must be accompanied by language explicitly advising that it constitutes agreement.

The practical standard. Notice in a size and contrast a reasonable user would see, positioned adjacent to the action, with the terms hyperlinked in visibly link-styled text, and the action button accompanied by language stating that clicking it agrees to the terms.

Designing a Flow That Holds

Put the notice above the button, not below it and not in a footer.

Use the same font size and colour weight as the surrounding interface, not a smaller grey.

Style the hyperlink as a hyperlink. Blue, underlined, or otherwise plainly distinguishable. Berman treats this as a distinct requirement.

Label the action. "By clicking Create Account, you agree to the Terms of Service and Privacy Policy" is the standard formulation, and the button itself may say "Create Account."

Consider a checkbox for high-stakes terms. An unchecked box the user must tick is the strongest form and is worth the friction for arbitration clauses and significant limitations.

Do not bury it in a modal the user can dismiss.

Test on mobile. Most formation failures are mobile layout failures, where the notice falls below the fold or the hyperlink loses its styling.

Capture the evidence. Screenshot of the exact flow, the version identifier, the terms version served, the timestamp, the user identifier, and the interaction record. Retain it for the limitations period.

Version everything. Every flow change and every terms change, with dates. The single most common evidentiary failure is being unable to show what a user saw on a specific date.

Keep the terms readable. Extremely long, dense terms invite unconscionability arguments even where formation is clean, and a readable document is a better exhibit.

Modification

The problem. Companies change terms constantly and assume continued use constitutes acceptance.

The rule. A modification requires notice and assent, like any contract change. Continued use may suffice where the user had actual or constructive notice of the change and of the fact that continued use constitutes acceptance.

Douglas v. U.S. District Court holds that a party cannot unilaterally change a contract by posting a revised version without notice — a customer is not bound by amendments they had no reason to know about.

A modification clause is necessary but not sufficient. Reserving the right to modify does not remove the notice requirement.

What works. Email or in-app notice describing the change, a reasonable period before it takes effect, a statement that continued use after that date constitutes acceptance, and a record of delivery.

For material changes, get affirmative assent. A re-acceptance flow on next login, with the same design discipline as the original.

Never apply changes retroactively to disputes that have already arisen; arbitration clauses added after a dispute has arisen face particular scrutiny.

Keep the archive. Every version of the terms, with effective dates, publicly accessible. This is both good practice and the evidence that a change was disclosed.

Watch the illusory promise problem. Terms permitting unlimited unilateral amendment, including retroactively, have been held illusory and unenforceable in some jurisdictions — which can take the arbitration clause with them.

Arbitration

The statutory framework. 9 U.S.C. § 2 makes written arbitration agreements valid, irrevocable, and enforceable save on grounds existing at law or in equity for the revocation of any contract. 9 U.S.C. § 3 provides for a stay and 9 U.S.C. § 4 for an order compelling arbitration.

Preemption. AT&T Mobility v. Concepcion holds that the Act preempts state rules conditioning enforceability on the availability of class procedures. That is what made consumer class waivers viable.

Cost is not a defence. American Express v. Italian Colors Restaurant holds that the fact that individual arbitration is uneconomic does not invalidate a class waiver.

Employment. Epic Systems v. Lewis upheld class waivers in employment agreements against a labour law challenge.

Delegation. Henry Schein v. Archer & White Sales holds that where the parties delegate arbitrability to the arbitrator, a court must respect that delegation even if it thinks the arbitrability argument is wholly groundless. A clear delegation clause therefore moves even the threshold fight out of court — except the formation question, which is always for the court.

Formation is always judicial. No delegation clause can send to arbitration the question whether any agreement was formed at all. That is why the assent record matters more than the clause's drafting.

Appeals. Coinbase v. Bielski holds that a district court must stay proceedings while an appeal from the denial of a motion to compel is pending under 9 U.S.C. § 16.

Representative actions. Viking River Cruises v. Moriana addresses the interaction between arbitration agreements and state representative-action statutes, and the position continues to develop under state law.

Unconscionability survives. Grounds for revoking any contract remain available, which is where fee-shifting provisions, one-sided carve-outs, inconvenient forums, and shortened limitations periods are attacked.

Draft to survive that. Company pays arbitration fees; no loser-pays; a forum convenient to the consumer or remote proceedings; no shortened limitations period; symmetric carve-outs; and a small-claims court exception.

Mass Arbitration

The development that changed the economics of the class waiver.

The mechanism. Plaintiffs' firms file thousands of individual arbitration demands simultaneously. Under most provider rules the company owes a per-case filing fee, and the aggregate can reach millions before any merits are reached.

Which inverts the incentive. The class waiver was designed to make aggregate litigation impossible; mass arbitration makes individual arbitration collectively more expensive than a class action would have been.

Responses in drafting. A bellwether or batching protocol under which an initial set of cases proceeds and the remainder are stayed pending their resolution. A mandatory pre-arbitration informal resolution period with a defined process. A provider selection whose rules accommodate mass filings. And a small-claims carve-out that channels genuinely small disputes elsewhere.

Responses that fail. Clauses that appear designed to prevent any adjudication at all, which invite unconscionability findings and can void the arbitration provision entirely.

Consistency matters. A company that compels arbitration when it suits and resists when it does not will find that recorded.

Consider whether arbitration is right at all. For some businesses, the class waiver's value no longer exceeds the mass arbitration exposure, and a well-drafted forum selection clause with a jury waiver may be a better structure.

Model it honestly. The question is not whether the clause is enforceable; it is what happens when ten thousand demands arrive, and the answer should be modelled before the clause is finalised.

Negative Options and Dark Patterns

The statute. 15 U.S.C. § 8403 requires, for internet transactions involving negative option features, clear and conspicuous disclosure of the material terms before obtaining billing information, informed consent before charging, and simple mechanisms to stop recurring charges.

The regulation. 16 C.F.R. § 425.1 and the negative option framework address prenotification plans, continuity plans, automatic renewals, and free-to-pay conversions.

The FTC Act. 15 U.S.C. § 45 reaches unfair or deceptive acts and practices, which is the general authority behind dark pattern enforcement.

What "clear and conspicuous" means in practice. Disclosure adjacent to the consent mechanism, in a size and contrast the consumer will see, unavoidable, and before billing information is collected — not in terms of service linked elsewhere.

Simple cancellation. The mechanism must be at least as easy as sign-up. A subscription sold in two clicks online cannot require a phone call during business hours to cancel.

State automatic renewal laws impose their own requirements — pre-renewal reminders, online cancellation, and specific disclosure formats — and several are stricter than federal law.

Dark patterns enumerated. Pre-checked consent boxes. Confirmshaming. Obscured cancellation paths. Countdown timers that are not real. Drip pricing where fees appear only at checkout. Interface elements designed to make the declining option hard to find.

Consent for privacy purposes is subject to its own dark pattern rules, and consent obtained through a manipulative interface may not be valid consent at all. See State Privacy Compliance Toolkit.

The design review. Every subscription flow, consent flow, and cancellation flow reviewed against these rules before launch and after any redesign, with screenshots retained.

The Evidence Problem

Formation cases are lost on records, not on doctrine.

What a motion to compel actually needs. A declaration from someone with knowledge establishing: the flow the user encountered, on the date they encountered it; that the flow displayed the notice and the hyperlink as described; that the user completed the action; the version of the terms served at that moment; and that the terms contained the arbitration clause.

Which requires four artefacts. A flow version register with dates. Screenshots or recorded renderings of each flow version, on desktop and mobile. A terms version archive with effective dates. And per-user interaction records tying the account to a flow version, a terms version, and a timestamp.

Most companies have none of them. They have the current flow and the current terms, which proves nothing about a user who signed up three years ago.

Instrument at the point of assent. Log the terms version identifier and the flow version identifier alongside the account creation event. This is a small engineering change and it is the single most valuable one in this area.

Retain for the limitations period. Contract claims run for years, and the record must outlast the flow it documents.

Screenshot every version. Automated capture on each deploy, stored with the version identifier.

Test the rendering. A flow that displays correctly on a desktop browser and collapses on a mobile viewport has two different evidentiary positions, and the plaintiff will have used the mobile one.

Keep the archive public. A publicly accessible terms archive with effective dates supports the notice argument for modifications and demonstrates good faith.

Prepare the declarant. The person who signs the declaration must have knowledge of the systems, and their preparation should include the version register and the retention practice.

And audit it annually. Pick a user account, and reconstruct what they saw and agreed to. If that takes more than an hour, the record is not adequate.

Substantive Terms Worth Getting Right

Formation is the threshold; the terms still have to do the work.

Licence to user content. Non-exclusive, worldwide, royalty-free, sublicensable to the extent needed to operate the service, and scoped to the purposes the service actually requires. Overbroad grants generate reputational problems and consumer complaints.

Licence to the service. What the user may do, and expressly what they may not — no scraping, no reverse engineering subject to statutory rights, no resale, no circumvention.

Acceptable use. Prohibited content and conduct, tied to the content policy so that enforcement is consistent with the published standard.

Termination and suspension. Grounds, notice where the terms promise it, and consequences for data and content. Promises about process here create exposure independent of any statutory immunity.

Disclaimers and limitations. Conspicuous, in the form the applicable law requires, and realistic — a total exclusion of liability in a consumer contract will be tested.

Warranty disclaimers in the required conspicuous form.

Indemnity from the user, scoped to their content and conduct.

Governing law and forum, coordinated with the arbitration clause so that the carve-outs point somewhere coherent.

Dispute resolution. Informal resolution period, arbitration provision, class waiver, small-claims carve-out, injunctive relief carve-out, and the mass arbitration protocol.

Modification. The clause, plus the notice practice that makes it work.

Severability, so that an unenforceable provision does not take the arbitration clause with it — and note that a poison-pill class waiver provision may be intended to do exactly that.

Contact and notice mechanics, including the address for legal notices and the designated agent references.

Readability. Plain language, defined sections, and a summary at the top. It reduces unconscionability exposure and it is a better exhibit.

Worked Example: Rebuilding a Flow

A subscription service with three million users discovers its terms have never been successfully enforced.

The audit. The sign-up flow displays "By continuing you agree to our Terms" in nine-point grey text below the button, with "Terms" in the same grey as the surrounding text. On mobile it falls below the fold. Under Berman v. Freedom Financial Network, the hyperlink is not readily apparent as a hyperlink and the notice is not conspicuous.

The redesign. Notice moved above the button, at the same size and weight as the surrounding interface. The hyperlink rendered in blue and underlined. The button labelled "Create Account," with adjacent text stating that clicking it agrees to the linked Terms of Service and Privacy Policy. Tested at three mobile viewport widths.

The instrumentation. Account creation events now log the flow version identifier, the terms version identifier, and the timestamp. Automated screenshots capture each flow version on deploy.

The existing users. Three million accounts formed under the old flow, with no reliable formation record. A re-acceptance flow is deployed at next login: the current terms presented, with a checkbox and a "Continue" action, logged.

The modification notice. Email to all users describing the material changes, thirty days before the effective date, with the archive link and a statement that continued use after the date constitutes acceptance. Delivery records retained.

The arbitration clause. Rewritten with company-paid fees, a small-claims carve-out, a remote-hearing option, an informal resolution period, a batching protocol for mass filings, and a delegation clause.

The subscription flow. Reviewed against 15 U.S.C. § 8403 and 16 C.F.R. § 425.1. Price, renewal frequency, and cancellation method disclosed adjacent to the payment step. The pre-checked auto-renew box removed. Cancellation moved online, two clicks, no retention interstitial that obscures the exit.

Eighteen months later. A putative class action arrives. The motion to compel is supported by a declaration attaching the flow screenshot for the plaintiff's sign-up date, the terms version served, and the interaction log. It is granted.

The cost. Two weeks of engineering, a week of design, and a fortnight of counsel time. Against a class action that would otherwise have proceeded on the merits.

Common Mistakes

Notice below the button. Specht v. Netscape Communications and every case since.

Hyperlinks that do not look like hyperlinks. Berman v. Freedom Financial Network treats this as its own failure.

Testing only on desktop. Most formation failures are mobile layout failures.

Browsewrap. A link in the footer is not a contract. Nguyen v. Barnes & Noble.

No version register. The company can show the current flow and cannot show what the plaintiff saw.

No per-user record tying an account to a terms version and a flow version.

Silent modification. Posting a revised version without notice, contrary to Douglas v. U.S. District Court.

Unlimited unilateral amendment clauses, which can render the promise illusory and take the arbitration clause with it.

Adding an arbitration clause after a dispute has arisen and expecting it to apply.

An arbitration clause that looks designed to prevent adjudication. Loser-pays, inconvenient forums, shortened limitations, and one-sided carve-outs invite unconscionability findings.

No mass arbitration protocol, and a per-case fee exposure nobody modelled.

Auto-renewal disclosed only in the terms, rather than adjacent to the payment step as 15 U.S.C. § 8403 requires.

Cancellation harder than sign-up, which is the single most enforced dark pattern.

Terms nobody can read. Length and density support unconscionability arguments and make a poor exhibit.

Business-to-Business Terms

The analysis differs where the counterparty is a business rather than a consumer, and the differences are worth stating.

Formation is easier. Sophisticated parties, negotiated agreements, and executed signature pages remove most of the assent problems. Where the relationship is nonetheless click-through — a self-service tier, an API agreement — the consumer formation standards apply, because they are standards about interfaces rather than about parties.

Unconscionability is harder to establish. Sophistication and bargaining power cut against it.

Limitations of liability generally hold, subject to the usual carve-outs for gross negligence, wilful misconduct, confidentiality breach, indemnity obligations, and payment obligations.

Arbitration is a commercial choice rather than a class-action shield, and the considerations are speed, confidentiality, enforceability abroad, and appellate rights.

Order-of-precedence clauses matter. Where an order form, a master agreement, click-through terms, and a data processing addendum all apply, the precedence clause determines which controls, and its absence produces the dispute.

Incorporation by reference works where the referenced document is identified and accessible, and fails where it is a moving target the customer never saw.

Modification rights are narrower. Enterprise customers negotiate against unilateral amendment, and the usual compromise is amendment on notice with a termination right if the customer objects.

Auto-renewal terms in business contracts are governed by the agreement rather than by consumer statutes, but notice-of-renewal obligations are increasingly negotiated.

The overlap that catches companies. A single terms of service applied to both consumers and businesses will be judged by the consumer standards where a consumer is the plaintiff. Separate the flows. See What You Are Actually Buying.

Diligence Questions

What is the formation flow, and has it been reviewed against Berman v. Freedom Financial Network? Screenshots on desktop and mobile.

Is there a flow version register with dates?

Is there a terms version archive with effective dates, publicly accessible?

Are per-user assent records captured? Terms version, flow version, timestamp.

How are modifications notified, and are delivery records retained?

Is there an arbitration clause, and has it been tested? How many motions to compel have been filed, and what happened?

Is there a mass arbitration protocol, and has the exposure been modelled?

Have subscription flows been reviewed against 15 U.S.C. § 8403, 16 C.F.R. § 425.1, and state automatic renewal statutes?

Is cancellation at least as easy as sign-up?

Are there pre-checked consent boxes anywhere in the product?

Any regulatory inquiries or enforcement relating to disclosures, renewals, or cancellation?

Do consumer and business customers pass through the same terms? If so, the consumer standard governs the whole thing.

Questions Clients Ask

Do we need a checkbox? Not always. A sign-in wrap with conspicuous notice above the button and a properly styled hyperlink is generally sufficient after Meyer v. Uber Technologies. A checkbox is stronger and is worth the friction for high-stakes terms.

Is our footer link enough? No. Nguyen v. Barnes & Noble holds that browsewrap without notice or a prompt does not form a contract.

Can we change the terms whenever we want? You can reserve the right, but you still need notice. Douglas v. U.S. District Court holds that a party is not bound by amendments it had no reason to know about, and unlimited amendment rights can render the promise illusory.

Does continued use count as acceptance? Where the user had notice of the change and of that consequence, generally yes. Without notice, no.

Will our arbitration clause be enforced? If a contract was formed and the clause is not unconscionable, generally yes under 9 U.S.C. § 2 and AT&T Mobility v. Concepcion. The usual failure is formation, not the clause.

Who decides whether the dispute is arbitrable? The arbitrator, if there is a clear delegation clause, per Henry Schein v. Archer & White Sales. Except formation, which is always for the court.

We received four thousand arbitration demands. That is mass arbitration, and the response depends on what the clause says about batching, bellwethers, and informal resolution. If it says nothing, the provider's fee schedule governs.

Do we have to let people cancel online? Under 15 U.S.C. § 8403 the mechanism must be simple, and state automatic renewal statutes are increasingly explicit that online sign-up requires online cancellation.

Can we pre-check the auto-renew box? No. Informed consent before charging is required, and pre-checked boxes are a paradigm dark pattern.

Can we require a phone call to cancel? Not where sign-up was online. The cancellation mechanism must be at least as easy.

How long do we keep the records? Through the limitations period for contract claims in the relevant jurisdictions, which means years — and longer than most retention schedules provide.

Can we use one set of terms for consumers and businesses? You can, and you will be judged by the consumer standard. Separate flows are better.

The Flow Review Standard

A single page that a designer, an engineer, and a lawyer can apply together. Every consent or purchase flow should pass all of it.

Notice placement. Above the action, visible without scrolling, on the smallest supported viewport.

Notice styling. Same font family as surrounding interface; size no smaller than surrounding body text; contrast ratio meeting accessibility standards.

Hyperlink styling. Visually distinct as a link — colour and underline, or an equivalent convention the interface uses consistently.

Action language. "By clicking [button label], you agree to the [Terms of Service] and [Privacy Policy]." Button label matches exactly.

No dismissible interposition. The notice cannot be inside a modal the user can close without reading.

Consent boxes unchecked. Every consent, every time.

Price and renewal disclosure adjacent to the payment step, before billing information is collected, per 15 U.S.C. § 8403.

Cancellation path discoverable in the account interface within two interactions, with no more steps than sign-up required.

Retention interstitials limited to a single offer that does not obscure the exit.

No countdown timers or scarcity claims that are not factually true.

No confirmshaming. Decline options labelled neutrally.

Fee disclosure complete at first price display, not at checkout.

Screenshots captured on deploy, at three viewport widths, stored against the flow version.

Logging. Flow version, terms version, timestamp, and user identifier written at the assent event.

Sign-off. Design, engineering, and legal, recorded, before release.

The One-Page Position

Online terms position — [service], [date]. Formation flow version [N], deployed [date], reviewed against Berman v. Freedom Financial Network on [date]; notice above action, link styled, action language present, tested at [N] viewports. Flow version register: [N] versions recorded from [date]; screenshots on file for [N]. Terms archive: [N] versions with effective dates, publicly accessible at [URL]. Per-user assent logging active since [date]; coverage [N] per cent of accounts. Legacy accounts without a reliable record: [N]; re-acceptance flow [deployed / planned]. Modification practice: notice by [method], [N] days before effect, delivery records retained. Arbitration: clause in force since [date]; company-paid fees, small-claims carve-out, delegation clause, batching protocol; motions to compel filed [N], granted [N]. Mass arbitration exposure modelled [date]. Subscription flows reviewed against 15 U.S.C. § 8403 and 16 C.F.R. § 425.1 on [date]; [N] findings, [N] remediated; cancellation now [N] clicks against [N] for sign-up. State automatic renewal statutes mapped for [N] states. Recommended actions: [instrument assent logging / deploy re-acceptance / rewrite the arbitration clause / remove the pre-checked box in flow X / move cancellation online].

Working With Other Advisers

Product design, who own the flow. This is the collaboration that determines everything else, and it works best as a shared standard applied at design review rather than as a legal veto applied at launch.

Engineering, who own the instrumentation. The assent logging change is small and it is the difference between a provable contract and an unprovable one.

Litigation counsel, for the motion to compel practice, the declarant preparation, and the assessment of whether arbitration remains the right structure given mass filing exposure.

Consumer protection counsel, for the negative option and dark pattern review, which is where the enforcement risk has concentrated.

Privacy counsel, because consent flows are subject to both the contract analysis and the privacy analysis, and a manipulative interface can invalidate consent for both purposes.

Marketing, whose scarcity claims, countdown timers, and promotional framing are what dark pattern enforcement actually targets.

Customer support, whose cancellation scripts and retention practices are the operational reality behind the "simple mechanism" requirement.

Records management, for the retention periods that must outlast the flows they document.

A Closing Note

The recurring lesson in this area is that the document everyone spends money on is not the document that decides the case.

Companies negotiate their limitation of liability to the comma and cannot prove anyone agreed to it. They draft arbitration clauses with delegation provisions and batching protocols and lose the motion on formation. They add a modification clause and then change the terms silently.

The fix is not more drafting. It is four things a company can do in a fortnight: put the notice above the button and style the link, log the terms version at the assent event, keep the flow screenshots and the terms archive, and give notice before changes take effect.

Do those, and the terms mean what they say. Skip them, and the terms are a document the company wrote to itself.

Electronic Signatures and Records

A related question that arises whenever the transaction is more formal than an account signup.

The statute. 15 U.S.C. § 7001 provides that a signature, contract, or record relating to a transaction may not be denied legal effect solely because it is in electronic form, and that a contract may not be denied effect solely because an electronic signature was used in its formation.

Consumer disclosures require consent to electronic delivery. Where a statute or regulation requires that information be provided in writing to a consumer, the electronic version satisfies it only if the consumer has affirmatively consented in a manner that reasonably demonstrates they can access the format used, and has been given specified disclosures about the consent.

Which is a separate consent from the terms assent, and it is frequently overlooked in flows that deliver required disclosures electronically.

Record retention. Electronic records satisfy retention requirements where they accurately reflect the information and remain accessible to those entitled to it, in a form capable of being accurately reproduced.

Attribution. An electronic signature is attributable to a person if it was the act of that person, shown in any manner, including the efficacy of any security procedure. The logging practice described above is precisely that evidence.

State law runs alongside. Most states have adopted a uniform electronic transactions statute, and the interaction with the federal provisions is generally complementary.

Practical consequence. For high-value or regulated transactions, use a signature process that captures identity, intent, and record integrity — and keep the audit trail. For ordinary account terms, the assent logging described above serves the same evidentiary function at far lower cost.

Cadence

At every flow change. Legal sign-off against the flow review standard, screenshots captured, version register updated.

At every terms change. Archive updated with the effective date, notice sent by the defined method, delivery records retained, and material changes assessed for whether affirmative re-acceptance is required.

Quarterly. Sample an account and reconstruct what that user saw and agreed to. If it takes more than an hour, fix the record before fixing anything else.

Semi-annually. Subscription and cancellation flows reviewed against 15 U.S.C. § 8403, 16 C.F.R. § 425.1, and the state automatic renewal statutes in the markets served.

Annually. Arbitration clause reviewed against current authority and against the company's own mass filing exposure; unconscionability provisions reassessed; retention periods checked against limitations periods.

On any adverse ruling. A post-mortem on which element failed, fed back into the flow review standard.

On entering a new market. Local formation, consumer protection, and automatic renewal requirements assessed before launch, because several jurisdictions impose requirements materially stricter than the ones described here.

What it costs. The flow redesign is a fortnight of design and engineering. The assent logging is a day. The screenshot capture is an hour of build pipeline work. The terms archive is a static page. The version register is a spreadsheet. Together they are less than the cost of a single unsuccessful motion to compel arbitration — and they are what makes that motion succeed.

And one last framing for the business. Terms of service are not a legal document that sits beside the product. They are part of the product, presented in the product's interface, accepted through the product's flows, and proved by the product's logs. Treating them as a document to be drafted rather than a feature to be built is why so many of them turn out to be unenforceable at exactly the moment they matter.

A Suggested Reading Path

For formation:

For the surrounding compliance:

For the platform context:

Primary Authorities

| Authority | Proposition | |---|---| | 9 U.S.C. § 2 | Validity of arbitration agreements | | 9 U.S.C. § 3 | Stay pending arbitration | | 9 U.S.C. § 4 | Order compelling arbitration | | 9 U.S.C. § 16 | Appeals | | 15 U.S.C. § 7001 | Electronic signatures and records | | 15 U.S.C. § 8403 | Negative option; ROSCA | | 15 U.S.C. § 45 | Unfair or deceptive acts or practices | | 16 C.F.R. § 425.1 | Negative option plans | | Specht v. Netscape Communications | No assent without notice | | Nguyen v. Barnes & Noble | Browsewrap unenforceable | | Meyer v. Uber Technologies | Sign-in wrap upheld on the design | | Berman v. Freedom Financial Network | Two-part standard; hyperlink styling | | Douglas v. U.S. District Court | Unilateral modification requires notice | | AT&T Mobility v. Concepcion | FAA preempts state rules against class waivers | | American Express v. Italian Colors Restaurant | Cost of individual arbitration no bar | | Epic Systems v. Lewis | Class waivers in employment | | Henry Schein v. Archer & White Sales | Delegation clauses enforced | | Coinbase v. Bielski | District court stays pending appeal | | Viking River Cruises v. Moriana | Representative claims and arbitration |

Forms and Templates

Online terms are the one contract most companies never draft from a template, which is why they so often fail on formation rather than on substance. The License Agreement Template supplies the grant, restriction, and termination architecture that the content and service sections of online terms need, and reading it alongside a live terms of service page usually reveals what the terms left out — a defined licence to user content, a defined licence to the service, and clean termination consequences. The Portfolio Inventory Template is an unexpected but useful home for the terms version register: one row per version, with the effective date, the flow version served alongside it, the material changes, and the notice method used. That register is what answers the question a motion to compel arbitration actually turns on, which is what a specific user saw on a specific date. The Cease and Desist Template is relevant where the terms are being enforced against scrapers or abusive users, and the enforceability question there is the same formation question in a different posture.

Related Toolkits and Checklists

The Platform Liability and Section 230 Toolkit covers the statutory immunity that sits alongside the contract layer, and the promises made in terms of service are precisely the exposure that immunity does not reach. The Online Terms Enforceability Checklist runs the formation and evidence steps in order. The Promotions and Advertising Compliance Toolkit covers the advertising and disclosure rules that govern the flows in which terms are presented. And the State Privacy Compliance Toolkit covers the privacy notice obligations that sit in the same interface and are subject to their own dark pattern rules on consent.