Cookie Policy
This page covers the cookies ElevenReview sets, what each one does, and how you change your mind about them. What we collect more broadly, and how to exercise your rights, is in our Privacy Policy.
What a cookie is
A cookie is a small file a site asks your browser to store so it can recognise the same browser on the next page or the next visit. Some cookies are needed for a site to work at all, and everything past that is optional. This site sets the first kind and only the first kind.
The cookies we set
Nothing on this site is set to remember you. A reader who never signs in is served every page without a cookie that records what they read or identifies who they are, which is why the list below is short: the necessary cookies in it appear only where the site cannot run without them.
- Strictly necessary, and they exist for the people who edit the site. WordPress sets two: a session cookie when an editor signs in, and a test cookie so that sign-in works. A reader is given neither. Anything else the site ever has to store in order to work belongs in this group, and this page is where it gets listed. None of them records what you read, and none can be switched off, because the pages would stop working without them.
- No analytics. We do not count page views, sessions or traffic sources, and nothing here builds a picture of how you move through the site. If we ever need to know which pages get read, the answer will come from our own server logs, which stay on our host and are never shared.
- No advertising and no tracking. Nothing on this site follows you elsewhere or profiles you for ads. There is no pixel, no tag manager and no advertising identifier, and no third party loads anything through these pages.
Because there is nothing third-party here, following an affiliate link is an ordinary move to another site. What that merchant stores once you arrive is their cookie, on their domain, under their policy; our Affiliate Disclosure explains the relationship between us and them.
Your choice
There is nothing optional on this site for you to accept or refuse, so no consent banner is shown. A banner asks permission before something optional is stored. With nothing optional to store, it would be a button asking a question the site has already answered.
If that ever changes
If we ever add something optional (analytics, an embedded player, a form served by someone else), it will not load until you allow it, and the banner asking for that permission will exist before the change does. Refusing will be one click, offered in the same place and at the same size as accepting, nothing will be pre-ticked, and withdrawing your choice later will be as easy as giving it.
Browser settings
The browser you are reading this in lets you block or delete cookies, usually site by site. Blocking them here does not break the reading, because the reading does not depend on a cookie. If you are signed in as an editor it ends that session; for a reader there is nothing to lose.
Changes
If we add a cookie, drop one or change where something is loaded from, we update this page and its last-updated date first. Anything optional arrives with a banner, and nothing optional is set before you allow it.