Skip to main content
ITISYOU
Menu

Check

Trust page checklist

Which pages does your site owe its readers, and what has to be on each one? Answer eight questions and find out — including where each requirement comes from.

What does your site do?

Tick everything that is true. The list below changes as you do.

4 pages to write

2 required · 2 recommended

  1. About — who publishes this

    required

    A reader deciding whether to trust anything else here starts by asking who wrote it. Nothing else on the site substitutes for that.

    What it has to say

    • Who runs the site — a person or an organisation, named.
    • Where they are based, at least to the country.
    • What the site is for, in a sentence a stranger would understand.
    • How it is funded, if money is involved anywhere.

    Where this comes from: Convention, and the ownership signal every ad and search platform looks for.

  2. Contact

    required

    Every other promise on the site — corrections, refunds, security reports, data requests — needs somewhere to arrive.

    What it has to say

    • A monitored address, not a form that goes nowhere.
    • Roughly how long a reply takes, honestly.
    • Where specific things should go instead, if they have their own route.

    Where this comes from: Convention, and a precondition of the routes below.

  3. Terms of use

    recommended

    Nothing is sold, so little is required — but the limits of what you are promising are still worth stating once.

    What it has to say

    • That the content is provided as-is, and what it is not (advice, a guarantee, a professional opinion).
    • What readers may and may not do with what you publish.

    Where this comes from: Convention.

  4. Accessibility statement

    recommended

    It tells someone who cannot use part of the site that you know, what you are doing about it, and where to tell you.

    What it has to say

    • What standard you aim at, and how you tested against it.
    • What is known not to work yet — the gaps, named.
    • How to report a barrier, and what happens then.

    Where this comes from: Required for UK public sector bodies; good practice otherwise, and the honest way to handle known gaps.

What this is for

Almost every site needs a few pages that are not the product: who runs this, how to reach them, what happens to your data, what you are agreeing to. Which ones you need depends entirely on what the site does — and the usual failure is not malice but omission. Somebody adds analytics without adding a consent choice, or sells something without writing down the cancellation right that exists whether or not they mention it.

This turns that into a list. Each answer brings specific pages into existence, and each page comes with what it actually has to contain and the rule behind it, so you can go and read the rule rather than take this page’s word for it.

Read this before you rely on it

  • This is not legal advice. It is a checklist written by someone who worked through these questions for one small site. It cannot see your site, does not know your circumstances, and is no substitute for the regulator’s own guidance or a solicitor.
  • It describes the UK position, with UK GDPR, PECR and consumer law in mind. Untick the UK question and the specifically-UK items drop out, but what remains is general convention rather than a survey of other regimes.
  • “Required” means a regime or a platform policy compels it, as best this checklist understands it — not that a court has said so about your site.
  • It covers pages, not implementation. A cookie page saying nothing loads before consent is worth nothing if something does. The claim checker is the tool for whether your words match what you actually do.
  • The regulators are the authority. For data protection and cookies that is the ICO; for consumer rights, Citizens Advice publishes the plain-language version. Both beat anything written here.

Where this came from

Working through these questions for this site, and being wrong about several of them. The assumption that collecting almost no personal data means the obligations mostly do not apply is a common one and it is incorrect; there is a written account of finding that out. The pages under the trust centre are the result, and this checklist is the reasoning behind them made reusable.

Nothing you tick is recorded

The answers describe your site, which is not information this site has any business keeping. The rules run in your browser; nothing is sent anywhere and nothing is stored. This site runs no analytics and sets no cookies of its own; the advertising on it does set cookies, but it cannot see which boxes you tick — see privacy and cookies.

If a requirement here is wrong, out of date, or missing, please say so: kpleelaaravind@gmail.com. Corrections to this page are handled the same way as everything else.