Why Your Legal Copy Doesn't Have to Be Unreadable

There’s a widespread belief that legal copy has to be unreadable. That terms of service, privacy policies, refund rules, and disclaimers are somehow required, by law or by prudence, to be written in a dialect no customer can follow. I want to push on this belief, because I’ve read a lot of these documents while auditing websites, and the unreadability is almost never doing what people think it’s doing.

Start with what legal language is actually for. The good reason legal text gets precise is that precision prevents disputes. “We’ll refund you if you’re unhappy” invites an argument about what unhappy means; “we’ll refund any order within 30 days of delivery, no questions asked” doesn’t. Precision like that is a gift to both sides. But notice that the precise version is also the more readable one. Precision and readability are not opposites. The thirty-day sentence is both tighter legally and easier for an eighth grader to follow than the vague one. What people mistake for necessary precision is usually something else: accumulated boilerplate, copied from a template that copied from another template, in prose style inherited from an era when these documents were read only by other lawyers, if they were read at all.

That inheritance is the real story. Most small companies never wrote their legal pages. They pasted them, from a generator or a competitor, and the paste included the register: the shall-heretofores, the defined terms in capital letters, the sentences that run nine lines because splitting them was nobody’s job. The company then treats this text as untouchable, the way you’d treat a load-bearing wall. But it isn’t load-bearing. What binds you is what the words mean, not how convoluted they sound. A refund policy that says “if you cancel in the first 30 days, we refund everything you paid” commits you to exactly the same thing as the impenetrable version, and a court reads meaning, not costume. Complicated phrasing doesn’t strengthen a term. Sometimes it weakens one, because a term the customer plausibly couldn’t understand is a term they can argue they never really agreed to. Regulators have been moving the same direction for years; modern privacy law, notably, explicitly asks that disclosures be in clear and plain language, intelligible to the person they’re aimed at. The law is not the thing demanding your fog. In places, the law is asking you to clear it.

Meanwhile the fog has a price that never shows up on the legal department’s ledger, because it’s paid on the sales side. Customers read legal pages at exactly one moment: when they’re nervous. About to pay, about to hand over data, wondering what happens if they need to cancel. They arrive at your refund policy looking for reassurance, and you answer with four paragraphs of defined terms. Some fraction of them just leave. Not because your terms were bad. Because they couldn’t tell whether your terms were bad, and when the stakes are your own money, illegible is indistinguishable from unfavorable. The unreadable policy functions as a wall between a nervous customer and the reassurance you were, in substance, already offering. You wrote “30 days, full refund” and they experienced “who knows.”

The fix doesn’t require choosing between lawyers and readers, and the best sites demonstrate this with a two-layer structure. Keep the full legal document if your counsel wants it, but put a plain summary where the anxiety actually occurs. Next to the buy button: “Cancel anytime in 30 days for a full refund.” At the top of the privacy policy: “We don’t sell your data. We use it to run your account and nothing else.” Label the summary as a summary, keep it consistent with the full text, and you’ve lost nothing legally while gaining everything commercially. The plain sentence converts; the long document governs. And in my experience the exercise of writing the summary improves the long document too, because summarizing forces you to discover what you actually committed to, and occasionally you find the template committed you to something you’d never knowingly choose.

I check legal-adjacent pages when GazeSite audits a site, and there’s a detail I keep encountering: the readability scores on terms pages are frequently the worst on the entire site, worse than engineering docs, worse than anything. On the pages where a stranger decides whether to trust you with money, the writing is at its most hostile. That’s exactly backwards, and no statute made it that way. Habit made it that way, and habit plus a template plus nobody’s-job-to-fix-it is how it stays.

So if you own a website, here’s a modest proposal. Open your refund policy on your phone and read it as if your own money were at stake. If you, who wrote or at least pasted it, can’t get through it comfortably, your customers certainly can’t. Then write the one-sentence version of each promise it contains and put those sentences where people actually look. Have a lawyer confirm the summaries match the document. That’s the whole project, an afternoon of work. Unreadable legal copy isn’t caution. It’s clutter wearing caution’s clothes, and clearing it is one of the rare changes that makes your lawyer, your customer, and your conversion rate all better off at once.