Cookie Policy
This policy explains the cookies and similar technologies used on car-claimscheck.com. The website is run by Consumer Reclaim Ltd, trading as Car Claims Check. In short: we use only what the website needs to work, to remember your cookie choice and, on our claim form, to help prevent fraud. We do not use analytics or advertising cookies.
1. What cookies and similar technologies are
A cookie is a small file that a website asks your browser to store on your device. Your browser sends it back to the website on later visits, so the website can remember something, such as a choice you made.
Websites can also store information in your browser in other ways, known as browser storage. They can also use scripts to read details from your device, such as your screen size. The law treats these in the same way as cookies. This policy covers all of them.
The rules are set by the Privacy and Electronic Communications Regulations 2003 (PECR). Cookies that are strictly necessary for a service you ask for can be used without your consent. That includes cookies needed to prevent or detect fraud in connection with that service. Most other cookies need your consent first.
2. What we do and do not use
- We use only strictly necessary cookies and storage. They are listed in sections 3 to 6.
- We do not use analytics or statistics cookies.
- We do not use advertising or marketing cookies.
- We do not use social media buttons, or pixels for advertising or analytics.
- Our fonts are stored on this website, so loading a page does not send your details to a font provider.
- Our check on 12 October 2026 found that no page on this website loaded content from any other website. Since then, our claim form has added a device check, which does (see section 6).
3. Cookies we use
| Name | Set by | What it does | Type | How long it lasts |
|---|---|---|---|---|
mspc_consent |
This website | Remembers the choice you made in our cookie banner, so we do not ask you again on every page. It records only which option you chose. | Strictly necessary | 12 months |
wordpress_test_cookie |
This website | Set only if someone opens the website’s administrator login page. It checks that the browser accepts cookies. Visitors to our normal pages do not receive it. | Strictly necessary | Until you close your browser |
clientside-cookie |
Kount’s script, through the device check on our claim form | May hold an identifier for this browser, which the device check can use to recognise the browser again, to help prevent fraud. | Strictly necessary, to prevent fraud | 12 months |
Our website administrators also receive login cookies when they sign in to manage the website. Visitors never receive these.
On a first visit to our normal pages, our check on 12 October 2026 found that no cookies were set at all. The mspc_consent cookie is only set once you make a choice in the cookie banner. The device check’s cookie may be set once you start a claim on our claim form (see section 6).
4. Security cookies Cloudflare may set
Cloudflare delivers and protects this website. If its security features need to check that a visitor is a person and not an automated program, Cloudflare may set one of these cookies:
__cf_bm: helps tell people apart from automated traffic. It expires after 30 minutes without activity.cf_clearance: remembers that your browser has passed a security check, so you are not asked again. Cloudflare’s security settings control how long it lasts.
These cookies are strictly necessary to protect the website. Our check on 12 October 2026 found that Cloudflare set no cookies on normal visits. Cloudflare explains its cookies on its cookie information page.
5. Browser storage
| Name | Set by | What it does | Type | How long it lasts |
|---|---|---|---|---|
KountSessionID |
Kount’s script, through the device check on our claim form | May hold the device check’s session code for this visit. | Strictly necessary, to prevent fraud | Until you close the browser tab |
kountCookie |
Kount’s script, through the device check on our claim form | May hold a working copy, for this visit, of the browser identifier described in section 3. | Strictly necessary, to prevent fraud | Until you close the browser tab |
clientside-local |
Kount’s script, through the device check on our claim form | May hold a copy of the browser identifier described in section 3, in your browser’s local storage. | Strictly necessary, to prevent fraud | Until it is deleted: it has no expiry date |
msp_dsid |
This website, on our claim form | Holds the session code our form creates for the device check, so that the same code goes with your claim. | Strictly necessary, to prevent fraud | Until you close the browser tab |
msp_dsid_done |
This website, on our claim form | Records that the device check has finished for this visit, so that it is not run again. | Strictly necessary, to prevent fraud | Until you close the browser tab |
wpEmojiSettingsSupports |
This website (WordPress), only on the embed version of a page | Records whether your browser can show emoji characters. WordPress sets it only on the embed version of a page (an address ending in /embed/), which other websites can show inside their own pages. Our normal pages do not use it. It holds no personal data. | Strictly necessary, to show pages correctly | Until you close the browser tab |
If your browser blocks this kind of storage, our form keeps the session code in the page instead, until you leave it.
On the embed version of a page, if your browser cannot show emoji characters itself, WordPress may load images of them from WordPress.org. WordPress.org would then see your IP address. Up-to-date browsers do not need this.
6. The device check on our claim form
When you start a claim on our claim form, the form runs a device check from Kount, a fraud-prevention company that is part of Equifax. The check helps detect and prevent fraud, including identity fraud, on the claim you ask us to make. It runs only on our claim forms, and only once you start using one. It does not run on our other pages.
To run the check, your browser loads Kount’s script from jsDelivr, a public content delivery network. The script then opens a small, invisible frame from one of Kount’s own web addresses on kaptcha.com. Through it, the check reads technical details about your browser and device and sends them to Kount, with your IP address. Kount may set its own cookies or storage inside that frame, under its own address. The items in sections 3 and 5 that are set by Kount’s script are stored under this website’s address.
Kount’s script is able to read your device’s location, but only where a website already has your permission to use it. This website never asks for that permission, and it tells your browser to block location access on its pages.
We use the check only to prevent fraud, never for advertising. Kount may also use what it collects to help spot fraud on other websites and services that use Kount. Our Privacy Policy explains who receives the result.
7. Details read from your device when you sign
When you sign our claim form, we read some details from your browser and device. These are the type of device, the browser and operating system, the screen size, the language setting and the time zone. We also work out a short code from those details.
We record these details with your signature, as evidence that the signature is yours. We do this only when you use our claim form, because it is part of the signing service you ask for. We do not use these details for advertising, or to recognise you on other websites. This is separate from the device check in section 6. Our Privacy Policy explains how we use and keep them.
8. Other technologies on this website
- Email address protection. Cloudflare adds a small script that hides the email addresses on our pages from spam robots. The script is served from this website’s own address and sets no cookies.
- Address finder. When you search for your address, the request goes to our own server, which looks up the postcode with Ideal Postcodes. Ideal Postcodes sets no cookies on your device and does not receive your IP address.
- Forms and the signature pad. These run in your browser and on our server, and set no cookies of their own. The device check in section 6 runs alongside them.
9. Your choices
When you first visit, a banner explains our use of cookies. You can choose to accept all cookies or essential cookies only.
As we use only strictly necessary cookies and storage, both choices currently have the same effect: no analytics or advertising cookies are set either way. The device check in section 6 runs with either choice, because our claim form needs it to prevent fraud on the claim you ask us to make. If we ever want to use optional cookies, we will update this policy first. We will only set them if you agree, and you will be able to change your mind as easily as you agreed.
You can change your choice at any time with this button. It needs JavaScript to work.
You can also use your browser’s settings to delete cookies, block them, or alert you when one is set. Your browser’s help pages explain how. If you block all cookies, the cookie banner will appear on every page. If you delete our cookie, we will ask for your choice again on your next visit.
10. Questions and complaints
If you have a question about this Cookie Policy, email [email protected]. You can also write to Consumer Reclaim Ltd (Car Claims Check), Station House, Stamford New Road, Altrincham, WA14 1EP.
If you are unhappy with how we use cookies, please tell us first. You can also complain to the Information Commission (still known as the ICO) at ico.org.uk/make-a-complaint.
Our Privacy Policy explains how we use personal data and your rights.
11. Changes to this policy
We will update this policy whenever the cookies or technologies we use change. The version number and dates at the top show when it last changed, and when we last checked the website.