Consumer Protection

A contract normally binds both sides to whatever they agreed. Online, only one side writes the agreement. The seller sets the terms and the buyer scrolls to the bottom and clicks accept. Almost nobody has read eighteen pages of terms of service before paying.

Left alone, that arrangement lets one line — "no refunds after purchase" — settle every dispute in advance. The buyer never handled the product, and with a service they pay before using it at all. When what arrives differs from what the page showed, and the way back is closed off in the terms, the remaining options are to give up or to complain to the card issuer.

Consumer protection is the exception carved into freedom of contract at that point. It layers a floor of rights onto the buyer's side and refuses to enforce terms that fall below that floor, on the premise that "both sides agreed" only means something if the buyer could tell what they were agreeing to.

It works by adding rights the law defines and cancelling the contract clauses that reach below them. Three rights make up most of the floor.

1. A cooling-off window — for a set period after purchase, the buyer can undo the sale without giving a reason. The length varies by market; two weeks is a common figure, and the clock often restarts from the day the buyer learns that the description didn't match what arrived. The point is that no defect is required. Having changed their mind is enough, which is what separates this from a warranty claim.
2. Disclosure before payment — a defined list has to reach the buyer before money moves: who is selling, what the price is and when it will be charged, what the next cycle costs, and how to cancel. If those four weren't clear at the moment the pay button was pressed, the side that failed to disclose carries the consequence.
3. A way out — the exit has to be roughly as easy as the entrance. Signing up with one click while cancelling requires emailing support and waiting for a reply is the shape this rule targets.

A fourth principle holds the other three up: where the contract is worse for the buyer than the law, that clause loses effect on its own. The rest of the agreement stands, so nothing is voided wholesale — the offending line is simply treated as absent. That's why "you agreed to the no-refund policy" carries little weight in a dispute. The test isn't whether consent was collected but whether the term sits below the legal floor.

Each right comes with its own exceptions. Items made to order, or goods that can't be resold once the seal is broken, generally fall outside the cooling-off window. Using an exception requires having told the buyer about it at the time of sale.

For the people building the product, this arrives as four places on screen rather than as statute text.

1. The pay button — the label reads "Pay $8 per month," not "Get started." The requirement that a charge be visible before it happens shows up as button copy.
2. The handoff from free trial to paid — a trial opens the full product for a fixed period, and before auto-renewal produces the first charge, a separate notice says when the money moves and how much it is. Treating the one line shown at signup as sufficient is the risky reading.
3. The subscription cancellation flow — because a subscription bills on a repeating cycle, this screen sits directly on revenue, which is exactly why teams want to insert save offers into it. Flows built that way land somewhere between what design calls a dark pattern and an outright violation.
4. Refund handling — returning money has deadlines attached. Accepting a cancellation and then paying late creates its own liability, and if the customer goes to the card issuer for a chargeback instead, the company absorbs both a fee and a dispute record.

The list gets reread every time a feature ships. Change the pricing structure and items 1 and 2 come back; move the cancel button one screen deeper and item 3 does. Nothing on the list is finished once and filed away.

"I can't approve moving cancellation into settings. Signup is two clicks and cancelling would be five."

An instruction to pull the flow back toward the legal standard.

"Are we sending the billing notice three days before the trial ends?"

Checking whether the pre-charge disclosure actually goes out.

"Writing it into the terms doesn't settle this one."

Contract language can't cut below a right the law grants.

The quarter Pagedeck opened card payments to individual users, this was the subject Grace spent the longest on. Until then every deal had been a signed contract with a company customer, so almost none of the list applied. Adding card payments meant rereading everything from the checkout copy to the cancellation path.

The cancellation flow took the longest. The first version put a discount offer, a survey, and a final confirmation between the customer and the exit. Grace moved the survey to after the cancellation had gone through and cut the discount offer down to a single screen. Trying to retain someone isn't itself prohibited, but each added step makes the design read more like a barrier placed in front of someone leaving.

The most common mistake is assuming that whatever the terms say will hold. Contracts usually do work that way, so the assumption is reasonable on its face. Consumer protection rules exist as the exception to it, which reverses the direction: a clause below the legal floor has no effect even with consent recorded. Running on "no refunds" without knowing that means unwinding the policy all at once after the disputes pile up, with every earlier rejection still sitting in the complaint queue.

The other mistake is treating a harder cancellation as a win. Adding steps does push the cancellation rate down for a while, so the metric looks like a success. But people held back that way tend to dispute the next charge with their card issuer or describe the experience in a review. What the team keeps is handling cost and reputation damage rather than a customer, and this design is precisely what the rules aim at.