Skip to main content
FYNORALAUNCH home

THIS SESSION · FINTECH · MONEY TOOLS

Risk Warnings and Disclaimers That People Actually Read

Compliance Basics · 9 min read ·

A risk warning nobody sees protects nobody. How to word, place and design warnings and disclaimers so they inform readers instead of hiding in the footer.

Illustration: A charcoal page mock-up in monospace type with a tiny grey footer disclaimer crossed out in red beside a clear green-bordered warning placed next to the headline

Every finance site has a footer full of grey text beginning with "Capital at risk" or "Terms apply". Hardly anyone reads it. That is a problem for readers, who miss information that matters, and for founders, because a warning that cannot be seen may not count as a warning at all.

This guide is about writing and placing risk warnings and disclaimers so that they work. It is general information, not legal advice, and the wording you need depends on your product and your country.

What a warning is for

A risk warning has one job: to make sure the reader understands something that could affect their decision. Not to protect you in a dispute, not to satisfy a template, not to meet a quota of words.

If you keep that purpose in mind, many choices become easy. A warning is good if a reasonable reader, who sees it, understands what could go wrong. It is bad if it is technically on the page but practically invisible.

The overall impression rule

Regulators look at how a promotion comes across as a whole. The UK advertising code's section on misleading advertising says the ASA takes into account the impression created by marketing communications as well as specific claims, and rules on the likely effect on consumers, not on the marketer's intentions. The FCA says financial promotions must be clear, fair and not misleading.

Two consequences follow:

  1. A disclaimer cannot rescue a misleading headline. If the main message creates a false impression, a note in small print does not fix it.
  2. Prominence matters. A risk that matters should be about as easy to notice as the benefit that tempts.

Place it where the claim is

Position is half the battle.

  • Next to the claim, not at the bottom of the page. If a headline mentions returns, the warning belongs beside it.
  • On every page the claim appears. A home page headline that appears on a social post needs the warning there too, or a clear link that does the job.
  • In the flow. If a user is about to commit money, repeat the key risk at that step, in a calm, readable form.
  • Not hidden behind a click if the information is important enough to affect a decision.

Where space is truly limited, such as a short social post, keep the post itself non-misleading and link to a page that carries the full information. Do not use the shortness of the format as an excuse to say more than you can support.

Say it in plain words

A warning in dense legal language is not read. Write the key point as you would say it to a friend.

Weak: "The value of investments may fluctuate and past performance is not indicative of future results; investors may not recover the amount originally invested."

Better, in addition: "You could lose some or all of the money you put in."

Lead with the plain sentence, then add the formal wording or a link. The formal text may still be needed, but the short sentence is the one people will take in.

Avoid:

  • Double negatives.
  • Long strings of conditions in one sentence.
  • Words only specialists understand.
  • Burying the main risk in the third paragraph.

Make it visible

Design decides whether a warning is seen.

Size. Small enough to be neat, big enough to read on a phone without zooming.

Contrast. The Web Content Accessibility Guidelines set a minimum contrast ratio for normal text against its background. Light grey on white fails, and many footers use exactly that. Check your colours with a contrast tool.

Position in the reading order. Screen reader users hear a page in order. A warning placed after fifty links in the footer will be heard last or never.

Real text. Not an image of text, which cannot be resized or read aloud.

Not hidden by design. A scrolling ticker, an auto-hiding banner or a collapsed panel can make a warning easy to miss. If the information matters, show it.

Consistent style. Use one clear style for risk notes across the site so people learn to look for it.

Disclaimers versus warnings

The two are often confused.

A warning tells someone about a risk they might face.

A disclaimer limits what you take responsibility for, or clarifies what you are not.

Both can be useful. "This tool does not give financial advice" is a clarification that helps people understand what to expect. But it should not be a way to dodge accuracy elsewhere. If your page behaves like advice, the label will not change that.

Also note that you cannot disclaim away certain rights. In many places consumer law gives people protections that no notice can remove. Take advice before relying on a disclaimer for anything important.

Test with real readers

You cannot judge your own page, because you know what it says. Test it.

  1. Ask three people who have not seen the product to read your page for thirty seconds.
  2. Take it away and ask: what does this product do? What is the main risk? What does it cost?
  3. If they cannot answer the second question, the warning is not working. Move it, simplify it or make it bigger.
  4. Repeat on a phone.

This takes an afternoon and is more convincing than any checklist.

Wording for common situations

Here are patterns, to adapt with advice.

A tool that shows data but does not advise. "This tool shows information about your accounts. It does not give financial advice or recommend any product."

A product where value can fall. "The value can go down as well as up, and you could get back less than you put in."

A feature that depends on third parties. "This feature relies on connections to banks, which may not always be available."

An illustration or estimate. "This is an example, not a forecast. Your results will differ."

A beta. "This is an early version. Some features may not work as expected."

Each is short, specific and states the point. Replace the content with what is true for your product.

Keep warnings in step with the product

Warnings go stale. A new feature may bring a new risk. A change in rules may require different wording. Add a review of warnings to your release checklist: any time you change a feature, a fee or a claim, ask whether a warning needs to change as well.

Record the wording, the date and who approved it. If a question ever arises, you will want the history.

What not to do

  • Do not put the warning in tiny grey text.
  • Do not use a long scroll box that nobody will scroll.
  • Do not make the user hunt for it in terms and conditions.
  • Do not contradict it with cheerful claims next to it.
  • Do not copy another firm's warning without checking that it fits your product.

On this site

The terms and privacy pages here set out the rules in full, and the launches page shows how entries read. The contact page is the way to ask a question, and the submit page starts an entry.

A short story of a footer that failed

A small investing app launched with a bold headline about "growing your money" and a risk statement in pale grey text at the bottom of a long page. Users who arrived from a social post never saw the footer at all. When markets fell and balances dipped, support received dozens of angry messages from people who said they had never been told they could lose money. The team had technically published a warning. In practice, nobody had met it.

They rewrote the page. The headline now described the product without promising growth, a plain sentence about the possibility of loss sat directly beneath it in readable type, and the same sentence appeared again before any deposit. Complaints of that kind stopped. Conversion barely changed, and the people who did sign up knew what they were joining, which made them better customers.

A quick audit you can run today

Open your own page on a phone. Scroll to the first benefit claim and look at what sits next to it. Find your main risk statement and note its size and colour. Ask whether you would notice it if you were in a hurry. Then read it aloud: if you stumble, so will your readers. Fix the weakest point first, set a date to repeat the audit after every release and keep a screenshot of each version for your records.

Record-keeping for warnings

Keep a dated copy of every page that carries a warning, with a note of who approved the wording. If a regulator, partner or customer ever asks what you showed on a given day, you can answer with evidence instead of memory. A simple folder of dated screenshots is enough, and takes seconds to add whenever a page changes.

The short version

A warning should help a reader understand a real risk. Put it next to the claim, say it in plain words first, make it large and contrasting enough to read on a phone, never rely on it to rescue a misleading headline and test it with strangers. If they cannot tell you the main risk after thirty seconds, rewrite it.

Questions and answers

Where should a risk warning go?
Close to the claim or product it relates to, at a size and contrast that makes it as noticeable as the benefit statement.
How long should a disclaimer be?
As short as clarity allows. Put the key point first in plain words and link to fuller detail.
Does a disclaimer cancel a misleading headline?
No. The overall impression of a promotion counts, and fine print cannot correct a headline that misleads.
What is a good test of a warning?
Ask someone to read your page for thirty seconds, then ask what the main risk is. If they cannot say, the warning is not working.
Do warnings need to be accessible?
Yes. Use real text, enough contrast and a size readable on a phone so everyone can see them.

Sources

Related guides

Help centre