Cookie policy
Last updated · version 1
This English text is provided for your convenience. The Thai version is the operative one under Thai law.
What a cookie is
A small file a website asks your browser to store, so it can recognise the browser on a later visit. Some are necessary for a site to work at all; others exist to measure or advertise.
Our position
Three commitments, and they are testable rather than rhetorical:
- Nothing non-essential loads before you choose. No analytics, no advertising, no third-party embed runs until you accept. If you never answer the banner, nothing beyond the strictly necessary ever runs.
- Rejecting is exactly as easy as accepting. "Reject all" sits next to "Accept all", in the same size and the same weight. A design that hides the refusal is not consent, and the PDPC guidance says as much.
- You can change your mind at any moment, from Cookie settings in the footer of every page. Withdrawal is as easy as consent — which the PDPA requires.
Categories
Strictly necessary — cannot be switched off. These make the site function: remembering your cookie choice itself, and basic security. No consent is required for these because the site cannot be provided without them.
Analytics — off until you accept. Tells us which pages people actually use, in aggregate, so we can improve them. Not used to identify you.
Functionality — off until you accept. Remembers preferences such as your language or the pickup point you use most, and allows embedded maps and the LINE chat button to load.
Advertising — off until you accept. Measures whether our advertising works and allows relevant ads to be shown on other platforms.
What is actually set right now
| Cookie | Category | Purpose | Duration |
|---|---|---|---|
cc_cookie | Strictly necessary | Stores your own consent choice | 6 months |
That is the complete list at the time of writing. No analytics or advertising tags are installed on this site yet. The categories above exist so that consent is collected correctly before anything is added — not after, which is the wrong order and the most common failure we see.
When anything is added, this table will list it with its real name and duration, the version number at the top of this page will change, and the banner will ask again.
Other browser storage
Cookies are not the only way a site can store data locally, and it would be misleading to describe only cookies.
sessionStorage holds the personal details you type into the booking form — name, phone, email — so that moving between booking steps does not lose them. It is cleared automatically when you close the tab, and it is never sent to any server unless you choose to send your booking to us. We use sessionStorage rather than localStorage specifically so that it does not persist.
The page URL holds your non-personal selections: car, dates, pickup point, cover, extras. That is what makes the page refresh-proof and shareable. Personal details are never placed in the URL.
Changing or withdrawing consent
Cookie settings in the footer of any page. Change any category and save; it takes effect immediately.
Withdrawing consent stops future processing. It does not undo processing already carried out while consent was in force, which is inherent in how consent works rather than a limitation we have chosen.
Browser-level controls
You can also block or delete cookies in your browser settings, and most browsers offer a "block third-party cookies" option. Blocking strictly necessary cookies may mean the site asks for your consent choice on every page load, because the record of your choice is itself the thing being blocked.
More information
For how we handle personal data generally, including your rights under the PDPA and how to exercise them, see the privacy policy.
Questions about personal data: 091 072 3336, or the email address in the footer.
Revision history
Version 1 — 1 August 2026. First published.