Cookie Policy

This page can be audited rather than trusted. Load any page of drivecappadocia.com, open the storage panel of the browser inspector, and check the list against the table below. You should find one functional cookie holding a session together, a short-lived cache of recent car searches, and, once the page has been interacted with, whatever our booking partner writes. No advertising network, no retargeting pixel and no social widget appears on any page of this site, which is why no consent wall stands in the corner asking permission for machinery that was never installed.

Two different mechanisms, and why it matters which one

A cookie travels. The browser keeps it and then attaches it to every later request to the same site, and that property is exactly what makes cookies the raw material of tracking. Local storage stays put: the browser holds it, no request carries it by itself, and it leaves the device only if a script reads it and deliberately sends it somewhere. Almost everything this site writes for its own purposes belongs to the second kind, and the motive is speed rather than recognition. Every page here loads the same car list, so with no short cache, walking from the airport page to a town page to the day trips page would fetch an identical hundred cars three times over, often on a phone showing one bar between Avanos and Ortahisar.

Everything this site puts in your browser

What the search actually keeps, and for how long

A search between two dates returns a list of around a hundred vehicles, and that list is filed in local storage under a key built from the collection point, the return point and the dates. It is discarded five minutes later, deliberately sooner than the booking token behind it expires, and the code holds no more than four such lists, dropping the oldest as a new one appears. Inside an entry there are cars, prices and image addresses. There is no name, no email address, nothing that describes whoever ran the search, which is precisely why it can sit in a browser with no consent question attached to it. Where local storage is unavailable, in a private window or with site data blocked, the code notices and runs uncached instead of failing.

Nothing from our booking partner loads until you touch the page

The booking widget is a heavy piece of software, and fetching it on page load would make every reader pay for something most readers never use. Instead it waits for a first genuine signal: a pointer moving, a tap, a scroll, a key. Somebody who opens the page about collecting at Nevşehir Kapadokya, reads it over breakfast and closes the tab produces no such signal, and therefore receives nothing from our partner at all. When it does arrive, that partner may write cookies of its own, usually to keep a part-finished reservation attached to the right car and to credit the booking to this site. Those belong to the partner's policy, shown at the booking step. We neither control their contents nor read them.

Your language is in the address, not in a cookie

Every language of this site lives at its own URL. Switching language changes the address instead of recording a preference in the browser, so a bookmark carries the language onto any device, and a link handed to a travelling companion opens in the language it was sent in. Nothing is stored for it, and there is nothing to clear.

Switching it off, and the exact cost of doing so

Browsers let a visitor block or wipe storage for a single site, normally behind a privacy or site-data menu, and nothing on this domain tries to argue anyone out of it. Doing it on this domain costs a little speed and nothing more: each search runs from scratch rather than reusing a copy from a minute earlier. The one setting with a real consequence is a block on third party cookies, since the handover to the booking partner can depend on them to hold a reservation against the car it began from, and a booking begun under that block may fail at the supplier end. Wiping site data clears the cached searches instantly and leaves nothing behind with us, because none of it was ever with us.

What changes on a phone or in a private window

A private window blocks nothing while it is open. It destroys the storage when it closes, so a comparison abandoned the night before will not be waiting in the morning. Mobile browsers behave identically, which is worth knowing if the plan is to shortlist cars on a phone during the drive up from Kayseri and finish the booking on a laptop later: the shortlist does not travel, only the confirmation email does. Applications launched from a link here, a maps app for instance, keep storage under their own rules, which this policy has no reach over. Where a browser still transmits a Do Not Track header we honour it, although few browsers have sent one for years.

Keeping this page honest

A claim that no tracker runs here is worth something only while it stays checkable. Should we ever install measurement, or anything else that stores data for some purpose past making a page function, the rewrite of this page and a consent notice come first and the tool second. The date at the head of the page is how to see how long the current statement has stood.

Something here left unexplained? Email [email protected]. The Privacy Policy deals with data, the Terms and Conditions with the booking itself.