CHECKSURE — COOKIE POLICY
Cookie Policy
Version 1.3 | Last updated: 17 September 2026 | Review by: 17 September 2027
How CheckSure uses cookies
This Cookie Policy explains how CheckSure uses cookies and similar technologies on checksure.co.uk. It should be read alongside our Privacy Notice.
What are cookies and similar technologies?
Cookies are small text files placed on your computer, tablet or mobile device when you visit a website. Similar technologies can store or access information on your device in other ways, including browser session storage.
Some technologies are necessary to provide a service you request or to make the website work. Optional analytics technologies require your consent.
Your analytics choice
On your first visit, CheckSure asks whether you accept or reject analytics. Accept and reject are equally available. There is one optional category—analytics—so no separate category-selection screen is needed.
If you accept, CheckSure loads Google Tag Manager and Google Analytics 4 and permits the analytics cookies listed below. If you reject or make no choice, those Google services remain wholly blocked: no optional analytics cookie, analytics request or cookieless ping is sent.
Your choice is remembered for 180 days. You can reopen Cookie settings from the website footer and change or withdraw your choice at any time. If you withdraw, future analytics stops and the website attempts to remove visible Google Analytics cookies. You may also delete cookies through your browser.
Rejecting analytics does not prevent you from using the website or sending an inspection request.
Essential and functional technologies
The consent-choice cookie records only whether analytics was accepted or rejected. It is used to respect and remember the choice you requested and does not measure website use.
WordPress uses session storage to remember the result of a browser emoji-capability check for the current browser session. This prevents the same functional test being repeated unnecessarily and does not create an analytics profile.
Optional Google Analytics
With your consent, Google Analytics 4 helps CheckSure understand how people reach and use the website and move through the enquiry process. It may process a random browser identifier, browser and device information, approximate location, pages viewed, traffic source and campaign information, and controlled non-personal interaction events.
CheckSure does not configure analytics to receive names, email addresses, telephone numbers, postal or property addresses, free-text answers, dates entered in the form, customer references, uploaded filenames or document contents. Query strings are removed from the analytics page location except for the controlled utm_source, utm_medium, utm_campaign, utm_term and utm_content campaign parameters.
Advertising, remarketing, Google Signals, demographic profiling, personalised advertising, user-ID and user-provided-data collection are disabled. Google Analytics user-level and event-level retention is set to 14 months. The staging website uses a separate test property so its activity does not enter production reporting.
International processing
Google may process analytics information outside the United Kingdom. Google provides Google Analytics under its data-processing terms and states that it acts as a processor for Analytics customers. CheckSure relies on the applicable UK transfer safeguards described in those terms, including the UK Addendum or another lawful transfer mechanism where required. Contact privacy@checksure.co.uk for further information.
External websites and embedded services
The website contains links to external services, including WhatsApp and social-media websites. If you follow an external link, that provider may use its own cookies or similar technologies under its own privacy information. CheckSure does not currently load maps, videos, social-media embeds, live chat, advertising pixels or payment widgets on ordinary public pages.
Contact and review
For questions about this Cookie Policy or the website’s use of cookies, email privacy@checksure.co.uk. The policy owner is CheckSure Ltd. This version takes effect on 17 September 2026 and will be reviewed by 17 September 2027, or earlier if the website, providers, purposes or technologies change.
Cookie and similar-technology inventory
| Name | Provider | Purpose | Category | Duration | When used |
|---|---|---|---|---|---|
| checksure_analytics_consent | CheckSure Ltd | Remembers accepted or rejected analytics choice | Necessary consent preference | 180 days | After the visitor accepts or rejects |
| wpEmojiSettingsSupports (session storage) | WordPress / CheckSure hosting | Caches the browser emoji-support test | Functional | Current browser session | During ordinary page rendering where WordPress performs the check |
| _ga | Google Analytics 4, set first party | Distinguishes a browser using a random identifier | Optional analytics | Up to 2 years, subject to browser limits | Only after Accept analytics |
| _ga_<container-id> | Google Analytics 4, set first party | Persists analytics session state | Optional analytics | Up to 2 years, subject to browser limits | Only after Accept analytics |
The exact Google Analytics cookie suffix differs between the controlled staging-test and production streams. The pattern above is used because Google documents the cookie by container ID. Final-domain browser testing must confirm the actual production suffix before indexation approval.