You can check every claim on this page yourself. Open your browser's developer tools on any page of muscatcarhire.com, find the storage panel, and the whole of what this site keeps on your device is listed there. It is short. There is no analytics tag, no advertising pixel, no social tracker and no consent vendor on this site, so there is nothing here to opt out of and no banner asking you to. What follows is the list, one item at a time, with what sets it, what it holds, when it disappears and how to remove it.
A cookie named XSRF-TOKEN
What sets it. Laravel, the framework this site runs on, as the page is built.
What it holds. A random, signed value with no meaning outside this site. When a form on muscatcarhire.com is submitted, the value sent with it is compared against the one in this cookie. If they do not match, the submission is rejected. That is the standard defence against a form on somebody else's page being used to act on this one in your name. It holds no identifier for you and nothing about your searches.
When it goes. It expires with the session, or sooner when you clear site data.
A session cookie whose name begins with "muscatcarhire"
What sets it. The same framework, for the same visit.
What it holds. A random session identifier and nothing else. The identifier lets our server recognise that two requests came from the same visit, which is what keeps a chosen language in place as you move between pages and what the security token above is anchored to. The name carries a short suffix so that this site's session cannot collide with another one in the same browser. No name, email or search history is stored inside it.
When it goes. When the session expires or when you clear site data for this domain.
Both of the above are strictly necessary cookies in the sense the European rules use. The site cannot offer a working form without them, which is why they are set without asking and why there is no toggle for them.
A script loaded from the supplier's domain, static.localrent.com
What sets it. This page, when it asks your browser for the booking widget.
What it does. The window that opens when you choose a car is not our code. It is the supplier network's booking component, fetched from their servers and rendered inside our page. Your browser therefore makes a direct request to that domain, which means their servers see the request, and they are free to set storage of their own under their own name, governed by their policy rather than this one. The details you type into that window go to them, not to us.
How to avoid it. Block third party scripts or that domain specifically in your browser or an extension. The site will still search and still show cars. The booking window will not open, because it is the thing you blocked.
For completeness, two more third party hosts are contacted while a page loads: the font service that serves the typeface and the public code network that serves the JavaScript library behind the interactive parts of the page. Neither is used to track you and neither is given anything about your search, but your browser does reach them and they can see that a request was made.
Several entries beginning "lrCars:" in local storage, which are not cookies
What sets it. Our own search code, after a set of results comes back.
Why it is not a cookie. This matters enough to spell out. A cookie is attached by your browser to every request it makes to the site, so the server receives it. Local storage is not. These entries stay on your device, are read only by the page's own JavaScript, and are never transmitted to our server or to anyone else. You will find them under local storage in the storage panel rather than under cookies, and a cookie banner would be the wrong instrument for them.
What it holds. The list of cars returned for a particular pickup point and date range, so that changing a filter or paging through the results does not refetch the whole list and leave you waiting again. Each entry is keyed by the search it belongs to and stamped with the time it was written.
When it goes. An entry is treated as stale after five minutes and discarded on the next search, and only the few most recent searches are kept, with the oldest dropped as new ones arrive. Clearing site data removes them immediately, and in private browsing they never outlive the window.
Removing or blocking any of it
Everything described above lives in your browser and is yours to delete. Clearing cookies and site data for muscatcarhire.com removes the two cookies and the cached searches in one action, and every current browser offers that from the padlock or site information control in the address bar. Browsing privately gives the same result automatically when the window closes.
Blocking is also available, with a consequence worth knowing before you choose it. Block the two necessary cookies and forms on this site will stop working, because the security check has nothing to compare against. Block local storage and the site still works, though every change of filter will fetch the list again. Block the supplier's domain and you keep browsing but lose the booking window. None of these choices affects whether you can read the site.
Changes, and how to ask about this
If we add anything that stores data on your device, this page is updated before it ships, and the version published when you visit is the one that describes the site you are looking at. Muscat Car Hire works by email and keeps no telephone line, so questions and answers both stay in writing. Write to [email protected].