Cookie Policy
Last updated: August 2026.
What a cookie is, and what else behaves like one
A cookie is a small file a site asks your browser to keep, so your next request carries something the site can read back: that you have answered the consent banner, or an identifier an advert counter recognises. That is the whole mechanism. It cannot read your files, and on its own it holds no name.
Other things do the same job, and this page counts them all as cookies. Local storage keeps a setting in the browser without sending it with every request, and we use it for your consent choice and for light or dark mode. A pixel is a tiny image request that records an email being opened or an advert displayed. Code inside embedded video players and advert frames sets its own storage.
The four kinds used here
Everything set on this site falls into one of four categories, and only the first is set without asking you.
- Strictly necessary: security, load balancing, and the record of your consent choice. The site cannot run without these, so there is no switch for them.
- Preferences: the settings that keep the site as you left it, such as light or dark mode and text size.
- Analytics: aggregate measurement of which pages get read and for how long.
- Advertising: the identifiers exchanges use to select an advert, cap how often you see the same one, and count that it was displayed.
Nothing in the middle two categories builds a profile of you. What the advertising category does amounts to profiling of a sort, which is why the banner asks about it rather than assuming. Our privacy policy covers what happens to that data once it leaves your browser.
Who else sets them
We set very little ourselves. The strictly necessary and preference cookies are ours. Everything else comes from a supplier: our analytics provider, the embedded players on the few pieces carrying video, and the programmatic exchanges that fill the display slots we do not sell directly.
We describe those advertising partners by category rather than printing names. The set of vendors permitted on a page shifts as exchanges add and drop partners, so a list typed here would be wrong within a quarter. The consent manager holds the live version: open it and you can see every vendor currently allowed to set anything, and a switch for each one. What we refuse to sell to any of them is on our advertise page.
Personalised and non-personalised advertising
Consenting to advertising cookies lets an exchange use an identifier to choose adverts it thinks suit you, limit repetition, and report that the advert was seen. Refuse, and the slots still fill. They fill with non-personalised adverts picked from the page and the rough region of the request rather than from a profile, which pay us less.
Refusing locks nothing behind a wall. Every guide, recall item and maintenance page stays open, because a reader mid-repair should not have to trade a consent decision for a torque figure. Advertising pays for all of this, so a non-personalised session is worth less to us, and we would still rather have you reading.
Changing your mind, in the site and in the browser
The consent manager is reachable from every page and it is the quickest way to change any of this. Switch a category or an individual vendor off and save, and the change applies from the next page load. If California law covers you, that advertising switch is also the Do Not Sell or Share My Personal Information mechanism, and we honour a Global Privacy Control signal from your browser without waiting for a click.
Browsers give you blunter controls that work anywhere: block third-party cookies, clear everything on close, or delete what is stored through the privacy settings in Chrome, Safari, Firefox or Edge. Blocking all cookies takes out the consent record too, so the banner will greet you on every visit. The advertising trade bodies also run cross-industry opt-out pages, YourAdChoices in the United States, Your Online Choices in Europe and the Network Advertising Initiative’s tool, covering the members that participate.
How long they last
Session cookies die when you close the browser, and most of the strictly necessary ones are that kind. The consent record is kept for up to a year, because asking again every week would only train everybody to click accept without reading. Preference settings persist for roughly a year as well.
Analytics identifiers run up to two years by default, and event-level analytics data is kept for fourteen months before only aggregates remain. Third-party advertising identifiers commonly last from thirty days to two years depending on the vendor, and the consent manager has the live figures. Server logs are not cookies, but they are collected as you browse, and they are held for thirty days.
Where this sits alongside the rest
This page describes what gets set and how to stop it. Our privacy policy covers the data itself: the legal bases, retention, transfers and the rights you can use, all of which run through the single inbox at support@isuzuownersclub.com. Cookie questions go there too. When this policy changes materially, the date at the top moves.
One thing no cookie here does is connect you to a manufacturer. Isuzu Owners Club is an independent, unofficial publication, not affiliated with, endorsed by, sponsored by or connected to Isuzu Motors Limited, its subsidiaries, its dealers or its distributors, and no advertiser, dealer or manufacturer receives a list of who read what. The names we use, “Isuzu”, “D-Max”, “MU-X” and the series names, are trademarks of their respective owners, used descriptively to identify the vehicles we cover, and we claim ownership of none of them. Our purpose is educational and community-based: helping owners maintain these vehicles and find each other. Nothing here is official manufacturer guidance, warranty questions and recall registration belong with Isuzu or an authorised dealer whose documentation outranks ours, and that route needs no cookie from us.
