1. The short answer
This website sets no cookies. It runs no analytics, no tag manager, no advertising pixel, no session recording and no social widgets. It stores nothing in your browser at all — not a cookie, not local storage, not session storage.
That is why you were not asked to accept anything when you arrived. There is nothing here to accept, and nothing to refuse.
2. What this site loads
Every page here is built in advance and served as a plain file. Loading one asks this site for the page, its stylesheet, a small amount of JavaScript for page-to-page navigation, and one typeface — which is served from this site as a font file rather than fetched from Google Fonts or any other host.
There are no third-party images, no embedded video, no maps, no chat widget, no comment system, no A/B testing tool and no error-reporting script. Visiting a page here tells nobody but this site that you did.
3. Why there is no cookie banner
The Privacy and Electronic Communications Regulations require your consent before a site stores information on your device or reads information already stored there, unless it is strictly necessary to provide what you asked for. This site stores nothing, so there is nothing to ask you about. A banner asking permission for none of it would be decoration, not compliance.
4. What the server records
A cookie is something stored in your browser. A server log is a record of the request itself, and it is a different thing. When our hosting provider serves you a page, it records the IP address the request came from, the date and time, what was requested, and the user-agent string your browser sends.
We use that to keep the site available and to investigate abuse. It is not used to identify you, to build a profile, or to follow you between visits, and it is not combined with anything else. It is deleted after 30 days. The privacy policy covers it in full.
5. Links to other sites
Pages here link out — to the App Store, to GOV.UK, to legislation.gov.uk and to the HSE, among others. Those sites set their own cookies and have their own policies, and we have no control over either. Following a link is your decision, and it is the point at which this site stops being the only one involved.
A link to a public source is a link, not an endorsement, and not a sign of any connection between us and the organisation at the other end.
6. The app itself
The Indate app is not a web browser and uses no cookies. It does two things over the network: it downloads a configuration file that contains no information about you, and — unless you switch it off in Settings — it sends usage counts and crash reports through Firebase, which stores a random identifier for the installation on your device.
That identifier is the kind of thing the same regulations cover, which is why it is switchable and why we treat leaving the switch on as your consent. The privacy policy sets out exactly what is collected, and what never is.
7. If this ever changes
We have no plans to add anything that stores information in your browser. If that changes, we will update this page before it happens, and we will ask for your consent before setting anything that is not strictly necessary. We will not make that request by burying it in a banner with a pre-ticked box.
Questions about any of this go to [email protected].
Related pages: privacy policy · terms and conditions · support.