Cookie Policy

YourCar keeps a small amount of data on your device. Some of it is needed to run the site and cannot be switched off. Everything else is optional, and we store none of it until you say yes. You are asked once, and you can change the answer whenever you like on the cookie preferences page.

Cookies are only part of the story, so this policy covers browser local storage and session storage too. The rules that apply on the Isle of Man are about storing anything on your device, not about the word “cookie”.

The tables below are generated from the same list the site itself uses to decide what may load, so they describe what actually happens rather than what we remember writing down. Disclosure version 14.

Keeping you signed in, checking that a sign-in you started with Google is finished by the same browser, holding a part-finished listing while you fill it in, checking that a person rather than a script is reporting a car advert, and storing this consent choice itself. Switching these off would break the thing you asked us to do, so there is no switch.

Counts which pages and cars get looked at, and where people give up looking, so we can fix the parts of the site that lose you. Sent to PostHog, who process it for us in the EU. Web addresses are cleaned first, so one-time links never travel with them.

Records the pointer movement, clicks and scrolling of your visit (with all text and everything you type hidden), so we can watch back where the site confused you. Sent to PostHog, who process it for us in the EU. Signing pages are never recorded.

Sends us the technical detail of a crash or a page that failed to load, so we can fix it rather than wait to be told.

Keeps the referral or campaign link you arrived through, so the right person gets the credit if you go on to register.

Lets the live auction stream play on the page. The player comes from YouTube, which stores data on your device as soon as it loads, so nothing loads until you say yes.

We count how the marketplace is used on our own servers, not on your device. When your browser asks us for a page (a listing, say), our own API records that the page was looked at, as it answers the request. Nothing is written to or read from your device to make that count, so it does not depend on the choices above and there is no switch for it here: it keeps working whatever you decide.

Separately, and only if you allow it above, we also use PostHog to understand how the site is used, and to record how you move around it. That is a third party, it is processed in the EU, and neither part loads until you say yes. There is still no advertising script and no cross-site tracking anywhere on the site: nothing here follows you onto other people’s websites.

One more third party runs in your browser, and it measures nothing: Sentry receives a report when something on the site actually breaks, so we find out without waiting to be told. It too is processed in the EU and loads only if you allow “Reporting errors when something breaks” above. Our servers report their own faults to it whatever you decide: that happens on our machines, not on your device, and it is how we hear about the failures your browser never sees.

If you are signed in, that record is linked to your account, because the request carries your sign-in. If you are not signed in, it holds nothing that points back to you or your device: no name, no account, no advertising identifier. We remove the account link from these records after 24 months, and signed-in event data is de-identified if you delete your account: see our Privacy Policy.

Separately, the site can send one extra event from your browser to our own API (a POST /events request on our own domain) when there is something a server cannot see for itself, chiefly which campaign link brought you here. That needs the attribution permission above. Refuse it and your browser sends nothing of the kind, while the count above carries on exactly as described. Where your browser does send an event (tapping a share button, for example), it carries only the type of event and which listing it was about, with no campaign values, no cookies and no sign-in attached.

We keep the counting on our servers under legitimate interest rather than consent, which is why it is written down here rather than hidden behind a switch. Running a marketplace without knowing which listings get looked at is not a serious option, and it stores nothing on your device to do it.

The cookie preferences page is the quickest route: turning a category off stops it loading again, deletes what YourCar stored on this device, and reloads the page so nothing keeps running in the background. Your choice is kept on the device you made it on, for six months, and is not tied to your account. That is deliberate: permission to store data on a device cannot sensibly be given from a different one.

One limit, stated plainly. Some of what you can allow is served from another company’s website rather than ours: that is “Playing video from other sites” above. For those, switching the category off stops it loading again, and that is the control that matters, because nothing further can be stored. What a previous visit already stored was stored by that company on its own domain, and no website is able to reach into another’s to delete it, ours included. Clearing that is done in your browser’s settings for cookies and site data, which clears everything on this page at the same time.

You can also clear or block cookies and local storage in your browser settings at any time, though clearing your session tokens will sign you out. For any question about this policy, email privacy@yourcar.im.