Privacy, in plain language.
Updated 10 October 2026. TrekTripTour uses your information to arrange day trips from Chiang Mai, manage bookings, and answer enquiries.
Information we collect and why
Bookings and enquiries include your name, e-mail, phone, trip and date, party size, hotel or pickup point, and any message or contact preferences you provide. We keep booking references, payment status, and operational records to deliver your trip and handle changes and refunds.
For passenger insurance and trip arrangements we collect passenger names, nationality, age band, date of birth, and ID or passport details. ID/passport details and dates of birth are encrypted in storage. Authorised office staff can access them for insurance and booking administration.
If you create an account, we keep sign-in details and saved trips. Optional Google or Facebook sign-in shares account identity information needed to sign you in. Saved trips can be stored on your device and synced to your account. The service worker caches only the offline shell, not booking details.
Three optional features store or share more. The newsletter keeps your e-mail, the consent text and time you agreed to, and the trip interests you ticked; every issue carries an unsubscribe link, and a cancelled subscription stays recorded as cancelled. A comment on a blog post is published under the name you type, together with the text, once the office approves it. The free-text trip search sends your words, scrubbed of e-mail addresses and phone numbers, to Anthropic’s model when that feature is switched on; the anonymous search log is cleared after 90 days.
Payments and service providers
Stripe processes card payments. Card details go directly to Stripe and never reach our server; we keep payment references, amounts, and status. Stripe may set its own fraud prevention cookies on checkout.
Resend delivers booking confirmations, tickets, sign-in links, and other service e-mails. LINE carries staff and driver messages needed to organise trips, including relevant pickup information. Google Maps and Places provide place lookup and maps on checkout when configured; searches and map requests go to Google.
Hosting, database, and delivery providers process information needed to run the service. Providers may process data outside Thailand. We share relevant passenger information with the insurer and trip staff for insurance and trip delivery.
Cookies and analytics
Essential cookies support sign-in, booking access, and preferences. On HTTPS, credential cookie names use the __Host- prefix shown below. Cookie lifetimes are distinct from how long booking records remain in our database.
| Name | Purpose | Lifetime |
|---|---|---|
| ttt_session / __Host-ttt_session | Customer sign-in (HTTP-only) | 30 days; renewed while active |
| ttt_admin / __Host-ttt_admin | Office sign-in (HTTP-only) | 12 hours |
| ttt_oauth | Google/Facebook sign-in state (HTTP-only) | 10 minutes; cleared after callback |
| ttt_res_<ref> / __Host-ttt_res_<ref> | Access to a booking from a private link (HTTP-only) | 2 hours; may be renewed |
| ttt_staff / __Host-ttt_staff | Staff sign-in (HTTP-only) | 8 hours |
| ttt_staff_setup / __Host-ttt_staff_setup | Staff password setup (HTTP-only) | 15 minutes |
| ttt_staff_line_code / __Host-ttt_staff_line_code | Staff LINE linking (HTTP-only) | 10 minutes |
| site_locale | Your language preference | 1 year |
| site_currency | Your display currency preference | 1 year |
| ttt_consent | Your analytics choice | 180 days |
| Stripe: __stripe_mid, __stripe_sid | Payment fraud prevention on checkout | Typically 1 year and 30 minutes respectively; controlled by Stripe |
| Google Analytics: _ga, _ga_<stream> | Visitor and session measurement, only after acceptance | Typically up to 2 years; controlled by Google and property settings |
Cloudflare Web Analytics and, when configured, Umami Cloud measure site usage without cookies. Google Analytics 4 loads only after you accept analytics cookies. Choosing “Only necessary” prevents Google Analytics from loading. Advertising storage and advertising personalisation are denied. Our booking, payment-confirmation, and enquiry analytics events contain only trip slug and party size, never names or contact details.
Cookie choices
You can change your analytics choice at any time.
Retention and protection
The scheduled cleanup clears passenger ID/passport details (including the stored last four characters) and dates of birth once the trip is more than 90 days past, from day 91 in Bangkok time. This includes cancelled bookings and associated booking drafts. Names, nationality, and age band remain; this cleanup does not delete the whole booking.
Cleanup also removes expired unattached booking holds and removes passwords and sessions from sign-ups whose e-mail remains unproven for more than 14 days, while keeping the account row and bookings. Ticket access expires 30 days after the trip and its tombstones are purged after a year. Anonymous style-search query logs are purged after 90 days. These jobs require the scheduled worker to run. Other booking, enquiry, account, payment, and operational records have no universal automatic deletion deadline in the current code; the operator reviews retention for service, accounting, and legal needs. Backups and provider records may remain beyond deletion from the live database.
Access controls restrict customer and staff data. Sign-in and submission limits use hashed identifiers and expire their limit records. Hosting infrastructure may keep access logs.
Your choices and rights
You can ask to access, correct, or delete your information, object to or restrict processing, or request a portable copy where applicable. You can withdraw optional analytics consent using Cookie choices above. Necessary booking and legal records may need to be retained.
For privacy requests, contact contact@trektriptour.com with your booking reference if you have one. Please do not e-mail passport details.
See also the booking terms.