Loading the page
Loading the page
Policies
Policy documents are usually written to be defensible rather than legible. We have tried to make these both. Each one carries a version number and an effective date.
The documents
How these are kept
Two of these — the shipping policy and the returns policy — describe a service that does not yet operate. They are published in advance deliberately, so that the terms are set before there is any commercial pressure on how they are written.
The rest apply now. A policy without a revision history cannot be audited, which is why every document here carries a version and a date, and why the three steps below are a commitment rather than a description of housekeeping.
01
The number shown against the document above moves up, so a copy taken before the change can be told apart from one taken after it.
02
The date the revised wording takes effect is published with it, rather than applied backwards over the period it was not in force.
03
What moved is written down against the document, so that a revision can be read rather than inferred from two saved copies.
Awaiting publication
No document here has been revised yet, so there is no revision history to read.
Each policy is still at the version it was first published at.
The first time one of them changes, the version and the effective date in the table above move, and what changed is recorded against that document.
Questions
Anything about how we handle data, or about a document above, can be sent to us directly. We respond to policy queries within five working days. A complaint follows a separate route, set out in the consumer grievance policy, which states what we do and by when.
Cookie choices sit on their own page rather than inside a policy, because a decision you may want to revisit needs somewhere to revisit it.